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: 983
Popularity: 21.25
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 .. 16 17 18 19 20 21 22 23 24 Next › Last »

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

class101 commented on 2021-06-01 13:51 (UTC) (edited on 2021-06-01 13:52 (UTC) by class101)

@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

freecorndogs commented on 2021-06-01 13:46 (UTC) (edited on 2021-06-01 13:52 (UTC) by freecorndogs)

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?

zerophase commented on 2021-06-01 11:52 (UTC)

With 1.7 I get Failed to find OpenSSL development headers. openssl is installed.

alerque commented on 2021-06-01 08:57 (UTC) (edited on 2021-06-01 09:00 (UTC) by alerque)

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

bartus commented on 2021-06-01 08:32 (UTC)

Rather CARGO_MAKEFLAGS

starquake commented on 2021-06-01 08:13 (UTC)

Shouldn't RUSTFLAGS be used for that?

bartus commented on 2021-06-01 07:42 (UTC)

Could we extract -j N from MAKEFLAGS and pass to cargo ?

Check out my solution for scons:

https://aur.archlinux.org/cgit/aur.git/tree/PKGBUILD?h=boost-python2#n38

local JOBS; JOBS="$(grep -oP -- "-j\s*[0-9]+" <<< "${MAKEFLAGS}")" || JOBS="-j1"
cargo build "${JOBS}" --locked --features "${_features:-}" --release --target-dir target

protolatte commented on 2021-06-01 07:15 (UTC)

v1.7 not building, got this error:

error: failed to run custom build command for `alpm v2.0.0`

TheToblin commented on 2021-06-01 06:37 (UTC)

Confirming that 1.7.0 works for me as well. It builds without a hitch and installs properly. Running and updating works as well. Built from git clone.