Differences between revisions 5 and 6
Revision 5 as of 2008-10-02 11:37:48
Size: 1991
Comment: Add notes concerning the use of backports.org
Revision 6 as of 2008-10-02 11:44:44
Size: 2297
Comment:
Deletions are marked like this. Additions are marked like this.
Line 3: Line 3:
Line 6: Line 7:
||<tablestyle="width:100%;" style="width:32px;border-color:#ff9ec2" >inline:Portal/IDB/official-doc.png||<style="border-color:#ff9ec2;background-color:#ffe4f1" >Debian [:DebianLenny:Lenny] Release notes ~-[[BR]]. http://www.debian.org/releases/stable/i386/release-notes/ -~ ||
||<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/ -~ ||
Line 9: Line 9:
Line 13: Line 12:
Line 18: Line 16:
Line 23: Line 20:
For instance, as of 02082008, the trac package in backports has version

{{{
0.11.1-2~bpo40+1
}}}
and in lenny

{{{
0.11.1-2
}}}
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.
Line 25: Line 34:

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
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

[:DebianLenny:Debian Lenny] > Etch to Lenny Upgrade


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

attachment:Portal/IDB/official-doc.png

Debian DebianLenny Release notes ?BR. http://www.debian.org/releases/stable/i386/release-notes/

This page is a placeholder for future (semi-official) contents.

License

  • This page is licensed under [:GPL:GPL v2], or later.

CategoryPermalink

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).

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 instance, as of 02082008, the trac package in backports has version

0.11.1-2~bpo40+1

and in lenny

0.11.1-2

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.

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 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