py-lmdb for Debian
This is the py-lmdb Debian source package, which is collaboratively maintained
by the Debian pkg-db group in a Git repository with the following conventions.
* Source packages are built with gbp.
* Packaging branches should be named according to the codename of the target
distribution. In the case of Debian, that means for example debian/sid,
debian/jessie, debian/experimental, debian/wheezy, debian/wheezy-backports,
etc. (From DEP-14.)
* There are no branches corresponding to upstream's branches. We use gbp's
'--git-upstream-tree=tag' option, so this is unnecessary.
* Upstream does not make independent tarball releases beyond the tarballs
automatically generated by GitHub from the release tags. There is no need to
be able to reproduce these tarballs since their content matches the release
tags exactly, so we ignore them. However, we do enable 'pristine-tar' and
'pristine-tar-commit' in debian/gbp.conf, so that subsequent Debian package
releases for the same upstream release version will have .orig.tar.gz files
with matching checksums.
* New upstream releases are imported via upstream's release tags, which are
prefixed by us with 'upstream/'. You may want to add the upstream Git
repository as a remote to your local clone with the following commands:
git remote add --no-tags upstream https://github.com/dw/py-lmdb
git config --add remote.upstream.fetch 'refs/tags/*:refs/tags/upstream/*'
git fetch upstream
This results in tags like upstream/py-lmdb_0.84. Do not import upstream's
tags without the 'upstream/' prefix.
* New releases are non-fast-forward merged onto the packaging branch, e.g.:
git checkout debian/sid
git merge --no-ff --no-edit upstream/py-lmdb_0.86
* Use gbp-dch to generate the changelog, but there is no need to list every
upstream commit in the Debian changelog.
* Only branch names matching debian/* and pristine-tar should be pushed to our
* Only tag names matching debian/* or upstream/* should be pushed to our Git