How to roll back Ubuntu to a previous version?
I just installed a new version of Ubuntu and I want to roll it back to the previous version.
How can I do that? Is that even possible?
release-management downgrade
add a comment |
I just installed a new version of Ubuntu and I want to roll it back to the previous version.
How can I do that? Is that even possible?
release-management downgrade
2
Here is one on ubuntu wiki.
– Quazi Irfan
Nov 29 '13 at 12:45
This is one of the reasons why one would really want this to happen and be successful: Revisiting How We Put Together Linux Systems. Booting another operating system or release from the same filesystem? It could be a problem of the past.
– LiveWireBT
Dec 16 '14 at 16:46
add a comment |
I just installed a new version of Ubuntu and I want to roll it back to the previous version.
How can I do that? Is that even possible?
release-management downgrade
I just installed a new version of Ubuntu and I want to roll it back to the previous version.
How can I do that? Is that even possible?
release-management downgrade
release-management downgrade
edited Oct 28 '15 at 17:23
Tim
19.6k1484140
19.6k1484140
asked Jun 21 '11 at 15:19
OHLÁLÁOHLÁLÁ
2,15272748
2,15272748
2
Here is one on ubuntu wiki.
– Quazi Irfan
Nov 29 '13 at 12:45
This is one of the reasons why one would really want this to happen and be successful: Revisiting How We Put Together Linux Systems. Booting another operating system or release from the same filesystem? It could be a problem of the past.
– LiveWireBT
Dec 16 '14 at 16:46
add a comment |
2
Here is one on ubuntu wiki.
– Quazi Irfan
Nov 29 '13 at 12:45
This is one of the reasons why one would really want this to happen and be successful: Revisiting How We Put Together Linux Systems. Booting another operating system or release from the same filesystem? It could be a problem of the past.
– LiveWireBT
Dec 16 '14 at 16:46
2
2
Here is one on ubuntu wiki.
– Quazi Irfan
Nov 29 '13 at 12:45
Here is one on ubuntu wiki.
– Quazi Irfan
Nov 29 '13 at 12:45
This is one of the reasons why one would really want this to happen and be successful: Revisiting How We Put Together Linux Systems. Booting another operating system or release from the same filesystem? It could be a problem of the past.
– LiveWireBT
Dec 16 '14 at 16:46
This is one of the reasons why one would really want this to happen and be successful: Revisiting How We Put Together Linux Systems. Booting another operating system or release from the same filesystem? It could be a problem of the past.
– LiveWireBT
Dec 16 '14 at 16:46
add a comment |
9 Answers
9
active
oldest
votes
Downgrading releases is possible to some extent. With enough fighting, it can be done (see some of the other answers here for the the technical details).
However the result you end up with is not the same as what you had before the upgrade. During an upgrade certain one-way changes are made to make new packages happy and downgrading them won't reverse those edits. It's impossible to guarantee a downgrade will work at all, let alone if it'll be stable.
In short, your easiest option is always going to be a reinstall. Don't think of it as a chore, look at it as a nice opportunity to trim down on packages and configure things better.
If you want to test things in the future and you fear you might have issues, always make sure you do the following:
- Test the LiveCD first. If you're going to have immediate hardware issues, this should let you know.
- Back up before you do anything. I know everybody and their mother has already told you to do this, but it's really important if you think you're going to have issues. If you can't do without your machine for more than 20 minutes, consider some full-disk cloning tools like Clonezilla so you can just restore a previous version of the disk. There are other tools that can offer similar results.
- Keep your data separate. Having your
/home/
within the same partition as your installation is a recipe for a headache if you're constantly upgrading/downgrading things. Push it off to another disk or at least another partition so that when you do need to reinstall, you really just need to set up the mount. - There was a critical bug for downgrading that was fixed by the Ubuntu QA team. Make sure you read up on that, as some people will recommend you just stick in an older CD and "upgrade" to it, but this is a bad idea.
6
You don't need a separate partition, you can just reinstall over the broken system, see here: askubuntu.com/questions/247/…
– Jorge Castro
Sep 13 '11 at 0:32
The critical bug appears to be fixed for 12.04 (Precise). So this issue will still affect 11.04 and 11.10, both of which are by now end-of-life. Anyone able to confirm?
– david6
Jun 2 '13 at 10:47
1
Is it possible to just overwrite the system files with the desired release? i.e. if I use 12.10 and want to go back to 12.04 or older, without backing up anything, is it possible just to overwrite the system files with fresh installation.
– Quazi Irfan
Nov 29 '13 at 12:47
@iamcreasy That's what my second paragraph deals with. Upgrades are often transformation. None of what you describe is something I'd do without backing up.
– Oli♦
Nov 29 '13 at 12:50
1
I was talking about overwriting the system files only. Re-installation of the OS without formatting the hdd.
– Quazi Irfan
Nov 29 '13 at 13:31
add a comment |
There's a saying in my language which can be roughly translated as "You can't turn mince back into meat by rotating the mincer's handle in the opposite direction" :)
The upgrade procedure is one-way - while installing new versions of software, your configuration files and settings are modified by packages' post-install scripts to use new format which is required by new software. Basically, there's no opposite procedure - to make a newer configuration file compatible with old software.
9
I disagree, upgrading a system is about replacing old packages with new packages, which should be a reversible process (replace new packages with old ones). There's no inherent need to destroy anything during an upgrade, it's just that most systems we use don't really care about downgrading and don't support it (well).
– Georges Dupéron
Oct 8 '13 at 16:04
10
@GeorgesDupéron: you're right, there is no law of physics which would make downgrades impossible, so it is totally possible to build a tool which can upgrade/downgrade a system to any version. However, there's no such tool, so my answer stands for the real-life Ubuntu and its upgrade tools.
– Sergey
Oct 8 '13 at 20:42
add a comment |
It's possible at the level of the packaging tools (apt). But the resulting system may not be equivalent to doing a reinstall, and you may get errors along the way. This is because many packages contain specific support for upgrades (e.g. handling changes in configuration files) but not for downgrades.
Normally, apt prefers to install the most recent version of a package. But you can change this through pinning: you can declare that packages from the old release have higher priority than the installed packages, so that they will be downgrades when you do aptitude dist-upgrade
.
Change your /etc/apt/sources.list
to include only the old release (either edit the file or use your favorite GUI), and run aptitude update
. Then edit /etc/apt/preferences
(documented in the apt_preferences
man page) and add the following lines (to downgrade to lucid):
Package: *
Pin: release v=10.04
Pin-Priority: 1001
Then run aptitude dist-upgrade
. Every package has a priority greater than 1000, so every package that is present in 10.04 and installed on your system will be downgraded. You'll have to remove packages that weren't in 10.04 manually; they'll be listed under “Obsolete and locally created packages” in aptitude.
This helped me after running twicedo-release-upgrade
(as first call has hung). So I could revert apt lists to proper release.
– PeterM
Nov 22 '16 at 19:26
add a comment |
They say, "never say never", and "nothing is impossible" - both of which are true, but not in your case. I suggest you either back up your data and reinstall, or stick it out. The system should become more and more stable as the weeks go by.
You can also reinstall on top of the existing installation (it will keep your files).
As a rule of thumb though, try to avoid upgrading to development versions on production systems (especially if you are not a tester/developer).
add a comment |
You can do it manually.
First generate a list of what you have installed on your system. You can do this by typing the following in the terminal.
sudo dpkg --get-selections | grep '[[:space:]]install$' | awk '{print $1}' > package_list
copy your /home and /etc folder to a backup media.
Re install ubuntu 10.04. Restore your backup (remember to set the correct premissions). Then run the following to reinstall all the program you had before.
cat package_list | xargs sudo apt-get install
Note that you might have to do some cleaning of the /etc and /home folder for incompatible settings.
add a comment |
This is why you are not supposed to upgrade your main install to the development release. If you want to test the development release, you should do so on a separate partition so you can boot back into the stable release when things go wrong.
At this point if you want to go back to 11.04, you need to reinstall it, and choose manual partitioning. Do NOT check the format box when configuring your partitions and your user files should remain intact.
add a comment |
Simple method is booting up from a CD/DVD or USB stick of previous version and reinstall Ubuntu by overwriting existing installation.
Don't forget backup first: your home
directory any anywhere else you may have personal data.
2
Backup your files first ;)
– Achu
Feb 22 '12 at 18:26
add a comment |
Roll-backs may work fine for certain packages in isolation, but I wouldn't ever expect a large-scale roll-back of an entire distribution to leave you with anything other than a horribly broken system (or one which, on the surface looks to be fine, but strange things keep surfacing as you discover it is more and more broken).
APT is just designed to avoid roll-backs as much as possible, and the packages that make up the Ubuntu (and Debian, for that matter) distribution aren't designed with smooth roll-backs as a design goal.
Unless you have whole-system backups that are reliable, what you really need to do is ensure your entire home directory is backed up (and possibly also on a separate partition), re-install from the CD image of your chosen version, and start restoring your data from your home folder(s). You may even need to selectively restore the dotfiles in your home directory in case any which have become accustomed to the new version don't quite work well with the older version.
Before you do, you may want to peruse your installed packages and write down which ones you rely on, so you can re-install them. There are tools to backup and restore your list of installed packages, but I wouldn't normally recommend doing this if you are going between versions as the packages needed/included may have changed.
add a comment |
To put it simply: no there's not. Sorry... (These are the dangers of upgrading to testing releases!)
2
Had I been aware that Ubuntu has crippled the Netbook Remix as horribly as they did before hand, I would not have done the upgrade at all. Re-installing is not a major issue, but I though the question was worth the effort of posting it.
– Diago
Sep 5 '10 at 16:52
@Diago Just out of curiosity is this a complete dislike of the new interface? Or simply a belief it's not finished yet?
– 8128
Sep 5 '10 at 19:26
A bit of both. I am frustrated by the lack of usability from a non technical user perspective. I can find my way around and install additional software to get functionality, but fail to see how a complete novice will survive. I believe it needs a lot more work if they plan to meet the October deadline.
– Diago
Sep 5 '10 at 19:33
add a comment |
protected by Community♦ Nov 4 '11 at 13:14
Thank you for your interest in this question.
Because it has attracted low-quality or spam answers that had to be removed, posting an answer now requires 10 reputation on this site (the association bonus does not count).
Would you like to answer one of these unanswered questions instead?
9 Answers
9
active
oldest
votes
9 Answers
9
active
oldest
votes
active
oldest
votes
active
oldest
votes
Downgrading releases is possible to some extent. With enough fighting, it can be done (see some of the other answers here for the the technical details).
However the result you end up with is not the same as what you had before the upgrade. During an upgrade certain one-way changes are made to make new packages happy and downgrading them won't reverse those edits. It's impossible to guarantee a downgrade will work at all, let alone if it'll be stable.
In short, your easiest option is always going to be a reinstall. Don't think of it as a chore, look at it as a nice opportunity to trim down on packages and configure things better.
If you want to test things in the future and you fear you might have issues, always make sure you do the following:
- Test the LiveCD first. If you're going to have immediate hardware issues, this should let you know.
- Back up before you do anything. I know everybody and their mother has already told you to do this, but it's really important if you think you're going to have issues. If you can't do without your machine for more than 20 minutes, consider some full-disk cloning tools like Clonezilla so you can just restore a previous version of the disk. There are other tools that can offer similar results.
- Keep your data separate. Having your
/home/
within the same partition as your installation is a recipe for a headache if you're constantly upgrading/downgrading things. Push it off to another disk or at least another partition so that when you do need to reinstall, you really just need to set up the mount. - There was a critical bug for downgrading that was fixed by the Ubuntu QA team. Make sure you read up on that, as some people will recommend you just stick in an older CD and "upgrade" to it, but this is a bad idea.
6
You don't need a separate partition, you can just reinstall over the broken system, see here: askubuntu.com/questions/247/…
– Jorge Castro
Sep 13 '11 at 0:32
The critical bug appears to be fixed for 12.04 (Precise). So this issue will still affect 11.04 and 11.10, both of which are by now end-of-life. Anyone able to confirm?
– david6
Jun 2 '13 at 10:47
1
Is it possible to just overwrite the system files with the desired release? i.e. if I use 12.10 and want to go back to 12.04 or older, without backing up anything, is it possible just to overwrite the system files with fresh installation.
– Quazi Irfan
Nov 29 '13 at 12:47
@iamcreasy That's what my second paragraph deals with. Upgrades are often transformation. None of what you describe is something I'd do without backing up.
– Oli♦
Nov 29 '13 at 12:50
1
I was talking about overwriting the system files only. Re-installation of the OS without formatting the hdd.
– Quazi Irfan
Nov 29 '13 at 13:31
add a comment |
Downgrading releases is possible to some extent. With enough fighting, it can be done (see some of the other answers here for the the technical details).
However the result you end up with is not the same as what you had before the upgrade. During an upgrade certain one-way changes are made to make new packages happy and downgrading them won't reverse those edits. It's impossible to guarantee a downgrade will work at all, let alone if it'll be stable.
In short, your easiest option is always going to be a reinstall. Don't think of it as a chore, look at it as a nice opportunity to trim down on packages and configure things better.
If you want to test things in the future and you fear you might have issues, always make sure you do the following:
- Test the LiveCD first. If you're going to have immediate hardware issues, this should let you know.
- Back up before you do anything. I know everybody and their mother has already told you to do this, but it's really important if you think you're going to have issues. If you can't do without your machine for more than 20 minutes, consider some full-disk cloning tools like Clonezilla so you can just restore a previous version of the disk. There are other tools that can offer similar results.
- Keep your data separate. Having your
/home/
within the same partition as your installation is a recipe for a headache if you're constantly upgrading/downgrading things. Push it off to another disk or at least another partition so that when you do need to reinstall, you really just need to set up the mount. - There was a critical bug for downgrading that was fixed by the Ubuntu QA team. Make sure you read up on that, as some people will recommend you just stick in an older CD and "upgrade" to it, but this is a bad idea.
6
You don't need a separate partition, you can just reinstall over the broken system, see here: askubuntu.com/questions/247/…
– Jorge Castro
Sep 13 '11 at 0:32
The critical bug appears to be fixed for 12.04 (Precise). So this issue will still affect 11.04 and 11.10, both of which are by now end-of-life. Anyone able to confirm?
– david6
Jun 2 '13 at 10:47
1
Is it possible to just overwrite the system files with the desired release? i.e. if I use 12.10 and want to go back to 12.04 or older, without backing up anything, is it possible just to overwrite the system files with fresh installation.
– Quazi Irfan
Nov 29 '13 at 12:47
@iamcreasy That's what my second paragraph deals with. Upgrades are often transformation. None of what you describe is something I'd do without backing up.
– Oli♦
Nov 29 '13 at 12:50
1
I was talking about overwriting the system files only. Re-installation of the OS without formatting the hdd.
– Quazi Irfan
Nov 29 '13 at 13:31
add a comment |
Downgrading releases is possible to some extent. With enough fighting, it can be done (see some of the other answers here for the the technical details).
However the result you end up with is not the same as what you had before the upgrade. During an upgrade certain one-way changes are made to make new packages happy and downgrading them won't reverse those edits. It's impossible to guarantee a downgrade will work at all, let alone if it'll be stable.
In short, your easiest option is always going to be a reinstall. Don't think of it as a chore, look at it as a nice opportunity to trim down on packages and configure things better.
If you want to test things in the future and you fear you might have issues, always make sure you do the following:
- Test the LiveCD first. If you're going to have immediate hardware issues, this should let you know.
- Back up before you do anything. I know everybody and their mother has already told you to do this, but it's really important if you think you're going to have issues. If you can't do without your machine for more than 20 minutes, consider some full-disk cloning tools like Clonezilla so you can just restore a previous version of the disk. There are other tools that can offer similar results.
- Keep your data separate. Having your
/home/
within the same partition as your installation is a recipe for a headache if you're constantly upgrading/downgrading things. Push it off to another disk or at least another partition so that when you do need to reinstall, you really just need to set up the mount. - There was a critical bug for downgrading that was fixed by the Ubuntu QA team. Make sure you read up on that, as some people will recommend you just stick in an older CD and "upgrade" to it, but this is a bad idea.
Downgrading releases is possible to some extent. With enough fighting, it can be done (see some of the other answers here for the the technical details).
However the result you end up with is not the same as what you had before the upgrade. During an upgrade certain one-way changes are made to make new packages happy and downgrading them won't reverse those edits. It's impossible to guarantee a downgrade will work at all, let alone if it'll be stable.
In short, your easiest option is always going to be a reinstall. Don't think of it as a chore, look at it as a nice opportunity to trim down on packages and configure things better.
If you want to test things in the future and you fear you might have issues, always make sure you do the following:
- Test the LiveCD first. If you're going to have immediate hardware issues, this should let you know.
- Back up before you do anything. I know everybody and their mother has already told you to do this, but it's really important if you think you're going to have issues. If you can't do without your machine for more than 20 minutes, consider some full-disk cloning tools like Clonezilla so you can just restore a previous version of the disk. There are other tools that can offer similar results.
- Keep your data separate. Having your
/home/
within the same partition as your installation is a recipe for a headache if you're constantly upgrading/downgrading things. Push it off to another disk or at least another partition so that when you do need to reinstall, you really just need to set up the mount. - There was a critical bug for downgrading that was fixed by the Ubuntu QA team. Make sure you read up on that, as some people will recommend you just stick in an older CD and "upgrade" to it, but this is a bad idea.
edited Jul 5 '14 at 12:38
Braiam
51.5k20136220
51.5k20136220
answered Jun 21 '11 at 15:37
Oli♦Oli
220k86558762
220k86558762
6
You don't need a separate partition, you can just reinstall over the broken system, see here: askubuntu.com/questions/247/…
– Jorge Castro
Sep 13 '11 at 0:32
The critical bug appears to be fixed for 12.04 (Precise). So this issue will still affect 11.04 and 11.10, both of which are by now end-of-life. Anyone able to confirm?
– david6
Jun 2 '13 at 10:47
1
Is it possible to just overwrite the system files with the desired release? i.e. if I use 12.10 and want to go back to 12.04 or older, without backing up anything, is it possible just to overwrite the system files with fresh installation.
– Quazi Irfan
Nov 29 '13 at 12:47
@iamcreasy That's what my second paragraph deals with. Upgrades are often transformation. None of what you describe is something I'd do without backing up.
– Oli♦
Nov 29 '13 at 12:50
1
I was talking about overwriting the system files only. Re-installation of the OS without formatting the hdd.
– Quazi Irfan
Nov 29 '13 at 13:31
add a comment |
6
You don't need a separate partition, you can just reinstall over the broken system, see here: askubuntu.com/questions/247/…
– Jorge Castro
Sep 13 '11 at 0:32
The critical bug appears to be fixed for 12.04 (Precise). So this issue will still affect 11.04 and 11.10, both of which are by now end-of-life. Anyone able to confirm?
– david6
Jun 2 '13 at 10:47
1
Is it possible to just overwrite the system files with the desired release? i.e. if I use 12.10 and want to go back to 12.04 or older, without backing up anything, is it possible just to overwrite the system files with fresh installation.
– Quazi Irfan
Nov 29 '13 at 12:47
@iamcreasy That's what my second paragraph deals with. Upgrades are often transformation. None of what you describe is something I'd do without backing up.
– Oli♦
Nov 29 '13 at 12:50
1
I was talking about overwriting the system files only. Re-installation of the OS without formatting the hdd.
– Quazi Irfan
Nov 29 '13 at 13:31
6
6
You don't need a separate partition, you can just reinstall over the broken system, see here: askubuntu.com/questions/247/…
– Jorge Castro
Sep 13 '11 at 0:32
You don't need a separate partition, you can just reinstall over the broken system, see here: askubuntu.com/questions/247/…
– Jorge Castro
Sep 13 '11 at 0:32
The critical bug appears to be fixed for 12.04 (Precise). So this issue will still affect 11.04 and 11.10, both of which are by now end-of-life. Anyone able to confirm?
– david6
Jun 2 '13 at 10:47
The critical bug appears to be fixed for 12.04 (Precise). So this issue will still affect 11.04 and 11.10, both of which are by now end-of-life. Anyone able to confirm?
– david6
Jun 2 '13 at 10:47
1
1
Is it possible to just overwrite the system files with the desired release? i.e. if I use 12.10 and want to go back to 12.04 or older, without backing up anything, is it possible just to overwrite the system files with fresh installation.
– Quazi Irfan
Nov 29 '13 at 12:47
Is it possible to just overwrite the system files with the desired release? i.e. if I use 12.10 and want to go back to 12.04 or older, without backing up anything, is it possible just to overwrite the system files with fresh installation.
– Quazi Irfan
Nov 29 '13 at 12:47
@iamcreasy That's what my second paragraph deals with. Upgrades are often transformation. None of what you describe is something I'd do without backing up.
– Oli♦
Nov 29 '13 at 12:50
@iamcreasy That's what my second paragraph deals with. Upgrades are often transformation. None of what you describe is something I'd do without backing up.
– Oli♦
Nov 29 '13 at 12:50
1
1
I was talking about overwriting the system files only. Re-installation of the OS without formatting the hdd.
– Quazi Irfan
Nov 29 '13 at 13:31
I was talking about overwriting the system files only. Re-installation of the OS without formatting the hdd.
– Quazi Irfan
Nov 29 '13 at 13:31
add a comment |
There's a saying in my language which can be roughly translated as "You can't turn mince back into meat by rotating the mincer's handle in the opposite direction" :)
The upgrade procedure is one-way - while installing new versions of software, your configuration files and settings are modified by packages' post-install scripts to use new format which is required by new software. Basically, there's no opposite procedure - to make a newer configuration file compatible with old software.
9
I disagree, upgrading a system is about replacing old packages with new packages, which should be a reversible process (replace new packages with old ones). There's no inherent need to destroy anything during an upgrade, it's just that most systems we use don't really care about downgrading and don't support it (well).
– Georges Dupéron
Oct 8 '13 at 16:04
10
@GeorgesDupéron: you're right, there is no law of physics which would make downgrades impossible, so it is totally possible to build a tool which can upgrade/downgrade a system to any version. However, there's no such tool, so my answer stands for the real-life Ubuntu and its upgrade tools.
– Sergey
Oct 8 '13 at 20:42
add a comment |
There's a saying in my language which can be roughly translated as "You can't turn mince back into meat by rotating the mincer's handle in the opposite direction" :)
The upgrade procedure is one-way - while installing new versions of software, your configuration files and settings are modified by packages' post-install scripts to use new format which is required by new software. Basically, there's no opposite procedure - to make a newer configuration file compatible with old software.
9
I disagree, upgrading a system is about replacing old packages with new packages, which should be a reversible process (replace new packages with old ones). There's no inherent need to destroy anything during an upgrade, it's just that most systems we use don't really care about downgrading and don't support it (well).
– Georges Dupéron
Oct 8 '13 at 16:04
10
@GeorgesDupéron: you're right, there is no law of physics which would make downgrades impossible, so it is totally possible to build a tool which can upgrade/downgrade a system to any version. However, there's no such tool, so my answer stands for the real-life Ubuntu and its upgrade tools.
– Sergey
Oct 8 '13 at 20:42
add a comment |
There's a saying in my language which can be roughly translated as "You can't turn mince back into meat by rotating the mincer's handle in the opposite direction" :)
The upgrade procedure is one-way - while installing new versions of software, your configuration files and settings are modified by packages' post-install scripts to use new format which is required by new software. Basically, there's no opposite procedure - to make a newer configuration file compatible with old software.
There's a saying in my language which can be roughly translated as "You can't turn mince back into meat by rotating the mincer's handle in the opposite direction" :)
The upgrade procedure is one-way - while installing new versions of software, your configuration files and settings are modified by packages' post-install scripts to use new format which is required by new software. Basically, there's no opposite procedure - to make a newer configuration file compatible with old software.
edited Jun 10 '12 at 10:11
fossfreedom♦
149k37326372
149k37326372
answered Nov 10 '11 at 1:28
SergeySergey
36.2k98799
36.2k98799
9
I disagree, upgrading a system is about replacing old packages with new packages, which should be a reversible process (replace new packages with old ones). There's no inherent need to destroy anything during an upgrade, it's just that most systems we use don't really care about downgrading and don't support it (well).
– Georges Dupéron
Oct 8 '13 at 16:04
10
@GeorgesDupéron: you're right, there is no law of physics which would make downgrades impossible, so it is totally possible to build a tool which can upgrade/downgrade a system to any version. However, there's no such tool, so my answer stands for the real-life Ubuntu and its upgrade tools.
– Sergey
Oct 8 '13 at 20:42
add a comment |
9
I disagree, upgrading a system is about replacing old packages with new packages, which should be a reversible process (replace new packages with old ones). There's no inherent need to destroy anything during an upgrade, it's just that most systems we use don't really care about downgrading and don't support it (well).
– Georges Dupéron
Oct 8 '13 at 16:04
10
@GeorgesDupéron: you're right, there is no law of physics which would make downgrades impossible, so it is totally possible to build a tool which can upgrade/downgrade a system to any version. However, there's no such tool, so my answer stands for the real-life Ubuntu and its upgrade tools.
– Sergey
Oct 8 '13 at 20:42
9
9
I disagree, upgrading a system is about replacing old packages with new packages, which should be a reversible process (replace new packages with old ones). There's no inherent need to destroy anything during an upgrade, it's just that most systems we use don't really care about downgrading and don't support it (well).
– Georges Dupéron
Oct 8 '13 at 16:04
I disagree, upgrading a system is about replacing old packages with new packages, which should be a reversible process (replace new packages with old ones). There's no inherent need to destroy anything during an upgrade, it's just that most systems we use don't really care about downgrading and don't support it (well).
– Georges Dupéron
Oct 8 '13 at 16:04
10
10
@GeorgesDupéron: you're right, there is no law of physics which would make downgrades impossible, so it is totally possible to build a tool which can upgrade/downgrade a system to any version. However, there's no such tool, so my answer stands for the real-life Ubuntu and its upgrade tools.
– Sergey
Oct 8 '13 at 20:42
@GeorgesDupéron: you're right, there is no law of physics which would make downgrades impossible, so it is totally possible to build a tool which can upgrade/downgrade a system to any version. However, there's no such tool, so my answer stands for the real-life Ubuntu and its upgrade tools.
– Sergey
Oct 8 '13 at 20:42
add a comment |
It's possible at the level of the packaging tools (apt). But the resulting system may not be equivalent to doing a reinstall, and you may get errors along the way. This is because many packages contain specific support for upgrades (e.g. handling changes in configuration files) but not for downgrades.
Normally, apt prefers to install the most recent version of a package. But you can change this through pinning: you can declare that packages from the old release have higher priority than the installed packages, so that they will be downgrades when you do aptitude dist-upgrade
.
Change your /etc/apt/sources.list
to include only the old release (either edit the file or use your favorite GUI), and run aptitude update
. Then edit /etc/apt/preferences
(documented in the apt_preferences
man page) and add the following lines (to downgrade to lucid):
Package: *
Pin: release v=10.04
Pin-Priority: 1001
Then run aptitude dist-upgrade
. Every package has a priority greater than 1000, so every package that is present in 10.04 and installed on your system will be downgraded. You'll have to remove packages that weren't in 10.04 manually; they'll be listed under “Obsolete and locally created packages” in aptitude.
This helped me after running twicedo-release-upgrade
(as first call has hung). So I could revert apt lists to proper release.
– PeterM
Nov 22 '16 at 19:26
add a comment |
It's possible at the level of the packaging tools (apt). But the resulting system may not be equivalent to doing a reinstall, and you may get errors along the way. This is because many packages contain specific support for upgrades (e.g. handling changes in configuration files) but not for downgrades.
Normally, apt prefers to install the most recent version of a package. But you can change this through pinning: you can declare that packages from the old release have higher priority than the installed packages, so that they will be downgrades when you do aptitude dist-upgrade
.
Change your /etc/apt/sources.list
to include only the old release (either edit the file or use your favorite GUI), and run aptitude update
. Then edit /etc/apt/preferences
(documented in the apt_preferences
man page) and add the following lines (to downgrade to lucid):
Package: *
Pin: release v=10.04
Pin-Priority: 1001
Then run aptitude dist-upgrade
. Every package has a priority greater than 1000, so every package that is present in 10.04 and installed on your system will be downgraded. You'll have to remove packages that weren't in 10.04 manually; they'll be listed under “Obsolete and locally created packages” in aptitude.
This helped me after running twicedo-release-upgrade
(as first call has hung). So I could revert apt lists to proper release.
– PeterM
Nov 22 '16 at 19:26
add a comment |
It's possible at the level of the packaging tools (apt). But the resulting system may not be equivalent to doing a reinstall, and you may get errors along the way. This is because many packages contain specific support for upgrades (e.g. handling changes in configuration files) but not for downgrades.
Normally, apt prefers to install the most recent version of a package. But you can change this through pinning: you can declare that packages from the old release have higher priority than the installed packages, so that they will be downgrades when you do aptitude dist-upgrade
.
Change your /etc/apt/sources.list
to include only the old release (either edit the file or use your favorite GUI), and run aptitude update
. Then edit /etc/apt/preferences
(documented in the apt_preferences
man page) and add the following lines (to downgrade to lucid):
Package: *
Pin: release v=10.04
Pin-Priority: 1001
Then run aptitude dist-upgrade
. Every package has a priority greater than 1000, so every package that is present in 10.04 and installed on your system will be downgraded. You'll have to remove packages that weren't in 10.04 manually; they'll be listed under “Obsolete and locally created packages” in aptitude.
It's possible at the level of the packaging tools (apt). But the resulting system may not be equivalent to doing a reinstall, and you may get errors along the way. This is because many packages contain specific support for upgrades (e.g. handling changes in configuration files) but not for downgrades.
Normally, apt prefers to install the most recent version of a package. But you can change this through pinning: you can declare that packages from the old release have higher priority than the installed packages, so that they will be downgrades when you do aptitude dist-upgrade
.
Change your /etc/apt/sources.list
to include only the old release (either edit the file or use your favorite GUI), and run aptitude update
. Then edit /etc/apt/preferences
(documented in the apt_preferences
man page) and add the following lines (to downgrade to lucid):
Package: *
Pin: release v=10.04
Pin-Priority: 1001
Then run aptitude dist-upgrade
. Every package has a priority greater than 1000, so every package that is present in 10.04 and installed on your system will be downgraded. You'll have to remove packages that weren't in 10.04 manually; they'll be listed under “Obsolete and locally created packages” in aptitude.
edited Dec 1 '10 at 0:54
answered Sep 5 '10 at 16:13
GillesGilles
44.6k13100140
44.6k13100140
This helped me after running twicedo-release-upgrade
(as first call has hung). So I could revert apt lists to proper release.
– PeterM
Nov 22 '16 at 19:26
add a comment |
This helped me after running twicedo-release-upgrade
(as first call has hung). So I could revert apt lists to proper release.
– PeterM
Nov 22 '16 at 19:26
This helped me after running twice
do-release-upgrade
(as first call has hung). So I could revert apt lists to proper release.– PeterM
Nov 22 '16 at 19:26
This helped me after running twice
do-release-upgrade
(as first call has hung). So I could revert apt lists to proper release.– PeterM
Nov 22 '16 at 19:26
add a comment |
They say, "never say never", and "nothing is impossible" - both of which are true, but not in your case. I suggest you either back up your data and reinstall, or stick it out. The system should become more and more stable as the weeks go by.
You can also reinstall on top of the existing installation (it will keep your files).
As a rule of thumb though, try to avoid upgrading to development versions on production systems (especially if you are not a tester/developer).
add a comment |
They say, "never say never", and "nothing is impossible" - both of which are true, but not in your case. I suggest you either back up your data and reinstall, or stick it out. The system should become more and more stable as the weeks go by.
You can also reinstall on top of the existing installation (it will keep your files).
As a rule of thumb though, try to avoid upgrading to development versions on production systems (especially if you are not a tester/developer).
add a comment |
They say, "never say never", and "nothing is impossible" - both of which are true, but not in your case. I suggest you either back up your data and reinstall, or stick it out. The system should become more and more stable as the weeks go by.
You can also reinstall on top of the existing installation (it will keep your files).
As a rule of thumb though, try to avoid upgrading to development versions on production systems (especially if you are not a tester/developer).
They say, "never say never", and "nothing is impossible" - both of which are true, but not in your case. I suggest you either back up your data and reinstall, or stick it out. The system should become more and more stable as the weeks go by.
You can also reinstall on top of the existing installation (it will keep your files).
As a rule of thumb though, try to avoid upgrading to development versions on production systems (especially if you are not a tester/developer).
answered Jun 21 '11 at 15:30
RolandiXor♦RolandiXor
44.4k25140229
44.4k25140229
add a comment |
add a comment |
You can do it manually.
First generate a list of what you have installed on your system. You can do this by typing the following in the terminal.
sudo dpkg --get-selections | grep '[[:space:]]install$' | awk '{print $1}' > package_list
copy your /home and /etc folder to a backup media.
Re install ubuntu 10.04. Restore your backup (remember to set the correct premissions). Then run the following to reinstall all the program you had before.
cat package_list | xargs sudo apt-get install
Note that you might have to do some cleaning of the /etc and /home folder for incompatible settings.
add a comment |
You can do it manually.
First generate a list of what you have installed on your system. You can do this by typing the following in the terminal.
sudo dpkg --get-selections | grep '[[:space:]]install$' | awk '{print $1}' > package_list
copy your /home and /etc folder to a backup media.
Re install ubuntu 10.04. Restore your backup (remember to set the correct premissions). Then run the following to reinstall all the program you had before.
cat package_list | xargs sudo apt-get install
Note that you might have to do some cleaning of the /etc and /home folder for incompatible settings.
add a comment |
You can do it manually.
First generate a list of what you have installed on your system. You can do this by typing the following in the terminal.
sudo dpkg --get-selections | grep '[[:space:]]install$' | awk '{print $1}' > package_list
copy your /home and /etc folder to a backup media.
Re install ubuntu 10.04. Restore your backup (remember to set the correct premissions). Then run the following to reinstall all the program you had before.
cat package_list | xargs sudo apt-get install
Note that you might have to do some cleaning of the /etc and /home folder for incompatible settings.
You can do it manually.
First generate a list of what you have installed on your system. You can do this by typing the following in the terminal.
sudo dpkg --get-selections | grep '[[:space:]]install$' | awk '{print $1}' > package_list
copy your /home and /etc folder to a backup media.
Re install ubuntu 10.04. Restore your backup (remember to set the correct premissions). Then run the following to reinstall all the program you had before.
cat package_list | xargs sudo apt-get install
Note that you might have to do some cleaning of the /etc and /home folder for incompatible settings.
edited Aug 31 '13 at 21:01
LantzR
17414
17414
answered Sep 5 '10 at 14:54
user1362567user1362567
32612
32612
add a comment |
add a comment |
This is why you are not supposed to upgrade your main install to the development release. If you want to test the development release, you should do so on a separate partition so you can boot back into the stable release when things go wrong.
At this point if you want to go back to 11.04, you need to reinstall it, and choose manual partitioning. Do NOT check the format box when configuring your partitions and your user files should remain intact.
add a comment |
This is why you are not supposed to upgrade your main install to the development release. If you want to test the development release, you should do so on a separate partition so you can boot back into the stable release when things go wrong.
At this point if you want to go back to 11.04, you need to reinstall it, and choose manual partitioning. Do NOT check the format box when configuring your partitions and your user files should remain intact.
add a comment |
This is why you are not supposed to upgrade your main install to the development release. If you want to test the development release, you should do so on a separate partition so you can boot back into the stable release when things go wrong.
At this point if you want to go back to 11.04, you need to reinstall it, and choose manual partitioning. Do NOT check the format box when configuring your partitions and your user files should remain intact.
This is why you are not supposed to upgrade your main install to the development release. If you want to test the development release, you should do so on a separate partition so you can boot back into the stable release when things go wrong.
At this point if you want to go back to 11.04, you need to reinstall it, and choose manual partitioning. Do NOT check the format box when configuring your partitions and your user files should remain intact.
answered Jun 21 '11 at 22:32
psusipsusi
31k15088
31k15088
add a comment |
add a comment |
Simple method is booting up from a CD/DVD or USB stick of previous version and reinstall Ubuntu by overwriting existing installation.
Don't forget backup first: your home
directory any anywhere else you may have personal data.
2
Backup your files first ;)
– Achu
Feb 22 '12 at 18:26
add a comment |
Simple method is booting up from a CD/DVD or USB stick of previous version and reinstall Ubuntu by overwriting existing installation.
Don't forget backup first: your home
directory any anywhere else you may have personal data.
2
Backup your files first ;)
– Achu
Feb 22 '12 at 18:26
add a comment |
Simple method is booting up from a CD/DVD or USB stick of previous version and reinstall Ubuntu by overwriting existing installation.
Don't forget backup first: your home
directory any anywhere else you may have personal data.
Simple method is booting up from a CD/DVD or USB stick of previous version and reinstall Ubuntu by overwriting existing installation.
Don't forget backup first: your home
directory any anywhere else you may have personal data.
edited Mar 28 '13 at 10:57
Warren Hill
15.4k165376
15.4k165376
answered Feb 22 '12 at 18:22
swiftswift
2,95621743
2,95621743
2
Backup your files first ;)
– Achu
Feb 22 '12 at 18:26
add a comment |
2
Backup your files first ;)
– Achu
Feb 22 '12 at 18:26
2
2
Backup your files first ;)
– Achu
Feb 22 '12 at 18:26
Backup your files first ;)
– Achu
Feb 22 '12 at 18:26
add a comment |
Roll-backs may work fine for certain packages in isolation, but I wouldn't ever expect a large-scale roll-back of an entire distribution to leave you with anything other than a horribly broken system (or one which, on the surface looks to be fine, but strange things keep surfacing as you discover it is more and more broken).
APT is just designed to avoid roll-backs as much as possible, and the packages that make up the Ubuntu (and Debian, for that matter) distribution aren't designed with smooth roll-backs as a design goal.
Unless you have whole-system backups that are reliable, what you really need to do is ensure your entire home directory is backed up (and possibly also on a separate partition), re-install from the CD image of your chosen version, and start restoring your data from your home folder(s). You may even need to selectively restore the dotfiles in your home directory in case any which have become accustomed to the new version don't quite work well with the older version.
Before you do, you may want to peruse your installed packages and write down which ones you rely on, so you can re-install them. There are tools to backup and restore your list of installed packages, but I wouldn't normally recommend doing this if you are going between versions as the packages needed/included may have changed.
add a comment |
Roll-backs may work fine for certain packages in isolation, but I wouldn't ever expect a large-scale roll-back of an entire distribution to leave you with anything other than a horribly broken system (or one which, on the surface looks to be fine, but strange things keep surfacing as you discover it is more and more broken).
APT is just designed to avoid roll-backs as much as possible, and the packages that make up the Ubuntu (and Debian, for that matter) distribution aren't designed with smooth roll-backs as a design goal.
Unless you have whole-system backups that are reliable, what you really need to do is ensure your entire home directory is backed up (and possibly also on a separate partition), re-install from the CD image of your chosen version, and start restoring your data from your home folder(s). You may even need to selectively restore the dotfiles in your home directory in case any which have become accustomed to the new version don't quite work well with the older version.
Before you do, you may want to peruse your installed packages and write down which ones you rely on, so you can re-install them. There are tools to backup and restore your list of installed packages, but I wouldn't normally recommend doing this if you are going between versions as the packages needed/included may have changed.
add a comment |
Roll-backs may work fine for certain packages in isolation, but I wouldn't ever expect a large-scale roll-back of an entire distribution to leave you with anything other than a horribly broken system (or one which, on the surface looks to be fine, but strange things keep surfacing as you discover it is more and more broken).
APT is just designed to avoid roll-backs as much as possible, and the packages that make up the Ubuntu (and Debian, for that matter) distribution aren't designed with smooth roll-backs as a design goal.
Unless you have whole-system backups that are reliable, what you really need to do is ensure your entire home directory is backed up (and possibly also on a separate partition), re-install from the CD image of your chosen version, and start restoring your data from your home folder(s). You may even need to selectively restore the dotfiles in your home directory in case any which have become accustomed to the new version don't quite work well with the older version.
Before you do, you may want to peruse your installed packages and write down which ones you rely on, so you can re-install them. There are tools to backup and restore your list of installed packages, but I wouldn't normally recommend doing this if you are going between versions as the packages needed/included may have changed.
Roll-backs may work fine for certain packages in isolation, but I wouldn't ever expect a large-scale roll-back of an entire distribution to leave you with anything other than a horribly broken system (or one which, on the surface looks to be fine, but strange things keep surfacing as you discover it is more and more broken).
APT is just designed to avoid roll-backs as much as possible, and the packages that make up the Ubuntu (and Debian, for that matter) distribution aren't designed with smooth roll-backs as a design goal.
Unless you have whole-system backups that are reliable, what you really need to do is ensure your entire home directory is backed up (and possibly also on a separate partition), re-install from the CD image of your chosen version, and start restoring your data from your home folder(s). You may even need to selectively restore the dotfiles in your home directory in case any which have become accustomed to the new version don't quite work well with the older version.
Before you do, you may want to peruse your installed packages and write down which ones you rely on, so you can re-install them. There are tools to backup and restore your list of installed packages, but I wouldn't normally recommend doing this if you are going between versions as the packages needed/included may have changed.
answered May 24 '12 at 6:40
thomasrutterthomasrutter
26.5k46389
26.5k46389
add a comment |
add a comment |
To put it simply: no there's not. Sorry... (These are the dangers of upgrading to testing releases!)
2
Had I been aware that Ubuntu has crippled the Netbook Remix as horribly as they did before hand, I would not have done the upgrade at all. Re-installing is not a major issue, but I though the question was worth the effort of posting it.
– Diago
Sep 5 '10 at 16:52
@Diago Just out of curiosity is this a complete dislike of the new interface? Or simply a belief it's not finished yet?
– 8128
Sep 5 '10 at 19:26
A bit of both. I am frustrated by the lack of usability from a non technical user perspective. I can find my way around and install additional software to get functionality, but fail to see how a complete novice will survive. I believe it needs a lot more work if they plan to meet the October deadline.
– Diago
Sep 5 '10 at 19:33
add a comment |
To put it simply: no there's not. Sorry... (These are the dangers of upgrading to testing releases!)
2
Had I been aware that Ubuntu has crippled the Netbook Remix as horribly as they did before hand, I would not have done the upgrade at all. Re-installing is not a major issue, but I though the question was worth the effort of posting it.
– Diago
Sep 5 '10 at 16:52
@Diago Just out of curiosity is this a complete dislike of the new interface? Or simply a belief it's not finished yet?
– 8128
Sep 5 '10 at 19:26
A bit of both. I am frustrated by the lack of usability from a non technical user perspective. I can find my way around and install additional software to get functionality, but fail to see how a complete novice will survive. I believe it needs a lot more work if they plan to meet the October deadline.
– Diago
Sep 5 '10 at 19:33
add a comment |
To put it simply: no there's not. Sorry... (These are the dangers of upgrading to testing releases!)
To put it simply: no there's not. Sorry... (These are the dangers of upgrading to testing releases!)
edited Sep 5 '10 at 11:28
answered Sep 5 '10 at 11:22
81288128
24.8k21100137
24.8k21100137
2
Had I been aware that Ubuntu has crippled the Netbook Remix as horribly as they did before hand, I would not have done the upgrade at all. Re-installing is not a major issue, but I though the question was worth the effort of posting it.
– Diago
Sep 5 '10 at 16:52
@Diago Just out of curiosity is this a complete dislike of the new interface? Or simply a belief it's not finished yet?
– 8128
Sep 5 '10 at 19:26
A bit of both. I am frustrated by the lack of usability from a non technical user perspective. I can find my way around and install additional software to get functionality, but fail to see how a complete novice will survive. I believe it needs a lot more work if they plan to meet the October deadline.
– Diago
Sep 5 '10 at 19:33
add a comment |
2
Had I been aware that Ubuntu has crippled the Netbook Remix as horribly as they did before hand, I would not have done the upgrade at all. Re-installing is not a major issue, but I though the question was worth the effort of posting it.
– Diago
Sep 5 '10 at 16:52
@Diago Just out of curiosity is this a complete dislike of the new interface? Or simply a belief it's not finished yet?
– 8128
Sep 5 '10 at 19:26
A bit of both. I am frustrated by the lack of usability from a non technical user perspective. I can find my way around and install additional software to get functionality, but fail to see how a complete novice will survive. I believe it needs a lot more work if they plan to meet the October deadline.
– Diago
Sep 5 '10 at 19:33
2
2
Had I been aware that Ubuntu has crippled the Netbook Remix as horribly as they did before hand, I would not have done the upgrade at all. Re-installing is not a major issue, but I though the question was worth the effort of posting it.
– Diago
Sep 5 '10 at 16:52
Had I been aware that Ubuntu has crippled the Netbook Remix as horribly as they did before hand, I would not have done the upgrade at all. Re-installing is not a major issue, but I though the question was worth the effort of posting it.
– Diago
Sep 5 '10 at 16:52
@Diago Just out of curiosity is this a complete dislike of the new interface? Or simply a belief it's not finished yet?
– 8128
Sep 5 '10 at 19:26
@Diago Just out of curiosity is this a complete dislike of the new interface? Or simply a belief it's not finished yet?
– 8128
Sep 5 '10 at 19:26
A bit of both. I am frustrated by the lack of usability from a non technical user perspective. I can find my way around and install additional software to get functionality, but fail to see how a complete novice will survive. I believe it needs a lot more work if they plan to meet the October deadline.
– Diago
Sep 5 '10 at 19:33
A bit of both. I am frustrated by the lack of usability from a non technical user perspective. I can find my way around and install additional software to get functionality, but fail to see how a complete novice will survive. I believe it needs a lot more work if they plan to meet the October deadline.
– Diago
Sep 5 '10 at 19:33
add a comment |
protected by Community♦ Nov 4 '11 at 13:14
Thank you for your interest in this question.
Because it has attracted low-quality or spam answers that had to be removed, posting an answer now requires 10 reputation on this site (the association bonus does not count).
Would you like to answer one of these unanswered questions instead?
2
Here is one on ubuntu wiki.
– Quazi Irfan
Nov 29 '13 at 12:45
This is one of the reasons why one would really want this to happen and be successful: Revisiting How We Put Together Linux Systems. Booting another operating system or release from the same filesystem? It could be a problem of the past.
– LiveWireBT
Dec 16 '14 at 16:46