| 1 |
-----BEGIN PGP SIGNED MESSAGE----- |
| 2 |
Hash: SHA1 |
| 3 |
|
| 4 |
Hi, |
| 5 |
|
| 6 |
~ > Then, revdep-rebuild display like this. |
| 7 |
| [ebuild R ] media-libs/tiff-3.8.2-r5 |
| 8 |
| [ebuild R ] media-gfx/imagemagick-6.4.3.5 |
| 9 |
| [ebuild R ] media-libs/lcms-1.17 |
| 10 |
| [ebuild U ] media-libs/vigra-1.6.0 [1.5.0-r1] |
| 11 |
| [ebuild R ] net-print/cups-1.3.8-r1 |
| 12 |
| [ebuild R ] x11-libs/gtk+-2.12.12 |
| 13 |
| [ebuild R ] app-text/ghostscript-gpl-8.63 |
| 14 |
| [ebuild R ] app-text/evince-2.22.2-r1 |
| 15 |
| [ebuild R ] media-gfx/gthumb-2.10.9 |
| 16 |
| |
| 17 |
| |
| 18 |
~ > But there is no "vigra" in result of "emerge -p --update world"(with |
| 19 |
| --deep also). |
| 20 |
| Of course, it still shows flag "U" if I do "emerge -p vigra" |
| 21 |
| |
| 22 |
| What is difference with emerge --update world and emerge vigra? |
| 23 |
| And how can I update all new package without exceptions? |
| 24 |
|
| 25 |
I am also curious to know why portage just "forgets" to update certain |
| 26 |
packages. What I used to do to find them is a plain |
| 27 |
eix -I | grep "\[U\]" |
| 28 |
which just greps for the pattern [U] marking an upgradeable package. |
| 29 |
Then you can format this list and run |
| 30 |
emerge -1 `insert packagelist here` |
| 31 |
The -1 is important to not register these packages in your world file, |
| 32 |
which you probably don't wont for some package that only is a dependency. |
| 33 |
|
| 34 |
Still, I would like to know how this happens... |
| 35 |
|
| 36 |
hth |
| 37 |
Tom |
| 38 |
-----BEGIN PGP SIGNATURE----- |
| 39 |
Version: GnuPG v2.0.9 (GNU/Linux) |
| 40 |
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org |
| 41 |
|
| 42 |
iEYEARECAAYFAkjbHhQACgkQrpEWPKIUt7MaBwCghPThHp8lCQbfQyvSG/UwaYN+ |
| 43 |
zgsAmgL3W8mcNfvjEJZxc+aUKTeNTLX1 |
| 44 |
=luJw |
| 45 |
-----END PGP SIGNATURE----- |
Archives