[Bug 1962225] Autopkgtest regression report (glibc/2.31-0ubuntu9.8)

[Ubuntu SRU Bot]

All autopkgtests for the newly accepted glibc (2.31-0ubuntu9.8) for focal have finished running.
The following regressions have been reported in tests triggered by the package:

ruby-stackprof/0.2.15-2 (arm64)
sphinxbase/0.8+5prealpha+1-8 (armhf)
r-cran-ps/1.3.2-2 (s390x)
linux-hwe-5.13/5.13.0-37.42~20.04.1 (armhf)
mercurial/5.3.1-1ubuntu1 (armhf, ppc64el)
linux-hwe-5.11/5.11.0-61.61 (armhf)
mbedtls/2.16.4-1ubuntu2 (s390x)
libreoffice/1:6.4.7-0ubuntu0.20.04.4 (armhf)
ruby-ferret/0.11.8.7-2 (amd64)
cross-toolchain-base/43ubuntu3.1 (ppc64el)


Please visit the excuses page listed below and investigate the failures, proceeding afterwards as per the StableReleaseUpdates policy regarding autopkgtest regressions [1].

https://people.canonical.com/~ubuntu-archive/proposed-
migration/focal/update_excuses.html#glibc

[1] https://wiki.ubuntu.com/StableReleaseUpdates#Autopkgtest_Regressions

Thank you!

-- 
You received this bug notification because you are a member of Ubuntu
Foundations Bugs, which is subscribed to glibc in Ubuntu.
https://bugs.launchpad.net/bugs/1962225

Title:
  preinst check that kernel revision < 255 now does more harm than good

Status in glibc package in Ubuntu:
  Fix Released
Status in glibc source package in Bionic:
  Confirmed
Status in glibc source package in Focal:
  Fix Committed

Bug description:
  [impact]
  Amazon Linux 2 currently has a kernel with version 4.14.262-200.489.amzn2.x86_64. This causes complaints from libc6's preinst that asserts that the "revision" part of the kernel version is less than 255.

  The significance of the check is much less than it used to be when the
  major part of the kernel version was stuck at 2, so we should follow
  Debian and just drop it.

  [test case]
  Boot an Amazon Linux 2 instance. Install docker. Run an ubuntu container of the series being tested. Run "apt-get update && apt-get install --reinstall libc6" and look for error messages / failures.

  [regression potential]
  It's possible that some binaries run using the "uname26" personality will fail -- but they will already fail with the glibc as currently installed, there's no value in preventing an upgrade.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/glibc/+bug/1962225/+subscriptions