fedora

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