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
this post was submitted on 16 Sep 2024
107 points (92.1% liked)
linuxmemes
26255 readers
195 users here now
Hint: :q!
Sister communities:
Community rules (click to expand)
1. Follow the site-wide rules
- Instance-wide TOS: https://legal.lemmy.world/tos/
- Lemmy code of conduct: https://join-lemmy.org/docs/code_of_conduct.html
2. Be civil
- Understand the difference between a joke and an insult.
- Do not harrass or attack users for any reason. This includes using blanket terms, like "every user of thing".
- Don't get baited into back-and-forth insults. We are not animals.
- Leave remarks of "peasantry" to the PCMR community. If you dislike an OS/service/application, attack the thing you dislike, not the individuals who use it. Some people may not have a choice.
- Bigotry will not be tolerated.
3. Post Linux-related content
- Including Unix and BSD.
- Non-Linux content is acceptable as long as it makes a reference to Linux. For example, the poorly made mockery of
sudoin Windows. - No porn, no politics, no trolling or ragebaiting.
4. No recent reposts
- Everybody uses Arch btw, can't quit Vim, <loves/tolerates/hates> systemd, and wants to interject for a moment. You can stop now.
5. π¬π§ Language/ΡΠ·ΡΠΊ/Sprache
- This is primarily an English-speaking community. π¬π§π¦πΊπΊπΈ
- Comments written in other languages are allowed.
- The substance of a post should be comprehensible for people who only speak English.
- Titles and post bodies written in other languages will be allowed, but only as long as the above rule is observed.
6. (NEW!) Regarding public figures
We all have our opinions, and certain public figures can be divisive. Keep in mind that this is a community for memes and light-hearted fun, not for airing grievances or leveling accusations. - Keep discussions polite and free of disparagement.
- We are never in possession of all of the facts. Defamatory comments will not be tolerated.
- Discussions that get too heated will be locked and offending comments removed. Β
Please report posts and comments that break these rules!
Important: never execute code or follow advice that you don't understand or can't verify, especially here. The word of the day is credibility. This is a meme community -- even the most helpful comments might just be shitposts that can damage your system. Be aware, be smart, don't remove France.
founded 2 years ago
MODERATORS
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...
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...
this hits sΔ± close home from the last time I broke my system
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