| 1 |
>> I'm synced up and emerge world doesn't want to emerge anything, but |
| 2 |
>> python-updater wants to re-emerge an old version of libxslt which is |
| 3 |
>> currently installed, which looks like it should have been updated via |
| 4 |
>> emerge world: |
| 5 |
>> |
| 6 |
>> # equery depends libxslt |
| 7 |
>> [ Searching for packages depending on libxslt... ] |
| 8 |
>> dev-lang/php-5.2.6-r2 (xsl? dev-libs/libxslt) |
| 9 |
>> dev-libs/glib-2.16.3-r1 (doc? >=dev-libs/libxslt-1.0) |
| 10 |
>> |
| 11 |
>> Can anyone explain this? |
| 12 |
>> |
| 13 |
> |
| 14 |
> As you stated correctly: phython-updater wants *re*-emerge libxslt, |
| 15 |
> because something, in this case phython, on which libxlst depends has |
| 16 |
> changed. |
| 17 |
> |
| 18 |
> There is no update of libxslt, so why sgould emerge -u world bother? |
| 19 |
|
| 20 |
But there is: |
| 21 |
|
| 22 |
# emerge -pv libxslt |
| 23 |
|
| 24 |
These are the packages that would be merged, in order: |
| 25 |
|
| 26 |
Calculating dependencies... done! |
| 27 |
[ebuild U ] dev-libs/libxslt-1.1.24 [1.1.20] USE="crypt python |
| 28 |
-debug -examples%" 3,286 kB |
| 29 |
|
| 30 |
That's the confusing part. |
| 31 |
|
| 32 |
- Grant |
Archives