Summary: | emerge --resume merges more than expected (portage-2.1.1-r2) | ||
---|---|---|---|
Product: | Portage Development | Reporter: | Martin Gramatke <xmit> |
Component: | Core - Ebuild Support | Assignee: | Portage team <dev-portage> |
Status: | RESOLVED FIXED | ||
Severity: | normal | Keywords: | InVCS |
Priority: | High | ||
Version: | 2.1 | ||
Hardware: | All | ||
OS: | Linux | ||
Whiteboard: | |||
Package list: | Runtime testing required: | --- | |
Bug Depends on: | |||
Bug Blocks: | 181949, 187293 |
Description
Martin Gramatke
2006-11-28 11:51:17 UTC
That's actually the intended behavior (though it's undocumented). A common use case is that a user is running `emerge -e world` and on package fails to compile. After the user has corrected the problem and merged the problematic package individually, the previous resume list is still available so that `emerge -e world` can be restarted exactly where it left off. I searched for the packages to be resumed in emerge.log. At least some of them have been emerged successful. So I suspect once emerge marks a package for resume it will be only unmarked by --resume and not by e.g. an explicit emerge. Can you confirm this? (In reply to comment #2) > I searched for the packages to be resumed in emerge.log. At least some of them > have been emerged successful. So I suspect once emerge marks a package for > resume it will be only unmarked by --resume and not by e.g. an explicit emerge. > Can you confirm this? Yes, that's mostly correct. It's also possible to skip a package in the resume list via --skipfirst. One final question: How do I clean the resume list? Zac, care to update the docs to reflect reality (not 100% sure about the behavior myself)? (In reply to comment #4) > One final question: How do I clean the resume list? There is currently no way to do that via emerge. It's possible to wipe it out by removing /var/cache/edb/mtimedb (that will wipe out some other history but nothing that is really critical). In svn r6742 I've updated the docs to show that the resume history is capable of storing two merge lists. This has been released in 2.1.2.10. |