After an "emerge sync" there was a notice that a new version of portage was available, and to update that before others. So I did "emerge portage" and things seemed to go smoothly. However, then I did "emerge -up world" and go the following error. sagan root # emerge -up world These are the packages that I would merge, in order: Calculating world dependencies \Traceback (most recent call last): File "/usr/bin/emerge", line 2513, in ? if not mydepgraph.xcreate(myaction): File "/usr/bin/emerge", line 1105, in xcreate myeb=portage.portdb.xmatch("bestmatch-visible",mydep) File "/usr/lib/portage/pym/portage.py", line 4673, in xmatch myval=best(self.xmatch("match-visible",None,mydep,mykey)) File "/usr/lib/portage/pym/portage.py", line 4684, in xmatch myval=match_from_list(mydep,self.xmatch("list-visible",None,mydep,mykey)) File "/usr/lib/portage/pym/portage.py", line 3531, in match_from_list raise KeyError, "Specific key requires an operator (%s) (try adding an '=')" % (mydep) KeyError: "Specific key requires an operator (net-www/apache-2.0.47) (try adding an '=')" downgrading to portage-2.0.49-r21 seemed to fix the problem Reproducible: Always Steps to Reproduce: 1. 2. 3. sagan themes # emerge info Portage 2.0.50 (default-x86-1.4, gcc-3.2.3, glibc-2.3.2-r9, 2.4.22-gentoo-r5) =============================================================== == System uname: 2.4.22-gentoo-r5 i686 AMD Athlon(TM) XP 2000+ Gentoo Base System version 1.4.3.10p1 Autoconf: sys-devel/autoconf-2.58 Automake: sys-devel/automake-1.7.7 ACCEPT_KEYWORDS="x86" AUTOCLEAN="yes" CFLAGS="-march=athlon-xp -O3 -pipe -fomit-frame-pointer" 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/share/config /usr/share/config /var/qmail/control" CONFIG_PROTECT_MASK="/etc/gconf /etc/env.d" CXXFLAGS="-march=athlon-xp -O3 -pipe -fomit-frame-pointer" DISTDIR="/usr/portage/distfiles" FEATURES="autoaddcvs ccache sandbox" GENTOO_MIRRORS="http://gentoo.oregonstate.edu http://distro.ibiblio.org/pub/Linux/distributions/ gentoo" MAKEOPTS="-j2" PKGDIR="/usr/portage/packages" PORTAGE_TMPDIR="/var/tmp" PORTDIR="/usr/portage" PORTDIR_OVERLAY="" SYNC="rsync://rsync.gentoo.org/gentoo-portage" USE="X alsa apache2 apm arts avi berkdb cdr crypt cups encode foomaticdb gdbm gif gpm gtk2 imap imlib java jpeg kde libg++ libwww mad maildir mikmod mmx motif mpeg mysql ncurses nls oggvorbis opengl oss pam pdflib perl png python qt quicktime readline samba sasl sdl slang spell sse ssl svga tcltk tcpd truetype v4l x86 xml2 xmms xv zlib"
*** This bug has been marked as a duplicate of 29856 ***
I believe that this bug was marked a dup of #29856 in error. That bug is a rambling argument about correct syntax for portage, and what the man page should say. My problem is simple. With 2.0.50 "emerge -up world" fails. This is a basic command, that should just work. Changing to 2.0.49-r21 and everything works as expected.
no, i'm pretty sure marius meant it yeah it's supposed to work but that doesnt change where the error is coming from
`grep apache /var/cache/edb/world`
ahh, I see. adding I had a pinned version of apache, but without the "=" sign. I unpinned it, and everything is dandy. Thanks for the help.
I have similar problems after the upgrade as well - I got the failed to update counter problem.
I have the same problem after the upgrade, and I do not have any packages pinned.
*** Bug 40760 has been marked as a duplicate of this bug. ***
Then check the files in /etc/portage/ if it exists
2.0.50-r1 fixes the world file... any further issues are more than likely due to bad ebuild deps or a user modification of some kind.
*** Bug 42930 has been marked as a duplicate of this bug. ***
