Public bug reported:
In 2012 (eglibc 2.16-0experimental0), the Debian packaging for glibc
renamed upstream's /sbin/ldconfig static binary to /sbin/ldconfig.real,
and added a wrapper script around it, debian/local/sbin/ldconfig
(installed as /sbin/ldconfig) which defers regeneration of ld.so.cache
to a dpkg trigger if it is not immediately needed. This was a workaround
for redundant calls to ldconfig by packages' maintainer scripts, mainly
in code generated automatically by debhelper's dh_makeshlibs.
In 2015 (debhelper 9.20151004), dh_makeshlibs stopped emitting those
calls to ldconfig: instead, it now relies on glibc's dpkg trigger.
In 2016 (glibc 2.22-0experimental2), Debian's glibc responded to that
change by removing the workaround: since then, /sbin/ldconfig *in
Debian* is upstream's static binary again, and there is no
ldconfig.real.
However, Ubuntu's glibc never removed the workaround: /sbin/ldconfig in
Ubuntu questing is still a script wrapper, which conditionally runs
/sbin/ldconfig.real, which is the actual static binary built by upstream
glibc. This is a source of awkwardness for container technologies like
Valve's Steam Runtime that want to work with the upstream ldconfig
binary directly.
It's now been a decade since dh_makeshlibs stopped emitting redundant
calls to ldconfig. Please could glibc in Ubuntu stop working around
them?
** Affects: glibc (Ubuntu)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2127856
Title:
please drop ldconfig wrapper around ldconfig.real if no longer needed
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/glibc/+bug/2127856/+subscriptions
--
ubuntu-bugs mailing list
[email protected]
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
