@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.
Search Criteria
Package Details: paru 2.0.4-1
Package Actions
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: | 1044 |
Popularity: | 21.83 |
First Submitted: | 2020-10-19 00:43 (UTC) |
Last Updated: | 2024-09-20 18:50 (UTC) |
Dependencies (6)
- git (git-gitAUR, git-glAUR)
- libalpm.so (pacman)
- pacman (pacman-gitAUR, pacman-fancy-gitAUR)
- cargo (rust-nightly-binAUR, rust-gitAUR, rust-beta-binAUR, rustup-stubAUR, rustup-gitAUR, rust, rustup) (make)
- bat (bat-cat-gitAUR) (optional) – colored pkgbuild printing
- devtools (devtools-gitAUR, devtools-doasAUR) (optional) – build in chroot and downloading pkgbuilds
Required by (40)
- aconfmgr-git (optional)
- arch-os-manager (optional)
- arch-update (optional)
- arch-update-git (optional)
- archlink (optional)
- ash-git
- autoinstallpackages (optional)
- dec-bin
- dec-git
- dpw (optional)
- fe
- fuzzy-pkg-finder (optional)
- fzpac (optional)
- fzpac-git (optional)
- garuda-rani (optional)
- garuda-rani-git (optional)
- iwant (optional)
- iwant-bin (optional)
- lsparu
- meta-package-manager (optional)
- Show 20 more...
Sources (1)
Latest Comments
« First ‹ Previous 1 .. 17 18 19 20 21 22 23 24 25 Next › Last »
alerque commented on 2021-06-01 08:57 (UTC) (edited on 2021-06-01 09:00 (UTC) by alerque)
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.
starquake commented on 2021-06-01 06:14 (UTC) (edited on 2021-06-01 06:15 (UTC) by starquake)
@m040601: Version 1.7.0 has been released and works for me
m040601 commented on 2021-06-01 03:30 (UTC) (edited on 2021-06-01 03:31 (UTC) by m040601)
PKGBUILD out of date : does not support libalpm v13.0.0 only v12
According to https://github.com/Morganamilo/paru,
Installation
sudo pacman -S --needed base-devel
git clone https://aur.archlinux.org/paru.git
cd paru
makepkg -si
this gives
error: failed to run custom build command for `alpm v1.1.12`
Caused by:
process didn't exit successfully: `/dev/shm/paru/src/paru-1.6.1/target/release/build/alpm-f7f9f91cea045c0b/build-script-build` (exit code: 101)
--- stderr
thread 'main' panicked at 'this version of alpm.rs does not support libalpm v13.0.0 only v12.x.0 - v12.x.2 is supported', /home/a1/.cargo/registry/src/github.com-1ecc6299db9ec823/alpm-1.1.12/build.rs:18:9
note: run with `RUST_BACKTRACE=1` environment variable to display a backtrace
warning: build failed, waiting for other jobs to finish...
class101 commented on 2021-05-15 15:39 (UTC)
For me Paru works a lot better than Yay. The problem that bothered me the most with this last one, it was always missing updates of git packages. I see you reworked this part, thank you for that.
Now I can fully trust my AUR helper because it does things the right way :)
androide7461 commented on 2021-05-10 21:02 (UTC)
@totogtr thank you! Had that issue for a while now. Thx for the fix :)
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