| 1 |
On Thursday 25 September 2008, Thomas Kahle wrote: |
| 2 |
> Hi, |
| 3 |
> |
| 4 |
> ~ > Then, revdep-rebuild display like this. |
| 5 |
> |
| 6 |
> | [ebuild R ] media-libs/tiff-3.8.2-r5 |
| 7 |
> | [ebuild R ] media-gfx/imagemagick-6.4.3.5 |
| 8 |
> | [ebuild R ] media-libs/lcms-1.17 |
| 9 |
> | [ebuild U ] media-libs/vigra-1.6.0 [1.5.0-r1] |
| 10 |
> | [ebuild R ] net-print/cups-1.3.8-r1 |
| 11 |
> | [ebuild R ] x11-libs/gtk+-2.12.12 |
| 12 |
> | [ebuild R ] app-text/ghostscript-gpl-8.63 |
| 13 |
> | [ebuild R ] app-text/evince-2.22.2-r1 |
| 14 |
> | [ebuild R ] media-gfx/gthumb-2.10.9 |
| 15 |
> |
| 16 |
> ~ > But there is no "vigra" in result of "emerge -p --update world"(with |
| 17 |
> |
| 18 |
> | --deep also). |
| 19 |
> | Of course, it still shows flag "U" if I do "emerge -p vigra" |
| 20 |
> | |
| 21 |
> | What is difference with emerge --update world and emerge vigra? |
| 22 |
> | And how can I update all new package without exceptions? |
| 23 |
> |
| 24 |
> I am also curious to know why portage just "forgets" to update certain |
| 25 |
> packages. What I used to do to find them is a plain |
| 26 |
> eix -I | grep "\[U\]" |
| 27 |
> which just greps for the pattern [U] marking an upgradeable package. |
| 28 |
> Then you can format this list and run |
| 29 |
> emerge -1 `insert packagelist here` |
| 30 |
> The -1 is important to not register these packages in your world file, |
| 31 |
> which you probably don't wont for some package that only is a dependency. |
| 32 |
> |
| 33 |
> Still, I would like to know how this happens... |
| 34 |
> |
| 35 |
> hth |
| 36 |
> Tom |
| 37 |
|
| 38 |
a) dependencies are not listed in world. |
| 39 |
|
| 40 |
b) an 'orphaned' dependency wouldn't get caught with --deep. |
Archives