Morganamilo
"paru: error while loading shared libraries: libalpm.so.14: cannot open shared object file: No such file or directory" when attempting to run paru
pacman --version: v7.0.0 libalpm v15.0.0
how to resolve this issue? i am new to arch and i really need to install a package for my work and i cant seem to use paru or yay both
do i need to downgrade something? if, yes then please guide me
This is the leading issue on this repository and the solution is to clone and makepkg the paru-git aur repo.
https://github.com/Morganamilo/paru/issues/1239#issuecomment-2351021340
Could you create a new release as the Arch Linux maintainer is following your release in his package build. https://aur.archlinux.org/cgit/aur.git/tree/PKGBUILD?h=paru#n7 Line 7 - version 2.0.3 - release from March - Could you make a new release? In the meantime we work with paru-git - last code from github is working on Arch
Could you create a new release as the Arch Linux maintainer is following your release in his package build. https://aur.archlinux.org/cgit/aur.git/tree/PKGBUILD?h=paru#n7 Line 7 - version 2.0.3 - release from March - Could you make a new release? In the meantime we work with paru-git - last code from github is working on Arch
Wow, the Man himself!!! OMG, I'm so excited to see your post here, Sir. Unfortunately, I have nothing technical to add to the discussion, just wanted to show my appreciation for all your wonderful work!
Could you create a new release as the Arch Linux maintainer is following your release in his package build. https://aur.archlinux.org/cgit/aur.git/tree/PKGBUILD?h=paru#n7 Line 7 - version 2.0.3 - release from March - Could you make a new release? In the meantime we work with paru-git - last code from github is working on Arch
The AUR package maintainer and the Paru author/developer is the same person (Morganamilo) 😄
Since it is fixed on master, why not just make a release?
Is there any reason this hasn't happened, and the issue was closed? As far as I can tell, the issue still isn't fixed in the latest update; even after pulling this repo running and makepkg, I still have the issue.
Since it is fixed on master, why not just make a release?
Is there any reason this hasn't happened, and the issue was closed? As far as I can tell, the issue still isn't fixed in the latest update; even after pulling this repo running and makepkg, I still have the issue.
The issue is closed and a new released has been done. It should work.
Since it is fixed on master, why not just make a release?
Is there any reason this hasn't happened, and the issue was closed? As far as I can tell, the issue still isn't fixed in the latest update; even after pulling this repo running and makepkg, I still have the issue.
The issue is closed and a new released has been done. It should work.
I was stupid and ran makepkg, running makepkg -si fixed the issue. Sorry for the erroneous comment.