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, overriding > GZIP environment variables or any similar sane defaults: > > 'compression-level': '9', > > This makes git-buildpackage needlessly differ from upstream tarballs > (e.g. those created on Github). An example, with the tuptime package: > > -gzip compressed data, from Unix > +gzip compressed data, max compression, from Unix > > To reproduce this: > > wget https://github.com/rfrail3/tuptime/archive/3.3.0.tar.gz > git clone https://github.com/anarcat/tuptime > cd tuptime > git-buildpackage > > This will create a new tarball in ../tuptime_3.3.0.orig.tar.gz that > will use maximal compression whereas the tarball created on github > uses a more reasonable default compression (-6). > > 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 maximum compression, > they can specify that option in gbp.conf! > > (tagged as timestamp for reproducible builds, but it's not really a > timestamp, it's just the closest tag i could find)
Just to bu sure: your suggestion is to not mess with compression levels at all by default and use the configures system defaults? -- Guido
