On Tue, Nov 12, 2019 at 11:23:08AM +0100, Thomas Goirand wrote:
>
> If you're rebuilding a package which is already in the archive, you're
> supposed to take the .orig.tar.xz from the archive, and if not, you're
> supposed to generate it with git archive (or with the shortcut for that
> command: ./debian/rules gen-orig-xz). Either ways, you don't need to set
> pristine-tar to do that.
... but there are teams that rely successfully on pristine-tar which
solves the problem you describe at least to my experience perfectly.
> I also think this should become the default too:
> no-create-orig = True
Please don't.
> because otherwise, you easily get a generated wrong file, which will not
> be the same as the archive one (because pristine-tar is broken in many
> ways, as many of us know already).
>From time to time I hear this statement. I can confirm that in all
teams I'm working on pristine-tar belongs to the team policy and I never
experienced in those > 2000 packages I've touched any problem with this.
For me this makes some statistically relevant set which makes me believe
that blaming pristine-tar to be broken in many ways is exaggerating and
should not become a reason to force standard options that would really
break pristine-tar.
> Besides this, nobody is forced to use gbp. Just typing "sbuild" to build
> a package is also perfectly valid. So why adding preferences for one set
> of tooling, when there's many alternatives? It doesn't make sense.
Except for not agreeing with your opinion about pristine-tar I agree that
debian/gbp.conf is frequently not very helpful and flooded with unneeded
options sometimes. It really makes sense to use ~/.gbp.conf instead.
Kind regards
Andreas.
--
http://fam-tille.de
