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

Re: Salsa repository and first upload of tinyarray

Path	csiph.com!aioe.org!bofh.it!news.nic.it!robomod
From	Christoph Groth <christoph@grothesque.org>
Newsgroups	linux.debian.maint.python
Subject	Re: Salsa repository and first upload of tinyarray
Date	Wed, 22 Aug 2018 14:10:01 +0200
Message-ID	<wpA7v-7op-1@gated-at.bofh.it> (permalink)
References	<wpwGB-5hs-9@gated-at.bofh.it> <wpyp3-6lD-5@gated-at.bofh.it>
X-Mailbox-Line	From debian-python-request@lists.debian.org Wed Aug 22 12:04:54 2018
Old-Return-Path	<christoph@grothesque.org>
X-Amavis-Spam-Status	No, score=-11.98 tagged_above=-10000 required=5.3 tests=[BAYES_00=-2, LDO_WHITELIST=-5, MURPHY_DRUGS_REL8=0.02, PGPSIGNATURE=-5, RCVD_IN_DNSWL_NONE=-0.0001] autolearn=ham autolearn_force=no
X-Policyd-Weight	using cached result; rate: -7
X-Greylist	delayed 13439 seconds by postgrey-1.36 at bendel; Wed, 22 Aug 2018 12:04:40 UTC
User-Agent	Gnus/5.13 (Gnus v5.13) Emacs/24.5 (gnu/linux)
MIME-Version	1.0
Content-Type	multipart/signed; boundary="=-=-="; micalg=pgp-sha512; protocol="application/pgp-signature"
X-Mailing-List	<debian-python@lists.debian.org> archive/latest/16257
List-ID	<debian-python.lists.debian.org>
List-URL	<https://lists.debian.org/debian-python/>
List-Archive	https://lists.debian.org/msgid-search/8736v6vc85.fsf@grothesque.org
Approved	robomod@news.nic.it
Lines	45
Organization	linux.* mail to news gateway
Sender	robomod@news.nic.it
X-Original-Date	Wed, 22 Aug 2018 14:04:42 +0200
X-Original-Message-ID	<8736v6vc85.fsf@grothesque.org>
X-Original-References	<87efeqvmll.fsf@grothesque.org> <CAOO6c=zNPMua7YPgBsE2fgapQKWxFxGprGi3x1KGY+4coXG0ng@mail.gmail.com>
Xref	csiph.com linux.debian.maint.python:10836

Show key headers only | View raw

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

Hello,

Ondrej, thank you for the quick reaction.  I've read the policy.  So far
(for my unofficial packages) I haven't been using pristine tar tool,
trusting PyPI to store the official release tarballs.  The package is
configured such that the pristine tars can be downloaded using the
command 'gbp import-orig --uscan'.  I find this approach more elegant
compared to the hack that is pristine-tar.

I've also kept the full upstream history in the upstream branch,
assuming this to be more robust and powerful.  For example, this allows
to directly cherry-pick commits into the patch queue.

Since both these practices are discouraged by the policy, I'm ready to
give them up, but before I spend time working on it, I would like to ask
whether tinyarray could be exempt from any one of both rules.  According
with the policy, I would provide a debian/README.source file with the
above rationale and instructions.

Thanks,
Christoph

Thread

Salsa repository and first upload of tinyarray Christoph Groth <christoph@grothesque.org> - 2018-08-22 10:30 +0200
  Re: Salsa repository and first upload of tinyarray Ondrej Novy <novy@ondrej.org> - 2018-08-22 12:20 +0200
    Re: Salsa repository and first upload of tinyarray Christoph Groth <christoph@grothesque.org> - 2018-08-22 14:10 +0200
      Re: Salsa repository and first upload of tinyarray Piotr Ożarowski <piotr@debian.org> - 2018-08-22 14:30 +0200
      Re: Salsa repository and first upload of tinyarray Ondrej Novy <novy@ondrej.org> - 2018-08-22 14:40 +0200
        Re: Salsa repository and first upload of tinyarray Christoph Groth <christoph@grothesque.org> - 2020-08-26 16:40 +0200
  Re: Salsa repository and first upload of tinyarray Ondrej Novy <novy@ondrej.org> - 2018-08-22 12:20 +0200

csiph-web