Ah. Slightly confusing.
This doesn't even use the binaries. :shrug:
Git Clone URL: | https://aur.archlinux.org/paru.git (read-only, click to copy) |
---|---|
Package Base: | paru |
Description: | Feature packed AUR helper |
Upstream URL: | https://github.com/morganamilo/paru |
Keywords: | AUR helper pacman rust wrapper yay |
Licenses: | GPL-3.0-or-later |
Submitter: | Morganamilo |
Maintainer: | Morganamilo |
Last Packager: | Morganamilo |
Votes: | 1016 |
Popularity: | 19.43 |
First Submitted: | 2020-10-19 00:43 (UTC) |
Last Updated: | 2024-09-20 18:50 (UTC) |
« First ‹ Previous 1 .. 15 16 17 18 19 20 21 22 23 24 25 Next › Last »
Ah. Slightly confusing.
This doesn't even use the binaries. :shrug:
Tags are just part of version control. Weather it's released or not is separate. Especially since the tag triggers the CI to do stuff to prepare for the release such as binary builds.
You tagged 1.7.3 tho, and it's obtainable from https://github.com/Morganamilo/paru/archive/refs/tags/v1.7.3.tar.gz?
1.7.2 is still the latest: https://github.com/Morganamilo/paru/releases
Why is not this PKGBUILD updated? The out of date flags were removed several times.
Wooow. Written in Rust. My hats off to you, sir.
It's also the highest-ranked pkg by the little aggressive "popularity" (https://aur.archlinux.org/packages/?O=0&SeB=nd&SB=p&SO=d&PP=50&do_Search=Go) (aggressive, because its calculation is 0.98^[day], so e.g. after 35 days, the "vote" is already worth less than 0.5 a vote).
@attila123
Nothing serious, it's just the normal process when a popular library makes changes
libalpm.so.12
changed to libalpm.so.13
in pacman6You must be wondering but why did they change the name of the library. This is to force clients to rebuilt their dependent applications.
If they had not done this, the applications would crash in segmentation fault because of the functions which have changed in the library.
So finally, instead of having a segmentation fault that is difficult to understand, you have a nice message that tells you that libalpm.so.12
is missing.
A common approach to know from where the file is comming is to execute pacman/paru -F libalpm.so.12
, you notice that libalpm.so.12
no longer officially exists, so you search by deduction for libalpm.so.13
and you find that it matches pacman.
Hi, not sure what is this alpm thing, but manually rebuilding paru helped.
Symptom: "paru: error while loading shared libraries: libalpm.so.12: cannot open shared object file: No such file or directory"
sudo pacman -S --needed base-devel
git clone https://aur.archlinux.org/paru.git
cd paru
makepkg -si
After this it worked fine. Source of info: https://magyarlinux.hu/paru-yay-gyorsjavitas/ (well, it is in Hungarian)
Second the explicit dependency note:
depends=('pacman>=6')
As @johnnybash says it's just another error, but at least it is the right one early on so people don't get messed up with cryptic things later, and it gets the blame where it belongs.
depending on pacman 6 just gives you another error message.
there's really no solution but waiting for manjaro to catch up.
Pinned Comments
haxie commented on 2023-05-26 17:45 (UTC)
you're better off contacting her via the github, this comments section is 90% "it's out of date" from people who didn't scroll down before posting