[SOLVED] "libcrypto.so.0.9.8 not found" errors during pacman -Syu

RobF · 2010-05-13 12:55:45

I ran pacman -Syu yesterday, running v.3.3.3-1. My last upgrade had been end of Feb. 2010, and 666 packages were upgraded yesterday. Pacman itself was upgraded (3.3.3-1 -> 3.3.3-5) during the upgrade. During the upgrade, the following error occurred in association with at least a dozen packages:

error while loading shared libraries: libcrypto.so.0.9.8: cannot open shared file: no such file

I can't identify now which programs were affected, as these errors are not listed in either pacman.log or errors.log.

/usr/lib/libcrypto.so.1.0.0 is what I have now, after the upgrade (file date 2010-04-01). When I ran another pacman -Syu immediately after the upgrade, it said the system is up to date.

Questions:

Were the packages for which the error was flagged upgraded or were they not? Most of them, I think, were from the extra repo but perhaps some of them were from AUR. If they were not upgraded, would I have to rebuild them now for libcrypto.so.1.0.0?

How can I find out for which packages this error occurred? Running "lsof | grep libcrypt" lists several dozen programs that depend on /usr/lib/libcrypto.so.1.0.0 (none that depend on /usr/lib/libcrypto.so.0.9.8). Most of them are essential KDE programs but some are daemons such as sshd, cupsd, ntpd. These daemons are running fine, it seems, and KDE (all of it?) is also running fine, after the upgrade.

So, what does this all mean? Do I have to do anything to fix it?

Last edited by RobF (2010-05-14 14:28:52)

Allan · 2010-05-13 13:18:09

By the sounds of things, this is vercmp giving an error. It is often used in install scripts to decide whether an action needs taken based on the previous version of a package. What should have happened is pacman updating itself only first and then rerun pacman for the rest of the update occuring and this would not have occured. I guess you selected "N" to updating pacman first...

The packages would have been upgraded, but some install scripts would not have run. Not sure what you can do to track these down....

Pierre · 2010-05-13 15:22:53

You probably missed the "SyncFirst=pacman" entry in pacman.conf. You should reinstall all failing packages after updating pacman. See pacman.log for those errors.

RobF · 2010-05-14 14:27:45

Thanks for your help. "SyncFirst=pacman" was indeed missing in my pacman.conf. Since I wasn't sure all packages had been upgraded and installed properly, I simply wiped my Arch system partition and then restored it with a backup image that I had made with partimage just before the upgrade. When I redid the upgrade, after pacman had been upgraded first, everything went smoothly, no more libcrypto errors.

hApy · 2010-06-02 23:33:36

It seems ridiculous that the standard functionality of having pacman update itself first automatically was removed and replaced with this easy to miss option that requires updating pacman.conf. If not having it do that was really necessary it should have been possible with an override setting or command line flag.

Allan · 2010-06-02 23:55:38

Glad to see you have your facts straight... The SyncFirst option has been in the default pacman.conf for years and as far as I know was the only way pacman knew to update itself first. So no functionality was removed.

Arch Linux

#1 2010-05-13 12:55:45

[SOLVED] "libcrypto.so.0.9.8 not found" errors during pacman -Syu

#2 2010-05-13 13:18:09

Re: [SOLVED] "libcrypto.so.0.9.8 not found" errors during pacman -Syu

#3 2010-05-13 15:22:53

Re: [SOLVED] "libcrypto.so.0.9.8 not found" errors during pacman -Syu

#4 2010-05-14 14:27:45

Re: [SOLVED] "libcrypto.so.0.9.8 not found" errors during pacman -Syu

#5 2010-06-02 23:33:36

Re: [SOLVED] "libcrypto.so.0.9.8 not found" errors during pacman -Syu

#6 2010-06-02 23:55:38

Re: [SOLVED] "libcrypto.so.0.9.8 not found" errors during pacman -Syu

Board footer