| 1 |
-----BEGIN PGP SIGNED MESSAGE----- |
| 2 |
Hash: SHA1 |
| 3 |
|
| 4 |
Erik wrote: |
| 5 |
> I did "emerge --update --deep --newuse world" and it says: |
| 6 |
> Calculating world dependencies... done! |
| 7 |
>>>> Auto-cleaning packages... |
| 8 |
> |
| 9 |
>>>> No outdated packages were found on your system. |
| 10 |
> |
| 11 |
> |
| 12 |
> But it seems like it is wrong about "No outdated packages were found on |
| 13 |
> your system.", because when I run "emerge -p world" it says: |
| 14 |
> |
| 15 |
> These are the packages that would be merged, in order: |
| 16 |
> |
| 17 |
> Calculating world dependencies... done! |
| 18 |
> [ebuild U ] media-gfx/digikam-0.9.2 [0.9.1] LINGUAS="-fa% -nds%" |
| 19 |
> [blocks B ] media-plugins/digikamimageplugins (is blocking |
| 20 |
> media-gfx/digikam-0.9.2) |
| 21 |
> |
| 22 |
> |
| 23 |
> So it seems like media-gfx/digikam is outdated despite what "emerge |
| 24 |
> --update --deep --newuse world" said. I just wonder how much sense this |
| 25 |
> behaviour makes. |
| 26 |
> |
| 27 |
|
| 28 |
It seems like something that you have installed depends on |
| 29 |
digikam-0-9.1 so the deep world update pulled that in instead of the |
| 30 |
new version. You can use the --debug option if you want to examine |
| 31 |
the dependency strings to see which package pulled in the lower version. |
| 32 |
|
| 33 |
Zac |
| 34 |
-----BEGIN PGP SIGNATURE----- |
| 35 |
Version: GnuPG v2.0.7 (GNU/Linux) |
| 36 |
|
| 37 |
iD8DBQFHv9uk/ejvha5XGaMRAsZpAKDsDIK6AGaS6syS7kt200wusMvz6QCfcpT2 |
| 38 |
XuBScoXX0+Q8DymXiH1T3Yc= |
| 39 |
=GtRH |
| 40 |
-----END PGP SIGNATURE----- |
| 41 |
-- |
| 42 |
gentoo-user@l.g.o mailing list |
Archives