Retrying failed unpack should not cause critical message

Bug #1001482 reported by Robie Basak
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
debootstrap (Ubuntu)
New
Undecided
Unassigned

Bug Description

A Quantal netinst failed with "Failure while unpacking required packages. This will be attempted up to five times.". As (I presume) this is priority critical, it breaks my automated installation.

Please consider making this message less than critical.

The bug that caused this situation is bug 1001460.

Robie Basak (racb)
Changed in debootstrap (Ubuntu):
assignee: nobody → Colin Watson (cjwatson)
Revision history for this message
Colin Watson (cjwatson) wrote :

I think that message needs to be critical if it happens. We always need to make sure it simply doesn't happen.

Colin Watson (cjwatson)
Changed in debootstrap (Ubuntu):
assignee: Colin Watson (cjwatson) → nobody
Revision history for this message
Ken Sharp (kennybobs) wrote :

Works as intended. I don't know why anyone would accept a failure as anything less than critical.

Changed in debootstrap (Ubuntu):
status: New → Invalid
Revision history for this message
Robie Basak (racb) wrote :

@Ken

Because if it can retry and succeed, then it wasn't a critical failure. An automatic installation could still succeed if the retry had been successful, but for the prompt that blocked it.

Changed in debootstrap (Ubuntu):
status: Invalid → New
Revision history for this message
Robie Basak (racb) wrote :

However it would make sense to have a critical message if it has retried and given up, of course. Just not if it is merely going to retry.

Revision history for this message
Robie Basak (racb) wrote :

Or, another way to look at this: the retry code is redundant if it cannot be used. I guess it still could manually, but why would you unnecessarily block automation then?

To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.