UbuntuBackports

Differences between revisions 18 and 19
Revision 18 as of 2006-05-18 17:45:19
Size: 4445
Editor: cpc3-cwma2-0-0-cust739
Comment:
Revision 19 as of 2006-06-08 13:30:43
Size: 4429
Editor: binx
Comment: Cleaned up some grammar
Deletions are marked like this. Additions are marked like this.
Line 47: Line 47:
 1. Backports of large, interdepending applications stacks are bad!
 1. New versions can be backported, when they're compatible with already OS and System relevant libraries.
 1. No new libraries, which will "break" or better say, affecting other applications (e.g. libvorbis, libz etc.) unless the update fixes an exploit.
 1. Backports of large, interdepending application stacks are bad!
 1. New versions can be backported, when they're already compatible with OS and system-relevant libraries.
 1. No new libraries which will "break" or affect other applications (e.g. libvorbis, libz, etc.) unless the update fixes an exploit.

What are Backports

Ubuntu releases a new version of its OS every 6 months. After a release, the version of all packages stays constant for the entire 6 months. For example, if Hoary ships with Firefox 1.0.1, Hoary will remain at Firefox 1.0.1 for the entire 6-month release cycle, even if 1.0.2, 1.0.3, or 1.0.4 gets released during this time. The Ubuntu team may apply important security fixes to 1.0.1, but any new features or non-security bugfixes won't be made available to Hoary.

This is where Ubuntu Backports comes in. The Backports team believes that the best update policy is a mix of Ubuntu's security-only policy AND providing new versions of some programs. Candidates for version updates are primarily desktop applications, such as your web browser, word processor, IRC client, IM client, and so on. These can be updated without replacing a chunk of the operating system that would affect stability of the whole system.

Backports also include an extras repository which holds some packages which are not found in the official package collections. These include mainly legally-risky packages, for example many multimedia formats which are patent protected or some freeware commercial programs like the Adobe Acrobat Reader or Sun's Java Runtime Enviroment/Development Kit which are protected by a strict EULA.

As of June 2005, we are also an official Ubuntu project, so we are acknowledged by the developers.

Stability

The new official backports currently do not receive testing (unlike the old unofficial backports). The stability of the packages should be the same as that of the Ubuntu unstable distribution (currently Breezy Badger). If you have problems with one package please report it in the [https://launchpad.net/products/ubp-hoary/+filebug Ubuntu community bugtracker] and not the official Bugtracker.

How to use

Command Line Interface

Just add the following lines to your /etc/apt/sources.list :

For Hoary Hedgehog 5.04:BR deb http://archive.ubuntu.com/ubuntu hoary-backports main universe multiverse restricted

For Breezy Badger 5.10:BR deb http://archive.ubuntu.com/ubuntu breezy-backports main universe multiverse restricted

Now issue the command: sudo apt-get update

Through Synaptic Package Manager

Using the directions on the [https://wiki.ubuntu.com/AddingRepositoriesHowto How To Add Repositories Page]; and the following information for each section:

For Hoary Hedgehog 5.04: {{{url: http://archive.ubuntu.com/ubuntu distribution: hoary-backports sections: main universe multiverse restricted }}}

For Breezy Badger 5.10: {{{url: http://archive.ubuntu.com/ubuntu distribution: breezy-backports sections: main universe multiverse restricted }}}

How to request new packages

When you need a package backported which isn't currently create a new bug report in the Breezy Backports Product of Launchpad using this link [https://launchpad.net/products/breezy-backports/+filebug]. Choose a good summary that will quickly indicate what's need (e.g. "Please backport Bittornado"). Indicate the current Breezy version of the package and version being requested. If you've checked, indicate if the requested version has entered Dapper to make our lives easier!

These are the rules we try to follow when backporting packages:

  1. Only packages currently in Ubuntu's development branches are eligible for backporting
  2. Backports of large, interdepending application stacks are bad!
  3. New versions can be backported, when they're already compatible with OS and system-relevant libraries.
  4. No new libraries which will "break" or affect other applications (e.g. libvorbis, libz, etc.) unless the update fixes an exploit.
  5. No changes to language interpreters (python, mono). These could affect existing packages in unexpected ways.
  6. Applications to be backported must have meaningful bug/security fixes or features.

How to Help

TODO

Useful Links


CategoryUbuntuTeams CategoryDocumentation CategoryCleanup

UbuntuBackports (last edited 2023-12-07 14:33:47 by ddstreet)