Bug#1016287: closed by Paul Gevers <elbrus@debian.org> (Re: Bug#1016287: release.debian.org: autopkgtest 2 to 5 days since addition of armel)
> Hi Jérémy,
>
> On 29-07-2022 19:36, Jérémy Lal wrote:
> > when a package pass all autopkgtests it can migrate in 2 days,
> > however if it depends on an architecture that reports "Not a
> > regression",
> > it seems that the bonus is lost and the package must wait 5 days.
>
> That's by design.
>
> > The problem is that it happens when a package depends on a package
> > that is not available in a given architecture.
>
> Unfortunately, that's indeed the price of that design. As we're
> supposed
> to try and support all architectures equally well, I decided that's
> acceptable.
>
> Paul
[...]
> Hi Jérémy.
>
> On 29-07-2022 22:17, Jérémy Lal wrote:
> > I don't see how artificially adding migration days will improve
> > debian quality in any way.
>
> We're not adding days, we're just not giving the bounty for success on
> all architectures where we run autopkgtests, which was the rule for
> the bounty.
>
> Paul
Hi,
this is not just a matter of bounty, but the key to upload during freeze.
Node.js isn't available on armel, and the consequence will be to not fix
some CVEs/BTS during freeze. Hope none of them will appear...
Maybe Britney could not consider autopkgtest as failing when a build
dependency is missing in one arch (at least for arch=all) ? Most of
node-* package build depends on nodejs but are usable without it. See
libjs-bootstrap4 for example
Reply to: