HOWTO:Upgrade 2009 to 2011 with upgrade manager
(→Upgrade Pardus 2009 to latest Pardus 2011) |
|||
| Line 1: | Line 1: | ||
== Upgrade Pardus 2009 to latest Pardus 2011 == | == Upgrade Pardus 2009 to latest Pardus 2011 == | ||
| − | An '''Upgrade Manager''' have been released just after Pardus 2011.1 Dama dama. | + | An '''Upgrade Manager''' have been released just after Pardus 2011.1 Dama dama. The 2009 specific tool can be found in 2009 repository and only works for users who wants to upgrade and use 2011 without a fresh install. |
A reminder: As Pardus 2009 was released only 32bit, it would not be possible to upgrade to an 64bit installation. Users who wants to use 64bit 2011 release should go for a fresh install. | A reminder: As Pardus 2009 was released only 32bit, it would not be possible to upgrade to an 64bit installation. Users who wants to use 64bit 2011 release should go for a fresh install. | ||
Revision as of 07:54, 19 August 2011
Upgrade Pardus 2009 to latest Pardus 2011
An Upgrade Manager have been released just after Pardus 2011.1 Dama dama. The 2009 specific tool can be found in 2009 repository and only works for users who wants to upgrade and use 2011 without a fresh install.
A reminder: As Pardus 2009 was released only 32bit, it would not be possible to upgrade to an 64bit installation. Users who wants to use 64bit 2011 release should go for a fresh install.
How it works?
If you are using Pardus 2009 (or any minor release, i.e. 2009.1 or 2009.2) you may find the upgrade manager in the repository after you check the updates.
As it needs root user privileges, you'll be asked for the root password as the first step.
As you enter the password, welcome screen will appear as below. It briefly tells what this tool will be doing and wait for you to hit the Next button.
In the third step, you will be asked for your choice of repository. Specially for the end users, it is highly recommended to use the stable depo. However, for contributors, testers or power users testing and devel repositories are available.
If you are using a custom repository of your own, you may enter your repository address manually.
As you choose your repository upgrade manager checks if your system has enough disk space for the packages.
In the next step, if there are any installed packages which won't be available on 2011, a warning will appear. In the screenshot, four packages can be seen as an example. Upgrade Manager suggests you to remove the packages before updating the system.
You will be asked for the last time as the configuration is complete.
Unavailable packages are removed.
Packages are upgraded as well as new PiSi.
New package index is built.
New packages will be downloaded, installed and configured in the last stage. If you happen to have an installation medium, copying the PiSi packages to /var/cache/pisi/packages destination may reduce the amount to be downloaded.
As August 2011, the application supports English and Turkish.
