diff options
author | Kali Kaneko <kali@leap.se> | 2013-10-31 11:19:52 -0200 |
---|---|---|
committer | Kali Kaneko <kali@leap.se> | 2013-10-31 11:19:52 -0200 |
commit | 2a8c459e7f45d0454d8a99d38eca99d0c49f5bd8 (patch) | |
tree | f7e5c9ae9d0a58b1314d0d817098320b485a7674 /docs | |
parent | e9e3cd7531d97a67ca4d08f102abe8fdb2585790 (diff) |
notes for repackaging
Diffstat (limited to 'docs')
-rw-r--r-- | docs/debian-repackaging.rst | 41 |
1 files changed, 41 insertions, 0 deletions
diff --git a/docs/debian-repackaging.rst b/docs/debian-repackaging.rst new file mode 100644 index 00000000..a7488a84 --- /dev/null +++ b/docs/debian-repackaging.rst @@ -0,0 +1,41 @@ +repackaging howto +================= + +How to repackage latest code +---------------------------- + +Enter debian branch:: + + git checkout debian + +Merge your latest and greatest:: + + git merge develop + +Bump the changelog:: + + vim debian/changelog + +dch should also get you there, adding a new entry. + +Edit the changelog so you get a new version (this is the version +that apt will report). For example, change:: + + soledad-common (0.3.4) unstable; urgency=low + +to:: + + soledad-common (0.3.4-1~testing_frobnication) unstable; urgency=low + + +Last, but not least, freeze the debian version:: + + python setup.py freeze_debianver + +It might be a good idea to edit by hand the version string +under _version too, so it's clear that you're packaging some bleeding +edge not to be confused with latest stable packages. + +And now you can happily repackage for your own deploys:: + + debuild -us -uc |