Different ebuilds fail to emerge. Possibly because of new portage. ebuilds seem not to be failing consistently tho, but if they do, they drop out of emerge with the following error: Traceback (most recent call last): File "/usr/bin/emerge", line 2149, in ? mydepgraph.merge(mydepgraph.altlist()) File "/usr/bin/emerge", line 1356, in merge retval=portage.doebuild(y,"merge",myroot,edebug) File "/usr/lib/python2.2/site-packages/portage.py", line 1821, in doebuild return merge(settings["CATEGORY"],settings["PF"],settings["D"],settings["BUILDDIR"]+"/ build-info",myroot,myebuild=settings["EBUILD"]) File "/usr/lib/python2.2/site-packages/portage.py", line 1940, in merge return mylink.merge(pkgloc,infloc,myroot,myebuild) File "/usr/lib/python2.2/site-packages/portage.py", line 4994, in merge return self.treewalk(mergeroot,myroot,inforoot,myebuild) File "/usr/lib/python2.2/site-packages/portage.py", line 4684, in treewalk unlockdir(mytmpdir_lock) File "/usr/lib/python2.2/site-packages/portage.py", line 5512, in unlockdir return unlockfile(mylock) File "/usr/lib/python2.2/site-packages/portage.py", line 5553, in unlockfile lockfilename,myfd,unlinkfile = mytuple TypeError: unpack non-sequence and leave <packet-name>.portage_lock files in the /var/db/pkg tree. Reverting back to a previous version of portage does not solve this. Which somehow makes me doubt it really is portage. the version that started all was 2.0.49-r9, but r8 is doing the same now. This behaviour is shown on three different machines, one of which is just updated to ~x86, and two of which are being freshly build with ~x86 enabled. The bootstrap.sh goes without a glitch, the emerge system however drops out of warp. Reproducible: Sometimes Steps to Reproduce: 1. 2. 3.
*** This bug has been marked as a duplicate of 30613 ***
