glibc and ldconfig dependency loop

Jacek Konieczny jajcus at jajcus.net
Mon Oct 1 10:36:17 CEST 2018


>From my logs of (automated) building a fresh system in a chroot:



build	01-Oct-2018 09:25:17	warning: LOOP:
build	01-Oct-2018 09:25:17	warning: removing glibc-2.28-5.aos1.i686
"Requires(postun): /sbin/ldconfig" from tsort relations.
build	01-Oct-2018 09:25:17	warning: removing ldconfig-2.28-5.aos1.i686
"Requires(auto): rtld(GNU_HASH)" from tsort relations.
[...]
build	01-Oct-2018 09:25:19	glibc
##################################################
build	01-Oct-2018 09:25:19	/sbin/ldconfig: No such file or directory
build	01-Oct-2018 09:25:19	error: %post(glibc-2.28-5.aos1.i686)
scriptlet failed, exit status 127
build	01-Oct-2018 09:25:19	ldconfig
##################################################

This causes whole poldek install command to fail.

Such loops make chroot installs or major updates unpredictable and when
glibc is installed before ldconfig, then its %post will fail. What is
worse, such loops can break installation order or other packages
installed in the batch.

Possible solutions:
– disable autogenerated dependency for ldconfig, to force installing it
before glibc
– include ldconfig in the main glibc package
– change glibc %post so it won't fail on ldconfig error. The easiest
one, will fix the glibc installation failure, but won't break the
dependency loop.

Any better ideas?

Jacek


More information about the pld-devel-en mailing list