Debian Admin - Your way to Debian World

April 8, 2007

Upgrade Debian Sarge to Debian Etch

by @ 5:32 pm. Filed under General

If you're new here, you may want to subscribe to my RSS feed. Thanks for visiting!

Before upgrading your system, it is strongly recommended that you make a full backup, or at least back up any data or configuration information you can’t afford to lose. The upgrade tools and process are quite reliable, but a hardware failure in the middle of an upgrade could result in a severely damaged system

The main things you’ll want to back up are the contents of /etc, /var/lib/dpkg and the output of dpkg --get-selections “*” (the quotes are important).

The upgrade process itself does not modify anything in the /home directory. However, some applications (e.g. parts of the Mozilla suite, and the GNOME and KDE desktop environments) are known to overwrite existing user settings with new defaults when a new version of the application is first started by a user. As a precaution, you may want to make a backup of the hidden files and directories (”dotfiles”) in users’ home directories. This backup may help to restore or recreate the old settings. You may also want to inform users about this.

Any package installation operation must be run with superuser privileges, so either login as root or use su or sudo to gain the necessary access rights.

Unofficial sources and backports

If you have any non-Debian packages on your system, you should be aware that these may be removed during the upgrade because of conflicting dependencies. If these packages were installed by adding an extra package archive in your /etc/apt/sources.list, you should check if that archive also offers packages compiled for etch and change the source line accordingly at the same time as your source lines for Debian packages.

Adding APT sources

The default configuration is set up for installation from main Debian Internet servers, but you may wish to modify /etc/apt/sources.list to use other mirrors, preferably a mirror that is network-wise closest to you.

For example, suppose your closest Debian mirror is http://mirrors.kernel.org/debian/. When inspecting that mirror with a web browser or FTP program, you will notice that the main directories are organized like this:

http://mirrors.kernel.org/debian/dists/etch/main/binary-i386/…
http://mirrors.kernel.org/debian/dists/etch/contrib/binary-i386/…

To use this mirror with apt, you add this line to your sources.list file

deb http://mirrors.kernel.org/debian etch main contrib

Note that the `dists’ is added implicitly, and the arguments after the release name are used to expand the path into multiple directories.

After adding your new sources, disable the previously existing “deb” lines in sources.list by placing a hash sign (#) in front of them.

Upgrading packages

The recommended way to upgrade from previous Debian GNU/Linux releases is to use the package management tool aptitude. This program makes safer decisions about package installations than running apt-get directly.

Next you should double-check that the APT source entries (in /etc/apt/sources.list) refer either to “etch” or to “stable”. There should not be any sources entries pointing to sarge. Note: source lines for a CD-ROM will often refer to “unstable”; although this may be confusing, you should not change it.

Once you’ve updated your sources.list in /etc/apt you can upgrade from Sarge to Etch by running:

# apt-get update

# apt-get install aptitude

# aptitude -f --with-recommends dist-upgrade

Tags: , ,

You may also be interested in...

5 Responses to “Upgrade Debian Sarge to Debian Etch”

  1. tiyun.de Says:

    ab nach Etch…

    Ich werde noch ein bisschen Zeit vergehen lassen bis der Rootie auf Etch gesetzt wird. Sobald genug Leute im Sycp-Forum positive Erfahrung gemacht haben, wird das in Angriff genommen. Vorher gucke ich dann nochmal über diese kleine Checkliste, der Di…

  2. Azar Says:

    Burning Question:
    Should we dist-upgrade to etch while still using the 2.6.8 kernel from sarge, or after changing the sources.list to “etch” we should first install the 2.6.18 kernel?

    Or immediately after dist-upgrade upgrade the kernel to 2.6.18?

    What is the safer way to do it?

  3. Admin Says:

    i would suggest use dist-upgrade it will install all the available upgrades

  4. Hans Ekbrand Says:

    Azar: see the release notes about the safest way to upgrade.

    Admin: 1. using “stable” instead of “etch” in sources.list saves you from having to change sources.list with each new release.
    2. Why do recommend using –with-recommends? I think with or without recommends is a personal preference that does not make the upgrade better or worse.
    3. The release notes recommends that the upgrade is done in several steps, not a simple aptitude -f dist-upgrade.

  5. Jason Says:

    Why are you recommending using “–with-recommends” ? That has the potential to pull in a HUGE amount of unnecessary packages rather than just upgrading the ones that are installed.

Leave a Reply

Subscribe RSS Feed

subscribe to the Debian Admin RSS feed

Internal links:

Sponsors:



Categories:

Support Debian Admin

Amount $:
Website(Optional):

Sponsors:

Archives:

Related Links:


Favourite Sites:

Wordpress Collection
Windows Reference
Ubuntu Geek
DebianHelp
All About Debian Tutorials
Power Electrical
Check Your IP Here
Debian,Ubuntu News
DebCentral
Tuxmachines
Capnkirby
Libervis
Nuxifield
Linux Horizon
Linux Appfinder
Debuntu
GNU/Linux For Everyone
Free Penguin
DebianAdmin is not related to the Debian Project.
This site is copyright © 2006,2007 Debian Admin
All Trademarks are the property of their respective owners.
The contents of this website may not be mirrored or archived without the express written permission of DebianAdmin Site Owner.

DISCLAIMER: All the information, troubleshooting methods, utilities offered in this website is provided AS-IS, without any warranties. Though I strive for perfection, and always test the validity and effectiveness of the troubleshooting content in various systems, I assume no responsibility for your use of these Fixes, Utilities and other troubleshooting advice. The author will not be liable for any special, incidental, consequential or indirect damages due to loss of data or any other reason. All use is completely at your own risk. Changes to the existing content and new additions are made to this website periodically, without notification.
Rodney's Kontera DynamiContext Plugin plugged in.