| Git Clone URL: | https://aur.archlinux.org/auracle-git.git (read-only, click to copy) |
|---|---|
| Package Base: | auracle-git |
| Description: | A flexible client for the AUR |
| Upstream URL: | https://github.com/falconindy/auracle |
| Keywords: | aur |
| Licenses: | MIT |
| Conflicts: | auracle |
| Provides: | auracle |
| Submitter: | Foxboron |
| Maintainer: | artafinde (falconindy) |
| Last Packager: | falconindy |
| Votes: | 128 |
| Popularity: | 1.22 |
| First Submitted: | 2017-07-02 16:40 (UTC) |
| Last Updated: | 2025-04-16 17:39 (UTC) |
jaap: can't reproduce locally - building in clean chroot works just fine. Not sure why according to your log you can download the fmt-release artifact but not the fmt-meson-patch meson patch.
Clearly this is not running on a clean chroot environment as suggested because your logs show evidence of cmake which is not included in dependencies.
This package wont build with the following log: https://pastebin.com/2VvN7V65
I do have internet, as evident by this post, and can download the linked file fine via firefox
(This is a clean build, after hitting the cache issue)
Hi guys, I'm having problems for building this package:
==> Starting build()...
Directory does not contain a valid build tree:
/home/pisotte/AUR/auracle-git/src/auracle/build
==> ERROR: A failure occurred in build().
For anyone else stupid like me, the solution for the validity check error was to delete the cache as explained below by @Volker_Weissmann, but your cache path will be different from "~/.cache/pacaur/auracle-git" if you are not using the "pacaur" package manager
There's a package build already which you can try out if you have issues from my repo.
Same problem as xiretza here. rm -rf ~/.cache/pacaur/auracle-git/ solved it
Remember to delete the abseil patch manually, if you have configured your own src folder (for some reason).
xiretza is right. I use no AUR helper, only makepkg and got the same error. My "fix" was deleting auracle-git folder then clone it again. (Yes, I know I am lazy).
xiretza is right. That is, if makepkg downloaded the patch files previously, it won't try to redownload them if the URL changed (because how would it know?).
Considering they're patches, perhaps they should be included in the AUR repository itself?
Pinned Comments
artafinde commented on 2022-01-26 09:15 (UTC) (edited on 2022-01-29 10:24 (UTC) by artafinde)
If the build fails:
SRCPKGDESTdirectoryThere's a package build already which you can try out from my repo.
falconindy commented on 2020-05-31 15:35 (UTC) (edited on 2025-04-28 14:23 (UTC) by falconindy)
FAQ:
PATHhandled by/etc/profile.d/perlbin.shmakepkg -A. The "any" architecture is reserved for packages with architecture independent files (and compiled C++ is not).