Bug 50999 – "emerge -s lame" fails with traceback

• Status: RESOLVED FIXED
• Product: Portage Development

[Description Thomas Heiserowski 2004-05-13 19:48:09 UTC]

I am not shure where the problem derives from. I can only tell that every time I am doing a "emerge -s lame" it fails with the same traceback:

Searching...  |Traceback (most recent call last):
  File "/usr/bin/emerge", line 2331, in ?
    searchinstance.execute(mysearch)
  File "/usr/bin/emerge", line 545, in execute
    if not portage.portdb.xmatch("match-visible",package):
  File "/usr/lib/portage/pym/portage.py", line 4701, in xmatch
    myval=match_from_list(mydep,self.xmatch("list-visible",None,mydep,mykey))
  File "/usr/lib/portage/pym/portage.py", line 4687, in xmatch
    myval=self.gvisible(self.visible(self.cp_list(mykey)))
  File "/usr/lib/portage/pym/portage.py", line 4782, in gvisible
    myaux=db["/"]["porttree"].dbapi.aux_get(mycpv, ["KEYWORDS"])
  File "/usr/lib/portage/pym/portage.py", line 4535, in aux_get
    if doregen or not self.eclassdb.is_current(cat,pkg,self.auxdb[cat][pkg]["INHERITED"].split()):
  File "/usr/lib/portage/pym/portage.py", line 4380, in is_current
    self.setup_package(cat, pkg)
  File "/usr/lib/portage/pym/portage.py", line 4357, in setup_package
    self.packages[cat] = self.dbmodule(self.cachedir, cat+"-eclass", [], uid, portage_gid)
  File "/usr/lib/portage/pym/portage_db_cpickle.py", line 23, in __init__
    self.db = mypickle.load()
EOFError

An "emerge -p lame" states the following:

These are the packages that I would merge, in order:

Calculating dependencies
!!! Problem in media-sound/lame dependencies.
!!!

My portage is a snapshot from 20040507, only the lame-3.96.ebuild is from today since I thought the problem may be fixed by the newer ebuild.

Here is my "emerge info":

Gentoo Base System version 1.4.3.8p1
Portage 2.0.50-r6 (default-x86-1.4, gcc-3.3.2, glibc-2.3.3_pre20040207-r0, 2.6.6)
=================================================================
System uname: 2.6.6 i686 AMD Athlon(tm) Processor
Autoconf: sys-devel/autoconf-2.59-r3
Automake: sys-devel/automake-1.8.2
ACCEPT_KEYWORDS="x86"
AUTOCLEAN="yes"
CFLAGS="-mcpu=athlon -O2 -pipe"
CHOST="i686-pc-linux-gnu"
COMPILER="gcc3"
CONFIG_PROTECT="/etc /usr/X11R6/lib/X11/xkb /usr/kde/2/share/config /usr/kde/3.1/share/config /usr/kde/3.2/share/config /usr/kde/3/share/config /usr/share/config /usr/share/texmf/dvipdfm/config/ /usr/share/texmf/dvips/config/ /usr/share/texmf/tex/generic/config/ /usr/share/texmf/tex/platex/config/ /usr/share/texmf/xdvi/ /var/qmail/control"
CONFIG_PROTECT_MASK="/etc/gconf /etc/env.d"
CXXFLAGS="-mcpu=athlon -O2 -pipe"
DISTDIR="/usr/portage/distfiles"
FEATURES="autoaddcvs buildpkg ccache sandbox"
GENTOO_MIRRORS=" ftp://sunsite.informatik.rwth-aachen.de/pub/Linux/gentoo ftp://linux.rz.ruhr-uni-bochum.de/gentoo-mirror http://gentoo.oregonstate.edu/ http://distro.ibiblio.org/pub/Linux/distributions/gentoo"
MAKEOPTS="-j2"
PKGDIR="/usr/portage/packages"
PORTAGE_TMPDIR="/store/portage/tmp"
PORTDIR="/usr/portage"
PORTDIR_OVERLAY="/usr/local/portage"
SYNC="rsync://rsync.de.gentoo.org/gentoo-portage"
USE="3dnow X aalib alsa apache2 apm arts avi berkdb bonobo cdr crypt cups curl dga directfb doc dvd dvdr encode esd flac foomaticdb gd gdbm ggi gif gimp gnome gphoto2 gpm gtk gtk2 gtkhtml guile imap imlib imlib2 ipv6 java jpeg kde ldap libg++ libwww mad matrox mikmod mmx motif mozcalendar mozilla mozp3p mozsvg mozxmlterm mpeg mysql ncurses nls odbc oggvorbis opengl oss pam pda pdflib perl png python qt quicktime readline samba scanner sdl slang spell ssl svga tcltk tcpd tetex tiff truetype usb wmf x86 xface xine xinerama xml2 xmms xv zlib"

Any help is appreciated.

*th

[Comment 1 Nicholas Jones (RETIRED) 2004-05-13 21:37:54 UTC]

emerge sync

You have data corruption in the cache db.

[Comment 2 Thomas Heiserowski 2004-05-14 10:04:21 UTC]

It is a bit hard for me to do an emerge sync since I only have an 56K dial up connection :( I thought it should be okay if I only copied the snapshot of portage to /usr/portage. Thus I did for a year without any problems so far.

According to emerge --help an emerge regen should help, should it not?

I regenerated the cache this way but without success.

Is there now other way? And: If there is no other way than emerge sync -- how do I have to understand the snapshots and emerge regen?

Thanks for your kind help,
Thomas

[Comment 3 Marius Mauch (RETIRED) 2004-05-14 14:24:50 UTC]

Try `emerge --metadata` or `emerge --regen` (slow).

[Comment 4 Thomas Heiserowski 2004-05-15 03:27:52 UTC]

emerge --metadata did the trick. thank you!

Have I missed anything or is this option undocumented? If it were so it should be made public because I think that it is important for users following the same strategy like me and they should know about it, should they not?

Thanks again for your help,
Thomas

PS: FIXED or WORKS FOR ME?

[Comment 5 Brian Harring (RETIRED) 2004-08-16 11:22:21 UTC]

Err.. Nick?  you keyworded this InCVS, although I don't see anything that was changed...
Aside from that, the corruption has popped up on occasion still.

[Comment 6 Nicholas Jones (RETIRED) 2004-09-14 22:43:39 UTC]

This should be managed in 2.0.51.

[Comment 7 Brian Harring (RETIRED) 2005-07-28 16:26:28 UTC]

Closing, open if it occurs again.