Description of problem: ldconfig in the trigger script barfs on RPM passing it the $1 parameter Version-Release number of selected component (if applicable): 2.7-24 How reproducible: When upgrading from a smaller version to this one. Steps to Reproduce: 1. Upgrade from a smaller version of cracklib to this one. Actual results: ldconfig complains about a relative path "2" passed to it -- this is the $1 parameter RPM passes to pre/post/trigger scripts Expected results: no error, ldconfig running flawlessly Additional info: will attach patch to spec file
Created attachment 97365 [details] patch to the spec file correcting the trigger script
Just wondering : What is this trigger useful for? From what I understand, it will run /sbin/ldconfig when cracklib < 2.7-24 is uninstalled, which means when upgrading from cracklib < 2.7-24 since this is from a more recent cracklib package... but this cracklib package has /sbin/ldconfig calls in %post and %postun... I would understand its usefulness if the last /sbin/ldconfig call done during the upgrade from the various %pre*/%post* scriplets was made while files of the older package were still installed, but that isn't the case if the older package had /sbin/ldconfig in its %postun, or is it exactly that it's lacking?