StableReleaseUpdates

Differences between revisions 4 and 5
Revision 4 as of 2013-03-11 00:24:56
Size: 217
Editor: h-4-180
Comment:
Revision 5 as of 2013-03-18 15:31:58
Size: 1470
Editor: h-4-180
Comment:
Deletions are marked like this. Additions are marked like this.
Line 8: Line 8:

= Fix Bug and do a SRU =

== Find Bug Fix ==

||<#FFFF00>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>
}}}

Create a debian patch using ''edit-patch''. Decide the name for the patch (some packages have a convention for how to name patches).

{{{
edit-patch <patchname>
}}}

''edit-patch'' will create a temprorary folder in /tmp. While in there, apply your fix doing:

{{{
patch -p1 < /path/to/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. For example:

{{{
}}}

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]
}}}

  • 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>

Create a debian patch using edit-patch. Decide the name for the patch (some packages have a convention for how to name patches).

edit-patch <patchname>

edit-patch will create a temprorary folder in /tmp. While in there, apply your fix doing:

patch -p1 < /path/to/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. For example:

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]

UbuntuStudio/StableReleaseUpdates (last edited 2013-05-17 01:34:08 by h-4-180)