Backports
Differences between revisions 6 and 8 (spanning 2 versions)
223
Comment:
|
868
|
Deletions are marked like this. | Additions are marked like this. |
Line 4: | Line 4: |
Backporting applications is sometimes nessecary. | [[UbuntuStudio/BackportsList]] - List of applications that are to be backported. |
Line 6: | Line 6: |
* When to backport * How to backport |
= What is backporting? = |
Line 9: | Line 8: |
[[UbuntuStudio/BackportsList]] | 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 [[UbuntuStudio/StableReleaseUpdates|SRU]] (Stable Release Update) instead. = How to Backport = == First step: Test Build == First, do a test build on the release that you want to backport to. == Do the bug report == Use the commandline tool '''requestbackport'''. For example: {{{ requestbackport -s saucy -d raring ardour3 }}} |
UbuntuStudio/BackportsList - List of applications that are to be backported.
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
First step: Test Build
First, do a test build on the release that you want to backport to.
Do the bug report
Use the commandline tool requestbackport.
For example:
requestbackport -s saucy -d raring ardour3
UbuntuStudio/Backports (last edited 2016-05-23 21:31:46 by rosco2)