I'm a n00b when it comes to understanding Portage's internals, but it seems to me that it would be both useful and simple to have emerge save the "--resume data" after each merge operation rather than only when "properly interupted". That way, --resume would work after power failures, system crashes, etc. Thanks for your consideration. Reproducible: Always Steps to Reproduce: 1. emerge -e world 2. After 100+ packages have been merged, drop limb on power line :-) 3. emerge --resume Actual Results: emerge: It seems we have nothing to resume... Expected Results: *** Resuming merge...
Putting a hold on feature requests for portage as they are drowning out the bugs. Most of these features should be available in the next major version of portage. But for the time being, they are just drowning out the major bugs and delaying the next version's progress. Any bugs that contain patches and any bugs for etc-update or dispatch-conf can be reopened. Sorry, I'm just not good enough with bugzilla. ;)
this is INVALID as emerge already does this.
Invalid
(In reply to comment #2) > emerge already does this. In 2.0.x??? portage 2.0.54 on my comp doesn't. I'll provide a specific test case of you want me to.
Please do.
Test case: 1. Run "emerge svn2cl cvs2cl" 2. While emerge is working on the second ebuild (i.e. cvs2cl), flip main power breaker (or just kill -9 the emerge process) 3. Run "emerge --resume" 4. Observe "emerge: It seems we have nothing to resume..." Notice how this behavior is different than what happens if kill -15 or Ctrl+C is used in step 2. I want portage to be able to resume regardless of how it dies.
I'll take some credit for misleading Alec by telling him that emerge does this already. :P --- portage-2.1_pre.orig/bin/emerge +++ portage-2.1_pre/bin/emerge @@ -2142,6 +2142,7 @@ class depgraph: # Unsafe for parallel merges del portage.mtimedb["resume"]["mergelist"][0] + portage.commit_mtimedb() emergelog(" *** Finished. Cleaning up...")
This is now in trunk for release in portage-2.1_pre5.
Released in 2.1_pre5.
