Hi Olaf, Am 25.10.2017 um 12:41 schrieb Olaf Meeuwissen: > Thomas Besser writes: > >> [...] >> As far as I understand, package libc-bin registers dpkg (?) triggers >> scripts which are executed on every update of any package. >> >> How can I find out, which trigger script of libc-bin causes this error? >> There must be a place, where dpkg stores this scripts. But where? > > The trigger definition for libc-bin is in > > /var/lib/dpkg/info/libc-bin.triggers > > On my machine it says > > $ cat /var/lib/dpkg/info/libc-bin.triggers > interest ldconfig > > I am not sure what exactly this does, but I *guess* it triggers updating > of /etc/ld.so.cache by running the ldconfig command in some way. > > IIRC, the error you posted earlier looked a lot like it came from a > piece of Perl code but I have no idea where it would come from. My > /sbin/ldconfig is a shell script wrapper that handles triggers via > dpkg-trigger, an ELF binary, and passes the buck to /sbin/ldconfig.real, > also an ELF binary. Both are unlikely to be directly responsible for > the error message you posted. > > # Running Devuan jessie, BTW. > > I know it doesn't answer your question completely but hope this helps > anyway,
Thanks for this information, that's a step forward. I will look into this places... I have created a base image of debian wheezy earlier. I will do an upgrade there now and see if I can reproduce this error there too. Regards Thomas _______________________________________________ Dng mailing list Dng@lists.dyne.org https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/dng
