1. Forum
  2. Usenet
  3. LINUX.DEBIAN.DEVEL.RELEAS

  • Uploading linux (6.12.32-1)

    From Salvatore Bonaccorso@21:1/5 to All on Thu Jun 5 22:10:01 2025
    XPost: linux.debian.kernel, linux.debian.maint.boot

    Hi

    I would like to upload the next version of the 6.12.y stable series to
    unstable (once linux/6.12.30-1 migrates to testing). There are two
    upstream stable versions imported, 6.12.31 and 6.12.32 where 6.12.31
    was of considerable size (note there is onging merge window for 6.16
    ongoing and from experience the first few stable series are bigger
    than usual, this might not be the best timing for trixie).

    There will be some changes on the packaging side:

    * [amd64] drivers/acpi: Make ACPI_HED built-in
    * [amd64] Add drivers/pinctrl/intel to kernel-image udeb (Closes: #1106658)
    * linux-image, linux-headers: Use linux-run-hooks instead of run-parts
    (Closes: #1101733)
    * drivers/net/can: Enable can327 as a module
    * drivers/gnss: Enable GNSS_MTK_SERIAL and GNSS_USB as modules
    (Closes: 1106744)

    We know that for beeing ready for trixie we need to find yet a
    solution for
    https://salsa.debian.org/kernel-team/linux/-/merge_requests/1524 (and
    to allow multiple uploads of one upstream version for instance if we
    need to pick a single fix for security reasons and needs to be pushed
    earlier than the next upstream stable version).

    Regards,
    Salvatore

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

    iQKTBAABCgB9FiEERkRAmAjBceBVMd3uBUy48xNDz0QFAmhB9+NfFIAAAAAALgAo aXNzdWVyLWZwckBub3RhdGlvbnMub3BlbnBncC5maWZ0aGhvcnNlbWFuLm5ldDQ2 NDQ0MDk4MDhDMTcxRTA1NTMxRERFRTA1NENCOEYzMTM0M0NGNDQACgkQBUy48xND z0SI4w/8DDkqFxzwvL/TisNQkUWqKrogAiAH6aByTJKH9lrfU4b4XHy8oJLRJHX9 4IW/4CG+01lacONYF6hfK0ZuORLz7haeEOVkQlebXnqY0q/ez8vx+ZnfCX5rTbwO Y8iYhhTKBDxvUYJzueGxcas9F1msq9EdXdHK+5YJQ/bi57m/MDgDKZjiwevRrClj SUAVDa8tKO9rfPWsRD0QMY4g/xYwrpetUbvg8P7bVLme/bABJVsG/kFGlacm8VsA 97JjBu3qKXLGMCp7bq+iytLbA8ESt9lHyQ0v09tHoeD5orcC5IGn6S9SoSgVSZVO j8IsSsKDjN7QvyBs5mRaIphZfCma4hbHAVAHSwoEjnt2/BrhQaXEfGk18F1HBLox Z3XHhCIxdwKIP7LBn7wP8SxQkifV4QKVjjA+BLPTlc6he/AN7kkX8r5lqc3vqR+m ATf3a78y9gUk789gK030ococRHnkwOpHlTaEhvNs64Laknw0ZvoMJq0gPNrGdvIX n+I+klu/9d8v2Cx/ZQYfZDp+HL56KF6X+XnUfnZbkAW9f7IfB5cS6YNV56LUBcMg K4Zz9JfQ5BIHkoHUZ2QXirtWuHsyAtS9npYO66YLPn17q41PG7WKF43HbPqP88mc rIDAuCfLZiZhHxiUZYV5OkDZc368/e4EZsDHidIXL0OFIeHp0lQ=
    =wZzQ
    -----END PGP SIGNATURE-----

    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)
  • From Cyril Brulebois@21:1/5 to All on Thu Jun 5 22:30:01 2025
    XPost: linux.debian.kernel, linux.debian.maint.boot

    Hi,

    Salvatore Bonaccorso <[email protected]> (2025-06-05):
    I would like to upload the next version of the 6.12.y stable series to unstable (once linux/6.12.30-1 migrates to testing). There are two
    upstream stable versions imported, 6.12.31 and 6.12.32 where 6.12.31
    was of considerable size (note there is onging merge window for 6.16
    ongoing and from experience the first few stable series are bigger
    than usual, this might not be the best timing for trixie).

    (Yeah, at this point it seems wise to let .30 migrate.) I don't have a
    precise timing for the next d-i release (there are things to consider
    which I have little control over), but given we're getting deeper and
    deeper into the freeze, maybe we're closer to the point where we should anticipate stopping kernel uploads, and staging them for publication via
    either trixie-proposed-updates (once 13.0 is published) or DSA depending
    on the security impacts?

    Anyway, at this point, still no objection to an extra upload.

    We know that for beeing ready for trixie we need to find yet a
    solution for
    https://salsa.debian.org/kernel-team/linux/-/merge_requests/1524 (and
    to allow multiple uploads of one upstream version for instance if we
    need to pick a single fix for security reasons and needs to be pushed
    earlier than the next upstream stable version).

    Oh, new challenges. G'luck!

    Just out of curiosity: there is no plan to change what the versioning
    looks like in bookworm(-proposed-updates) or bookworm-security, right?


    Cheers,
    --
    Cyril Brulebois ([email protected]) <https://debamax.com/>
    D-I release manager -- Release team member -- Freelance Consultant

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

    iQIzBAABCgAdFiEEtg6/KYRFPHDXTPR4/5FK8MKzVSAFAmhB/KkACgkQ/5FK8MKz VSDLCA/+OodZyk6Ol46hdNfdH5jrivrUNYSG8p5zyQYMqW7bVZ+yeW1/VkJTNj7I naxpXnvsTwX26qf9oWNkIlQAju3Q1pm95zdlmtXqn73WsPHlmB8inT9A6ejBSeTV NLeWCrEWfzW0dWPURr83qhnVIMnEZM2HBkF18mG39EV2oNtkxm39BfV9MYJUQbU3 1NeSvYmy0oq4lMC3PKylaQ9BwW8Dn/DSUcY5ar6Q7r1h7wGwB4/U6bIw1zkexrmO 9rmAybIfQsDuwQu50y/2nT9sOsAKQgIIRCy4HoTW2Jtm3lgENGoDwBO999E46Kz3 6hnEjWkqCtslImxslZf7h9jPhwb6RsCu7t7vzO3E6isyH+GSXqh2WL2+DUwuVaOd ZbTp184IQ5hKmpkY1vnyZwX9THWy6qsrNtxkDMCfd06O++DQMl7x4+CBxWCGG+QC EBBDzMb5Vw/uOyPVaATFuuHVy71dl7sEj8eoocZhMcG7fq3SWorcPqBSgjuNPvtl 5QbPtv5wqWHJDYQ2dqFqLu2KT33xQmbkpBQMa39Oz7xvWktpDB1D8tZM6mlPtuEL 5WxPw9Z6in1+VMIxX69Dj8OlEo/yDQeSU5Krbw7j9CY3zd7PCWUKS4BFZkODhSZ7 EaXLmB73b58suDuxwunCUsQAUEqRhpIRUsc39t/wGR64lyeyv3I=
    =FTgP
    -----END PGP SIGNATURE-----

    --- SoupGate-Win32 v1.05
    *
  • From Salvatore Bonaccorso@21:1/5 to Cyril Brulebois on Sat Jun 7 09:30:01 2025
    XPost: linux.debian.kernel, linux.debian.maint.boot

    Hi Cyril,

    On Thu, Jun 05, 2025 at 10:23:08PM +0200, Cyril Brulebois wrote:
    Hi,

    Salvatore Bonaccorso <[email protected]> (2025-06-05):
    I would like to upload the next version of the 6.12.y stable series to unstable (once linux/6.12.30-1 migrates to testing). There are two
    upstream stable versions imported, 6.12.31 and 6.12.32 where 6.12.31
    was of considerable size (note there is onging merge window for 6.16 ongoing and from experience the first few stable series are bigger
    than usual, this might not be the best timing for trixie).

    (Yeah, at this point it seems wise to let .30 migrate.) I don't have a precise timing for the next d-i release (there are things to consider
    which I have little control over), but given we're getting deeper and
    deeper into the freeze, maybe we're closer to the point where we should anticipate stopping kernel uploads, and staging them for publication via either trixie-proposed-updates (once 13.0 is published) or DSA depending
    on the security impacts?

    Anyway, at this point, still no objection to an extra upload.

    Ack.

    Yes we need to agree on when to stop doing further stable updates for
    trixie and postpone them for a DSA or trixie-proposed update, and I'm
    all ear when you think we should stop. As hopefully clear, we want to
    do here our best to support the release team and debia-boot work
    towards the trixie release.


    We know that for beeing ready for trixie we need to find yet a
    solution for https://salsa.debian.org/kernel-team/linux/-/merge_requests/1524 (and
    to allow multiple uploads of one upstream version for instance if we
    need to pick a single fix for security reasons and needs to be pushed earlier than the next upstream stable version).

    Oh, new challenges. G'luck!

    Well yes we are bit late on this.

    Just out of curiosity: there is no plan to change what the versioning
    looks like in bookworm(-proposed-updates) or bookworm-security, right?

    No there is no plan to change the versioning for bookworm and bookworm-security. And note the version for trxie imports will remain
    still e.g. 6.12.33-1.

    Regards,
    Salvatore

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