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: 1040
Popularity: 24.18
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 2 3 4 5 6 7 .. 25 Next › Last »

wag commented on 2024-09-22 15:33 (UTC) (edited on 2024-09-22 15:54 (UTC) by wag)

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

infernalbullfrog commented on 2024-09-21 22:13 (UTC) (edited on 2024-09-21 22:14 (UTC) by infernalbullfrog)

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

nicolasyang commented on 2024-09-21 07:36 (UTC)

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.

NeverSummer commented on 2024-09-21 05:17 (UTC) (edited on 2024-09-21 05:18 (UTC) by NeverSummer)

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.

tixetsal commented on 2024-09-20 14:27 (UTC)

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.

furrykef commented on 2024-09-20 05:47 (UTC)

Working for me now. I installed it the old-fashioned way by cloning the PKGBUILD and running makepkg and pacman.

urbenlegend commented on 2024-09-20 04:10 (UTC) (edited on 2024-09-20 04:25 (UTC) by urbenlegend)

I can not seem to upgrade paru with paru itself either. I get the following error message even after clearing the clone folder in .cache:

error: command failed: /home/user/.cache/paru/clone/paru: git rebase --stat:

ZhangHua commented on 2024-09-20 04:07 (UTC)

Yeah, cloning this aur repo and build manually with makepkg works, because the repo is not reset. You will see these outputs when cloning repo manually: 

$ LANG=C git clone https://aur.archlinux.org/paru.git
Cloning into 'paru'...
hint: Using 'master' as the name for the initial branch. This default branch name
hint: is subject to change. To configure the initial branch name to use in all
hint: of your new repositories, which will suppress this warning, call:
hint:
hint:   git config --global init.defaultBranch <name>
hint:
hint: Names commonly chosen instead of 'master' are 'main', 'trunk' and
hint: 'development'. The just-created branch can be renamed via this command:
hint:
hint:   git branch -m <name>
remote: Enumerating objects: 188, done.
remote: Counting objects: 100% (188/188), done.
remote: Compressing objects: 100% (132/132), done.
remote: Total 188 (delta 69), reused 173 (delta 56), pack-reused 0 (from 0)
Receiving objects: 100% (188/188), 55.26 KiB | 118.00 KiB/s, done.
Resolving deltas: 100% (69/69), done.
Note: switching to 'ae76b1e7afb2f604dc99afe16b01c6c5deeb0db0'.

You are in 'detached HEAD' state. You can look around, make experimental
changes and commit them, and you can discard any commits you make in this
state without impacting any branches by switching back to a branch.

If you want to create a new branch to retain commits you create, you may
do so (now or later) by using -c with the switch command. Example:

  git switch -c <new-branch-name>

Or undo this operation with:

  git switch -

Turn off this advice by setting config variable advice.detachedHead to false

And if you enter the directory, git log will show that HEAD is not origin/master

tixetsal commented on 2024-09-20 03:45 (UTC)

I removed paru-git and then built and installed this package manually without issue

« First ‹ Previous 1 2 3 4 5 6 7 .. 25 Next › Last »