Bug#947365: transition: libvigraimpex
On 2019-12-31 Sebastiaan Couwenberg <sebastic@xs4all.nl> 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.
> 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.
Hello,
Thanks for clearing this up. I was just unsure whether not building
for all suppported versions was acceptable.
>> 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.
Afaict the involved packages should propagate to testing in 3 days, when
enblend-enfuse is old enough. I have commited the fix. [1]
cu Andreas
[1] https://salsa.debian.org/ametzler/libvigraimpex/commit/c5a8c27cc018c8968036b73c39d0d02d0f229320
Reply to: