summary |
shortlog | log |
commit |
commitdiff |
tree
first ⋅ prev ⋅ next
Daniel Kahn Gillmor [Mon, 29 Aug 2016 16:34:42 +0000 (12:34 -0400)]
avoid regenerating defsincdate (use shipped file)
upstream ships doc/defsincdate in its tarballs. but doc/Makefile.am
tries to rewrite doc/defsincdate if it notices that any of the files
have been modified more recently, and it does so assuming that we're
running from a git repo.
However, we'd rather ship the documents cleanly without regenerating
defsincdate -- we don't have a git repo available (debian builds from
upstream tarballs) and any changes to the texinfo files (e.g. from
debian/patches/) might result in different dates on the files than we
expect after they're applied by dpkg or quilt or whatever, which makes
the datestamp unreproducible.
Gbp-Pq: Topic debian-packaging
Gbp-Pq: Name avoid-regenerating-defsincdate-use-shipped-file.patch
Debian GnuPG Maintainers [Tue, 14 Apr 2015 14:02:31 +0000 (10:02 -0400)]
avoid-beta-warning
avoid self-describing as a beta
Using autoreconf against the source as distributed in tarball form
invariably results in a package that thinks it's a "beta" package,
which produces the "THIS IS A DEVELOPMENT VERSION" warning string.
since we use dh_autoreconf, i need this patch to avoid producing
builds that announce themselves as DEVELOPMENT VERSIONs.
See discussion at:
http://lists.gnupg.org/pipermail/gnupg-devel/2014-November/029065.html
Gbp-Pq: Topic debian-packaging
Gbp-Pq: Name avoid-beta-warning.patch
Peter Michael Green [Wed, 25 Jul 2018 10:25:32 +0000 (11:25 +0100)]
gnupg2 (2.2.9-1+rpi1) buster-staging; urgency=medium
* Disable testsuite.
[dgit import unpatched gnupg2 2.2.9-1+rpi1]
Peter Michael Green [Wed, 25 Jul 2018 10:25:32 +0000 (11:25 +0100)]
Import gnupg2_2.2.9-1+rpi1.debian.tar.bz2
[dgit import tarball gnupg2 2.2.9-1+rpi1 gnupg2_2.2.9-1+rpi1.debian.tar.bz2]
Daniel Kahn Gillmor [Thu, 19 Jul 2018 18:02:31 +0000 (19:02 +0100)]
Import gnupg2_2.2.9.orig.tar.bz2
[dgit import orig gnupg2_2.2.9.orig.tar.bz2]