On Mon, 12 May 2025 at 19:58:10 +0200, Cyril Brulebois wrote:

For various reasons, I'll be trying to get D-I Trixie RC 1 out this
week, and I might freeze udeb-producing packages right away, or in the
very next few hours/days.

As a general rule, would you prefer maintainers of udeb-producing
packages to wait for your pre-approval before uploading anything
non-urgent to unstable during this period; or is it OK to upload to
unstable, and rely on the block-udeb hints to prevent our packages from reaching testing at an inconvenient time?

(subject to the usual release team approval, "targeted changes only",
etc. that apply to all frozen packages whether they have udebs or not)

Thanks,
smcv

--- SoupGate-Win32 v1.05
* Origin: fsxNet Usenet Gateway (21:1/5)

XPost: linux.debian.maint.boot

Hi Simon,

[ cc += debian-boot@ for information ]

Simon McVittie <smcv@debian.org> (2025-05-12):

As a general rule, would you prefer maintainers of udeb-producing
packages to wait for your pre-approval before uploading anything
non-urgent to unstable during this period; or is it OK to upload to
unstable, and rely on the block-udeb hints to prevent our packages
from reaching testing at an inconvenient time?

I've just done some picking and choosing between packages that show up
on <https://d-i.debian.org/testing-summary.html>; some of them looked
like things I needed or that made sense to have in trixie, some of them
looked like “unimportant” updates that could wait, and I've ignored
them. I haven't been consistent, but you can check debian-boot@ and/or debian-release@ from the last few hours for some public queries sent to maintainers/uploaders, as I tried to find the right balance:
https://lists.debian.org/debian-boot/2025/05/msg00153.html
https://lists.debian.org/debian-boot/2025/05/msg00155.html
https://lists.debian.org/debian-boot/2025/05/msg00175.html

(The linux kernel hinting was already managed earlier, the installer and
kernel teams have had a little routine for a number of release cycles.)

If you have packages with important changes (like that was the case for openssh, xorg-server), it's probably best to wait before uploading less important (but possibly worrying/distracting to me) things to unstable,
so that the existing packages might be picked up/pushed (either because
I'm doing that on my own — usually for debian-boot@ packages or things
that got patched because we asked — or because I'm told I really
should). Freezes usually don't last long, so I don't recall receiving
many requests to look at this or that package for an unblock-udeb (or
an age-days/urgent). Maybe also because the initial choice of packages
(see first paragraph) isn't too crazy to begin with (hopefully).

If testing and unstable are in sync already, and if you don't care when
it migrates, uploading to unstable without any pre-approval *should* be
fine. I'm sure we might be able to construct, or might even encounter, counterexamples, but I lack imagination right now.

(subject to the usual release team approval, "targeted changes only",
etc. that apply to all frozen packages whether they have udebs or
not)

(sure)


Cheers,
--
Cyril Brulebois (kibi@debian.org) <https://debamax.com/>
D-I release manager -- Release team member -- Freelance Consultant

-----BEGIN PGP SIGNATURE-----

iQIzBAABCgAdFiEEtg6/KYRFPHDXTPR4/5FK8MKzVSAFAmgkARoACgkQ/5FK8MKz VSBNVw//fbq2kDczKtOCp2U+mrCqTFGpNrI9PS4s0OrUsr2BM8DF6FYYOiR5kUL1 rqGHLmrgEdhfCCOn/2R0pQuydkyzTrqUFVM/oVs5BDab+OyZQZcubUk2PCEuNUCE cy7ah8D/aKak3DL/jGl0hefuwrQ4qgXDyTbCbYPYFUmj1JNq37/agd1pNaVF1ckq taHK+Mb69IIaq/mHr7UMDCHy75HP553mM70PVLgDUbhOzs8KoD+RDzXX4/034R7e FuvYHVL3/HfUimR5dhen0vdeB5IumeRjvlXl/V2uFncYkezvWuX9bqxfg4ERDkJB jKaPkJvfb04o42yHsQ1Qw3Y3REIlCe2exJSOmgmS7iXCDGCNVljxKvhdox+iLp5o Ec6VOwvTvmXJpm0lMnu9MWCIBHjSKfJDpbau1dWGq2n/eWnOTs3mnvTWD6IZWLIy 8GU6jO9G/LC+SBRFL5JA1VzN2SRKRl970z/I0HEyNnWdy9C58/4kI+Y6SPl1N9/b 16OmLwzUrkhGugVHJ02dM4ADUBq682kuDQ2+B0s//PuHEOI0K0K7T4YkqGWKlcPw 1zjq5mTbia1lF8XZ8pe9957Jd1sYc5Jv7BYg5SPRoOL51Di+o9v3VVSIGBZ/B2+z 4pQPVR7j7lh9f3nBrTYfHcZnyr1rQjTcFgWL05IcW3wP/vun+0I=
=u9pQ
-----END PGP SIGNATURE-----

--- SoupGate-Win32 v1.05
*

XPost: linux.debian.devel.release

Hi,

Cyril Brulebois <kibi@debian.org> (2025-05-12):

I do realize it might make some maintainers nervous as the next few days
are the last ones before the hard freeze (scheduled 2025-05-15), and I
do apologize for creating this awkward situation.

The very few packages that were out of sync between testing and unstable
got very special attention (a little more than usual).

Most maintainers were contacted, and responded very positively either to
the proposed earlier migration or to the proposed “let's wait a little” approach.

The other ones weren't contacted because their packages were either too
young (so they were too late regarding the hard freeze anyway) or almost
ready (so they insta-migrated as soon as I lifted the “udeb freeze”) — cryptsetup, libpng1.6, lvm2, during the 16:00Z britney run this Friday.

That being said, the release team has agreed (should it be needed) to
have at least one britney run between my unfreezing udeb-producing
packages, and implementing the hard freeze.

I'm not aware of any other packages that might have been caught up in that last-minute “udeb freeze”, but feel free to reach out to me if you think I've caused any problems.

[ FTR: Tue May 13 21:04:17 2025 +0000 → Fri May 16 15:21:27 2025 +0000]

Thanks for your understanding and your patience.

Thanks to the maintainers I contacted and answered quickly and nicely,
thanks to those who might have been affected and decided to wait it out,
and to the release team for the leeway they were willing to give.


Cheers,
--
Cyril Brulebois (kibi@debian.org) <https://debamax.com/>
D-I release manager -- Release team member -- Freelance Consultant

-----BEGIN PGP SIGNATURE-----

iQIzBAABCgAdFiEEtg6/KYRFPHDXTPR4/5FK8MKzVSAFAmgnyc8ACgkQ/5FK8MKz VSCZhg/+KAA71FAymtIsJWjP90CVtRlQ5QLf3TfksKoFVSV0oombcFyR6osR52rm 0SMdcZ+1FaF4UGk2x72AmGzJfeSesUt7qpWchyj5kORCyjBXzeBEuXzFgGRBi22d HT2teUw0TfjhBCdlOEYlhBrIQjceSxNA0VjG0CVs0BK0DgTVOhYpZBbqkTFPFsOk 7SzeROiKKieYBql7DeG7w+fsvVLKdCKzB+PMIZTiohFYgC5RhKH4ZS/pwwMCSnTF QyTAWTxXuWs/sMdZNMOoaKrrGxNy1LNhleqS9WuOUuOMBn963tw/adpdse8pUV60 t5erLCLQIVIko9uMT7wnvjlCdGDaE4oW5l3dGJoGRBzCCmx3vzfnQ6SI+pwuwGW7 0m4dLrzfPL4IQ8BuLrwmUqatZhumBoHGdmOO4WWsTrX5LMZ9uwPTTL8mo9S4GrrY VaVW0kzwk/j3AI/GA0SBqx8qKsGDtuHhdjvQFGNWl9ZAttMf0eA1zazwobdOoy3z khgKR0eyoP4bYrglH3dbFo4O3JW9uLJnFph9yVGqrAzNPrXmm0a7zmKEQ7TKO+Q/ xR7kKP3fXecFbiURNg1Znc9n/kXeeYjidAKuQYEi4qn/qk14ssv6+jqN9qngJ72a FzZfihkXCcFFG6DITb+WFTviRM5CUGFSu4tr0a/Uz1LoKvqxVf8=
=scrh
-----END PGP SIGNATURE-----

--- SoupGate-Win32 v1.05
*