Arch Linux User Repository

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

The following changes fixed the build on my aarch64 systems today:

diff --git a/PKGBUILD b/PKGBUILD
index f503694..6289b7e 100644
--- a/PKGBUILD
+++ b/PKGBUILD
@@ -9,6 +9,7 @@ backup=("etc/paru.conf")
 arch=('i686' 'pentium4' 'x86_64' 'arm' 'armv7h' 'armv6h' 'aarch64')
 license=('GPL-3.0-or-later')
 makedepends=('cargo')
+makedepends_aarch64=('cargo' 'clang')
 depends=('git' 'pacman' 'libalpm.so>=14')
 optdepends=('bat: colored pkgbuild printing' 'devtools: build in chroot and downloading pkgbuilds')
 sha256sums=('b9c67f1390caacc949c2eb2a254e8cf37778f382c3c6b8d057fa6feb6eaeb0f9')
@@ -29,6 +30,10 @@ build () {
     export CARGO_PROFILE_RELEASE_LTO=off
   fi

+  if [[ $CARCH = aarch64 ]]; then
+    _features+="generate,"
+  fi
+
   cargo build --frozen --features "${_features:-}" --release --target-dir target
   ./scripts/mkmo locale/
 }

This doesn't built on arm. Please see this github issue https://github.com/Morganamilo/paru/issues/1154. The "generate" feature should be enabled when building aarch64 or armv7h.

Also clang should be a dependency.

I had the issue with the libalpm.so and it was that the mirror I was using that was out of sync (per https://archlinux.org/mirrors/status/ ) . After updating the mirror and updating, the newer libalpm was available.

@wag Thank you -- that clears things up for me. I'm on Endeavour OS, and happy to be patient. But this fact was not clear in the below comments. I'll look forward to the update and be glad to have paru working again!

@infernalbullfrog don't go with the advice the other person gave about symlinking libalpm with the older version, just undo this symlink. The proper way to solve your problem is to upgrade your system and then clean-build paru manually.

It seems you have not upgraded your system yet (otherwise you should have the binary /usr/lib/libalpm.so.15.0.0, instead of version 14.0.0). And paru in the AUR is already updated to use this newer version, while your system doesn't have it installed yet. So there is your problem.

So undo this symlink the other person suggested, then upgrade your whole system ( sudo pacman -Syu ). This will give you the new libalpm version. I am assuming you're running actual Arch (instead of Manjaro or other derivative which do not use/follow Arch repos and release schedules, in which case this may not work until next week or later - that's why using AUR packages is only really recommended for Arch itself, not for these other slower release derivatives).

Then after upgrading your system, clean-build paru manually. Of course you should already know how to do it, but in case you're still confused, this should do it:

rm -rf ~/paru/ && cd ~ && git clone https://aur.archlinux.org/paru.git
cd ~/paru/ && makepkg -si
cd ~ && rm -rf ~/paru/

@NeverSummer that doesn't always work.

I am trying to rebuild the package manually and it fails. I've created the symlink, and it still fails.

 ⮞ ls -l /usr/lib/libalpm*
lrwxrwxrwx 1 root root     13 Mar 15  2024 /usr/lib/libalpm.so -> libalpm.so.14
lrwxrwxrwx 1 root root     17 Mar 15  2024 /usr/lib/libalpm.so.14 -> libalpm.so.14.0.0
-rwxr-xr-x 1 root root 247784 Mar 15  2024 /usr/lib/libalpm.so.14.0.0
lrwxrwxrwx 1 root root     17 Sep 21 15:06 /usr/lib/libalpm.so.15 -> libalpm.so.14.0.0
 ⮞

And the error I get:

==> Starting build()...
warning: Patch `alpm v3.0.4 (https://github.com/archlinux/alpm.rs?rev=306342#306342ef)` was not used in the crate graph.
Patch `aur-depends v3.0.0 (https://github.com/Morganamilo/aur-depends?rev=30c2c1#30c2c150)` was not used in the crate graph.
Check that the patched package version and available features are compatible
with the dependency requirements. If the patch has a different version from
what is locked in the Cargo.lock file, run `cargo update` to use the new
version. This may also occur with an optional dependency that is not enabled.
   Compiling zerocopy-derive v0.7.35
   Compiling serde_derive v1.0.210
   Compiling tokio-macros v2.4.0
   Compiling futures-macro v0.3.30
   Compiling openssl-macros v0.1.1
   Compiling regex v1.10.6
   Compiling thiserror-impl v1.0.63
   Compiling url v2.5.2
   Compiling alpm v4.0.1
   Compiling rustix v0.38.37
   Compiling rustls-pemfile v1.0.4
   Compiling ahash v0.8.11
   Compiling crossbeam-epoch v0.9.18
   Compiling num-traits v0.2.19
   Compiling html5ever v0.27.0
   Compiling cssparser-macros v0.6.1
error: failed to run custom build command for `alpm v4.0.1`

Caused by:
  process didn't exit successfully: `~/paru/src/paru-2.0.4/target/release/build/alpm-dc0f1c88985d1af8/build-script-build` (exit status: 101)
  --- stderr
  thread 'main' panicked at ~/.cargo/registry/src/index.crates.io-6f17d22bba15001f/alpm-4.0.1/build.rs:25:13:
  this version of alpm.rs does not support libalpm v14.0.0 only v15.x.x is supported
  note: run with `RUST_BACKTRACE=1` environment variable to display a backtrace
warning: build failed, waiting for other jobs to finish...
==> ERROR: A failure occurred in build().
    Aborting...

I found a temporary fix for error: command failed: /home/<user>/.cache/paru/clone/paru: git rebase --stat::

cd ~/.cache/paru/clone/paru
git checkout master
git reset --hard ae76b1e

And then let paru to update itself: paru -Sau.

Boy I can't believe people still bother writing comments just to tell people they refuse to help them. If you're too lazy to rebuild and your paru is still stuck on the libalpm error you can indeed just run:

ln -s /usr/lib/libalpm.so.15 /usr/lib/libalpm.so.14

paru

rm /usr/lib/libalpm.so.14

It's fine. There you go. That's the quick and dirty thing you can copy-paste. It's fine to be critical of solutions like this, but outright refusing to provide them is being "Arch guy". We're better than that.

I would post the exact commands that I used, but if you don't know how to manually build packages then you really shouldn't be using a helper like paru. I say that in the most well-meaning way. Please go back to fundamentals and start there vs running commands you found on the internet.