| 1 |
"Richard Lucking" <lists@×××××××.org> posted |
| 2 |
006101c69140$404d2590$d800a8c0@×××.cxm, excerpted below, on Fri, 16 Jun |
| 3 |
2006 13:27:36 +0100: |
| 4 |
|
| 5 |
> With all these lockups I seem to have "broken" portage though, after every |
| 6 |
> emerge I get: |
| 7 |
> |
| 8 |
>>>> Original instance of package unmerged safely. |
| 9 |
> Traceback (most recent call last): |
| 10 |
> File "/usr/bin/emerge", line 3505, in ? |
| 11 |
> mydepgraph.merge(pkglist) |
| 12 |
> File "/usr/bin/emerge", line 2034, in merge |
| 13 |
> retval=portage.doebuild(y,"merge",myroot,self.pkgsettings,edebug,tree="porttree") |
| 14 |
|
| 15 |
That's likely a bad db entry. Those are in /var/db/pkg/*, so first thing |
| 16 |
to do is to umount that partition (you may have to boot the liveCD or |
| 17 |
something if it's the root partition) and do a proper fsck. Once that's |
| 18 |
done, try another merge and see if the problem still occurs. |
| 19 |
|
| 20 |
If the problem still occurs, backup the dir and try the process of |
| 21 |
elimination, deleting one category at a time, putting it back (from the |
| 22 |
backup) if that doesn't solve the problem and trying the next. Once you |
| 23 |
get a category, try the individual packages, then the individual files. |
| 24 |
Eventually, you'll probably find one or more that are corrupt. You can |
| 25 |
try rebuilding the info in them manually if possible, or simply remerge |
| 26 |
that package to replace the info. |
| 27 |
|
| 28 |
If that doesn't help, it's probably time to get the portage devs involved. |
| 29 |
With the traceback, they should be able to figure out what's going on and |
| 30 |
tell you where to go from there. |
| 31 |
|
| 32 |
Note that as long as your world file is fine and your /etc/make.profile |
| 33 |
points to your correct profile, the worst that should happen is that |
| 34 |
you'll need to do an emerge --emptytree, to rebuild the database from |
| 35 |
scratch. If you have been using FEATURES=buildpkg, you can use emerge |
| 36 |
--emptytree --packageonly, and be done in an hour or so, using the binary |
| 37 |
packages you've collected to rebuild your system. If not, it could take |
| 38 |
awhile, recompiling every package. One more reason I think they should |
| 39 |
emphasize just how good that feature can be in a pinch, a bit more than |
| 40 |
they do in the handbook. |
| 41 |
|
| 42 |
|
| 43 |
|
| 44 |
-- |
| 45 |
Duncan - List replies preferred. No HTML msgs. |
| 46 |
"Every nonfree program has a lord, a master -- |
| 47 |
and if you use the program, he is your master." Richard Stallman |
| 48 |
|
| 49 |
-- |
| 50 |
gentoo-amd64@g.o mailing list |
Archives