-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Hi,
~ > Then, revdep-rebuild display like this. | [ebuild R ] media-libs/tiff-3.8.2-r5 | [ebuild R ] media-gfx/imagemagick-6.4.3.5 | [ebuild R ] media-libs/lcms-1.17 | [ebuild U ] media-libs/vigra-1.6.0 [1.5.0-r1] | [ebuild R ] net-print/cups-1.3.8-r1 | [ebuild R ] x11-libs/gtk+-2.12.12 | [ebuild R ] app-text/ghostscript-gpl-8.63 | [ebuild R ] app-text/evince-2.22.2-r1 | [ebuild R ] media-gfx/gthumb-2.10.9 | | ~ > But there is no "vigra" in result of "emerge -p --update world"(with | --deep also). | Of course, it still shows flag "U" if I do "emerge -p vigra" | | What is difference with emerge --update world and emerge vigra? | And how can I update all new package without exceptions? I am also curious to know why portage just "forgets" to update certain packages. What I used to do to find them is a plain eix -I | grep "\[U\]" which just greps for the pattern [U] marking an upgradeable package. Then you can format this list and run emerge -1 `insert packagelist here` The -1 is important to not register these packages in your world file, which you probably don't wont for some package that only is a dependency. Still, I would like to know how this happens... hth Tom -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.9 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iEYEARECAAYFAkjbHhQACgkQrpEWPKIUt7MaBwCghPThHp8lCQbfQyvSG/UwaYN+ zgsAmgL3W8mcNfvjEJZxc+aUKTeNTLX1 =luJw -----END PGP SIGNATURE-----
