File: README.source

package info (click to toggle)
py-lmdb 1.4.0-1
  • links: PTS, VCS
  • area: main
  • in suites: bookworm
  • size: 1,716 kB
  • sloc: ansic: 11,920; python: 4,646; makefile: 128
file content (33 lines) | stat: -rw-r--r-- 1,558 bytes parent folder | download | duplicates (2)
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
py-lmdb for Debian
------------------

This is the py-lmdb Debian source package, which is collaboratively maintained
by the Debian Python Team in a git repository with the following conventions
that still stem from the former team that maintained this.

 * 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/jnwatson/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/master
    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.