Bug #1299
pacman-5.0.1-5.parabola1 upgrade is broken
0%
Description
I upgrade pacman to pacman-5.0.1-5.parabola1 which went fine:
sudo pacman -S pacman resolving dependencies... looking for conflicting packages... Packages (1) pacman-5.0.1-5.parabola1 Total Download Size: 0.72 MiB Total Installed Size: 4.45 MiB Net Upgrade Size: -0.49 MiB :: Proceed with installation? [Y/n] :: Retrieving packages... pacman-5.0.1-5.para... 733.6 KiB 223K/s 00:03 [#####################] 100% (1/1) checking keys in keyring [#####################] 100% (1/1) checking package integrity [#####################] 100% (1/1) loading package files [#####################] 100% (1/1) checking for file conflicts [#####################] 100% (1/1) checking available disk space [#####################] 100% :: Processing package changes... (1/1) upgrading pacman [#####################] 100% :: Running post-transaction hooks... (1/1) Arming ConditionNeedsUpdate...
After the upgrade pacman couldn't load librycrypto.so
Error:
$ sudo pacman -Syu pacman: error while loading shared libraries: libcrypto.so.1.1: cannot open shared object file: No such file or directory $ pacman --help pacman: error while loading shared libraries: libcrypto.so.1.1: cannot open shared object file: No such file or directory
Related issues
History
Updated by kesara almost 7 years ago
My system have only libcrypto 1.0.0 installed.
$ gpg2 --version gpg (GnuPG) 2.1.20 libgcrypt 1.7.6
Updated by Anonymous almost 7 years ago
It's not due to libgcrypt, but pacman being updated for openssl 1.1.0 while you are on openssl 1.0.2
You'll need to boot into a Parabola liveDVD/USB to repair it.
Once you have a LiveDVD/USB:
Boot into the LiveDVD/USB
mount /your/root/drive/location /mnt
mount /your/home/drive/location /mnt/home
pacstrap /mnt openssl
arch-chroot /mnt
pacman -Syyu
exit
umount /mnt/home
umount /mnt
reboot
This should repair it.
Updated by isacdaavid almost 7 years ago
- Related to Bug #1310: updating only pacman breaks system [caused by openssl upgrade] added
Updated by isacdaavid almost 7 years ago
- Status changed from open to not-a-bug
I'm closing this one as duplicate of #1310.
See the recommendation there and an extra candidate solution. There's no way for us (or for Arch) to make sure that upgrading a subset of packages at a time won't break your system. Never
pacman -Sy pacman -S <PACKAGE>
without a
pacman -Su
in between.
Updated by libreuser almost 7 years ago
I found this 'manual intervention required' for 'ca-certificates-utils 20170307-1' from Arch web page:
dated 2017-03-15 !!!!!! 🙄