Arch Linux User Repository

Upon revision, pat-aur actually doesn't need devtools anymore. So it doesn't depend on systemd. I was using pkgctl for some stuff but not anymore.

Thanks a lot @patlefort, I was sure I read abour a wrapper around aurutils somewhere some time back, aurutils in turn depends on devtools, and systemd-nspawn.

I use aurutils, and if I used plain arch I'd be happy to use pat-aur. Sadly, I'm one of those who disagree with the systemd model, and I instead use artix, and my init system is dinit. Long time ago even before systemd-nspawn showed up, I requested Alad through a GH issue to support artix, by having two backends, one using devtools and the other using artools (the equivalent to devtools on artix) which also support clean chroot. As devtools and artools are pretty similar, except artools doesn't depende on anything systemd, supporting the two backends, for someone who really knows where to look at, is as simple as evaluating if system is present, if so, use the devtools stuff, otherwise use the artools stuff. He declined saying aurutils only support arch, and no derivatives (though any systemd derivative is supported), so I didn't insist. I didn't feel as understanding aurutils code that much (although I had to navigate its bash code for several reasons) as to make a fork myself for artix, but nevertheless I still would have needed to ask you to support the aurutils fork, jeje.

All that to say, I'm sort of out of luck automating through aurutils installing/upgrading packages using clean chroot. Actually I had to learn how to do it on artix, hehe. Thanks a lot for pat-aur though, I've heard the ones liking to use clean chroot (I wanted to be one of those) really appreciate your AUR helper.

@je-vv: You could try pat-aur, developed by yours truly.

@patlefort, you were right, I needed to build on a clean chroot to make it work. I already tried it and it's working fine. Sadly, building on clean chroot enables only aurutils as an aur helper, which can't be used on non systemd derivatives of arch. But you were right.

I'm wondering how come the tauri.conf.json gets lost just because not using a clean chroot.

At any rate, good to know it's building and working.

@touste, it's working if building on clean chroot as indicated by @patlefort.

Thanks a lot !

Got the same error today when upgrading:

> tauri build -b deb

thread '<unnamed>' panicked at crates/tauri-cli/src/helpers/app_paths.rs:119:5:
Couldn't recognize the current folder as a Tauri project. It must contain a `tauri.conf.json`, `tauri.conf.json5` or `Tauri.toml` file in any subfolder.
note: run with `RUST_BACKTRACE=1` environment variable to display a backtrace
/home/master/.cache/yay/open-tv/PKGBUILD: line 19: 117291 Aborted                 (core dumped) npm run -- tauri build -b deb

Can you try building in a clean container? With something like makechrootpkg.

It's failing to build with:

> tauri build -b deb

thread '<unnamed>' panicked at crates/tauri-cli/src/helpers/app_paths.rs:119:5:
Couldn't recognize the current folder as a Tauri project. It must contain a `tauri.conf.json`, `tauri.conf.json5` or `Tauri.toml` file in any subfolder.
note: run with `RUST_BACKTRACE=1` environment variable to display a backtrace
/home/vasqueja/.pkgs/src/laur/open-tv/PKGBUILD: line 19:  8001 Aborted                 npm run -- tauri build -b deb
==> ERROR: A failure occurred in build().
    Aborting...

Any hints? Thanks !