Bug#926701: [tlbuild] Bug#926701: dvisvgm binary fails to link on GNU Hurd
Am 26.07.2019 um 14:28 teilte Norbert Preining mit:
On Fri, 26 Jul 2019, Hilmar Preuße wrote:
Hi,
Yes. It has to got through the new queue. Once this is done we can care
Just to check, going to NEW do we need to do source only or
source/binary uploads? Do you remember?
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.
Hilmar
--
#206401 http://counter.li.org
Reply to: