Actionless Loveless

@lectrode could you please apply this patch to installed pikaur and next upload the file `~/.local/share/pikaur/aur_repos//.SRCINFO` from the failed attempt? ```diff diff --git a/pikaur/aur.py b/pikaur/aur.py index d29b771..01d5653 100644 --- a/pikaur/aur.py...

> print(srcinfo.package_name) > print(srcinfo.get_value('pkgbase')) > pikaur-git > None what i can see so far is what srcinfo is empty for some reason i'll try to figure out if it might...

@lectrode also i see in your test runs you're always using root/dynamic_users is it the same reproducible when running pikaur from unprivileged user without systemd dynamic users?

i think it would rather make sense to bypass `--nodeps` option from pikaur -G to underlaying pacman command which causing the error in this case

it does not function at all: ``` $ grep -R assume pikaur pikaur/core.py: # If BOM is not provided, then assume its the codepage pikaur/args.py: (None, 'assume-installed', None), # @TODO...

> adding a confirmation message e.g. "Press Enter to continue" message would be enough IMO such prompt also would require thinking of default choice for both manual and --noconfirm modes

> with --noconfirm it skips the prompt, that's no changes compared with today's behaviour in this case should the news be marked as read (as now) or not?

it sounds like a `--devel` option, isn't it?

ah, you mean to rebuild repo packages from source? yeah, there is no such option, though you can do it by combining two pikaur operations: `pikaur -G mpv && pikaur...

pikaur already have `--rebuild` flag for AUR packages i was thinking what it could be possible to implement handling that flag for repo packages and do the same as in...