Alad Wenter
Alad Wenter
Likely from the `sudo install` call https://github.com/AladW/aurutils/blob/master/lib/aur-chroot#L143
I wrote an example for v9 which does chroot builds without `sudoers` configuration: https://github.com/AladW/aurutils/tree/master/examples#chroot-batch edit: 9.1. will have https://github.com/AladW/aurutils/pull/977
As far as aurutils is involved, it hardly matters what language you use, as long as you can fork/exec and handle stdin/stdout.
I think `aurutils` and `aurto` have different audiences. Former is a toolset to adapt to AUR workflows, latter more of an "install and forget" solution. Apart from that if https://github.com/alexheretic/aurto/issues/43...
I guess the mirrorlist is outdated? But with manjaro, all bets are off.
Possibly related: https://github.com/AladW/aurutils/issues/771
`makepkg --sign` doesn't work inside the container, because it has no access to the necessary environment variables. aurutils just runs `gpg` manually on the host.
You should take some care with `pacsync aurto` due to usual concerns with partial upgrades. This holds, especially with `chroot` builds, which always build against the latest available packages.
Most dependency choices are, due to the virtue of a local repository, left to `pacman`. You can use the interactive prompts by using `aur-sync` without `--no-confirm`. If you want better...
Notice you can use `--continue` to avoid `aur-sync` from calling `aur-fetch` again.