Backports

Revision 10 as of 2016-05-23 19:28:02

Clear message

UbuntuStudio/BackportsList - List of applications that are to be backported. UbuntuStudio/BackportsHowToHelp - Older howto on backporting

What is backporting?

Backporting means adding an application from a newer release to an older release of Ubuntu.

When to do a backport?

When wanting to add new features to an older release, you may backport an application. Backporting is not done when wanting to fix a bug. In the case where you want to fix a bug, do a SRU (Stable Release Update) instead.

How to Backport

Claim the task

Go to UbuntuStudio/BackportsList and look for a package on the list that needs backporting. Double check the latest version in the development release by visiting launchpad using the link in the table. There may be a new version since the package was last backported.

Claim a backport by putting yourself in the Responsible column, and putting the status to "not started".

Remember that unless there is a good reason, the backport should be to any LTS reelase that we are still supporting.

Do the bug report

Use the commandline tool requestbackport.

For example:

requestbackport -s saucy -d raring ardour3

As the default source of the backport is the current development release, you can drop the -s option. The destination (-d) should be the oldest LTS release we are supporting. A task will be created in the bug for any intermediate releases.

The first time you do this, you might need to authorise the requestbackport tool to access launchpad.

An editor will opened for you to edit the bug description. Normally all you need to do is to explain the reason for the backport. Just state that "The Ubuntu Studio Team plan to regularly backport our priority packages to all still supported LTS releases."

The requestbackport tool will submit the bug for you, and output a URL for it. Copy this link to your clipboard, and then copy this link into the table on the UbuntuStudio/BackportsList.