I use one machine to build packages with emerge -b, then emerge onto multiple machines with emerge -k. Slave machines mount /usr/portage from the master. This was working fine until I updated portage to 2.0.11 and emerge -k now fails. Other uses of emerge still look fine. To rule out remote mounting as a cause I did the following on the master: emerge -b gentoolkit - fine emerge -k gentoolkit - failed as below >>> original instance of package unmerged safely. >>> Regenerating /etc/ld.so.cache... >>> app-admin/gentoolkit-0.1.13 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 3688, in pkgmerge cleanup_pkgmerge(mypkg,origdir) File "/usr/lib/python2.2/site-packages/portage.py", line 3632, 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/gentoolkit-0.1.13' I've left the first lines to show where the failure happens. This happens with more than one package so I don't believe the actual package is relevant. Also, I don't know if this is related but I was trying to merge a new package to a slave machine and had the following problem which prompted the portage update. If this is a separate and real bug then I can enter a new bug but it may be solved at the same time or be OK now but masked by this bug. emerge -p package shows a number of dependencies as I would expect. emerge -b package on master builds deps as well. emerge -k package on slave only builds package - not deps. TIA, George.
this is a duplicate of a bug that has already been solved Look at Bug 4606
So it is. PKG_TMPDIR line fixed it. One day I'll pick the right terms to search on. Thanks, George.
np dad ... just mark this bug as a dup now ? ;)
fixed in 2.0.13
For anyone else caught by this... I found a dir in / for each package which I saw this problem on. e.g. /gentoolkit-0.1.13/. I have deleted them with no apparent problems. George.
