Hi Fred, On 22-09-2022 16:34, picca wrote:
I removed the 32bit arch which are not supported by the upstream of cctbx from the cihttps://salsa.debian.org/science-team/cctbx/-/blob/master/debian/tests/control#L13 So my question is why cctbx doe not migrate after 2 days instead of 5 days.
The question is more appropriate for email@example.com, but I would have still be the one that would have answered it.
The point is that the faster migration is only applied if the package has an autopkgtest and it runs successfully on all architectures where binaries are available. In this case, you only disabled the autopkgtest on 32 bit archs, but the binaries are still successfully build.
I know it is only 1 days but it was the same with the previous migration https://tracker.debian.org/pkg/cctbx thanks for the explainations and even better a way to fix this :)
Make sure that there are non-trivial passing tests those archs :) (please don't cheat ). The alternative (if the binaries don't work on these architectures) is to stop building there and ask the ftpmasters to remove the old ones.
Paul See e.g https://release.debian.org/testing/rc_policy.txt 6(a) and https://release.debian.org/testing/freeze_policy.html#before what we say about the non-trivial requirement.
Description: OpenPGP digital signature