Groups > linux.debian.maint.python > #13564

Re: python-django-js-asset_1.2.2-3_source.changes REJECTED

From	Antonio Terceiro <terceiro@debian.org>
Newsgroups	linux.debian.maint.python
Subject	Re: python-django-js-asset_1.2.2-3_source.changes REJECTED
Date	2021-09-21 23:10 +0200
Message-ID	<CZVbA-5Wb-7@gated-at.bofh.it> (permalink)
References	(1 earlier) <CZaFH-2HO-11@gated-at.bofh.it> <CZaFH-2HO-7@gated-at.bofh.it> <CZceu-3Oh-23@gated-at.bofh.it> <CZpEJ-3D6-3@gated-at.bofh.it> <CZtfk-5SL-9@gated-at.bofh.it>
Organization	linux.* mail to news gateway

Show all headers | View raw

[Multipart message — attachments visible in raw view] - view raw

On Mon, Sep 20, 2021 at 11:14:44AM -0400, Sandro Tosi wrote:
> > That's because gbp does not use pristine-tar by default, and
> > debian/gbp.conf was missing `pristine-tar=True`. Just pushed a commit to
> > fix that.
> 
> I dont think this is the right approach: the default options to work
> on DPT packages should be in gbp default config file (or in another,
> global, config file), and not live in each and every package
> debian/gbp.conf file; it is already inconsistently maintained with
> several packages having uncommon settings that will take precedence
> over the default ones.

I agree with you in theory; my global gbp.cons enables pristine-tar.

However, having it duplicated in every package means we as a team work
consistently regardless of people's global configuration, and that's one
less detail people need to get just right to be able to contribute
effectively.

Also, one's global configuration might not apply to all the packages
they contribute to; it's easier for everyone if gbp just does the
right thing based on per-package configuration than expecting people to
remember to switch their defaults, or to pass options explicitly.

Thread

Re: python-django-js-asset_1.2.2-3_source.changes REJECTED Antonio Terceiro <terceiro@debian.org> - 2021-09-19 21:30 +0200
  Re: python-django-js-asset_1.2.2-3_source.changes REJECTED Carsten Schoenert <c.schoenert@t-online.de> - 2021-09-19 23:10 +0200
    Re: python-django-js-asset_1.2.2-3_source.changes REJECTED Andrey Rahmatullin <wrar@debian.org> - 2021-09-20 09:30 +0200
    Re: python-django-js-asset_1.2.2-3_source.changes REJECTED Antonio Terceiro <terceiro@debian.org> - 2021-09-20 13:30 +0200
      Re: python-django-js-asset_1.2.2-3_source.changes REJECTED Sandro Tosi <morph@debian.org> - 2021-09-20 17:20 +0200
        Re: python-django-js-asset_1.2.2-3_source.changes REJECTED Andrey Rahmatullin <wrar@debian.org> - 2021-09-20 17:30 +0200
          Re: python-django-js-asset_1.2.2-3_source.changes REJECTED Sandro Tosi <morph@debian.org> - 2021-09-21 03:20 +0200
        Re: python-django-js-asset_1.2.2-3_source.changes REJECTED Thomas Goirand <zigo@debian.org> - 2021-09-20 21:50 +0200
        Re: python-django-js-asset_1.2.2-3_source.changes REJECTED Antonio Terceiro <terceiro@debian.org> - 2021-09-21 23:10 +0200
          Re: python-django-js-asset_1.2.2-3_source.changes REJECTED Sandro Tosi <morph@debian.org> - 2021-09-22 00:40 +0200
          Re: writing debian/gbp.conf considered harmful [was:  python-django-js-asset_1.2.2-3_source.changes REJECTED] Thomas Goirand <zigo@debian.org> - 2021-09-22 09:30 +0200

csiph-web