Re: Please add 'stappers' to PAPT, 403
Hi, Dmitry Shachnev píše v So 12. 01. 2019 v 20:34 +0300: > Looks like you were added to DPMT but not PAPT: yes, sorry, my mistake. Fixed. -- Ondřej Nový vedoucí vývoje Zprávy/TV tel: +420 777 963 207 ondrej.n...@firma.seznam.cz http://www.seznam.cz/ Seznam.cz, a.s., Business park - Londýnské nám. 856/2, 639 00 Brno signature.asc Description: This is a digitally signed message part
Re: [RFC] Dropping Python2 support for my package
On Sat, Jan 12, 2019 at 04:39:44PM +0100, Bastian Venthur wrote: > > just drop the python-debianbts binary, without doing any kind of > > strange migration, and keep the name python-debianbts for the > > python3 package, as the Debian Python Policy states. > > I think there's an error in your advice and I can't figure out what > you mean. You're suggesting to drop *and* to keep the python-debianbts > package :) Can you please clarify? Yes, I made an error there indeed (that I think Andrey corrected already). But let my try again: just drop the python-debianbts binary, without doing any kind of strange migration, and keep the name python3-debianbts for the python3 package, as the Debian Python Policy states. As Andrey wrote, don't touch the source package name either. Sorry if I spread confusion accidentally… -- regards, Mattia Rizzolo GPG Key: 66AE 2B4A FCCF 3F52 DA18 4D18 4B04 3FCD B944 4540 .''`. more about me: https://mapreri.org : :' : Launchpad user: https://launchpad.net/~mapreri `. `'` Debian QA page: https://qa.debian.org/developer.php?login=mattia `- signature.asc Description: PGP signature
Re: Please add 'stappers' to PAPT, 403
On Sat, Jan 12, 2019 at 06:14:51PM +0100, Geert Stappers wrote: > Thanks > > Tried it today: > > > $ git push --all > Username for 'https://salsa.debian.org': stappers > Password for 'https://stapp...@salsa.debian.org': > remote: You are not allowed to push code to this project. > fatal: unable to access > 'https://salsa.debian.org/python-team/applications/pelican.git/': The > requested URL returned error: 403 > $ > Looks like you were added to DPMT but not PAPT: https://salsa.debian.org/groups/python-team/modules/-/group_members?search=Stappers https://salsa.debian.org/groups/python-team/applications/-/group_members?search=Stappers I hope Ondřej or another admin can correct it. -- Dmitry Shachnev signature.asc Description: PGP signature
Re: Please add 'stappers' to PAPT, 403
On Wed, Jan 09, 2019 at 02:13:00PM +0100, Ondrej Novy wrote: > Hi, > > pá 4. 1. 2019 v 22:16 odesílatel Geert Stappers napsal: > > > Could you please add my account to PAPT and/or the python-team? > > > > welcome :) > Thanks Tried it today: $ git push --all Username for 'https://salsa.debian.org': stappers Password for 'https://stapp...@salsa.debian.org': remote: You are not allowed to push code to this project. fatal: unable to access 'https://salsa.debian.org/python-team/applications/pelican.git/': The requested URL returned error: 403 $ What to do to get beyond that HTTP 403 Forbidden? I'm also happy with email like * Works for me * Works for me, however I do use SSH * FWIW I do also get that 403 Groeten Geert Stappers -- Leven en laten leven signature.asc Description: PGP signature
Re: [RFC] Dropping Python2 support for my package
-BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Am 12.01.19 um 16:49 schrieb Andrey Rahmatullin: > On Sat, Jan 12, 2019 at 04:39:44PM +0100, Bastian Venthur wrote: The question is: if I drop Python2 support, what happens with the package names? Should I simply provide the python3-debianbts and drop python-debianbts, or shall I attempt some kind of migration to make the python-debianbts the new default package name for Python3? >>> >>> just drop the python-debianbts binary, without doing any kind >>> of strange migration, and keep the name python-debianbts for >>> the python3 package, as the Debian Python Policy states. >> >> I think there's an error in your advice and I can't figure out >> what you mean. You're suggesting to drop *and* to keep the >> python-debianbts package :) Can you please clarify? > Drop binary python-debianbts package, keep the source package name > as python-debianbts. > > Or were you asking about shipping the py3 module inside the > python-debianbts binary package? We don't do that. > > Thanks! - -- Dr. Bastian Venthur https://venthur.de Debian Developer venthur at debian org -BEGIN PGP SIGNATURE- iQIzBAEBCgAdFiEEh5WvLkoaTvugaKRJjoiVRNmFAA0FAlw6DhQACgkQjoiVRNmF AA07yRAAyHk8QZgk/GcDmINyrz1JfA9LyNFJCtBWzNxA9h8heZDQ0+YjJo5Nv9u6 9GNmq4OujP9yBEI7zTqROnI95sLJfSAQSOP2u+EWEji5e6gS7C/bQedhOIfjpX6O x9TMyI6wRfX0yN1A/sT8C/iA0Wku8afyEV81cNA5aLmZx2EKo+hpPaV4nkYaVFbH O/GBcrsqAxP591XsBFo5MhRS4mvCdBL5hM2pLCf8cdBAWjO/yYOPAFJuW+P7Q6Wu J700Dh8WDQQb/t/eudOiOihORwfBJPrgtiF+IH2zXIn6kLGNmqNNZEw6n9bnn/m4 srNYFY9oTaXjdYVzTCB1cRVhXMva2jxR7WKCYaWRDLsyK+EfZhATE9iRRO0S7waG y1BgKpCY4SkCGgH5vYIr20FpvYNUptYmQh/ZCDbl1guDfS0Lzy1h0ZDasOjbCt2L hl6Yqidphh1LdryZoOfrSCex5sj8mBOnpfeVxZyHQMpoULvSnx/+F/2wASIbWxTR 551rY6gy2B5rm2YGk1rGaN/OF44jhx8K8NoFB6uCsteOlFuR9Ll8wEFLIPqL8GSE 5EMgmuoNnMpFfhV8EIeASWfKbVor8RQwLcdoYYDuq9vXaMQ3loRflla5Y0+CVKtl SLWtx79FN/mfxaA2AMU3QxmgKJMkQXyKZ8fu+lHwQYFjMzJ7ix4= =xxSc -END PGP SIGNATURE-
Re: [RFC] Dropping Python2 support for my package
On Sat, Jan 12, 2019 at 04:39:44PM +0100, Bastian Venthur wrote: > >> The question is: if I drop Python2 support, what happens with the > >> package names? Should I simply provide the python3-debianbts and > >> drop python-debianbts, or shall I attempt some kind of migration > >> to make the python-debianbts the new default package name for > >> Python3? > > > > just drop the python-debianbts binary, without doing any kind of > > strange migration, and keep the name python-debianbts for the > > python3 package, as the Debian Python Policy states. > > I think there's an error in your advice and I can't figure out what > you mean. You're suggesting to drop *and* to keep the python-debianbts > package :) Can you please clarify? Drop binary python-debianbts package, keep the source package name as python-debianbts. Or were you asking about shipping the py3 module inside the python-debianbts binary package? We don't do that. -- WBR, wRAR signature.asc Description: PGP signature
Re: [RFC] Dropping Python2 support for my package
-BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Am 12.01.19 um 16:32 schrieb Mattia Rizzolo: > On Sat, Jan 12, 2019 at 04:28:26PM +0100, Bastian Venthur wrote: >> The question is: if I drop Python2 support, what happens with the >> package names? Should I simply provide the python3-debianbts and >> drop python-debianbts, or shall I attempt some kind of migration >> to make the python-debianbts the new default package name for >> Python3? > > just drop the python-debianbts binary, without doing any kind of > strange migration, and keep the name python-debianbts for the > python3 package, as the Debian Python Policy states. I think there's an error in your advice and I can't figure out what you mean. You're suggesting to drop *and* to keep the python-debianbts package :) Can you please clarify? Thanks! - -- Dr. Bastian Venthur https://venthur.de Debian Developer venthur at debian org -BEGIN PGP SIGNATURE- iQIzBAEBCgAdFiEEh5WvLkoaTvugaKRJjoiVRNmFAA0FAlw6CjQACgkQjoiVRNmF AA3TNA//eKN0UMeJ6iQDwwVs6cH/s+j3qcx4AfXCAaDuOrY3++BDZk03jKRlCu7a 357Tq1k0MOlAJ0w6sT4xqp4+4/9/Hf/nS2TnB0y4fvE/mLfkJiwMMCVh1eS6Hwu2 L0qiMf65aHOV3Jr5roWfVU35dXBE5PoTPJGP5ZgKVRQ/kJeD58oNORu70SnMhHyu a2qbyDVtc64mhq7uq8beylPd4H9lLRfras95EwKH+U9SAF8a9hh1H7a+Lxpb91mx 8ZarUQziSX2xMiOCtGPi2RDEJBdC4mVIfizQD536Aznp7OerRzkKwpW2aSLOJU2X rBlm96mGH79ekvt+pQbh+1PqsnA5feb96bWVq4CwCFCrhCcz7C1rFy4aN3LFNoIx vBGdpwRKdY6CColddqY2Yj73IebF9gMNrOybM69Q0xDvEOQVGTWP29yuKUdOQoKp FslNIATxITml4HpTBmI0Mh8wDMoNq7q47d0XzmmGvESbN+7gqR9XCBqvaBb7EALG XDNPBo55Zflgh82GpRbKcSV888pESTsYviZrtlpMFHIDH9kztaThTFX0eygZUPik 5Se+yKBpdB5BChVQznhemFTcKZcmvar1Eb1Hn9wKLUFZTlHs9Ecxu8uK5kAXN6Eq EGKJBSsto/RrmLC46WQaDbEDylzPRSAVBnkcAP+se0lTqTzulgA= =w1LF -END PGP SIGNATURE-
Re: [RFC] Dropping Python2 support for my package
On Sat, Jan 12, 2019 at 04:28:26PM +0100, Bastian Venthur wrote: > The question is: if I drop Python2 support, what > happens with the package names? Should I simply provide the > python3-debianbts and drop python-debianbts, or shall I attempt some > kind of migration to make the python-debianbts the new default package > name for Python3? just drop the python-debianbts binary, without doing any kind of strange migration, and keep the name python-debianbts for the python3 package, as the Debian Python Policy states. -- regards, Mattia Rizzolo GPG Key: 66AE 2B4A FCCF 3F52 DA18 4D18 4B04 3FCD B944 4540 .''`. more about me: https://mapreri.org : :' : Launchpad user: https://launchpad.net/~mapreri `. `'` Debian QA page: https://qa.debian.org/developer.php?login=mattia `- signature.asc Description: PGP signature
[RFC] Dropping Python2 support for my package
Hi, I'm about to drop Python2 support for python-debianbts. Currenty the source package produces two packages: python-debianbts and python3-debianbts. The question is: if I drop Python2 support, what happens with the package names? Should I simply provide the python3-debianbts and drop python-debianbts, or shall I attempt some kind of migration to make the python-debianbts the new default package name for Python3? Thanks for your hints! Bastian -- Dr. Bastian Venthur https://venthur.de Debian Developer venthur at debian org
