Ubuntu
update-manager package

edgy to feisty upgrades fail due to use of old-releases

Bug #241431 reported by Adam Conrad
12
Affects Status Importance Assigned to Milestone
update-manager (Ubuntu)
Fix Released
Medium
Michael Vogt
Feisty
Won't Fix
Medium
Michael Vogt
Gutsy
Won't Fix
Undecided
Unassigned
Hardy
Won't Fix
Undecided
Michael Vogt
Intrepid
Invalid
Undecided
Unassigned

Bug Description

Binary package hint: update-manager

Now that edgy is on old-releases, do-release-upgrade fails because it doesn't know how to cope with the situation. It considers old-releases a foreign mirror, giving you the option to quit, or to just s/edgy/feisty/ which, of course, won't work because feisty is (currently) hosted on archive.ubuntu.com.

The workaround for this is, when asked if you want to s/edgy/feisty/, hit another terminal, rewrite sources.list to use archive.ubuntu.com, and then say "yes, sure, use my custom mirror!", but this is clearly not ideal.

Either the release-upgrader needs a table of release->mirror mappings (not ideal, as it would require new uploads to every old dist as we archive releases), or a quick-n-dirty http prober that can check if a release lives on old-releases or archive, before mangling sources.list (this should future-proof feisty being archived to old-releases). On top of that, of course, old-releases needs to be considered a valid official mirror, not a custom mirror.

Revision history for this message
Michael Vogt (mvo) wrote :

Thanks for your bugreport.

Attached is a fix that should make upgrades at least work again.

Changed in update-manager:
importance: Undecided → Medium
status: New → In Progress
Revision history for this message
Michael Vogt (mvo) wrote :

This fix has the disadvantage that when feisty moves to old-release it will no longer work. However it at least gives people a chance to upgrade. Adding logic to figure out when archive.u.c and when old-releases.u.c is possible but a bit more work.

Changed in update-manager:
assignee: nobody → mvo
importance: Undecided → Medium
status: New → In Progress
assignee: nobody → mvo
status: In Progress → Fix Released
Revision history for this message
Martin Pitt (pitti) wrote :

Accepted into -proposed, please test and give feedback here. Please see https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. Thank you in advance!

Revision history for this message
Martin Pitt (pitti) wrote :

Accepted into feisty-proposed, please test and give feedback here.

Changed in update-manager:
status: In Progress → Fix Committed
Revision history for this message
Andreas Wenning (andreas-wenning) wrote :

Is it correctly understood, that this should fix the edgy -> feisty upgrade?
I've tested this by having an edgy install with edgy-proposed enabled and trying to upgrade; this still produces the errors about "no known repos to use" and offering to just rewrite, which doesn't work (it tries to fetch the feisty packages from old-releases).
Either this fix doesn't help; or my install simply doesn't fetch the package from feisty-proposed. If I have an edgy installed with edgy-proposed repos added, will it the end up fetching this new package? And can I in anyway test if it does that?

Revision history for this message
Martin Pitt (pitti) wrote :

Feisty went "end of life" last week, so this is not relevant any more.

Changed in update-manager:
status: Fix Committed → Won't Fix
Revision history for this message
Chris Jones (cmsj) wrote :

pitti: isn't this still relevant because it's not possible to upgrade edgy->feisty still, even though they are both now on old-releases?

Revision history for this message
Martin Pitt (pitti) wrote :

mvo> the proper fix is to backport the code from the jaunty version so that it auto-detect if it needs to use archive.u.c or old-releases.u.c

Changed in update-manager:
assignee: nobody → mvo
Revision history for this message
Sergio Zanchetta (primes2h) wrote :

The 18 month support period for Gutsy Gibbon 7.10 has reached its end of life -
http://www.ubuntu.com/news/ubuntu-7.10-eol . As a result, we are closing the
Gutsy task.

Changed in update-manager (Ubuntu Gutsy):
status: New → Won't Fix
Revision history for this message
Alex Valavanis (valavanisalex) wrote :

Intrepid Ibex reached end-of-life on 30 April 2010 so I am closing the
report. The bug has been fixed in newer releases of Ubuntu.

Changed in update-manager (Ubuntu Intrepid):
status: New → Invalid
Revision history for this message
Rolf Leggewie (r0lf) wrote :

Hardy has seen the end of its life and is no longer receiving any updates. Marking the Hardy task for this ticket as "Won't Fix".

Changed in update-manager (Ubuntu Hardy):
status: New → Won't Fix
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.
Subscribing...

Other bug subscribers

Remote bug watches

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