Re: Uploading linux (6.12.32-1)

[Salvatore Bonaccorso]

Hi Cyril,

On Thu, Jun 05, 2025 at 10:23:08PM +0200, Cyril Brulebois wrote:
> Hi,
> 
> Salvatore Bonaccorso  (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

Re: Uploading linux (6.12.32-1)

[Cyril Brulebois]

Hi,

Salvatore Bonaccorso  (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 (k...@debian.org)
D-I release manager -- Release team member -- Freelance Consultant


signature.asc
Description: PGP signature