• python-django-js-asset_1.2.2-3_source.changes REJECTED

    From Antonio Terceiro@21:1/5 to Carsten Schoenert on Sun Sep 19 21:30:01 2021
    Hi,

    On Sun, Sep 19, 2021 at 10:27:21AM +0200, Carsten Schoenert wrote:
    Hello Antonio,

    as you initially did the first upload for this package I'm now heading
    over to you.

    Am 19.09.21 um 09:48 schrieb Debian FTP Masters:

    python-django-js-asset_1.2.2-3.dsc: Invalid size hash for python-django-js-asset_1.2.2.orig.tar.gz:
    According to the control file the size hash should be 6360,
    but python-django-js-asset_1.2.2.orig.tar.gz has 6367.

    If you did not include python-django-js-asset_1.2.2.orig.tar.gz in your upload, a different version
    might already be known to the archive software.

    I've no idea where the size of 6360 for the orig.tar.gz file is coming
    from which DAK refers.

    If I look at the source package sites or on snapshot.d.o I always see a
    size of 6367.

    https://packages.debian.org/source/unstable/python-django-js-asset http://snapshot.debian.org/package/python-django-js-asset/1.2.2-1/

    And this size was recreated by gbp locally.
    But the question is now how to proceed now. A quick & dirty solution
    would be to simply use the old tar.gz file (if available).
    Another option would be more dramatically and let remove the package completely from the archive. Do you have opinions on that?

    Looking from my side, the tarball from the archive (apt source python-django-js-asset) and the one generated by pristine-tar are
    identical:

    4b6a2c8625b8e96bbc4ff1588a27238d7d418b03 /tmp/python-django-js-asset_1.2.2.orig.tar.gz
    4b6a2c8625b8e96bbc4ff1588a27238d7d418b03 /tmp/archive/python-django-js-asset_1.2.2.orig.tar.gz

    From reading the REJECT email, I think it implies that the .dsc/.changes
    you uploaded refer to an orig tarball with 6360 bytes. Do you still have
    the exact artifacts that you uploaded?

    -----BEGIN PGP SIGNATURE-----

    iQIzBAABCAAdFiEEst7mYDbECCn80PEM/A2xu81GC94FAmFHjnIACgkQ/A2xu81G C959Fg/+MdahLujhfCvV4EDtE8TD9BQnlJhYaz4bMbYMVUqgT8W3i0ZY4gAiVXL2 eZcBoLrPsPvhqJ+wo0FSq7PfbQBFd/QxvUenJNGfQfLwB2tti2tGCGo5bMzsVBsB AALtt30dB9pzsmCxT9bewilb25chW9T9KyUqPt5W8G7rufz8gkV4znVsyUM8PunW 13J0u0eHX2UxrpjNXudz6CV2vDnjNnxEoHSGvMkLmt94ZfKV8DBPdZI9uQbaYz3W 5MP28d+jAfH4nQpCXmjdcJQIEqey8fkvkCq8FZjTRy14JSytCGqZhUus0iC+qpCu dp/zAGPG+ZsgzgDs/UHW2lxsxUj80hI838xtdkKLS+7dfeQsNj8hmCNKpfEGr4U7 K42plqxcD79kKnMwOPPJ86ykNkJEYHIdhjoFCZ7HN9xK548PsLQDESnUo2e8Gko6 HgMGPfSuzKIvtWsG64tonuNYdO2mAHoygYeRRomLuJe1BAtj3hBrxvPtG1odDEUo dZ0bleZdCG+MVom7pzLxRCPenVE6vWoR/7ZPVKkn5MTjYQTWM1yi1HynU6OQZf/Y dJtxXRjz3xGbiPsyWywc5olNGNR8Ptc2Kg3DlbhwYT0xS9PuB/XJibfUvTG9u3Xa ITTJZJ77oE8siwMhcfptvxIjcft1kUxlXd6k3DB+Zogov4Ju1/I=
    =lOti
    -----END PGP SIGNATURE-----

    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)
  • From Carsten Schoenert@21:1/5 to All on Sun Sep 19 23:10:02 2021
    Hi Antonio,

    thanks for your quick feedback!

    Am 19.09.21 um 21:24 schrieb Antonio Terceiro:

    Looking from my side, the tarball from the archive (apt source python-django-js-asset) and the one generated by pristine-tar are
    identical:

    4b6a2c8625b8e96bbc4ff1588a27238d7d418b03 /tmp/python-django-js-asset_1.2.2.orig.tar.gz
    4b6a2c8625b8e96bbc4ff1588a27238d7d418b03 /tmp/archive/python-django-js-asset_1.2.2.orig.tar.gz

    From reading the REJECT email, I think it implies that the .dsc/.changes
    you uploaded refer to an orig tarball with 6360 bytes. Do you still have
    the exact artifacts that you uploaded?

    No, not completely.
    But I played around a bit with gbp and pristine-tar too and I was able
    to recreate a tarball which has the same size and the same hashes as the *.tar.gz in the archive and the one you've posted by using pristine-tar manually.

    If I clean out all completely and build the package from scratch by gbp
    I get again a wrong size and of course also different hashes.

    Currently I've no real clue why gbp is creating here different results,
    will look again at this once Guido is around, I'm sure he can blame me
    that I'm doing something wrong. :P

    I was able to upload 1.2.2-3 successful recently so no big problem any more.

    --
    Regards
    Carsten

    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)
  • From Andrey Rahmatullin@21:1/5 to Carsten Schoenert on Mon Sep 20 09:30:03 2021
    On Sun, Sep 19, 2021 at 10:56:33PM +0200, Carsten Schoenert wrote:
    Hi Antonio,

    thanks for your quick feedback!

    Am 19.09.21 um 21:24 schrieb Antonio Terceiro:

    Looking from my side, the tarball from the archive (apt source python-django-js-asset) and the one generated by pristine-tar are identical:

    4b6a2c8625b8e96bbc4ff1588a27238d7d418b03 /tmp/python-django-js-asset_1.2.2.orig.tar.gz
    4b6a2c8625b8e96bbc4ff1588a27238d7d418b03 /tmp/archive/python-django-js-asset_1.2.2.orig.tar.gz

    From reading the REJECT email, I think it implies that the .dsc/.changes you uploaded refer to an orig tarball with 6360 bytes. Do you still have the exact artifacts that you uploaded?

    No, not completely.
    But I played around a bit with gbp and pristine-tar too and I was able to recreate a tarball which has the same size and the same hashes as the *.tar.gz in the archive and the one you've posted by using pristine-tar manually.

    If I clean out all completely and build the package from scratch by gbp I
    get again a wrong size and of course also different hashes.
    As pristine-tar is not enabled in debian/gbp.conf you need to enable it explicitly with --git-pristine-tar each time you run a command that uses
    it.

    --
    WBR, wRAR

    -----BEGIN PGP SIGNATURE-----

    iQJhBAABCgBLFiEEolIP6gqGcKZh3YxVM2L3AxpJkuEFAmFIMuEtFIAAAAAAFQAP cGthLWFkZHJlc3NAZ251cGcub3Jnd3JhckBkZWJpYW4ub3JnAAoJEDNi9wMaSZLh iKAP+gJAceoiQr0uPywC8KcZBcaOwePgp4LJWLO3z+osczg9rfT2aVHxeFptXrcC 7lpx7vJcKLK0o7+PVqHb+Iet2sNaT2QFpMVPXJPs6oNYgzhjiSnnSABUu+tpv7Cj Q4QYhJT4INBxoAuXA1Ut9LnCdMXOT/g0jNYVgfLIQqx2Pj+XkTdDlAkG+3Vn6A+g G9hb78pSfVEUbwso0JYmg34AfvPnj6ZWwROq7/qUdM+2vt8B0kyJMqyeOYg20/R+ sK2REIC8Lb9PH5o6KmGcm/W70dVsHDJX/vatq5b03JZDtWNreGnitfVqc9P3N+vp 4B6nma9oS0n6KRJKvrkGlnC/YWGUAq1Br6HYamdP1uxjkfnl8r8jJTyHcboxbDwY rBw8uSQkMWBdjPwV/lGNyB28CfbKIYid2r04Q2PwhVm9yKYPZF2C4BwCMlI20Sqw pcNWofNZOpzAUBconzAtbaEXc86OMRPG0UY3XqmkBUfiAHhEoSpDkxRf+gda+aK/ LuaVQ6baWLoWE48YdP5VScu3IRiWqr5f89Z/q50Ye9tlZvWRV/WxmRlrP8UsJAAo YUwQLKBB9Dwq6CzNhdK02VS2q96N7gxcc3OelDJR+7sjHGgQqKwNnKzZe3I9Lsxe TTMmpBjiQY6BmCLGCNGF02KnskhmURPV+BdXCzqOnuhIoZMo
    =LJSE
    -----END PGP SIGNATURE-----

    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)
  • From Antonio Terceiro@21:1/5 to Carsten Schoenert on Mon Sep 20 13:30:02 2021
    On Sun, Sep 19, 2021 at 10:56:33PM +0200, Carsten Schoenert wrote:
    Hi Antonio,

    thanks for your quick feedback!

    Am 19.09.21 um 21:24 schrieb Antonio Terceiro:

    Looking from my side, the tarball from the archive (apt source python-django-js-asset) and the one generated by pristine-tar are identical:

    4b6a2c8625b8e96bbc4ff1588a27238d7d418b03 /tmp/python-django-js-asset_1.2.2.orig.tar.gz
    4b6a2c8625b8e96bbc4ff1588a27238d7d418b03 /tmp/archive/python-django-js-asset_1.2.2.orig.tar.gz

    From reading the REJECT email, I think it implies that the .dsc/.changes you uploaded refer to an orig tarball with 6360 bytes. Do you still have the exact artifacts that you uploaded?

    No, not completely.
    But I played around a bit with gbp and pristine-tar too and I was able to recreate a tarball which has the same size and the same hashes as the *.tar.gz in the archive and the one you've posted by using pristine-tar manually.

    If I clean out all completely and build the package from scratch by gbp I
    get again a wrong size and of course also different hashes.

    Currently I've no real clue why gbp is creating here different results, will look again at this once Guido is around, I'm sure he can blame me that I'm doing something wrong. :P

    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.

    -----BEGIN PGP SIGNATURE-----

    iQIzBAABCAAdFiEEst7mYDbECCn80PEM/A2xu81GC94FAmFIbLAACgkQ/A2xu81G C940GQ//U3o+VmHA9Bfr9RpX/NtJWQNOEDqK4jl4hU5d35lN5QY3Nok4fc2GnNwW oiVEMg1JE6tcHEhDtGKpSB94GLjHY7/0qKpivfktNdjzWvazH9hKO0GedijtCBT8 IA0cYLwsqNFodrAlVP0vwoc4bvUl2RAb2lB5jnZhlgWZTvaw/hTi/v1OdWdlUFwb ux/gO7SvEsJUFSAluM7tmoMbRUkbKWHeX4y4N/5Vk+t4OzPTtE5DPDy76qxsNc9c yUs25NIIJwa2Yihh8Yzo5p4hoG1R/nOOGkztV7e7hE/XNGpxHknkisqts8vXpPn0 7pDzX8BT1vbxokUZaxwqLpqy6xiT3PAl0PiTa3MNi928ymwgJffWqPgBHo08S3Sf vzLYzlQOjNuwzmJqiJuBDnbxKd2xUmYpKmkCcaX7p2j3IuncRKHazPXMggRlN8se IToa5GaEKT2a7c9AojIqFlw0RYWrdpPIqIhFVAQ/UX+5wrO9842n40hSBlIJ8cPH 8KfrvMMlXV67m82TvWa+jcptZlFPBIpFCIdDAsGl1reKrp38rqjXTrsNYOp1pOUN McDf5x0HrDrCDBl7JoXC2GJGFYMoanhxLUY/YQBM5CYttzTrWVGgcgNkHnbqiL6Y mIo71er4GaKF90BmXn2Md8Egys8uJpWR0NYXqbHy91V+TxWNoFE=
    =Fv2I
    -----END PGP SIGNATURE-----

    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)
  • From Andrey Rahmatullin@21:1/5 to Sandro Tosi on Mon Sep 20 17:30:01 2021
    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;
    What's the mechanism to put these options there for everyone who works on
    a DPT package? Or do you mean just working with whatever is shipped with
    gbp?

    --
    WBR, wRAR

    -----BEGIN PGP SIGNATURE-----

    iQJhBAABCgBLFiEEolIP6gqGcKZh3YxVM2L3AxpJkuEFAmFIpugtFIAAAAAAFQAP cGthLWFkZHJlc3NAZ251cGcub3Jnd3JhckBkZWJpYW4ub3JnAAoJEDNi9wMaSZLh L1cP/37mOX3Wvagj9YUSEsUAHYtwHU55QUAEjQ0H+jYVwtHykF3ZqmGA0yl7lscT g8jqDE4/Q4XKYRQMcwvY1eXOrPSvO/eX++Qap6GVI2zTnY0LkRU66KwBAsPwIKle XiEReXlTDKtjgAKdJvtjwwEHpGEUfJyveGlC3gJpn0fYQdQx/Uj7qeTMOnEG37kN 1Jw7MIGYfkDRXx4ModNQazy7iuoilX0hzjnpDKixnyECxmwMtRDSRTCzQ+G9emwL wjC2mvc3FBwP4L/wty92fzD86QOkTgI+A2xdtj/gOGd7ogzNYz3wCkNQV+EScknf jJltHt2hzN4pJT2ZF5fm5gxMXpv/MmyvaJ4S6vm0f91w0Fn7o0ltuBK2wyPodvkc M8ZBMr1UmbZmswrbIBs+hbuDAxN9MiDdHKJc8PVRVw11RiYPdvIu0ldCyuoIkGd+ GBoohyM/CgAV6aXPRPF4a3xXJWGkyd/aV61ycscUkWlNQmql6cf+zk2W9wQZcpxq pG2jW1348uXZ7nKrKVe0oClVIKmgM+3KU1h1Y6wae/zvIUpskg1YAlbylqD9XV5E OXVGWMNvtRvNWEkp4rJM+QD7rm9T8T6LZBSfbozehbz76YQzvWmiUKWtI++y4qYZ cjpR/t4BArQI6WtX+NxcODphAPr5gFA07KIAs0vRREWz3LbT
    =P+Bw
    -----END PGP SIGNATURE-----

    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)
  • From Sandro Tosi@21:1/5 to All on Mon Sep 20 17:20:02 2021
    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.

    --
    Sandro "morph" Tosi
    My website: http://sandrotosi.me/
    Me at Debian: http://wiki.debian.org/SandroTosi
    Twitter: https://twitter.com/sandrotosi

    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)
  • From Thomas Goirand@21:1/5 to Sandro Tosi on Mon Sep 20 21:50:01 2021
    On 9/20/21 5:14 PM, 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.

    +1

    Plus gbp is just *one* out of *many* tools available. Some people just
    prefer to use sbuild only, for example, and that's perfectly fine. IMO
    it's up to the person that's using gbp to know what they are doing.

    FYI, I've rebuilt regularly packages from the team, I even have
    "pristine-tar = False" in my ~/.gbp.conf, and it's all fine...

    Cheers,

    Thomas Goirand (zigo)

    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)
  • From Sandro Tosi@21:1/5 to wrar@debian.org on Tue Sep 21 03:20:01 2021
    On Mon, Sep 20, 2021 at 11:21 AM Andrey Rahmatullin <wrar@debian.org> wrote:
    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;
    What's the mechanism to put these options there for everyone who works on
    a DPT package?

    that's a great question! i dont think a technical solution currently exists.

    Or do you mean just working with whatever is shipped with
    gbp?

    that wont work, but there could be a solution if we request a new
    feature in gbp.

    According to man 5 gbp.conf, there is either a global configuration
    file, a per user file or a per repo/branch. In order to support
    different workflows (for different teams, f.e.), this is not
    sufficient.

    But it could work if gbp.conf supported something similar to gitconfig includeIf: in my ~/.gitconfig i have

    ```
    [includeIf "gitdir:~/deb/"]
    path = ~/.gitconfig-deb
    ```

    (~/deb is where i keep all my Debian work), and that means that if the
    CWD is part of the ~/deb/ tree, git will also include ~/.gitconfig-deb
    which contains Debian-specific configs, like the @d.o mail address.

    Now, we'd also need a single location to store the team-specific
    gbp.conf, and we already have a repo thta would fit: https://salsa.debian.org/python-team/tools/packages , which currently
    contains files useful to work on the entire team packages. This is
    useful in my specific workflow, which is suspect is rather unusual,
    but here how it goes:

    * i checked https://salsa.debian.org/python-team/tools/packages in
    ~/deb/python (this could be anywhere)
    * run ./checkout -a to checkout all team packages (or ./checkout
    <pkg1>... for only a subset)
    * use `mr` (via .mcrconfig) to work on _m_ultiple _r_epositories (mr)

    this repo could also contain a team-specific gbp.conf file we could
    use. Admittedly, we probably only need a handful of options,
    pristine-tar = True is only one that comes to mind (be aware this file
    will need to be compatible with *all* repos currently in the team, so
    setting the debian branch etc, wont work, until all repos are
    uniform).

    I'm going to file a feature request for the includeIf-like feature for gbp

    Regards,
    --
    Sandro "morph" Tosi
    My website: http://sandrotosi.me/
    Me at Debian: http://wiki.debian.org/SandroTosi
    Twitter: https://twitter.com/sandrotosi

    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)
  • From Antonio Terceiro@21:1/5 to Sandro Tosi on Tue Sep 21 23:10:02 2021
    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.

    -----BEGIN PGP SIGNATURE-----

    iQIzBAABCAAdFiEEst7mYDbECCn80PEM/A2xu81GC94FAmFKR+EACgkQ/A2xu81G C94RcQ//d1ggs0V69RcXr/TX5Bpy6LVz9iOLdLOgrUokPUyKatGLKgnb6R8JRn5W A0bIDUEy1RpsVOTSiDbCAmR0Y06W8p2VzyseGpA9CLTdR1jIX1ufseekzSeYcJ28 0TCl24ALhT64+FVYGPMoFUBgahGMzPKz56Xxjqq8aVXYrxNhnHUFieZ0U5NxkU/a ciFZbm4WZ00NPGrwpyIhiKJiYALPTiIV2GpxwPMbtuPAOPAZhbF5uQInuuxqNfom by/DrEHLR/WU5EYZy0gvegtgfNfG6RU+wD4lnnNFBylXCYUuIQwvwNrq5+J1wRKY yBk/KR/VeA7AwFP/mcLtstk5m3yS2wE9LxG+CMxbbjf4jib8X5GZlKUlP4z4TyTp oAwX4iAI2c2lbIHHd4zmS/GThOaaXn3SfrvqvV3Fnh3IlJy0qNE7ZfSGW0mcUqcR M8tdOu5pNZ2iP2YpojOdzaa1OcpI+3ABzBc94WFEFwavpkkRigSkrsxqTnO93WHy xaGpuTnhFFtQ44YxbNKGBYUcSjLHTYE0Nxar3KINOURARAvivrRYlpZ67pSaXOsI YyuAOClDeCrc4uLafHPzpm/8EUK31wMcKZCZYa3Ohn63W5t02TYvcB6MkVN4yDim XXkrBPo2VaPqrmn18ytM3sKPrEe010D83+gB16XbD97qWaZgw+Y=
    =msw9
    -----END PGP SIGNATURE-----

    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)
  • From Sandro Tosi@21:1/5 to terceiro@debian.org on Wed Sep 22 00:40:01 2021
    On Tue, Sep 21, 2021 at 5:00 PM Antonio Terceiro <terceiro@debian.org> wrote:

    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,

    not at all, right now we dont have a *consistent* debian/gbp.conf in
    each package, everyone writes their own and it's currently a mess.

    what when we decide to add a new option, or change the value of an
    existing one? DPT currently has ~2500 packages: how do you maintain
    consistency in all of them?

    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.

    please refer to
    https://lists.debian.org/debian-python/2021/09/msg00065.html for how i
    see this being implemented.


    --
    Sandro "morph" Tosi
    My website: http://sandrotosi.me/
    Me at Debian: http://wiki.debian.org/SandroTosi
    Twitter: https://twitter.com/sandrotosi

    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)
  • From Thomas Goirand@21:1/5 to Antonio Terceiro on Wed Sep 22 09:30:02 2021
    On 9/21/21 11:00 PM, Antonio Terceiro wrote:
    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.

    No. It *ALREADY* works by default, no need to tweak anything on debian/gbp.conf. Also, as I wrote already, using gbp buildpackage is
    *NOT* the only one way of doing things. One can use sbuild without gbp.
    What you're proposing is in fact the same as if you were proposing to
    add defaults for some text editors in the packaging: that's irrelevant,
    and hard to maintain consistently (like Sandro wrote).

    Also, one's global configuration might not apply to all the packages
    they contribute to

    It is the case for me: I contribute to both the OpenStack team and the
    Python team. Both teams have *very* different workflow (the Python team
    is using pristine-tar, I don't like it and that's the main reason why
    OpenStack is maintained outside of this team...).

    In the OpenStack team, we used to maintain per-package debian/gbp.conf.
    I am *very* happy we decided back in Debconf Montreal in 2017 to stop
    doing that.

    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.

    There's nothing to switch. One just needs to remember to explicitly
    generate the tarball with "gbp export-orig", OR (preferred) directly
    fetch the orig.tar.{gz,xz} from the Debian archive. If you forget, gbp complains about it and stops building (that is, as long as you have the
    option "no-create-orig = True" in your ~/.gbp.conf).

    Cheers,

    Thomas Goirand (zigo)

    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)