Bug#1109742: upgrade-reports: No new SSH connections possible during large part of upgrade to Debian Trixie
On Thu, Jul 24, 2025 at 09:36:43PM +0100, Colin Watson wrote:
> On Thu, Jul 24, 2025 at 06:44:21PM +0200, Salvatore Bonaccorso wrote:
> > IMHO, as this is not a security-update releaseing via a DSA is wrong,
> > but the correct target would be preparing it for bookworm point
> > release but release the updates with the reasoning above earlier via a
> > SUA (the release team obviously have to agree with that suggestion).
> > But IMHO stable-updates would be a perfect candidate for this usecase,
> > correct?
>
> I think I'd somehow managed to miss that SUAs were a thing. Yes, if the
> release team is happy with that then it sounds fine to me.
Yes please, at least for SRMs. stable-updates was my first thought when I
saw this bug and it's exactly the case they are designed for. The trixie
part will still need a normal unblock.
Please bear in mind that wider pre-release testing of SUAs is approximately
zero, so no pressure :)
Thanks,
--
Jonathan Wiltshire jmw@debian.org
Debian Developer http://people.debian.org/~jmw
4096R: 0xD3524C51 / 0A55 B7C5 1223 3942 86EC 74C3 5394 479D D352 4C51
ed25519/0x196418AAEB74C8A1: CA619D65A72A7BADFC96D280196418AAEB74C8A1
Reply to: