Re: Bits from the Release Team: ride like the wind, Bullseye!
Le 07/07/2019 à 03:47, Jonathan Wiltshire a écrit :
> No binary maintainer uploads for bullseye
> =========================================
>
> The release of buster also means the bullseye release cycle is about to begin.
> From now on, we will no longer allow binaries uploaded by maintainers to
> migrate to testing. This means that you will need to do source-only uploads if
> you want them to reach bullseye.
>
>
> Q: I already did a binary upload, do I need to do a new (source-only) upload?
> A: Yes (preferably with other changes, not just a version bump).
>
> Q: I needed to do a binary upload because my upload went to the NEW queue,
> do I need to do a new (source-only) upload for it to reach bullseye?
> A: Yes. We also suggest going through NEW in experimental instead of unstable
> where possible, to avoid disruption in unstable.
>
> Q: Does this also apply to contrib and non-free?
> A: No. Not all packages in contrib and non-free can be built on the buildds,
> so maintainer uploads will still be allowed to migrate for packages
> outside main.
Q: BinNMUs of packages uploaded before this new policy that have
arch:all binaries can no longer migrate to testing. Is that
intentional?
See for example ocaml-migrate-parsetree/amd64 (there are others).
This will make transitions that involve lots of binNMUs (such as
OCaml-related ones) much harder. For example, there is one such ongoing
(mini-)transition involving ocaml-migrate-parsetree, 26 other binNMUed
packages, and 7 updated packages. It will be delayed by the time to
upload all these binNMUed package and their aging. Meanwhile, this
transition may become bigger and longer as people unaware of this update
their OCaml-related packages.
Is there a public API to query the built-on-buildd flag for a given
binary package?
Cheers,
--
Stéphane
Please CC: me or debian-ocaml-maint on reply
Reply to: