| 1 |
Today, doing an "emerge -pvDu world" I get the report that no packages |
| 2 |
need to be updated. |
| 3 |
|
| 4 |
But while checking the status of another package, I happen to execute |
| 5 |
"emerge -pv rpm2targz." This then reports that the package rpm2targz |
| 6 |
needs to be updated. |
| 7 |
|
| 8 |
Why didn't the "emerge -pvDu world" tell me about this? |
| 9 |
|
| 10 |
Further checking reveals that all packages that are installed on my |
| 11 |
machine are contained in the /var/db/pkg directory. However, the "world" |
| 12 |
file, which is located at /var/lib/portage/world, should contain the same |
| 13 |
listing but it does not. I notice that some packages in /var/db/pkg |
| 14 |
are not listed in /var/lib/portage/world. |
| 15 |
|
| 16 |
Actually, the "world" file has 257 entries, while the "/var/lib/portage/world" |
| 17 |
directory contains 414 packages. |
| 18 |
|
| 19 |
Why has portage failed to add all packages to the "world" file? |
| 20 |
Have I been doing something wrong? |
| 21 |
|
| 22 |
In any case, I can rebuild the world file manually to accurately |
| 23 |
reflect the state my system, but, based upon this current observation, |
| 24 |
portage may fail to keep it accurate in the future. |
| 25 |
|
| 26 |
What is going on here? |
| 27 |
|
| 28 |
Frank Peters |
Archives