[Pkg-crosswire-devel] [GnomeSword-developers] Bits from Debian Crosswire Packaging Team

Dmitrijs Ledkovs dmitrij.ledkov at ubuntu.com
Thu Dec 2 21:18:00 GMT 2010

On 2 December 2010 21:03, Greg Hellings <greg.hellings at gmail.com> wrote:
> On Thu, Dec 2, 2010 at 2:36 PM, Dmitrijs Ledkovs
> <dmitrij.ledkov at ubuntu.com> wrote:
>> Hi there.
> <snip>
>> $ bzr co lp:~pkgcrosswire/sword/bridge
>> $ bzr merge lp:sword && bzr ci
>> $ bzr merge lp:~pkgcrosswire/sword/debian && bzr ci
> ^== More of this for the rest of your pkgcrosswire friends, in case
> you're AWOL next time a release needs to be made, so we can do it.

My reply was sent to pkg-crosswire-devel. The above "how-to" is for
upstream sword developers to do a daily build. Debian packaging is
still maintained as it was using bzr branch at
lp:~pkgcrosswire/sword/main which has released upstream code, cleaned
up for dfsg with packaging changes and patches.

>> Hope this clarifies how the bridge branch works and why this solution
>> has been chosen. Let's see how it will work out for us. I will be
>> monitoring and keeping the builds running smoothly.
> Nope, but I gave up trying to understand actual package maintainers'
> minds (and also trying to understand the minds of people set on
> maintaining all back history for projects at all costs - but that's
> just me).  I do understand conceptually what you're doing at the
> Bazaar level, but above that, not quite so much.  So a few basic "make
> a release" mappings for the rest of us so we can cover when you're
> gone, and that'd be grand!
> --Greg

The beauty of this implementation is that there are no actions needed
to "make a new release".

Debian packaging will be maintained as it currently was maintained.
Daily builds automatically do the above and publish daily builds in the PPA.
"Released" versions need only a push in the lp:sword/debian branch
which usually goes like so:

$ bzr branch lp:sword/debian sword-packaging
$ cd sword-packaging
$ ./debian/rules get-orig-source
$ mv sword*.tar.gz ../
$ dch -v 1.X.Y
$ bzr ci
$ bzr push

That is if nothing has changed in the packaging, patches still apply
fine and there are no other modifications needed.

If disaster happens, any Debian/Ubuntu developer will know how to do
upgrade to a new version using the debian source package available
from any mirror in the world ;-) launchpad can go down =)

More information about the Pkg-crosswire-devel mailing list