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
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
For now you can either use paru-git
, or the already updated yay
/yay-bin
packages. Please just don't symlink the libraries together
don't tell me what to do!
What's one or more custom lost symlink on the system anyway.
Why not? I already did it and it works great.
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
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)
Just update paru from source (exactly like the first time that you installed it)
Yeah. That's how it was installed...
this hits sı close home from the last time I broke my system
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.
That reminds me, I gotta restart.
Yeah I had to cargo install paru as a temp fix
Hasn't this been an issue a few days ago? Maybe only with testing.
They ran arch, btw 🥲
sudo sed -i 's/libalpm.so.14/libalpm.so.15/g' /usr/bin/paru
Hint: :q!
Sister communities:
Community rules (click to expand)
1. Follow the site-wide rules
sudo
in Windows.Please report posts and comments that break these rules!