Arch Linux

Affected Version

Tested:
yay v11.1.0 - libalpm v13.0.1
yay v11.1.0.r4.g09695c6 - libalpm v13.0.1
The issue likely goes back for many versions.

Describe the bug

If you attempt to install an AUR devel package and it fails for whatever reason, the package still gets added to vcs.json. This means that the git repository for the package will be checked on any system upgrade with

As discussed in THIS post, it is useful to execute things back in to the host.

It could be of use to generate an host-exec script in (for exampel) /usr/local/bin in the container.

Not all distributions in the compatibility list support flatpak-spawn so I would use chroot by default for that.

Example:

Adding an non existing project to a "_meta" file leads to 500.

How to reproduce it:

• Open a "meta" file from a page
• Add an non existing project to as path
• Save the file

i.e:

  <repository name="openSUSE_15.2">
    <path project="foo:bar" repository="openSUSE_15.2"/>
    <arch>x86_64</arch>
    <arch>armv7l</arch>
    <arch>aarch64</arch>
    <arch>ppc64le</arch>
  </rep

I used the install script, chose wine staging but got a warning in the terminal that the wine staging the script wants to install and the one on my system are not compatible. It asks if i want to uninstall my current wine staging and install the new one.
I declined that to keep my current one as this machine is also my gaming computer and the games i run work perfectly fine so i didnt want to dis