[Bug 1989082] Re: execute bit is missing on libc.so.6

[Brian Murray]

Hello Reinhold, or anyone else affected,

Accepted glibc into jammy-proposed. The package will build now and be
available at https://launchpad.net/ubuntu/+source/glibc/2.35-0ubuntu3.3
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-
jammy to verification-done-jammy. If it does not fix the bug for you,
please add a comment stating that, and change the tag to verification-
failed-jammy. 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.

** Tags removed: verification-done verification-done-jammy
** Tags added: verification-needed verification-needed-jammy

-- 
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/1989082

Title:
  execute bit is missing on libc.so.6

Status in glibc package in Ubuntu:
  In Progress
Status in glibc source package in Jammy:
  Fix Committed
Status in glibc source package in Kinetic:
  Won't Fix
Status in glibc source package in Lunar:
  Won't Fix

Bug description:
  [Impact]
  Starting with Ubuntu 22.04 the execute bit is no longer set on /lib/x86_64-linux-gnu/libc.so.6. This causes trouble for some scripts that try to determine the glibc version by executing this file, for instance the LSF scheduler.

  [Proposed fix]

  Adjust the build system to chmod the library after the fixperms stage.
  This has been fixed in Debian, although it's not easily cherry-
  pickable.

  [Test plan]

  Run the following script:

  ```
  #!/bin/bash

  for glibc in `ldconfig -p | grep libc.so.6 | sed 's/.*=>//'`
  do
      if [ -x "$glibc" ] ; then
          $glibc >/dev/null 2>&1
          if [ "$?" != "0" ] ; then
              continue
          fi
          _libcver=`$glibc 2>/dev/null | grep "GNU C Library" | awk '{print $10}' | awk -F. '{print $2}' | sed 's/,//'`
      fi
      if [ "$_libcver" != "" ] ; then
          echo "GLibc minor version is $_libcver"
          break
      fi
  done
  if [ "$_libcver" = "" ] ; then
      echo "Cannot figure out the GLibc version."
      exit 1
  fi
  ```

  On Focal, it prints out the following:
    GLibc minor version is 31

  On Jammy:
    Cannot figure out the GLibc version.
  Expected:
    GLibc minor version is 35

  [Regression potential]

  This change is fairly minimal, but could expose bugs in codepaths that
  were depending on the system version of glibc and were thus far
  dormant in Jammy.

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