Summary: | emerge --skipfirst without --resume tries to emerge wrong packages with portage 2.2.0_alpha72 | ||
---|---|---|---|
Product: | Portage Development | Reporter: | Matteo Modesti <mattemod> |
Component: | Core | Assignee: | Portage team <dev-portage> |
Status: | UNCONFIRMED --- | ||
Severity: | normal | ||
Priority: | Normal | ||
Version: | unspecified | ||
Hardware: | AMD64 | ||
OS: | Linux | ||
Whiteboard: | |||
Package list: | Runtime testing required: | --- |
Description
Matteo Modesti
2011-11-08 00:35:06 UTC
(In reply to comment #0) > I always get a build error when I try to emerge net-nds/openldap, so I tried to > use --skipfirst, not remembering that it required --resume. This way I > discovered that when I use that parameter, portage tries to emerge totally > different from what it should! As noted in the emerge --resume document `man emerge`: The resume history is capable of storing two merge lists. After one resume list completes, it is possible to invoke --resume once again in order to resume an older list. So, if you get unexpected results then it's probably do to emerge using an older saved list. You can use `emaint --fix cleanresume` to discard old lists. Maybe we can consider this bug a duplicate of bug 366723. As noted in bug 366723, comment #4, I'd like to display a warning message when the backup resume list is used. This could be caused by pointless dependencies check, not inhibited by --resume (though I did not check that). I already discovered, that --nodeps --resume combo prevents "Invalid resume list" error, which could also prevent reordering. |