You are not logged in.
I surprisingly found yay didn't work while producing such message:
yay: error while loading shared libraries: libalpm.so.12: cannot open shared object file: No such file or directory
I haven't done anything 'dangerous' to my system and I couldn't find out the reasons.
Could you please help me?
Offline
You need to rebuild yay for pacman 6, the AUR author has intentionally incremented the pkgrel so that a full system update with yay wouldn't lead to such a situation.
If you are in that situation înstall yay the traditional way with makepkg: https://aur.archlinux.org/packages/yay/#pinned-808720
Offline
Does this imply that when using yay, you should preform all updates through that tool?
Offline
Mod note: Moving to AUR Issues.
Sakura:-
Mobo: MSI MAG X570S TORPEDO MAX // Processor: AMD Ryzen 9 5950X @4.9GHz // GFX: AMD Radeon RX 5700 XT // RAM: 32GB (4x 8GB) Corsair DDR4 (@ 3000MHz) // Storage: 1x 3TB HDD, 6x 1TB SSD, 2x 120GB SSD, 1x 275GB M2 SSD
Making lemonade from lemons since 2015.
Offline
Does this imply that when using yay, you should preform all updates through that tool?
As far as having an active maintainer that bumps the pkgrel in reaction to changes like these yes. You should still be in general aware that this is a situation that "will" happen on libalpm/pacman soname bumps and then knowing the proper course of action to take, which is rebuilding the source application in question. This will help your general understanding of relations of packages in your system and this kind of error is not exclusive to yay.
So if you just want a "don't care how it works™" solution then yes continue to do all operations with yay and hope the maintainer keeps being as proactive as they are (... it helps that said maintainer is the developer of the tool in question directly, so as long as they don't lose interest then this should be a situation that will be relevantly handled) if you don't want to end up helpless if that isn't the case, then read up on what soname bumps are: https://en.wikipedia.org/wiki/soname
Offline
is the below the same issue
$ rua update
rua: error while loading shared libraries: libalpm.so.12: cannot open shared object file: No such file or directory
Offline
is the below the same issue
$ rua update rua: error while loading shared libraries: libalpm.so.12: cannot open shared object file: No such file or directory
See the pinned comment on the AUR page
https://aur.archlinux.org/packages/rua
Offline
is the below the same issue
$ rua update rua: error while loading shared libraries: libalpm.so.12: cannot open shared object file: No such file or directory
Did you read the pinned comment on the rua package page https://aur.archlinux.org/packages/rua/#pinned-811778?
Edit:
Beaten by skunktrader
Last edited by loqs (2021-06-19 03:28:43)
Offline
I have this problem too, I'm trying to upgrade archlinux. This is an recent problem ?
and when I try to install yay for pacman 6 I have that :
$ git clone https://aur.archlinux.org/yay.git
fatal: destination path 'yay' already exists and is not an empty directory.
Last edited by mito77 (2021-07-17 19:47:58)
$ uname -r
5.13.9-arch1-1
Offline
No. Closing.
Sakura:-
Mobo: MSI MAG X570S TORPEDO MAX // Processor: AMD Ryzen 9 5950X @4.9GHz // GFX: AMD Radeon RX 5700 XT // RAM: 32GB (4x 8GB) Corsair DDR4 (@ 3000MHz) // Storage: 1x 3TB HDD, 6x 1TB SSD, 2x 120GB SSD, 1x 275GB M2 SSD
Making lemonade from lemons since 2015.
Offline