Control: tags -1 + patch
This patch fixes things for *most* cases:
--- /usr/lib/python2.7/dist-packages/gbp/scripts/buildpackage.py
+++ /usr/lib/python2.7/dist-packages/gbp/scripts/buildpackage.py
@@ -320,7 +320,7 @@
upstream_tree))
Control: retitle -1 build tarballs reproducibly (compression level and date)
Actually, it's more than the compression level - because of the way gbp
builds the tarball, it can't build the tarball reproducibly. Or at
least, it varies from what would be expected from git archive $tag.
According to
On 2016-05-27 09:29:55, Guido Günther wrote:
> On Tue, Apr 12, 2016 at 08:58:13PM -0400, Antoine Beaupré wrote:
>> git-buildpackage correctly uses the -n flag to make the archive
>> reproducible otherwise, so one has to wonder why there is this
>> needless override, by default. if packages want
On 2016-05-27 02:29:55, Guido Günther wrote:
> Just to bu sure: your suggestion is to not mess with compression levels
> at all by default and use the configures system defaults?
Correct.
--
Software gets slower faster than hardware gets faster.
- Wirth's law
On Tue, Apr 12, 2016 at 08:58:13PM -0400, Antoine Beaupré wrote:
> Package: git-buildpackage
> Version: 0.6.22
> Severity: wishlist
> Control: usertag -1 timestamp
>
> git-buildpackage diverges from the default gzip settings. in
> gbp/config.py, a default compression level is specified,
Package: git-buildpackage
Version: 0.6.22
Severity: wishlist
Control: usertag -1 timestamp
git-buildpackage diverges from the default gzip settings. in
gbp/config.py, a default compression level is specified, overriding
GZIP environment variables or any similar sane defaults:
6 matches
Mail list logo
