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.
** Changed in: ubuntu-cdimage
Status: New => Won't Fix
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1913307
Title:
Releasing glibc to groovy-updates breaks Ubuntu Desktop installer when
3rd party software and online updates are enabled
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-cdimage/+bug/1913307/+subscriptions
--
ubuntu-bugs mailing list
[email protected]
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
