Colin Woodbury

Thanks for the report. Would you be willing to double-check if the same issue occurs when using the in-development Aura 4 beta? Here's how you'd install it: ``` cargo install...

The `aura-git` package does not yet track the Rust build. I have all of that work slated for June.

Can you provide me that specific command you're using to build the package that's failing? I'd like to try reproducing on my end.

I'm looking into it.

I was able to build it just now with the Aura 4 beta, although I had to make some improvements regarding `checkdeps` to deal with some of the Python packages....

I saw this too during my tests. It appears that within the build process, `meson` doesn't want `configure` ran more than once. To fix this: ``` > cd ~/.cache/aura/builds >...

It used to a problem that the compression algorithm used to finalise built packages (thus producting a`.pkg.tar.zst` file, etc.) wasn't being respected if the user had changed it within their...

Given that there are two `pkg` files, we know that this is a "split package". Just checking: did you manually alter the PKGBUILD in anyway, perhaps with `--hotedit`?

I just ran the build again, and it only produces the non-debug version for me, and I can only see the one tarball copied into the cache. Let's check if...

``` > aura -Aw gradience aura :: Cloning gradience... aura :: Done. > cd gradience/ > makepkg --packagelist /home/colin/code/aur/gradience/gradience-0.4.1_patch1-1-x86_64.pkg.tar.zst ``` What does the `OPTIONS` field of your `/etc/makepkg.conf` look like?...