1. Forum
  2. Usenet
  3. LINUX.DEBIAN.ANNOUNCE.DEV

  • Temporary freezes of udeb-producing packages for d-i releases

    From Cyril Brulebois@21:1/5 to All on Mon Sep 12 16:40:01 2022
    Hi,

    This mail is mostly a reminder of an existing practice documented in
    similar mails a few years ago, but I thought it wouldn't hurt to mention
    that process again. Even more so since it's been a while since the last
    such freeze…

    https://lists.debian.org/debian-devel-announce/2014/08/msg00003.html
    https://lists.debian.org/debian-devel-announce/2018/06/msg00002.html


    So it's been a few years now, and packages producing udebs are still
    getting frozen from time to time, when a Debian Installer (d-i) release
    is getting prepared. The list of currently affected packages can be
    found in the following release hints file:

    https://release.debian.org/britney/hints/freeze

    If you want to learn a bit more about the reasons behind this, you can
    read the following blog post of mine:

    https://mraw.org/blog/2014/08/10/Why_is_my_package_blocked/

    TL;DR: d-i is built upon many moving parts, testing takes some time and sometimes regressions happen right before final installation images get
    built. Avoiding such situations is the reason behind such udeb freezes.


    As a maintainer, if you feel your package should be unblocked during
    such a udeb freeze, you can file an “unblock” request against the release.debian.org pseudo package, mentioning the block-udeb you'd like
    to get an exception for. Bonus points if you include debian-boot@ and
    kibi@ in X-Debbugs-Cc directly so that the installer team notices you're requesting to get an exception. The release team would usually contact
    us anyway, but looping us in from the start can increase your chances of getting a swift reply.

    Depending on the amount of changes and (planned or tested) consequences
    for d-i, your package might be unblocked or might wait until after the
    release has been published.


    Looking at the previous release cycles, such freezes usually last for a
    few days only, from a given debian-installer upload until installation
    images have been built successfully, and haven't found to be crippled
    with obvious bugs.

    The freeze for the Debian Installer Bookworm Alpha 1 release should
    happen this week, and will be lifted as soon as the release is
    published.


    Thanks for your attention and for your patience.


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

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

    iQIzBAABCgAdFiEEtg6/KYRFPHDXTPR4/5FK8MKzVSAFAmMfQ3oACgkQ/5FK8MKz VSB3+Q/9G3iol+Cm1CEri9ZwwzKpDEfocfJa4xWQZDnh8IWz1Qu57y8C/258qjD9 HT0fMTY7c1hdTtcd/5ky90a32fiypJueX3k87vhQ+HITuj44WhxL8alkQ2Qr/JIp EcAfplESB5YTn1+NSHJh5h4Q+uGZAm5Qx2EweiwOe1e55gZDuBFbPAu7tE1m51FC kGSGviZnsCLXqLZFxW5zPeXY95zzipRXtsqoCFgyp8beKveHotD1PZ/w8lQ1hz2w 6TQVJI+42pRo4dVcZ8boaqadepmnfmmL5jVGZkueJ30RXK4RXKtVcBunuq8ggkOk 84Vvtt5Jms4AKKCELcIg3bdvDsD7G5DjiHSlmWwp6UH9Mz9XRDPzHKOTxzqu6Osr h105pmGIBZ2gRyb26vxTakNrxu7+aUSy8L4h3fAPA65FRY1gUU7jDEhFcxvdF44E CuSqtPOnfREzWC6XKQ7sjjxTNCBLuvB2n9L6x7dQOYHcbpDDgecNoj9dYdrQAs2N zHMTrk5UvwGSY+zjWUrMweE27Jux2kkCHR2d9Tq9eZoAxhCAup37TqcCypWSrk7G VzPDSqns9WaxRDPnuEWGID+XsQyLXLbEdrM8we7IdNrDeljRWW3QXwpIZA7LKXrW F9ll+wH8/G8k0M8pqtD+kXPRR5p0bbQFSBX61CGbjDyffZZuN04=
    =U5DG
    -----END PGP SIGNATURE-----

    --- SoupGate-Win32 v1.05
    *
  • From Cyril Brulebois@21:1/5 to All on Thu Dec 26 02:40:01 2024
    Hi,

    This mail is mostly a reminder of an existing practice documented in
    similar mails over the years, but I thought it wouldn't hurt to mention
    that process again. Even more so since it's been a while since the last
    such freeze…

    Packages producing udebs get frozen from time to time, when a Debian
    Installer (d-i) release is getting prepared. The list of currently
    affected packages can be found in the following release hints file:

    https://release.debian.org/britney/hints/freeze

    If you want to learn a bit more about the reasons behind this, you can
    read the following blog post of mine (yes, that was 10+ years ago):

    https://mraw.org/blog/2014/08/10/Why_is_my_package_blocked/

    TL;DR: d-i is built upon many moving parts, testing takes some time and sometimes regressions happen right before final installation images get
    built. Avoiding such situations is the reason behind such udeb freezes.


    As a maintainer, if you feel your package should be unblocked during
    such a udeb freeze, you can file an “unblock” request against the release.debian.org pseudo package, mentioning the block-udeb you'd like
    to get an exception for. Bonus points if you include debian-boot@ and
    kibi@ in X-Debbugs-Cc directly so that the installer team notices you're requesting to get an exception. The release team would usually contact
    us anyway, but looping us in from the start can increase your chances of getting a swift reply.

    Depending on the amount of changes and (planned or tested) consequences
    for d-i, your package might be unblocked or might wait until after the
    release has been published.


    Looking at the previous release cycles, such freezes usually last for a
    few days only, from a given debian-installer upload until installation
    images have been built successfully, and haven't found to be crippled
    with obvious bugs.

    The freeze for the Debian Installer Trixie Alpha 1 release should happen
    in the next few days, and will be lifted as soon as the release is
    published.


    Thanks for your attention and for your patience.


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

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

    iQIzBAABCgAdFiEEtg6/KYRFPHDXTPR4/5FK8MKzVSAFAmdssdgACgkQ/5FK8MKz VSBFKA/9HT1HeO2BM1pF9XjZMmnXaRdiKATBW9PF5PGJzsS6YfHu2R5dGKsk7kHi FHM7DpG3Cv3PEBLgIGCZJCJj2Jlxb54CRCe3eWwTRC3oy5C+pQadGJ0dvVe97vbu DTaPyWpvjTvN4ocoyr7IUGzY0rQC+Vd3juknuICP+ih7QXYuUe0Ag89H7r1xkZQ5 cwymX4D/UNa0Cj7kO3mVEmmDCIgZ4LzfvRQ4eqZiEz3RQNBD0B2rpfONzdrbXbFA gr+6ff++nkTsnjY2lQN/c8PoNF5R1DqwTZ0qvWjep1mrr2f2/2j2BOdo3s8sM/T9 7izp3GZry3c9PiSJLPgrennpnpIa9nIWdU1YKne0Ah2uh9r+kxkHyI1mQ5zbCNu1 5SUyAXf6+RM/KiQ+pq0OaLzQ7eyzsWR9kJaVQ+tQW3D6tw3okl8Xtl7wVGZNVcFV wpl2F0/QTNst8fHvoE1vqvjwMouXiRg22KSu3YycQ7KHEyrWnZUngbk2O2Rq0Kce Yv5PsbHYogUIkUfBdRbh/A9M3X+VKxM0CVvTXebzX7MWVWcDt2h8M5/ik+g/JOsS GL1FhX88ovQQSpZyiO/kC14XMuqmakUWV+TJVUtH71cMH2SuCVXGlaij3YnQtQo/ A4gfYRV4pqQmTyDajZ5UHf3KU/BZHgfDJ9h/Vn4IXTpIOuApVlw=
    =AV63
    -----END PGP SIGNATURE-----

    --- SoupGate-Win32 v1.05
    *