Bug#1109742: upgrade-reports: No new SSH connections possible during large part of upgrade to Debian Trixie

Jonathan Wiltshire <[email protected]> Sat, 26 Jul 2025 20:46:27 +0100
Newsgroups gmane.linux.debian.user.testing
Message-ID <aIUwkwzw1Gd3D-9s__31594.1547321685$1753559367$gmane$org@powdarrmonkey.net>
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,