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)"

Or install paru-git

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

That reminds me, I gotta restart.

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

this hits sı close home from the last time I broke my system

Just update paru from source (exactly like the first time that you installed it)

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.

Hasn’t this been an issue a few days ago? Maybe only with testing.

Yeah I had to cargo install paru as a temp fix

They ran arch, btw 🥲

sudo sed -i 's/libalpm.so.14/libalpm.so.15/g' /usr/bin/paru

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.