Upgrade from Breezy

Mario Vukelic mario.vukelic at dantian.org
Thu Feb 21 20:39:26 UTC 2008

On Thu, 2008-02-21 at 14:26 +0100, Sam Przyswa wrote:
> I had to upgrade Breezy because Breezy is no more supported by Ubuntu
> (!?) to solve this the only solution was UPGRADE to the next version

Yes, but as Andy already wrote in the other reply, support fro Breezy
endet nearly a year ago. I just meant that if you had stayed up-to-date
with the support cycles (which is easy if you subscribe to the
ubuntu-announce mailing list), then you would have known about the
ending support in advance. This in turn would have given you time to
properly plan the upgrade and test it on non-critical machine.

> with changed my sources.list to replace breezy with dapper, right, then
> I make update && apt-get dist-upgrade, right !
> I followed the https://help.ubuntu.com/community/DapperUpgrades

That's not what I meant. You probably did fine as far as following the
recommended upgrade procedure goes (though I do wonder how you ended up
with the backports repo active, as per the other subthread).

> I blame me "for not following proper processes" I just use the process
> given by help.ubuntu.com where is my mistake ?

What I meant was that you should have known when the support of Breezy
ends and plan accordingly, and you should have tested the upgrade on a
non-critical machine. Configuration changes can _always_ go wrong, and a
complete machine upgrade even more so. It is unwise to upgrade a
critical live system without testing the upgrade on a spare machine (and
generations of sysadmins found out the hard way and wrote books and
articles about it).

More information about the ubuntu-users mailing list