StableReleaseUpdates
1470
Comment:
|
2013
|
Deletions are marked like this. | Additions are marked like this. |
Line 31: | Line 31: |
Create a debian patch using ''edit-patch''. Decide the name for the patch (some packages have a convention for how to name patches). | We'll start by creating a debian patch using ''edit-patch''. Decide the name for the patch (some packages have a convention for how to name patches). Use a name that describes what the patch fixes. |
Line 34: | Line 34: |
edit-patch <patchname> | edit-patch <yourpatch>.patch |
Line 37: | Line 37: |
''edit-patch'' will create a temprorary folder in /tmp. While in there, apply your fix doing: | ''edit-patch'' will create a temporary folder in ''/tmp/''. While in there, apply your upstream patch doing: |
Line 40: | Line 40: |
patch -p1 < /path/to/patch | patch -p1 < /path/to/<upstream-fix>.patch |
Line 43: | Line 43: |
Once changes were applied, use ''Ctrl+D'' to exit ''edit-patch''. This will create the debian/patches/patch, and opens debian/changelog. Adjust it to contain the correct info. For example: | Once changes were applied, use ''Ctrl+D'' to exit ''edit-patch''. This will create the debian/patches/patch, and opens debian/changelog. Adjust it to contain the correct info. Rename RELEASE to the release in question (precise, in this case), and describe what the patch does (here I just add which bug it fixes). |
Line 46: | Line 46: |
jackd2 (1.9.8~dfsg.1-1ubuntu2) precise; urgency=low * debian/patches/jackdbus-stop-fix.patch: [fixes LP: #956438] -- Kaj Ailomaa <zequence@mousike.me> Mon, 18 Mar 2013 16:25:32 +0100 |
|
Line 53: | Line 58: |
To edit the patch description, open your patch with your text editor of choice: {{{ nano debian/patches/<yourpatch> |
- When to do stable release update
- How to do stable release update
https://wiki.ubuntu.com/StableReleaseUpdates
Fix Bug and do a SRU
Find Bug Fix
Add full description here |
Find the upstream fix. Then, create a patch of it.
Create bzr branch with the new fix
Get the source for the development version. You'll always start by fixing the development version first.
bzr branch ubuntu:<package>
You'll also want to get the source for all releases where you want to add the fix, going back one release at the time (if the development release includes the fix, just skip it).
bzr branch ubuntu:<release>/<package>
We'll start by creating a debian patch using edit-patch. Decide the name for the patch (some packages have a convention for how to name patches). Use a name that describes what the patch fixes.
edit-patch <yourpatch>.patch
edit-patch will create a temporary folder in /tmp/. While in there, apply your upstream patch doing:
patch -p1 < /path/to/<upstream-fix>.patch
Once changes were applied, use Ctrl+D to exit edit-patch. This will create the debian/patches/patch, and opens debian/changelog. Adjust it to contain the correct info. Rename RELEASE to the release in question (precise, in this case), and describe what the patch does (here I just add which bug it fixes).
jackd2 (1.9.8~dfsg.1-1ubuntu2) precise; urgency=low * debian/patches/jackdbus-stop-fix.patch: [fixes LP: #956438] -- Kaj Ailomaa <zequence@mousike.me> Mon, 18 Mar 2013 16:25:32 +0100
When ready, close down the editor. You'll be asked if to commit. Answer No. We still need to update the patch description.
OK to commit? [Y/n/e]
To edit the patch description, open your patch with your text editor of choice:
UbuntuStudio/StableReleaseUpdates (last edited 2013-05-17 01:34:08 by h-4-180)