Bug 96250 – emerge --resume should return non-0 exit status with no resumes to do

• Status: VERIFIED LATER
• Product: Portage Development

[Description Gherald 2005-06-15 23:57:59 UTC]

emerge --resume should return non-zero exit status when there is nothing toresume.

Reproducible: Always
Steps to Reproduce:
run "emerge --resume"
Actual Results:  
message: "emerge: It seems we have nothing to resume..." and a zero exit status.

Expected Results:  
the message is fine, but there should be a non-zero exit status

[Comment 1 Chris White (RETIRED) 2005-06-16 00:06:27 UTC]

I'm not sure how the logic holds on that one.  You asked emerge to --resume,  
and well, it did.. so technically it did its job... well we'll see what the  
actual portage devs want to say on this one :P.  
 
Adjusted the summary a little too. 

[Comment 2 Marius Mauch (RETIRED) 2005-06-16 03:24:09 UTC]

I also don't see a reason for this, lack of jobs to resume isn't a failure and
changing this would prevent at least one nice trick.

[Comment 3 Jason Stubbs (RETIRED) 2005-07-28 07:24:58 UTC]

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. ;) 

[Comment 4 Marius Mauch (RETIRED) 2007-01-12 06:11:36 UTC]

See comment #2