On Tue, Dec 31, 2019 at 04:35:22PM +0100, Sebastiaan Couwenberg wrote: > On 12/31/19 4:20 PM, Andreas Metzler wrote: > > as Bas correctly diagnoses I am not currently building for all supported > > versions but only for the default one because it is not trivial but > > requires some work. Looking at python policy I think that is acceptable > > but not perfect. > > > > Is my reading of polic correct? > > AFAIK the python policy doesn't document the build dependencies. It does: https://www.debian.org/doc/packaging-manuals/python-policy/build_dependencies.html > doko filed bugs for at least one of my packages that had python3-all-dev > in B-D but only built for the default interpreter with the request to > change the B-D or build for all supported versions, so either option is > fine. Indeed. Building for all supported python versions makes these kind of transitions much easier, but either variant is fine. > > Shall I make a timely upload fixing the > > build-dependency or can I wait for propagation of vigra packages to > > testing? > > I would commit the change now, and upload it after the testing migration > unless there are other blockers that hold up the migration for more than > 5 days, then I would upload it now. ACK. I likewise recommend waiting those 2 more days and then upload the build-dep change. Either that or add an autopkgtest in the same upload now ;) -- 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 `-
Attachment:
signature.asc
Description: PGP signature