Releasing glibc to groovy-updates breaks Ubuntu Desktop installer when 3rd party software and online updates are enabled

[Balint Reczey]

See LP: #1871268.

The Desktop installer needs to have fixed APT installed to make releasing glibc safe.

A possible fix is updating the Groovy installer to have the latest APT.

[Steve Langasek (vorlon)]

We do not do point releases of non-LTS releases except in extremis.

As far as I can tell by looking at https://launchpad.net/ubuntu/+source/glibc/2.32-0ubuntu3.1 the rationale for this SRU is groovy is not that it's important to fix these bugs on groovy, but that SRU policy requires us to fix bugs in the stable interim releases when we fix them in the LTS release. This SRU policy is not adequate justification for doing an extra point release in order to address a functional regression introduced by a low-priority SRU.

We should verification-failed the groovy glibc SRU, remove it from -proposed, and ignore this issue, hoping that we don't get any urgent security bugs in glibc in the next 6 months.

[Balint Reczey (rbalint)]

@vorlon Please don't remove the package from -proposed. I'd like to fix LP: #1899800 in Focal, and the package in Groovy's proposed is good for testing it. People can also use the package from groovy-proposed should they need fixes for any of the other bugs.