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

Status changed to 'Confirmed' because the bug affects multiple users.

Same on Ubuntu 20.04.4 LTS on arm64

$ sudo apt-get --fix-broken install
Reading package lists... Done
Building dependency tree
Reading state information... Done
Correcting dependencies... Done
The following additional packages will be installed:
  libc6
Suggested packages:
  glibc-doc
The following packages will be upgraded:
  libc6
1 upgraded, 0 newly installed, 0 to remove and 6 not upgraded.
1 not fully installed or removed.
Need to get 0 B/2266 kB of archives.
After this operation, 7168 B disk space will be freed.
Do you want to continue? [Y/n] y
Preconfiguring packages ...
(Reading database ... 102158 files and directories currently installed.)
Preparing to unpack .../libc6_2.31-0ubuntu9.7_arm64.deb ...
ERROR: Your kernel version indicates a revision number
of 255 or greater. Glibc has a number of built in
assumptions that this revision number is less than 255.
If you\'ve built your own kernel, please make sure that any
custom version numbers are appended to the upstream
kernel number with a dash or some other delimiter.

dpkg: error processing archive /var/cache/apt/archives/libc6_2.31-0ubuntu9.7_arm64.deb (--unpack):
 new libc6:arm64 package pre-installation script subprocess returned error exit status 1
Errors were encountered while processing:
 /var/cache/apt/archives/libc6_2.31-0ubuntu9.7_arm64.deb
E: Sub-process /usr/bin/dpkg returned an error code (1)

$ uname -a
Linux k2 4.9.277-82 #1 SMP PREEMPT Fri Feb 18 14:35:13 UTC 2022 aarch64 aarch64 aarch64 GNU/Linux

$ cat /etc/lsb-release
DISTRIB_ID=Ubuntu
DISTRIB_RELEASE=20.04
DISTRIB_CODENAME=focal
DISTRIB_DESCRIPTION="Ubuntu 20.04.4 LTS"

Are there any suggested workarounds in the meantime? This started happening after the libc6-dev package (and its dependants: libc-dev-bin, libc6) were upgraded from 2.31-0ubuntu9.2 to 2.31-0ubuntu9.7.

I'm running on AWS CodeBuild (so amd64 arch).

I tried installing the older version but it's not available. This is the output of `rmadison libc6-dev`:

 libc6-dev | 2.19-0ubuntu6 | trusty | amd64, arm64, armhf, i386, powerpc, ppc64el
 libc6-dev | 2.19-0ubuntu6.15 | trusty-security | amd64, arm64, armhf, i386, powerpc, ppc64el
 libc6-dev | 2.19-0ubuntu6.15 | trusty-updates | amd64, arm64, armhf, i386, powerpc, ppc64el
 libc6-dev | 2.23-0ubuntu3 | xenial | amd64, arm64, armhf, i386, powerpc, ppc64el, s390x
 libc6-dev | 2.23-0ubuntu11.3 | xenial-security | amd64, arm64, armhf, i386, powerpc, ppc64el, s390x
 libc6-dev | 2.23-0ubuntu11.3 | xenial-updates | amd64, arm64, armhf, i386, powerpc, ppc64el, s390x
 libc6-dev | 2.27-3ubuntu1 | bionic | amd64, arm64, armhf, i386, ppc64el, s390x
 libc6-dev | 2.27-3ubuntu1.5 | bionic-security | amd64, arm64, armhf, i386, ppc64el, s390x
 libc6-dev | 2.27-3ubuntu1.5 | bionic-updates | amd64, arm64, armhf, i386, ppc64el, s390x
 libc6-dev | 2.31-0ubuntu9 | focal | amd64, arm64, armhf, i386, ppc64el, riscv64, s390x
 libc6-dev | 2.31-0ubuntu9.4 | focal-proposed | riscv64
 libc6-dev | 2.31-0ubuntu9.5 | focal-proposed | amd64, arm64, armhf, i386, ppc64el, s390x
 libc6-dev | 2.31-0ubuntu9.7 | focal-security | amd64, arm64, armhf, i386, ppc64el, riscv64, s390x
 libc6-dev | 2.31-0ubuntu9.7 | focal-updates | amd64, arm64, armhf, i386, ppc64el, riscv64, s390x
 libc6-dev | 2.34-0ubuntu3 | impish | amd64, arm64, armhf, i386, ppc64el, riscv64, s390x
 libc6-dev | 2.34-0ubuntu3.2 | impish-security | amd64, arm64, armhf, i386, ppc64el, riscv64, s390x
 libc6-dev | 2.34-0ubuntu3.2 | impish-updates | amd64, arm64, armhf, i386, ppc64el, riscv64, s390x
 libc6-dev | 2.35-0ubuntu1 | jammy | amd64, arm64, armhf, i386, ppc64el, riscv64, s390x

The 2.31-0ubuntu9 version has the same issue though.

This bug is blocking my docker build from yesterday. Until a fix is in place if you have a workaround then could you please share it

The workaround I'm using is taken from here: https://support.aqueos.net/index.php?/Knowledgebase/Article/View/your-kernel-version-indicates-a-revision-number-of-255-or-greater

mv /bin/uname /bin/uname.orig
and copy in the script below as /bin/uname (with the correct permissions),
----
#!/bin/bash

if [[ $1 == "-r" ]] ;then
  echo '4.9.250'
  exit
else
  uname.orig "$@"
fi

Sorry that should be "$1" not an unquoted $1.

Thank you @Nic Doye for the workaround! It helped my docker build.

this worked!

AWS support gave me another (temporary) workaround for Codebuild. If you use the 2xl compute type (the largest one, with 145gb RAM), that fleet is still using the older AMI and the older kernel, and so that will unblock your builds. At least until that compute type gets the same upgrade eventually.

@Nic
@Rajesh

Can anyone give a snapshot of your dockerfile? I am running this on docker with no luck.
Thanks

Place the following script in bin/uname (where bin and Dockerfile are in the same directory):

-8<----- uname
#!/bin/bash

# Until the following bug is fixed:
# https://bugs.launchpad.net/ubuntu/+source/glibc/+bug/1962225
# https://bugs.launchpad.net/ubuntu/+source/glibc/+bug/1962606

# Workaround from https://support.aqueos.net/index.php?/Knowledgebase/Article/View/your-kernel-version-indicates-a-revision-number-of-255-or-greater
#
if [[ "$1" == "-r" ]] ;then
    echo '4.9.250'
    exit
else
    uname.orig "$@"
fi
-8<-----

In your Dockerfile, you can do this. (You could just copy the uname script, but we have other things we copy in).

-8<----- From Dockerfile

COPY . /tmp/
RUN mv /bin/uname /bin/uname.orig \
    && install -m 0755 /tmp/bin/uname /bin \
    && apt-get update \
    && apt-get upgrade -y \
    ...
-8<-----

For people working with Docker build
@Itay Elgazar (elgazaritay)

Copy the script above into a file(like ubuntuFix.sh)
Use it in your Dockerfile like below:-

FROM ubuntu:latest
USER root
WORKDIR /home/app
COPY . /home/app
#Workaround for ubuntu fix start
RUN mv /bin/uname /bin/uname.orig
RUN cp ./ubuntuFix.sh /bin/uname
RUN chmod 755 /bin/uname;
RUN cat /bin/uname
#Workaround for ubuntu fix end
RUN apt clean
RUN apt-get update
RUN apt -y install gnupg2

.....
.....
//Rest of the Dockerfile code
.....
.....

@Nic thanks for the solution..
Hope this works for others using Docker image

@vivmehra
You're the hero, man!

Many thanks @nic

Here is a version with no external file

RUN mv /bin/uname /bin/uname.orig
RUN printf '#!/bin/bash\n\nif [[ "$1" == "-r" ]] ;then\n echo '4.9.250'\n exit\nelse\n uname.orig "$@"\nfi' > /bin/uname
RUN chmod 755 /bin/uname

(The second statement should be all on one line if you copy-paste it)

This fix will land in glibc in a week or so (hopefully) but before that we can get new images out with the glibc from the security update in, which will make your builds work again.

New ubuntu official images have been published which contain the glibc update, so this issue should be less impactful now. The plan is still to fix this quickly though.

Thanks for the update @Michael

This bug was fixed in the package glibc - 2.35-0ubuntu3

---------------
glibc (2.35-0ubuntu3) jammy; urgency=medium

  * debian/rules.d/build.mk: build with --with-default-link=no.

 -- Michael Hudson-Doyle <email address hidden> Fri, 04 Mar 2022 15:54:17 +1300

I'm trying to install the fixed package on a docker image, running Ubuntu 18.04.6, but I get: `91mE: Version '2.35-0ubuntu3' for 'libc6' was not found`. Running: `RUN apt-get install -y --no-install-recommends libc6=2.35-0ubuntu3`

Ubuntu version:
19:36:03 NAME="Ubuntu"
19:36:03 VERSION="18.04.6 LTS (Bionic Beaver)"
19:36:03 ID=ubuntu
19:36:03 ID_LIKE=debian
19:36:03 PRETTY_NAME="Ubuntu 18.04.6 LTS"
19:36:03 VERSION_ID="18.04"
19:36:03 HOME_URL="https://www.ubuntu.com/"
19:36:03 SUPPORT_URL="https://help.ubuntu.com/"
19:36:03 BUG_REPORT_URL="https://bugs.launchpad.net/ubuntu/"
19:36:03 PRIVACY_POLICY_URL="https://www.ubuntu.com/legal/terms-and-policies/privacy-policy"
19:36:03 VERSION_CODENAME=bionic
19:36:03 UBUNTU_CODENAME=bionic

Dockerfile:
FROM ubuntu:bionic
RUN cat /etc/os-release
ENV DEBIAN_FRONTEND noninteractive
RUN apt-get update
RUN apt list -a libc6

Available libc6 versions:
19:36:11 libc6:
19:36:11 Installed: 2.27-3ubuntu1.4
19:36:11 Candidate: 2.27-3ubuntu1.5
19:36:11 Version table:
19:36:11 2.27-3ubuntu1.5 500
19:36:11 500 http://archive.ubuntu.com/ubuntu bionic-updates/main amd64 Packages
19:36:11 500 http://security.ubuntu.com/ubuntu bionic-security/main amd64 Packages
19:36:11 *** 2.27-3ubuntu1.4 100
19:36:11 100 /var/lib/dpkg/status
19:36:11 2.27-3ubuntu1 500
19:36:11 500 http://archive.ubuntu.com/ubuntu bionic/main amd64 Packages

Hello Michael, or anyone else affected,

Accepted glibc into focal-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/glibc/2.31-0ubuntu9.8 in a few hours, and then in the -proposed repository.

Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how to enable and use -proposed. Your feedback will aid us getting this update out to other Ubuntu users.

If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested, what testing has been performed on the package and change the tag from verification-needed-focal to verification-done-focal. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification-failed-focal. In either case, without details of your testing we will not be able to proceed.

Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance for helping!

N.B. The updated package will be released to -updates after the bug(s) fixed by this package have been verified and the package has been in -proposed for a minimum of 7 days.

For those on Bionic/18.04, it looks like the fix hasn't made it back to bionic yet so there's no package to install for Bionic at the moment.

Depending on how you're using Amazon Linux and/or ECS, you may be able to work around the issue by temporarily rebuilding a base image outside of ECS with a different kernel version, making sure to install libc6 in that base image, and using that image for any builds that occur under an Amazon Linux kernel.

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!

Hello Michael, or anyone else affected,

Accepted glibc into focal-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/glibc/2.31-0ubuntu9.9 in a few hours, and then in the -proposed repository.

Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how to enable and use -proposed. Your feedback will aid us getting this update out to other Ubuntu users.

If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested, what testing has been performed on the package and change the tag from verification-needed-focal to verification-done-focal. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification-failed-focal. In either case, without details of your testing we will not be able to proceed.

Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance for helping!

N.B. The updated package will be released to -updates after the bug(s) fixed by this package have been verified and the package has been in -proposed for a minimum of 7 days.

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

hilive/2.0a-3build2 (arm64)
tomb/2.7+dfsg2-1 (arm64)
linux-hwe-5.13/5.13.0-40.45~20.04.1 (armhf)
bali-phy/3.4.1+dfsg-2build1 (s390x, arm64)
smalt/0.7.6-9 (ppc64el)
mariadb-10.3/1:10.3.34-0ubuntu0.20.04.1 (armhf)
feersum/1.407-2 (s390x)
kopanocore/8.7.0-7ubuntu1 (amd64)
r-cran-ps/1.3.2-2 (s390x, ppc64el)
libreoffice/1:6.4.7-0ubuntu0.20.04.4 (amd64)
imagemagick/8:6.9.10.23+dfsg-2.1ubuntu11.4 (armhf)
ruby-stackprof/0.2.15-2 (amd64)
gnome-photos/3.34.1-1 (ppc64el)
linux-azure-5.11/5.11.0-1029.32~20.04.2 (amd64)
linux-intel-5.13/5.13.0-1010.10 (amd64)
php-luasandbox/3.0.3-2build2 (armhf, arm64)
mbedtls/2.16.4-1ubuntu2 (amd64, ppc64el)
cross-toolchain-base/43ubuntu3.1 (ppc64el)
rtags/2.37-1 (amd64)
gvfs/1.44.1-1ubuntu1 (arm64, ppc64el)
linux-oem-5.14/5.14.0-1033.36 (amd64)
linux-azure-cvm/5.4.0-1076.79+cvm1 (amd64)
mercurial/5.3.1-1ubuntu1 (armhf)
r-cran-satellite/1.0.2-1build1 (armhf)
s3ql/3.3.2+dfsg-1ubuntu1 (armhf)
snapd/2.54.3+20.04.1ubuntu0.2 (s390x, arm64, amd64, ppc64el)
sphinxbase/0.8+5prealpha+1-8 (armhf)
gemma/0.98.1+dfsg-1 (armhf)

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!

Hi,

Is it possible to add this fix to bionic-backport please? I'm happy to test and confirm the fix works if required.

It looks harmless to me: https://salsa.debian.org/glibc-team/glibc/-/commit/b3c76cf1cd0c8b6e4844c6362a45143c136a2900

Thank you.

I did some testing and I didn't run into any issues after updating to the newer libc6 from -proposed. Looks good.

FROM ubuntu:focal
ENV DEBIAN_FRONTEND noninteractive
RUN mv /bin/uname /bin/uname.orig
RUN printf '#!/bin/bash\n\nif [[ "$1" == "-r" ]] ;then\n echo '5.4.277-277'\n exit\nelse\n uname.orig "$@"\nfi' > /bin/uname
RUN chmod 755 /bin/uname
RUN echo "deb http://archive.ubuntu.com/ubuntu/ focal-proposed main" >> /etc/apt/sources.list
RUN apt-get update && apt-get upgrade -y libc6
RUN apt-get install --reinstall libc6

docker build -t ${USER}:focal-libc6 .

Hello, could someone affected by this bug test the version of glibc in focal-proposed? We had to rebuild the package for unrelated reasons.

Verified on an AL2 instance:

root@19bea50a89e2:/# uname -r
4.14.275-207.503.amzn2.x86_64
root@19bea50a89e2:/# apt install --reinstall libc6=2.31-0ubuntu9.7
Reading package lists... Done
Building dependency tree
Reading state information... Done
0 upgraded, 0 newly installed, 1 reinstalled, 0 to remove and 1 not upgraded.
Need to get 2714 kB of archives.
After this operation, 0 B of additional disk space will be used.
Get:1 http://archive.ubuntu.com/ubuntu focal-updates/main amd64 libc6 amd64 2.31-0ubuntu9.7 [2714 kB]
Fetched 2714 kB in 0s (16.7 MB/s)
debconf: delaying package configuration, since apt-utils is not installed
(Reading database ... 4127 files and directories currently installed.)
Preparing to unpack .../libc6_2.31-0ubuntu9.7_amd64.deb ...
debconf: unable to initialize frontend: Dialog
debconf: (No usable dialog-like program is installed, so the dialog based frontend cannot be used. at /usr/share/perl5/Debconf/FrontEnd/Dialog.pm li
ne 76.)
debconf: falling back to frontend: Readline
debconf: unable to initialize frontend: Readline
debconf: (Can't locate Term/ReadLine.pm in @INC (you may need to install the Term::ReadLine module) (@INC contains: /etc/perl /usr/local/lib/x86_64-
linux-gnu/perl/5.30.0 /usr/local/share/perl/5.30.0 /usr/lib/x86_64-linux-gnu/perl5/5.30 /usr/share/perl5 /usr/lib/x86_64-linux-gnu/perl/5.30 /usr/sh
are/perl/5.30 /usr/local/lib/site_perl /usr/lib/x86_64-linux-gnu/perl-base) at /usr/share/perl5/Debconf/FrontEnd/Readline.pm line 7.)
debconf: falling back to frontend: Teletype
ERROR: Your kernel version indicates a revision number
of 255 or greater. Glibc has a number of built in
assumptions that this revision number is less than 255.
If you\'ve built your own kernel, please make sure that any
custom version numbers are appended to the upstream
kernel number with a dash or some other delimiter.

dpkg: error processing archive /var/cache/apt/archives/libc6_2.31-0ubuntu9.7_amd64.deb (--unpack):
 new libc6:amd64 package pre-installation script subprocess returned error exit status 1
Errors were encountered while processing:
 /var/cache/apt/archives/libc6_2.31-0ubuntu9.7_amd64.deb
E: Sub-process /usr/bin/dpkg returned an error code (1)
root@19bea50a89e2:/# apt install libc-bin/focal-proposed libc6/focal-proposed
Reading package lists... Done
Building dependency tree
Reading state information... Done
Selected version '2.31-0ubuntu9.9' (Ubuntu:20.04/focal-proposed [amd64]) for 'libc-bin'
Selected version '2.31-0ubuntu9.9' (Ubuntu:20.04/focal-proposed [amd64]) for 'libc6'
Suggested packages:
  manpages glibc-doc locales
The following packages will be upgraded:
  libc-bin libc6
2 upgraded, 0 newly installed, 0 to remove and 6 not upgraded.
Need to get 3356 kB of archives.
After this operation, 7168 B of additional disk space will be used.
Get:1 http://archive.ubuntu.com/ubuntu focal-proposed/main amd64 libc6 amd64 2.31-0ubuntu9.9 [2722 kB]
Get:2 http://archive.ubuntu.com/ubuntu focal-proposed/main amd64 libc-bin amd64 2.31-0ubuntu9.9 [633 kB]
Fetched 3356 kB in 0s (18.6 MB/s)
debconf: delaying package configuration, since apt-utils is not installed
(Reading database ... 4981 files and directories c...

The verification of the Stable Release Update for glibc has completed successfully and the package is now being released to -updates. Subsequently, the Ubuntu Stable Release Updates Team is being unsubscribed and will not receive messages about this bug report. In the event that you encounter a regression using the package from -updates please report a new bug using ubuntu-bug and tag the bug report regression-update so we can easily find any regressions.

This bug was fixed in the package glibc - 2.31-0ubuntu9.9

---------------
glibc (2.31-0ubuntu9.9) focal; urgency=medium

  * Disable testsuite on riscv64. It is failing maths tests intermittently in
    ways that cannot be a glibc regression and is disabled in later series
    anyway.

glibc (2.31-0ubuntu9.8) focal; urgency=medium

  * Update for 20.04. (LP: #1951033)

  [ Balint Reczey ]
  * Cherry-pick upstream patch to fix building with -moutline-atomics
  * Prevent rare deadlock in pthread_cond_signal (LP: #1899800)

  [ Matthias Klose ]
  * Revert: Use DH_COMPAT=8 for dh_strip to fix debug sections for valgrind.
    Enables debugging ld.so related issues. (LP: #1918035)
  * Don't strip ld.so on armhf. (LP: #1927192)

  [ Gunnar Hjalmarsson ]
  * d/local/usr_sbin/update-locale: improve sanity checks. (LP: #1892825)

  [ Heitor Alves de Siqueira ]
  * d/p/u/git-lp1928508-reversing-calculation-of-__x86_shared_non_temporal.patch:
    - Fix memcpy() performance regression on x86 AMD systems (LP: #1928508)

  [ Aurelien Jarno ]
  * debian/debhelper.in/libc.preinst: drop the check for kernel release
    > 255 now that glibc and preinstall script are fixed. (LP: #1962225)

  [ Michael Hudson-Doyle ]
  * libc6 on arm64 is now built with -moutline-atomics so libc6-lse can now be
    an empty package that is safe to remove. (LP: #1912652)
  * d/patches/u/aarch64-memcpy-improvements.patch: Backport memcpy
    improvements. (LP: #1951032)
  * Add test-float64x-yn to xfails on riscv64.

 -- Michael Hudson-Doyle <email address hidden> Thu, 07 Apr 2022 13:24:41 +1200

Hello Michael, or anyone else affected,

Accepted glibc into bionic-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/glibc/2.27-3ubuntu1.6 in a few hours, and then in the -proposed repository.

Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how to enable and use -proposed. Your feedback will aid us getting this update out to other Ubuntu users.

If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested, what testing has been performed on the package and change the tag from verification-needed-bionic to verification-done-bionic. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification-failed-bionic. In either case, without details of your testing we will not be able to proceed.

Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance for helping!

N.B. The updated package will be released to -updates after the bug(s) fixed by this package have been verified and the package has been in -proposed for a minimum of 7 days.

Verified that libc6 2.27-3ubuntu1.6 can be installed fine in a bionic docker container an Amazon Linux 2 system with the problematic kernel version:

root@eef8e8932f4b:/# apt install libc6
Reading package lists... Done
Building dependency tree
Reading state information... Done
Suggested packages:
  glibc-doc locales
The following packages will be upgraded:
  libc6
1 upgraded, 0 newly installed, 0 to remove and 5 not upgraded.
Need to get 2831 kB of archives.
After this operation, 1024 B disk space will be freed.
Get:1 http://archive.ubuntu.com/ubuntu bionic-proposed/main amd64 libc6 amd64 2.27-3ubuntu1.6 [2831 kB]
Fetched 2831 kB in 1s (3348 kB/s)
debconf: delaying package configuration, since apt-utils is not installed
(Reading database ... 4140 files and directories currently installed.)
Preparing to unpack .../libc6_2.27-3ubuntu1.6_amd64.deb ...
debconf: unable to initialize frontend: Dialog
debconf: (No usable dialog-like program is installed, so the dialog based frontend cannot be used. at /usr/share/perl5/Debconf/FrontEnd/Dialog.pm line 76.)
debconf: falling back to frontend: Readline
debconf: unable to initialize frontend: Readline
debconf: (Can't locate Term/ReadLine.pm in @INC (you may need to install the Term::ReadLine module) (@INC contains: /etc/perl /usr/local/lib/x86_64-linux-gnu/perl/5.26.1 /usr/local/share/perl/5.26.1
/usr/lib/x86_64-linux-gnu/perl5/5.26 /usr/share/perl5 /usr/lib/x86_64-linux-gnu/perl/5.26 /usr/share/perl/5.26 /usr/local/lib/site_perl /usr/lib/x86_64-linux-gnu/perl-base) at /usr/share/perl5/Debcon
f/FrontEnd/Readline.pm line 7.)
debconf: falling back to frontend: Teletype
Unpacking libc6:amd64 (2.27-3ubuntu1.6) over (2.27-3ubuntu1.5) ...
Setting up libc6:amd64 (2.27-3ubuntu1.6) ...
debconf: unable to initialize frontend: Dialog
debconf: (No usable dialog-like program is installed, so the dialog based frontend cannot be used. at /usr/share/perl5/Debconf/FrontEnd/Dialog.pm line 76.)
debconf: falling back to frontend: Readline
debconf: unable to initialize frontend: Readline
debconf: (Can't locate Term/ReadLine.pm in @INC (you may need to install the Term::ReadLine module) (@INC contains: /etc/perl /usr/local/lib/x86_64-linux-gnu/perl/5.26.1 /usr/local/share/perl/5.26.1
/usr/lib/x86_64-linux-gnu/perl5/5.26 /usr/share/perl5 /usr/lib/x86_64-linux-gnu/perl/5.26 /usr/share/perl/5.26 /usr/local/lib/site_perl /usr/lib/x86_64-linux-gnu/perl-base) at /usr/share/perl5/Debcon
f/FrontEnd/Readline.pm line 7.)
debconf: falling back to frontend: Teletype
Processing triggers for libc-bin (2.27-3ubuntu1.5) ...
root@eef8e8932f4b:/# uname -r
4.14.275-207.503.amzn2.x86_64

All autopkgtests for the newly accepted glibc (2.27-3ubuntu1.6) for bionic have finished running.
The following regressions have been reported in tests triggered by the package:

docker.io/20.10.7-0ubuntu5~18.04.3 (i386, amd64, s390x, arm64, ppc64el)
sbd/1.3.1-2 (amd64)
chromium-browser/100.0.4896.127-0ubuntu0.18.04.1 (armhf)
pymol/1.8.4.0+dfsg-1build1 (s390x, ppc64el)
nvidia-graphics-drivers-390/390.147-0ubuntu0.18.04.1 (i386)
pgbouncer/1.8.1-1build1 (amd64)
r-cran-urltools/1.7.0-1ubuntu1 (arm64, ppc64el)
firefox/100.0+build2-0ubuntu0.18.04.1 (arm64)
python-llfuse/1.3.3+dfsg-3 (arm64)
c-icap/1:0.4.4-1 (ppc64el)
givaro/4.0.2-8ubuntu1 (armhf)
apport/2.20.9-0ubuntu7.27 (amd64)
threadweaver/5.44.0-0ubuntu1 (i386)
apt/1.6.14 (arm64)
containerd/1.5.5-0ubuntu3~18.04.2 (amd64, arm64)
glibc/2.27-3ubuntu1.6 (armhf)
cura-engine/1:3.1.0-2 (arm64)

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/bionic/update_excuses.html#glibc

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

Thank you!

This bug was fixed in the package glibc - 2.27-3ubuntu1.6

---------------
glibc (2.27-3ubuntu1.6) bionic; urgency=medium

  [ Gunnar Hjalmarsson ]
  * d/local/usr_sbin/update-locale: improve sanity checks. (LP: #1892825)

  [ Aurelien Jarno ]
  * debian/debhelper.in/libc.preinst: drop the check for kernel release
    > 255 now that glibc and preinstall script are fixed. (LP: #1962225)

 -- Michael Hudson-Doyle <email address hidden> Tue, 03 May 2022 22:19:39 +1200