Where were you when yay/paru was kill
I was at home trying to yay
when:
yay: error while loading shared libraries: libalpm.so.14: cannot open shared object file: No such file or directory
No
You can either patch the binary
sudo patchelf --replace-needed libalpm.so.14 libalpm.so.15 "$(which paru)"
sudo pacman -S --needed base-devel
git clone https://aur.archlinux.org/paru-git.git
cd paru-git
makepkg -si
Or do both, patch the binary, then use it to install paru-git
(which is what i did)
For now you can either use paru-git
, or the already updated yay
/yay-bin
packages. Please just don't symlink the libraries together
Somebody who needs the dopamine of running yay -Syyyyyuuuuuuu 4 times a day wouldn't be running broken and outdated *-bin packages but always target *-git alternatives /s
welp, guess I'm keeping this thread open for tomorrow morning when I get to fixing this. Hopefully by then things will be more fixed upstream...
Weird. I was just having an issue with pamac and started using paru as a backup and paru is working fine last I checked.
I found a hack.
Assuming you now have libalpm.so.15
, just make a copy of it and rename it to libalpm.so.14
:
cp /usr/lib/libalpm.so.15 /usr/lib/libalpm.so.14
Edit: It's not a permanent one and it works for the time being, can't see the reason for the downvotes honestly.
It’s not a permanent one and it works for the time being, can’t see the reason for the downvotes honestly.
It's just a bad idea in general. A better option would be to patch the binary to use 15. They both have the issue of forcing paru to work with a library it wasn't explicitly designed for, but symlinking (or copying) 15 to 14 forces the hack to be "system wide" instead of restricted to a single binary
as well, your solution is "temporary" only if you remember to fix it, vs patching which is (by default) overwritten the next time paru is updated
it "works", but it's not something i'd recommend someone else do