-----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-----
