yay: error while loading shared libraries: libalpm.so.13: cannot open shared object file: No such file or directory
You can fix the error simply by sudo pacman -Suy, pacman will update and the error will disappear.
Git Clone URL: | https://aur.archlinux.org/yay.git (read-only, click to copy) |
---|---|
Package Base: | yay |
Description: | Yet another yogurt. Pacman wrapper and AUR helper written in go. |
Upstream URL: | https://github.com/Jguer/yay |
Keywords: | arm AUR go helper pacman wrapper x86 |
Licenses: | GPL-3.0-or-later |
Submitter: | jguer |
Maintainer: | jguer |
Last Packager: | jguer |
Votes: | 2314 |
Popularity: | 29.33 |
First Submitted: | 2016-10-05 17:20 (UTC) |
Last Updated: | 2024-09-19 14:27 (UTC) |
« First ‹ Previous 1 2 3 4 5 6 7 8 9 10 .. 36 Next › Last »
yay: error while loading shared libraries: libalpm.so.13: cannot open shared object file: No such file or directory
You can fix the error simply by sudo pacman -Suy, pacman will update and the error will disappear.
Yay stopped working. Getting error
yay: error while loading shared libraries: libalpm.so.13: cannot open shared object file: No such file or directory
after recent update.
Uninstalling yay and building from scratched solved the issue. More here: https://old.reddit.com/r/EndeavourOS/comments/1be08gg/yay_paru_broken_cant_do_anything_with_them_even/kv196lu/
Hello,
You bumped the pkgver but you didn't reset the pkgrel to 1... nothing you can really do about it now...
I assume this was accidental?
Polarian
@Pillgar: You're missing the prerequisites for using the AUR, this has nothing to do with yay
.
@suddengunter: What error? See above.
I was able to fix the error by 1. Removing yay 2. Updating system with pacman (without limiting/pinning pacman version) 3. Reinstalling yay from scratch with makepkg
When I try building yay with makepkg -si using latest pacman, I get an ERROR: Cannot find the debugedit binary required for including source files in debug packages. Downgrading pacman, and it builds fine after.
Update: So apparently you need debugedit to build with pacman v6.1.0-3.
Yep, now works ;)
The revised PKGBUILD should now build with the correct flag for libalpm.so=14-64. If you've upgraded pacman separately from yay (or upgraded yay separately from pacman) a manual rebuild should succeed.
@gromit. Correct, it is the second case. PACMAN is now at v14. This yay version is requesting v13. I downgraded pacman to the 6.0.x for the meantime.
gromit: I think the second
Pinned Comments
jguer commented on 2024-03-16 08:06 (UTC)
This will happen if you upgrade pacman and yay separately If you have this error you need to manually recompile yay
jguer commented on 2019-04-16 14:08 (UTC)
I cannot delete the spam comments appearing regularly in this page, which has also led me to disable notifications from here. I remind that the best way to receive support or report a problem is through the Upstream URL.