[pkg-xtuple-maintainers] Repositories re-created from upstream Github

Daniel Pocock daniel at pocock.pro
Mon Sep 7 10:09:55 UTC 2015


Up to now, we've been taking the upstream tarballs from Sourceforge or
the Git / Github tags and importing them into Debian packaging repositories.

xTuple are very actively using Github these days and very open to
accepting pull requests that improve the packaging experience, e.g.
removing non-free stuff and binary artifacts from their repositories.

Therefore, I've started building the packages using a clone of the
upstream repositories.  This has a couple of benefits:

- easier to support a CI workflow (using Jenkins or travis-ci perhaps)
to automatically test package builds after upstream tags

- easier/faster for developers to create their own local branches in
Git, cherry-picking things from upstream and merging them with the
Debian packaging branches to build local packages for testing

The old repositories are still present on alioth, I've added legacy to
their names:

/git/collab-maint/csvimp-legacy.git
/git/collab-maint/openrpt-legacy.git
/git/collab-maint/postbooks-legacy.git
/git/collab-maint/postbooks-updater-legacy.git

Anybody who is building packages will need to be aware of the following:

- if you have a clone from alioth, point it to the legacy repository, e.g.

    git remote set-url origin \
      git+ssh://$USER@git.debian.org/git/collab-maint/openrpt-legacy.git


- if you have a clone from upstream on Github, you can add the new
alioth repositories as remotes:

    git remote add alioth \
      git+ssh://$USER@git.debian.org/git/collab-maint/openrpt.git


- when upstream releases a tag, merge it into the debian/sid branch,
your workflow may involve something like this:

    git remote add XTUPLE https://github.com/xtuple/qt-client


    git fetch XTUPLE --tags
    git archive .....   (make an orig.tar of the tag
                          and then compress it)
    git checkout debian/sid
    git merge v4.9.2
    vi debian/changelog    (add v4.9.2-1)
    git commit -m 'Update for v4.9.2-1'
    pdebuild --pbuilder cowbuilder --auto-debsign \
         --debbuildopts "-j13 -i.*"
    dput ....
    git tag -s -m 'Debian version 4.9.2-1' debian/4.9.2-1
    git push -u alioth debian/sid
    git push --tags

- as well as the debian/sid branch, I've also created a
debian/jessie-backports branch and I'll use that to upload 4.9.1 to
backports as soon as it is propagates from sid to testing.

- be careful when merging or cherry-picking changes from the debian/sid
branch to debian/jessie-backports due to the change in the libopenrpt1
binary package name.  The old name is still used in jessie-backports.




More information about the pkg-xtuple-maintainers mailing list