[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Bug#507118: marked as done (release-notes: Document use of backports.org packages during upgrade ( proposed text included ))

Your message dated Wed, 25 Feb 2009 16:20:07 +0100
with message-id <20090225152007.GH1980@dedibox.ebzao.info>
and subject line Closing "pending" Lenny release-notes bugs
has caused the Debian Bug report #507118,
regarding release-notes: Document use of backports.org packages during upgrade ( proposed text included )
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact owner@bugs.debian.org
immediately.)


-- 
507118: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=507118
Debian Bug Tracking System
Contact owner@bugs.debian.org with problems
--- Begin Message --- 
Package: release-notes
Severity: normal


As backports.org is now semi official ( ie links from the packages web
interface ) I propose to document properly how to deal with the
backported packages when doing a etch2lenny upgrade.

This text should go in the userbackports section of the release note
and is a rewording of http://backports.org/dokuwiki/doku.php?id=faq.

Backports.org is a semi-official repository provided by debian
developpers, which provides newer packages for the stable release,
based on a rebuild from the packages 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.

-- System Information:
Debian Release: lenny/sid
  APT prefers testing
  APT policy: (500, 'testing')
Architecture: i386 (i686)

Kernel: Linux 2.6.26-1-686 (SMP w/1 CPU core)
Locale: LANG=fr_FR.UTF-8, LC_CTYPE=fr_FR.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/bash

--- End Message ---
--- Begin Message --- 
On Wed, Feb 25, 2009 at 01:31:39PM +0100, W. Martin Borgert wrote:
> Quoting "Simon Paillard" <simon.paillard@resel.enst-bretagne.fr>:
>> Can we :
>> - asssume all pending bugs have been commited to SVN ?
>
> Yes.

Closing Lenny release-notes pending bugs, since the relevant patches have been
commited to SVN trunk and are published on line at
http://debian.org/releases/lenny/releasenotes

Sorry for the mass mail.

-- 
Simon Paillard

--- End Message ---
Reply to: