| 1 |
20.12.2013 13:53, Neil Bothwick пишет: |
| 2 |
> On Fri, 20 Dec 2013 13:47:25 +0400, Yuri K. Shatroff wrote: |
| 3 |
> |
| 4 |
>>> What is the contents of /var/lib/portage/world? |
| 5 |
> |
| 6 |
>> Hm, really, it's almost empty except for the last packages I have added |
| 7 |
>> yesterday... So that's clearly not an emerge bug, but ... Could |
| 8 |
>> anything mess it up? |
| 9 |
> |
| 10 |
> Plenty, with the favourite being user error. If the packages aren't in |
| 11 |
> world nor depended on by something n world, portage will not upgrade them. |
| 12 |
> |
| 13 |
>> I have copied the system to a new HDD recently and done an `emerge |
| 14 |
>> @world`, too, and everything went OK. |
| 15 |
> |
| 16 |
> OK as in everything you expected to build built? Or OK as in no error |
| 17 |
> messages appeared? |
| 18 |
|
| 19 |
The former. When I do an eix-sync, I expect that emerge -Du @world |
| 20 |
updates every package listed with the U-mark. |
| 21 |
There are no error messages anyway. |
| 22 |
|
| 23 |
> Your first step would be to restore the world file |
| 24 |
> from the old drive, adding the entries from the current version. |
| 25 |
|
| 26 |
I'll do this, but now I'm just wondering how I ended up with an empty |
| 27 |
world file. |
| 28 |
|
| 29 |
-- |
| 30 |
Regards, |
| 31 |
Yuri K. Shatroff |
Archives