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.
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: | 982 |
Popularity: | 19.64 |
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)
- cargo (rustup-gitAUR, rust-nightly-binAUR, rust-gitAUR, rust-beta-binAUR, rustup-stubAUR, rust, rustup) (make)
- bat (bat-cat-gitAUR) (optional) – colored pkgbuild printing
- devtools (devtools32-gitAUR, devtools-gitAUR, devtools-doasAUR) (optional) – build in chroot and downloading pkgbuilds
Required by (31)
- aconfmgr-git (optional)
- arch-os-manager (optional)
- arch-update (optional)
- arch-update-git (optional)
- dec-bin
- dec-git
- fe
- fuzzy-pkg-finder (optional)
- fzpac (optional)
- fzpac-git (optional)
- iwant (optional)
- iwant-bin (optional)
- lsparu
- meta-package-manager (optional)
- meta-package-manager-git (optional)
- octopi (optional)
- packageprovides (optional)
- pacrs (optional)
- pacup-arch-git (optional)
- pacupdate-git
- Show 11 more...
Sources (1)
Latest Comments
« First ‹ Previous 1 2 3 4 5 6 7 .. 24 Next › Last »
tixetsal commented on 2024-09-20 14:27 (UTC)
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
ZhangHua commented on 2024-09-20 03:40 (UTC)
It seems that the cloned aur repo is staying at detached state, which results that we cannot upgrade to newer paru with old paru because paru will reset the repository to master branch, and the detached commit, which contains newer paru's PKGBUILD, will be lost.
ibanezfr commented on 2024-09-14 17:37 (UTC) (edited on 2024-09-14 17:38 (UTC) by ibanezfr)
This is a temporary workaround until a new release: https://github.com/Morganamilo/paru/issues/1239#issuecomment-2351021340
hirak99 commented on 2024-09-14 13:51 (UTC)
Yup. It's broken, but in paru upstream it is fixed as the alpm version has been bumped here, https://github.com/Morganamilo/paru/commit/90656a901479b77cb3b7a54e393dff9a0ca6a45f
We will need to wait until a new release is made.
For now, you could use paru-git.
tmarkee commented on 2024-09-14 13:35 (UTC)
@haxie: won't work ;-(
error: failed to run custom build command for
alpm v3.0.4 (https://github.com/archlinux/alpm.rs?rev=306342#306342ef)
Caused by:
process didn't exit successfully:
/home/tmarkee/paru/src/paru-2.0.3/target/release/build/alpm-fe8130be9696cf00/build-script-build
(exit status: 101)
--- stderr
thread 'main' panicked at /home/tmarkee/.cargo/git/checkouts/alpm.rs-a0070a235cf20bfa/306342e/alpm/build.rs:25:13:
this version of alpm.rs does not support libalpm v15.0.0 only v14.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...
haxie commented on 2024-09-14 12:29 (UTC)
@SteavenGamerYT No, you have just updated pacman, and so you need to rebuild paru.
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