Backports
3066
Comment: Add a description of what the backportpackage tool does
|
3160
Add status = started
|
Deletions are marked like this. | Additions are marked like this. |
Line 50: | Line 50: |
The ''backportpackage'' tool will download the package source, and build the source package. You will need to sign the *.dsc & *.changes files with you gpg key, and then you will be prompted about uploading to the ppa. Say yes! Then the package will be uploaded to the ppa for building. | The ''backportpackage'' tool will download the package source, and build the source package. You will need to sign the *.dsc & *.changes files with your gpg key, and then you will be prompted about uploading to the ppa. Say yes! Then the package will be uploaded to the ppa for building. Go to [[UbuntuStudio/BackportsList]] and change the status of your backport to 'started'. |
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.
Build the source packages & upload to a ppa
Go to the backport bug in Launchpad, assign yourself to the bug, put the status to "In Progress", and subscribe ubuntustudio-dev to the bug (so that we can track what happens to it).
The bug will give guidance on the command(s) for doing the backport. You can copy the commands one at a time to your terminal and edit the ppa address. If you are part of the ubuntustudio-dev team you could use the Backport Testing ppa, or just use your own. For example:
backportpackage -u ppa:ubuntustudio-dev/backport-testing -s yakkety -d xenial ardour
The backportpackage tool will download the package source, and build the source package. You will need to sign the *.dsc & *.changes files with your gpg key, and then you will be prompted about uploading to the ppa. Say yes! Then the package will be uploaded to the ppa for building.
Go to UbuntuStudio/BackportsList and change the status of your backport to 'started'.
UbuntuStudio/Backports (last edited 2016-05-23 21:31:46 by rosco2)