I have run this command on all machines - and then forgot it. I was not in focus that the folder contents can vanish without my action. I have 8 machines running Arch Linux - and the issue was present on all machines... Very strange! Thanks to you for pointing me to the right direction.
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
- paczf
- paru-static
- parui (optional)
- parui-git (optional)
- paruz (optional)
- paruz-git (optional)
- pkg-listn (optional)
- pkg-listn-git (optional)
- plasma6-applets-arch-update-notifier (optional)
- ppac-git (optional)
- upgrade
Sources (1)
Latest Comments
« First ‹ Previous 1 .. 10 11 12 13 14 15 16 17 18 19 20 .. 24 Next › Last »
df8oe commented on 2022-03-22 18:23 (UTC)
whynothugo commented on 2022-03-22 17:38 (UTC)
@df8oe: It's empty by default on a clean arch install. You have to run the command I mentioned before using paru in chroot mode.
That's why I mentioned: I'm under the impression that this is not mentioned in some obvious place in the docs, but it only happens once when you set up a new system.
df8oe commented on 2022-03-22 17:16 (UTC)
@whynothugo: that was the issue. Strange that this folder was empty on all systems I own. I have not deleted any files there...
whynothugo commented on 2022-03-22 15:48 (UTC)
@df8oe: Is /var/lib/aurbuild/x86_64/root
empty? I've seen the same issue you're seeing each time I bootstrap a new system. You need to run mkarchroot /var/lib/aurbuild/aarch64/root base base-devel
.
I'm not sure if it's a bug in makechrootpkg
, or just a missing steps in the docs somewhere.
df8oe commented on 2022-03-22 15:24 (UTC)
@MarsSeed: Misunderstanding. I meant I cannot build any other package using
paru --chroot -S package_name
which worked before flawlessly. I cannot provide the exact time the issue popped up: I do not build in chroot very often.
MarsSeed commented on 2022-03-22 15:06 (UTC)
@df8oe, last change was on 2022-02-17.
And it was only a version bump.
Therefore the error you've encountered is unlikely to be coming from paru's PKGBUILD.
df8oe commented on 2022-03-22 13:14 (UTC)
paru stops building in a chroot environment on all of my machines:
==> ERROR: This must be run in a directory containing a PKGBUILD.
Fehler: Ausführung fehlgeschlagen: makechrootpkg -C /tmp/.tmplqx3u4 -M /etc/makepkg.conf /var/lib/aurbuild/x86_64/root base-devel:
Any ideas what can be the cause?
MarsSeed commented on 2022-03-20 10:11 (UTC)
Oh, and base-devel
is not a package, therefore it does not have dependencies.
It is a package group, which is not more than a textual tag given to certain packages.
To install all packages "tagged" with base-devel
, users have to run:
sudo pacman -Syu --needed base-devel
MarsSeed commented on 2022-03-20 10:07 (UTC)
@RobinHood2015 pkgconf
is part of the group base-devel
on Manjaro.
Neither Arch nor Manjaro installs base-devel
group as a whole upon fresh install.
Users have to manually install this group of packages before using foreign PKGBUILDs.
sajattack commented on 2022-03-20 07:04 (UTC)
Tested on riscv64. Would you be willing to add this as a supported arch?
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