Differences between revisions 6 and 24 (spanning 18 versions)
Revision 6 as of 2008-10-02 11:44:44
Size: 2297
Comment:
Revision 24 as of 2009-03-21 11:40:03
Size: 3475
Editor: FranklinPiat
Comment: update Debian "official material" banner
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 7: Line 16:
||<tablewidth="100%" tablestyle=""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 DebianLenny Release notes ~-[[BR]]. http://www.debian.org/releases/stable/i386/release-notes/ -~ || {{{#!wiki debian
http://www.debian.org/releases/stable/releasenotes - Debian Lenny Release notes
}}}
Line 10: Line 22:
== License ==
 * This page is licensed under [:GPL:GPL v2], or later.
## http://www.debian.org/releases/stable/i386/release-notes/ch-whats-new.html
CategoryPermalink
== Quick steps ==
Line 15: Line 24:
=== If you use Backports ===
In general, backports.org only has backports made from testing but with reduced version numbers (apt considers ~ lower than -), 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).
'''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 [[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.

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).
Line 20: Line 38:
For instance, as of 02082008, the trac package in backports has version For example, the trac package in backports.org has version
Line 28: Line 46:
0.11.1-2 0.11.1-2.1
Line 30: Line 48:
As 0.11.1-2~bpo40+1 < 0.11.1-2 in debian versioning, the backports package will be replaced by the lenny package when you update to lenny. 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.
Line 32: Line 50:
This behaviour has been confirmed by the backports team in this [http://lists.backports.org/lurker-bpo/message/20080930.090902.0f29d785.en.html mail]. 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 34: Line 52:
If you use backports, but does not upgrade to ''Lenny'' immediatly 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 build based on testing, and testing will change fron 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 backport people 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.
}}}

== License ==
##Since the content can be merged into the release notes :
 * This page is licensed under [[GPL|GPL v2]].
----
## This page is referenced from
## http://www.debian.org/releases/lenny/i386/release-notes/ch-whats-new.html
CategoryPermalink

Debian Lenny > Etch to Lenny Upgrade


Upgrading Debian GNU/Linux from Etch (4.0) to Lenny (5.0)

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.

  • {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.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.


CategoryPermalink