Package Details: paru 2.0.4-1

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: 975
Popularity: 22.62
First Submitted: 2020-10-19 00:43 (UTC)
Last Updated: 2024-09-20 18:50 (UTC)

Dependencies (6)

Sources (1)

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

Latest Comments

« First ‹ Previous 1 .. 15 16 17 18 19 20 21 22 23 24 Next › Last »

Spixmaster commented on 2021-06-25 16:37 (UTC)

Why is not this PKGBUILD updated? The out of date flags were removed several times.

Det commented on 2021-06-18 08:58 (UTC)

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).

class101 commented on 2021-06-07 09:28 (UTC) (edited on 2021-06-07 09:28 (UTC) by class101)

@attila123

Nothing serious, it's just the normal process when a popular library makes changes

  • alpm is pacman (a library of)
  • paru depends on pacman
  • pacman5 library name libalpm.so.12 changed to libalpm.so.13 in pacman6
  • an so on, on systems with pacman6, it is necessary to rebuild the products dynamically linked on pacman5.

You 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.

attila123 commented on 2021-06-07 08:52 (UTC)

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)

alerque commented on 2021-06-02 16:15 (UTC)

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.

johnnybash commented on 2021-06-02 12:23 (UTC)

depending on pacman 6 just gives you another error message.

there's really no solution but waiting for manjaro to catch up.

ebo commented on 2021-06-02 11:44 (UTC) (edited on 2021-06-02 11:44 (UTC) by ebo)

this build error for v1.7 is discussed in more detail here: https://github.com/Morganamilo/paru/issues/391

it seems to affect the Manjaro distribution as it still uses pacman 5.2

I would suggest making explicit the dependency on pacman 6, i.e.:

--- PKGBUILD.orig       2021-06-02 12:37:02.564049924 +0100
+++ PKGBUILD    2021-06-02 12:42:05.389066870 +0100
@@ -9,7 +9,7 @@
 arch=('i686' 'pentium4' 'x86_64' 'arm' 'armv7h' 'armv6h' 'aarch64')
 license=('GPL3')
 makedepends=('cargo')
-depends=('git' 'pacman')
+depends=('git' 'pacman>=6.0.0')
 optdepends=('asp: downloading repo pkgbuilds' 'bat: colored pkgbuild printing' 'devtools: build in chroot')
 sha256sums=('68e1761d3e6bcebce18bef6c49a8f0b00ce3469de7a7297e21b95e94407f24af')

freecorndogs commented on 2021-06-01 16:05 (UTC)

@class101 Yeah, I'm on Manjaro Testing Branch so I'll have to wait a few days for the libalpm.so.13 update to roll out to my branch.

m040601 commented on 2021-06-01 15:15 (UTC)

can confirm that the update from 1.6.2 to 1.70 solves the problem I was having, https://aur.archlinux.org/cgit/aur.git/commit/?h=paru&id=b4ac587bba5990ede9ea04e42d7d57a24a190271

@caleb:

... your system is out of date... run pacman -Syu

my system was not out of date, when posting this issue.

Everyone posting issues here on AUR with aur helpers like paru or yay,, makes sure that before posting:

  • They have the latest pacman version
  • Their system is up to date
  • They remove any previous versions or leftovers of yay or paru

« First ‹ Previous 1 .. 15 16 17 18 19 20 21 22 23 24 Next › Last »