| 1 |
On Wed, Sep 9, 2009 at 5:45 AM, Dale <rdalek1967@×××××.com> wrote: |
| 2 |
> Mark Knecht wrote: |
| 3 |
>> On Wed, Sep 9, 2009 at 4:43 AM, Dale <rdalek1967@×××××.com> wrote: |
| 4 |
>> |
| 5 |
>>> Hi folks, |
| 6 |
>>> |
| 7 |
>>> Can someone tell me what this means? |
| 8 |
>>> |
| 9 |
>>> root@smoker / # emerge -p --depclean |
| 10 |
>>> |
| 11 |
>>> * Always study the list of packages to be cleaned for any obvious |
| 12 |
>>> * mistakes. Packages that are part of the world set will always |
| 13 |
>>> * be kept. They can be manually added to this set with |
| 14 |
>>> * `emerge --noreplace <atom>`. Packages that are listed in |
| 15 |
>>> * package.provided (see portage(5)) will be removed by |
| 16 |
>>> * depclean, even if they are part of the world set. |
| 17 |
>>> * |
| 18 |
>>> * As a safety measure, depclean will not remove any packages |
| 19 |
>>> * unless *all* required dependencies have been resolved. As a |
| 20 |
>>> * consequence, it is often necessary to run `emerge --update |
| 21 |
>>> * --newuse --deep @system @world` prior to depclean. |
| 22 |
>>> |
| 23 |
>>> Calculating dependencies... done! |
| 24 |
>>> |
| 25 |
>>>>>> Checking for lib consumers... |
| 26 |
>>>>>> Assigning files to packages... |
| 27 |
>>>>>> |
| 28 |
>>> * In order to avoid breakage of link level dependencies, one or more |
| 29 |
>>> * packages will not be removed. This can be solved by rebuilding the |
| 30 |
>>> * packages that pulled them in. |
| 31 |
>>> * |
| 32 |
>>> * dev-lang/python-2.5.4-r3 pulled in by: |
| 33 |
>>> * app-office/scribus-1.3.3.11 |
| 34 |
>>> * |
| 35 |
>>> |
| 36 |
>>>>>> Adding lib providers to graph... |
| 37 |
>>>>>> |
| 38 |
>>> \ |
| 39 |
>>> Calculating dependencies... done! |
| 40 |
>>> |
| 41 |
>>> |
| 42 |
>>> I have re-compiled scribus about three times now. I have also ran |
| 43 |
>>> python-updater a few times and it just keeps rebuilding scribus and |
| 44 |
>>> boost in a endless loop. What am I missing here? |
| 45 |
>>> |
| 46 |
>>> Thanks. |
| 47 |
>>> |
| 48 |
>>> Dale |
| 49 |
>>> |
| 50 |
>>> :-) :-) |
| 51 |
>>> |
| 52 |
>>> |
| 53 |
>>> |
| 54 |
>> |
| 55 |
>> Possibly scribus isn't compatible with python-2.6? The few times I've |
| 56 |
>> run into this with depclean I've removed the app (scribus in this |
| 57 |
>> case) cleaned up the machine with depclean and revdep-rebuild, and |
| 58 |
>> then reinstalled the app from scratch. If it tries to pull in |
| 59 |
>> phython-2.5 then you just have to make a choice whether you want it or |
| 60 |
>> not. (Or look for a mased ebuild, etc. |
| 61 |
>> |
| 62 |
>> - Mark |
| 63 |
>> |
| 64 |
>> |
| 65 |
>> |
| 66 |
> |
| 67 |
> LOL Since I would rather try to remove Scribus than python, I'll remove |
| 68 |
> Scribus, do some cleaning, then reinstall and see what happens. We all |
| 69 |
> know what could happen if I remove python that portage is using. o_O |
| 70 |
> |
| 71 |
> I'll report back if it continues after all this. Thanks to both Alan |
| 72 |
> and Mark on this one. I was getting drunk going around in circles with |
| 73 |
> this. |
| 74 |
> |
| 75 |
> Dale |
| 76 |
> |
| 77 |
> :-) :-) |
| 78 |
> |
| 79 |
> |
| 80 |
|
| 81 |
I assume you've installed python-2.6 as part of emerge @system or |
| 82 |
@world and then run python-updater? That process has worked on my |
| 83 |
machines but I don't use too many office apps. |
| 84 |
|
| 85 |
Good luck! |
| 86 |
|
| 87 |
Cheers, |
| 88 |
Mark |
Archives