|
Size: 3659
Comment:
|
Size: 3646
Comment: converted to 1.6 markup
|
| Deletions are marked like this. | Additions are marked like this. |
| Line 2: | Line 2: |
| [:DebianLenny:Debian Lenny] > Etch to Lenny Upgrade | ## ## ## ## ## DO NOT DUPLICATE THE RELEASE NOTES HERE ! (send contributions on debian-doc ML). ## ## ## ## ## [[DebianLenny|Debian Lenny]] > Etch to Lenny Upgrade |
| Line 4: | Line 14: |
| Line 5: | Line 16: |
| == Release Notes == First you should read the Lenny release notes (this link is for i386): [http://www.debian.org/releases/stable/i386/release-notes/] - this has exhaustive and official documentation on how to upgrade and the change log. For most users, this quick guide will suffice. If you are on a production system, you should probably read the official documentation instead of this. == Sources == Edit your {{{/etc/apt/sources.list }}} and replace any instance of {{{etch}}} with {{{lenny}}}. Here's an example {{{sources.list}}}: {{{ #Main deb http://ftp.us.debian.org/debian/ lenny main contrib non-free deb-src http://ftp.us.debian.org/debian/ lenny main contrib non-free |
||<tablewidth="100%"width="32px" style="border-color: rgb(255, 158, 194);"> {{attachment:Portal/IDB/official-doc.png}} ||<bgcolor="#ffe4f1" style="border-color: rgb(255, 158, 194);">Debian Lenny Release notes ~-<<BR>>. http://www.debian.org/releases/stable/releasenotes -~ || ''This page is a placeholder for future (semi-official) contents.'' |
| Line 15: | Line 19: |
| #Updates deb http://security.debian.org/ lenny/updates main contrib non-free deb-src http://security.debian.org/ lenny/updates main contrib non-free }}} |
== Quick steps == |
| Line 20: | Line 21: |
| === testing === Note that some of you may have been on '''testing''' which would have been '''lenny''' while it was in development. If you have such a system and you upgraded, you are now on testing for '''squeeze''', or '''lenny +1'''. === stable === If in your {{{sources.list}}} you had '''stable''' then when you upgrade you will move to the '''stable''' distribution, or '''lenny'''. Here is the {{{sources.list}}} that is distributed with Lenny (for i386), in case you need a reference: == Upgrading == Run:{{{ apt-get update apt-get dist-upgrade}}} |
'''RTFM''' (__Read__ the Fine Manual) : it contains important information ! |
| Line 30: | Line 23: |
| Once that process is finished, you will be running Lenny. === Notes on Backports === [:Backports:Backports.org] is a semi-official repository provided by Debian Developers, which provides newer packages for the stable release, based on a rebuild of the package from the "testing" archive. |
Before upgrading to Lenny, make sure you read the paragraph ''Upgrades from previous releases'' and also have a look at ''Issues to be aware of for lenny'' of the [[http://www.debian.org/releases/stable/releasenotes|releasenotes]]. {i} Yes, this is the quick steps. anything shorter/faster may leave your system in broken state. == Notes on /etc/apt/sources.list == === Backports === [[Backports|Backports.org]] is a semi-official repository provided by Debian Developers, which provides newer packages for the stable release, based on a rebuild of the package from the "testing" archive. |
| Line 50: | Line 47: |
| If you use backports, but does not upgrade to ''Lenny'' immediately after ''Lenny'' is released, you should disable backports.org entries in your sources.list, if you don't want to get packages from ''Squeeze''. This can happen because backports are built based on testing, and testing will change from lenny to squeeze as soon as Lenny is released. This issue is discussed in [http://lists.debian.org/debian-isp/2008/09/msg00046.html this thread] on the debian-isp mailing list. ''TBD: confirm or infirm this from backports.org'' | If you use backports, but does not upgrade to ''Lenny'' immediately after ''Lenny'' is released, you should disable backports.org entries in your sources.list, if you don't want to get packages from ''Squeeze''. This can happen because backports are built based on testing, and testing will change from lenny to squeeze as soon as Lenny is released. This issue is discussed in [[http://lists.debian.org/debian-isp/2008/09/msg00046.html|this thread]] on the debian-isp mailing list. ''TBD: confirm or infirm this from backports.org'' |
| Line 52: | Line 49: |
| This behaviour has been confirmed by the backports team in this[http://lists.backports.org/lurker-bpo/message/20080930.090902.0f29d785.en.html mail]. | This behaviour has been confirmed by the backports team in this[[http://lists.backports.org/lurker-bpo/message/20080930.090902.0f29d785.en.html|mail]]. === Sample sources.list === Here is a typical {{{sources.list}}} as it is configured with Lenny, in case you need a reference: {{{ # Main deb http://ftp.us.debian.org/debian/ lenny main contrib non-free deb-src http://ftp.us.debian.org/debian/ lenny main contrib non-free # Security Updates deb http://security.debian.org/ lenny/updates main contrib non-free deb-src http://security.debian.org/ lenny/updates main contrib non-free # Some systems may have other entries, like the "volatile" service. }}} |
| Line 56: | Line 68: |
| * This page is licensed under [:GPL:GPL v2]. | * This page is licensed under [[GPL|GPL v2]]. |
Debian Lenny > Etch to Lenny Upgrade
Upgrading Debian GNU/Linux from Etch (4.0) to Lenny (5.0)
|
Debian Lenny Release notes |
This page is a placeholder for future (semi-official) contents.
Quick steps
RTFM (Read the Fine Manual) : it contains important information !
Before upgrading to Lenny, make sure you read the paragraph Upgrades from previous releases and also have a look at Issues to be aware of for lenny of the releasenotes.
Yes, this is the quick steps. anything shorter/faster may leave your system in broken state.
Notes on /etc/apt/sources.list
Backports
Backports.org is a semi-official repository provided by Debian Developers, which provides newer packages for the stable release, based on a rebuild of the package from the "testing" archive.
The backports.org repository contains packages from testing, but with reduced version numbers, therefore the upgrade path from etch-backports to lenny is saved. However, there are a few backports only which are made from unstable (security updates and the following exceptions: firefox, kernel, openoffice.org, xorg).
If you do not use one of these exceptions, you can safely upgrade to lenny. If you use one of these exceptions, set the pin-priority (see man apt_preferences) temporarily to 1001 for all packages from etch, and you should be able to do a safe dist-upgrade too.
For example, the trac package in backports.org has version
0.11.1-2~bpo40+1
and in lenny
0.11.1-2.1
As 0.11.1-2~bpo40+1 < 0.11.1-2.1 (apt considers ~ lower), the backports package will be replaced by the lenny package when you upgrate to lenny.
If you use backports, but does not upgrade to Lenny immediately after Lenny is released, you should disable backports.org entries in your sources.list, if you don't want to get packages from Squeeze. This can happen because backports are built based on testing, and testing will change from lenny to squeeze as soon as Lenny is released. This issue is discussed in this thread on the debian-isp mailing list. TBD: confirm or infirm this from backports.org
This behaviour has been confirmed by the backports team in thismail.
Sample sources.list
Here is a typical sources.list as it is configured with Lenny, in case you need a reference:
# Main deb http://ftp.us.debian.org/debian/ lenny main contrib non-free deb-src http://ftp.us.debian.org/debian/ lenny main contrib non-free # Security Updates deb http://security.debian.org/ lenny/updates main contrib non-free deb-src http://security.debian.org/ lenny/updates main contrib non-free # Some systems may have other entries, like the "volatile" service.
License
This page is licensed under GPL v2.