Actionless Loveless

that could happen if you did Ctrl+C while it checking out the repo or smth like that, just hit 'C' or 'R' to fix it

and could you do `git status` inside that problematic directory while the error message occurs?

@steven-omaha fixed the clone problem

@jody-frankowski oh, that's a new error :-)

@jody-frankowski what you can do now is to do `pacman -R zfs-dkms zfs-utils spl-utils spl-dkms` in another terminal and hit `Y` to retry in pikaur's prompt

so far i think it could be solved only by building inside chroot using makechrootpkg or setting chroot env using systemd. both will require extra space for installing again all...

also i think to avoid reinstalling all the deps inside chroot each time mb to keep packcages installed in chroot between the builds but just if build fails to show...

hm, or to avoid that dirty hack with caching/flushing chroot: in pikaur config file to set to build in chroot only specific packages (unless `*` is specified to build all...

@micwoj92 thanks for update, i'll rename the ticket to be more general

try: ```bash systemd-run --pipe --wait -p DynamicUser=yes -p CacheDirectory=pikaur -E HOME=/tmp -p WorkingDirectory=/var/cache/pikaur/build/aurutils gpg --recv-keys 6BC26A17B9B7018A ```