| Thread Previous • Date Previous • Date Next • Thread Next |
(using LP handles rather than names, too many Simons around on this bug)
Hi smcv, thanks for looking into this!
This was deliberately reverted from Debian a long while ago, with this
as the only comment:
- Revert dropping the ldconfig wrapper, as we still have a lot of
packages that don't ship a trigger but instead call in postinst.
Sadly, it was done by Adam Conrad so we can't ask him for more context,
but between the data you dug up and the date of the upload (2016-03-22,
2.23-0ubuntu2 to Xenial), I think I can now fill in the blanks: at the
time, we probably still had quite a few packages that hadn't picked up
the new dh_makeshlibs behavior because they simply hadn't been rebuilt,
both in the archive and in the wider ecosystem, and it did make sense to
try and minimize the impact for the LTS.
Assuming I'm correct, I think we can afford the risk. I say we drop the
delta in the upcoming merge, mention it in the Resolute release notes in
case somebody out there relies on it, and try and find any call to
either ldconfig or ldconfig.real in the Ubuntu archive, to migrate the
latter to plain ldconfig, and check if the former is still needed.
Assigning this to another Simon, @simpoir, since he's handling the
upcoming merge.
--
You received this bug notification because you are a member of
Debcrafters packages, which is subscribed to glibc in Ubuntu.
https://bugs.launchpad.net/bugs/2127856
Title:
please drop ldconfig wrapper around ldconfig.real if no longer needed
Status in glibc package in Ubuntu:
Triaged
Bug description:
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?
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/glibc/+bug/2127856/+subscriptions
| Thread Previous • Date Previous • Date Next • Thread Next |
