Summary: | emerge leaves cruft in /var/tmp/portage even if the package was merged successfuly | ||
---|---|---|---|
Product: | Portage Development | Reporter: | Petr Baudis <pasky> |
Component: | Core | Assignee: | Portage team <dev-portage> |
Status: | RESOLVED FIXED | ||
Severity: | minor | CC: | jakub |
Priority: | High | Keywords: | InVCS |
Version: | 2.1 | ||
Hardware: | All | ||
OS: | All | ||
Whiteboard: | |||
Package list: | Runtime testing required: | --- | |
Bug Depends on: | |||
Bug Blocks: | 115839 |
Description
Petr Baudis
2005-09-12 09:38:26 UTC
I already discussed a similar issue myself on #gentoo-portage. I can confirm this problem. Additionally - for me at least - portage leaves *everything* in /var/tmp/portage, the whole work, image, temp subtrees and sources/temp files when I do 'emerge -B some-ebuild'. Of course, a lot of cruft accumulater really quickly and /var runs out of disk space periodically. :( P.S. No, I *don't* have keeptemp or keepwork in FEATURES. ;) (In reply to comment #0) > Emerging a package leaves files "eclass-debug.log" and "environment" Actually, it is when the previous version is unmerged that ${T}/{eclass-debug.log,environment} are left behind. That makes the reported issue a duplicate of bug 85803. (In reply to comment #1) > Additionally - for me at least - portage leaves *everything* in > /var/tmp/portage, the whole work, image, temp subtrees and sources/temp files > when I do 'emerge -B some-ebuild'. Jakub, have you resolved your issue? If so, do you know what caused it? (In reply to comment #2) > Jakub, have you resolved your issue? If so, do you know what caused it? No, it's still broken here and I have NFC what's the problem. :-( i dont think it's broken the behavior i see is: - /var/tmp/portage is empty - i install package test-0 - /var/tmp/portage has the 'test-0' subdir cleaned out - i upgrade to test-1 - /var/tmp/portage has the 'test-1' subdir cleaned out but the 'test-0' is left behind (In reply to comment #4) > the behavior i see is: > - /var/tmp/portage is empty > - i install package test-0 > - /var/tmp/portage has the 'test-0' subdir cleaned out > - i upgrade to test-1 > - /var/tmp/portage has the 'test-1' subdir cleaned out but the 'test-0' is left > behind Well, what I see here is that anything emerged with -B leaves all the cruft behind; don't think this should be considered a feature... Okay, I did emerge -B somepackage and got the same results as Jakub. The code inside emerge clearly shows that the "clean" target is only run after the merge if "--buildpkgonly" not in myopts. This is in svn r2840 for release in 2.1_pre6. Released in 2.1_pre6. |