Bug#1106070: Raising the severity?

From	Cyril Brulebois <kibi@debian.org>
Newsgroups	linux.debian.bugs.dist, linux.debian.maint.boot, linux.debian.devel.release, linux.debian.kernel
Subject	Bug#1106070: Raising the severity?
Date	2025-05-25 17:10 +0200
Message-ID	<KQl98-5EiB-11@gated-at.bofh.it> (permalink)
References	<KO64x-4c2e-5@gated-at.bofh.it> <KQfZL-5AZC-1@gated-at.bofh.it> <KQkPL-5DVJ-5@gated-at.bofh.it> <KO64x-4c2e-5@gated-at.bofh.it> <KQkPL-5DVJ-5@gated-at.bofh.it>
Organization	Debian

Cross-posted to 4 groups.

Show all headers | View raw

[Multipart message — attachments visible in raw view] - view raw

Hi,

To be honest, I almost asked what the plans were for 6.12.29-1 regarding
this issue, and whether Severity: important was appropriate. But I got
busy with other things and let this fly…

Salvatore Bonaccorso <carnil@debian.org> (2025-05-25):
> I see your point and having though the ITS mitigations in my opinion
> is more important. But stepping a bit back I fully understand as well
> your point of view.
> 
> Cyril and Debian boot people, would you actually want to not get
> 6.12.29-1 into trixie? 

Regarding the installer itself, I'm fine with either having .29 then .30
or just waiting for .30. I definitely can see how live people might want
to avoid a known broken kernel's reaching testing though.

> FWIW, the next upload *will* include a fix for the loop issue. I have
> already imported 6.12.30 for the packaging and marked the loop fix as
> to be backported to 6.12.

Great news!


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

Thread

Bug#1106070: Raising the severity? Salvatore Bonaccorso <carnil@debian.org> - 2025-05-25 16:50 +0200
  Bug#1106070: Raising the severity? Cyril Brulebois <kibi@debian.org> - 2025-05-25 17:10 +0200
    Bug#1106070: Raising the severity? Salvatore Bonaccorso <carnil@debian.org> - 2025-05-25 20:40 +0200

csiph-web