when emerge -uDp world works, adding the -k option to see if binary packages are available on my system don't work. However, removing the -D option makes the -k option do again what it should do but this way I lose the --deep function. It turns out the options -D and -k don't work together. Reproducible: Always Steps to Reproduce: 1. emerge -uDpk world Actual Results: These are the packages that I would merge, in order: Calculating world dependencies ...done! !!! aux_get(): ebuild for 'x11-libs/openmotif-2.2.2-r1' does not exist at: !!! /usr/portage/x11-libs/openmotif/openmotif-2.2.2-r1.ebuild Traceback (most recent call last): File "/usr/bin/emerge", line 2583, in ? mydepgraph.display(mydepgraph.altlist()) File "/usr/bin/emerge", line 1239, in display mynewslot=portage.portdb.aux_get(x[2],["SLOT"])[0] File "/usr/lib/portage/pym/portage.py", line 4515, in aux_get raise KeyError KeyError Expected Results: These are the packages that I would merge, in order: Calculating world dependencies ...done! [ebuild U ] net-p2p/xmule-1.9.0 [1.8.4] [ebuild U ] app-office/openoffice-1.1.2 [1.1.1-r1] Gentoo Base System version 1.4.16 Portage 2.0.50-r10 (default-x86-1.4, gcc-3.3.3, glibc-2.3.3.20040420-r1, 2.6.8.1) ================================================================= System uname: 2.6.8.1 i686 AMD Athlon(tm) XP 2600+ distcc 2.13 i686-pc-linux-gnu (protocols 1 and 2) (default port 3632) [disabled] ccache version 2.3 [disabled] Autoconf: sys-devel/autoconf-2.59-r4 Automake: sys-devel/automake-1.8.5-r1 ACCEPT_KEYWORDS="x86" AUTOCLEAN="yes" CFLAGS="-O2 -march=athlon-xp -pipe" CHOST="i686-pc-linux-gnu" COMPILER="" CXXFLAGS="-O2 -march=athlon-xp -pipe" FEATURES="autoaddcvs buildpkg sandbox" MAKEOPTS="-j2" USE="X apm arts avi berkdb cdr crypt cups directfb encode esd foomaticdb gdbm gif gnome gpm gtk gtk2 imlib java jpeg ldap libg++ libwww mad mikmod mmx motif mozilla mpeg mysql ncurses oggvorbis opengl oss pam pdflib perl png python qt quicktime readline ruby sdl slang sse ssl svga tcpd tiff truetype x86 xml2 xmms xv zlib"
Can you try to (re)move your binaries out of the way and test again ? Might be just a broken .tbz2 package that's only touched with --deep.
Well, that seems to do the trick. This also happened to me on alpha. But it looks very strange to me. In my opinion, "emerge -uDpk world" only differs in the fact that for every package it would update with "emerge -uDp world" it should look if a binary package is available on the system and not give me some fancy error msg. Or am I thinking too simple now?
2.0.50-r10's binary support was mildly broken. Please test again on 2.0.50-r11.
Since I removed the binaries, 2.0.50-r10 workes OK for me and so does 2.0.50-r11 so I can't tell the difference anymore so I'll mark this bug as fixed...