When using --usepkg, portage gives the error below. The package seems to be installed ok however. >>> Regenerating /etc/ld.so.cache... >>> kde-base/kdetoys-3.0.2 merged. Traceback (most recent call last): File "/usr/bin/emerge", line 1265, in ? mydepgraph.merge(mydepgraph.altlist()) File "/usr/bin/emerge", line 643, in merge retval=portage.pkgmerge(mytbz2,x[1]) File "/usr/lib/python2.2/site-packages/portage.py", line 3619, in pkgmerge cleanup_pkgmerge(mypkg,origdir) File "/usr/lib/python2.2/site-packages/portage.py", line 3569, in cleanup_pkgmerge shutil.rmtree(settings["PKG_TMPDIR"]+"/"+mypkg) File "/usr/lib/python2.2/shutil.py", line 117, in rmtree _build_cmdtuple(path, cmdtuples) File "/usr/lib/python2.2/shutil.py", line 132, in _build_cmdtuple for f in os.listdir(path): OSError: [Errno 2] No such file or directory: '/var/tmp/portage-pkg/kdetoys-3.0.2'
In addition to the error, emerge --usepkg appears to be expanding the package files in /.
how does portage 2.0.10 behave for you?
2.0.10 does the same thing for me - packages are expanded in /, and then the emerge terminates with an error.
what packages does this error on for you ? i use -b and -k all the time w/out problems (except for Bug 4508)
weird i just started getting the same problem ... i'm using portage-2.0.11 ... i know drobbins started asking ppl if he could log into their box to track down weird portage errors ... if he doesnt have this one figured out/reproducible on his own machines, ill offer mine up
the following line got lost between versions 2.0.8 and 2.0.9... PKG_TMPDIR=${PORTAGE_TMPDIR}/portage-pkg put it back in make.globals and be happy... ;-)
hmm i recalled doing a diff on ._cfg_0000_make.global and make.global and noticing a few missing lines ... i also remember thinking 'how odd the new one is missing a few vars' ;) thx ulf, works for me now
