Comment 17 for bug 2002429

Hm, maybe I've been unclear.

What I mean is: while the launchpad buildds don't use gcc-11 for anything in kinetic onwards, launchpad buildds aren't the only users of a compiler and the Ubuntu kernel is not the only thing that users of a compiler might compile.

gcc-11 is a package available in the archive, and users can use it¹, regardless of the particular rationale that *we* have for including it in the archive. If a jammy user is deliberately using gcc-11 I would expect that upgrading to kinetic would not regress any fixes we've made to the jammy package.

I don't *think* we have a policy that non-default compilers are not subject to the usual SRU policy? If we do, maybe that should be better communicated :)

Again, I'm OK with deciding to tell users of gcc-11 that to get this fix they need to either stay on Jammy or upgrade all the way to Lunar. I just want to make sure that we've actively decided to tell users this is unsupported, rather than just verifying that it doesn't affect *us*.

¹: Maybe they're working around a gcc-12 miscompilation, or don't want to revalidate gcc-12 just now, or just like the number 11.