1 |
2009/8/27 Alan McKinnon <alan.mckinnon@×××××.com> |
2 |
|
3 |
> On Thursday 27 August 2009 11:07:24 Xavier Parizet wrote: |
4 |
> > Hi everyone, |
5 |
> > |
6 |
> > I had some problem with /var/db/pkg : it's empty. So, how can i fix this |
7 |
> > without rebuilding world and system from scratch ? |
8 |
> |
9 |
> You need to rebuild world from scratch :-) |
10 |
> |
11 |
> Portage has now no way of knowing what you had. If emerge world does not |
12 |
> work |
13 |
> for some reason, you will have to: |
14 |
> |
15 |
> 1. download a recent suitable stage tarball |
16 |
> 2. Back up everything that tarball might want to overwrite |
17 |
> 3. Unpack that tarball to / |
18 |
> 4. Put critical files back that the stage overwrote |
19 |
> 5. emerge world |
20 |
> |
21 |
> You might also want to do all this in a chroot off a LiveCD |
22 |
> |
23 |
> -- |
24 |
> alan dot mckinnon at gmail dot com |
25 |
> |
26 |
> |
27 |
You may find some useful informations in /var/log/emerge.log : all lines |
28 |
containing ":::" show a succesful emerge. |
29 |
|
30 |
If you have kept the contents of this file since you installed your system, |
31 |
you could then get the list of all packages you have installed. It would be |
32 |
a start that you could cleanup afterwards. However, this will include system |
33 |
packages and dependencies. And if you have uninstalled many packages (as |
34 |
with any update), they would also still be present in that list. |
35 |
|
36 |
Mickaël |