Hello. I've noticed that at least since 2.3.33 portage leaves behind an empty ${PORTAGE_TMPDIR}/portage/${CATEGORY}, e.g. I have PORTAGE_TMPDIR=/vat/tmp and after merging sys-apps/portage I have an empty /var/tmp/portage/sys-apps dir. Still reproducible with 2.3.35. Wasn't happening at least with 2.3.31
Created attachment 529714 [details] emerge --info portage
The bug has been referenced in the following commit(s): https://gitweb.gentoo.org/proj/portage.git/commit/?id=17604fd598d799c6af24b66fc2c240f90dddd420 commit 17604fd598d799c6af24b66fc2c240f90dddd420 Author: Zac Medico <zmedico@gentoo.org> AuthorDate: 2018-05-04 16:47:49 +0000 Commit: Zac Medico <zmedico@gentoo.org> CommitDate: 2018-05-04 16:51:32 +0000 EbuildMerge: wait build dir to unlock (bug 654812) Wait for the build dir to unlock, in order to ensure that the category directory is removed when appropriate. Fixes: 720fef408d07 ("Binpkg: use async_unlock (bug 614108)") Fixes: 5ca8ef781952 ("EbuildBuild: use async_unlock (bug 614108)") Bug: https://bugs.gentoo.org/654812 pym/_emerge/Binpkg.py | 12 +++++++++++- pym/_emerge/EbuildBuild.py | 12 +++++++++++- pym/_emerge/EbuildMerge.py | 26 +++++++++++++++++++++----- 3 files changed, 43 insertions(+), 7 deletions(-)
Fixed since portage-2.3.36.