Since installation of portage-2.0.50 emerge -uD world has refused to work, crashing repeatedly and consistently. By amending portage to print the world 'scan' process I traced the cause to the presence of fuse 0.6.1.1 whose presence caused this error (tested by emerging and unmerging it). The problem appears to be associated with the conditional gtk/gtk2 dependency in the ebuild. Removing this gtk dependency completely causes the error to go away. This appears to be only present in the --deep --world scan; emerging fuse works fine under all cirumstances. [Is the problem associated with the comment around line 1120 of /usr/bin/emerge ?] This bug appears to be quite common judging from the discussion boards, but there appears to be no standard fix for it, various suggestions (fix-db, regenworld,fixpackages, portage-rescue) tried but none work. This appears to be a problem which occurs only on some systems but it is unclear as to the precise cause and I'm not enough of a portage expert to sort it out exactly. Reproducible: Always Steps to Reproduce: 1. emerge sync (refix up my modified fuse 0.6.1.1 ebuild which I hacked) 2. emerge -upD world 3. Actual Results: /usr/bin/emerge crashes giving what appears from the stack trace to be a dependency error (refers to mydep[:1]). Point of crash is in portage.py and traces back to emerge. I can reproduce the exact text if required,don't have it now as have fudged things to work and didn't keep the old ebuild. Expected Results: Listed apps due to be updated. Portage 2.0.50-r1 (default-x86-1.4, gcc-3.3.2, glibc-2.3.2-r9, 2.6.2-gentoo) ================================================================= System uname: 2.6.2-gentoo i686 Intel(R) Pentium(R) 4 CPU 2.80GHz Gentoo Base System version 1.4.3.13 Autoconf: sys-devel/autoconf-2.58-r1 Automake: sys-devel/automake-1.7.7 ACCEPT_KEYWORDS="x86" AUTOCLEAN="yes" CFLAGS="-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/tex/generic/config/ /usr/share/texmf/tex/platex/config/ /var/qmail/control" CONFIG_PROTECT_MASK="/etc/gconf /etc/env.d" CXXFLAGS="-O2 -pipe" DISTDIR="/usr/portage/distfiles" FEATURES="autoaddcvs ccache sandbox" GENTOO_MIRRORS="http://212.219.247.10/sites/www.ibiblio.org/gentoo/" MAKEOPTS="-j3" PKGDIR="/usr/portage/packages" PORTAGE_TMPDIR="/var/tmp" PORTDIR="/usr/portage" PORTDIR_OVERLAY="" SYNC="rsync://rsync.gentoo.org/gentoo-portage" USE="X aalib alsa apm arts avi berkdb bonobo cdr crypt cups dvd encode esd fbdirect foomaticdb gdbm gif gphoto2 gpm gtk gtk2 gtkhtml guile imlib java jpeg kde libg++ libwww mad mikmod motif mozilla mpeg mysql ncurses nls oggvorbis opengl oss pam pdflib perl png ppds python qt quicktime readline scanner sdl slang spell ssl svga tcltk tcpd tetex truetype usb x86 xml2 xmms xv zlib" Both gtk+ v1 and v2 are installed.
Error report is : Traceback (most recent call last): File "/usr/bin/emerge", line 2520, in ? if not mydepgraph.xcreate(myaction): File "/usr/bin/emerge", line 1138, in xcreate if not self.create(myk): File "/usr/bin/emerge", line 825, in create if not self.select_dep("/",mydep["/"],myparent=mp,myuse=myuse): File "/usr/bin/emerge", line 936, in select_dep mycheck=portage.dep_check(depstring,self.mydbapi[myroot],self.pkgsettings,myuse=myuse) File "/usr/lib/portage/pym/portage.py", line 3309, in dep_check mylist=flatten(dep_listcleanup(dep_zapdeps(mysplit,mysplit2))) File "/usr/lib/portage/pym/portage.py", line 3052, in dep_zapdeps myresult=dep_zapdeps(unreduced[x],reduced[x]) File "/usr/lib/portage/pym/portage.py", line 3019, in dep_zapdeps if not mydbapi.match(y): File "/usr/lib/portage/pym/portage.py", line 4138, in match mydep=dep_expand(origdep,self,use_cache=use_cache) File "/usr/lib/portage/pym/portage.py", line 3255, in dep_expand elif mydep[:1] in "=<>~!": TypeError: 'in <string>' requires string as left operand
Clarification of original statement. portage-rescue does work in that the problem disappears and emerge -upD works again *but* the problem returns after updating again. (tried this twice).
Fixed in cvs.
*** Bug 40697 has been marked as a duplicate of this bug. ***
*** Bug 45688 has been marked as a duplicate of this bug. ***
I just faced this problem yesterday, having been on portage 2.0.50 for a while now; funny. Is the proposed solution to upgrade to the unstable portage version?
Bug has been fixed and released in stable portages on or before 2.0.51-r2
