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.
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: | 901 |
Popularity: | 26.38 |
First Submitted: | 2020-10-19 00:43 (UTC) |
Last Updated: | 2024-03-26 04:28 (UTC) |
« First ‹ Previous 1 .. 13 14 15 16 17 18 19 20 21 22 Next › Last »
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.
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')
@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.
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:
@freecorndogs
I think yes, one way to verify is /usr/lib/libalpm.so should link to libalpm.so.13, if it is libalpm.so.12 you are on the older version
I am also getting the error
error: failed to run custom build command for
alpm v2.0.0
this version of alpm.rs does not support libalpm v12.0.2 only v13.x.0 is supported
My guess is that it's due to I'm running Manjaro and libalpm is a version behind?
With 1.7 I get Failed to find OpenSSL development headers.
openssl is installed.
@m040601 Your base system is out of date. Run pacman -Syu
(or paru --repo -Syu
if you still have a previous version working) to get your base system updated first, then it will build and run fine using the commands you showed.
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