Not possible to nicely upgrade from old dist

Bug #371000 reported by Roland Orre
8
This bug affects 1 person
Affects Status Importance Assigned to Milestone
update-manager (Ubuntu)
Invalid
Undecided
Unassigned

Bug Description

Binary package hint: upgrade-system

Our media computer at home (kubuntu) was running feisty, and I as was going to update the system.
Then it says things like:
Failed to fetch http://se.archive.ubuntu.com/ubuntu/dists/feisty/main/binary-amd64/Packages.gz 404 Not Found [IP: 130.239.18.173 80]

I searched the web for a reasonable way to update from feisty to jaunty but didn't find any
The only reasonable way I could do it was to edit /etc/apt/sources.list as
s/feisty/hardy/g
which is consider only doable for computer geeks.

I have been disappointed by debian's update path earlier, as suddenly your system is obsolete, I consider that
it should always be possible to upgrade. Even though I realize that it can be a tough problem.

Revision history for this message
Roland Orre (roland-orre) wrote :

The goal should be that anyone, computer illiterate or not should be able to perform an upgrade, otherwise ubuntu has failed, despite fancy things in new releases.

description: updated
Revision history for this message
Martin-Éric Racine (q-funk) wrote :

Please note that the only supported upgraded paths are:

1) from LTS (long-term stable) to LTS.
2) from each 6-monthly release to the next 6-monthyl release.

To solve your problem, you thus need to successively upgrade to Gutsy, then Hardy, then Intrepid, then Jaunty, since directly upgrading from Feisty to Jaunty is NOT supported. Additionally, Feisty is no longer supported as a release. See http://www.ubuntu.com/getubuntu/upgrading for the latest upgrading info.

affects: upgrade-system (Ubuntu) → update-manager (Ubuntu)
Revision history for this message
Jean-Baptiste Lallement (jibel) wrote :

I'm closing this report because upgrading from feisty to hardy is not supported.
Don't hesitate to submit any new bug.

Changed in update-manager (Ubuntu):
status: New → Invalid
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.