Path: csiph.com!aioe.org!bofh.it!news.nic.it!robomod From: Christoph Groth 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: References: X-Mailbox-Line: From debian-python-request@lists.debian.org Wed Aug 22 12:04:54 2018 Old-Return-Path: 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: archive/latest/16257 List-ID: List-URL: 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> Xref: csiph.com linux.debian.maint.python:10836 --=-=-= Content-Type: text/plain 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 --=-=-= Content-Type: application/pgp-signature; name="signature.asc" -----BEGIN PGP SIGNATURE----- iQIzBAEBCgAdFiEEUimQV/rXmWU8TwiKw/FH9ZgPNTUFAlt9UVoACgkQw/FH9ZgP NTUTzA/8CHBsz15b8rObaFQN/RGgn+weQVqt4X4vEKCHoA6AKERevfgGYNHHMoBW hYNyU4465tV7J1wxme++K43AXdNXuI6DdOZkH7TpaEXu8wZbDu8FliPp7eUI/Ez1 YVG93E7Q+WUN7W5Y2ClyOEg2uI3w3vRco6WpnJ/mkfslz0RHniLBqeducMTKFze9 PoRhLKcaxyvT1H4Q8OcT5k9+X+GWRAP5Dm8/ieh3t7rj5zbiOdAlI/Ynw76hHSfX ht1hrSFyKsKF7LDhgF0aZgXPDucS+bjma7Y6WtO1UNe24Q2omxIYwXDYSi+5B/iB 1RX3xVJoHKpSFH5wLp6qZTGkjpxJCjWQIjYRUSZiP7Wyi90rwx1qFUDg7X2sJWMh caxgqTFpeHKrg3XlQGP3fkQLUkyD1mQEMAlSRxZFclEFOOQOOyapA3nvlLWeiGsc q2YE3612gAp3fTvTpU037Ivj/wkv/8tgezZ/gL1xfax0fhzugWgtTGSlnLna1Cc5 nlvrq7Pl3/rpBaJfbFHLGgMsy2qI9ijb2PAKl338y1EN7yFwsRDQJTA3wKJ4Iudv xXfFF1zdb4tDLMK52C2fP1vql3HhBcQJdGDAyiFRI8ia0yiXJwbZn85/2P+pJLZZ DCu8Knn/hbBPpidFfgHvGioR7GGoeCvfP+AQzh9fr95LZtJgXuQ= =voHR -----END PGP SIGNATURE----- --=-=-=--