I just tried out to run my own spin using BlueBuild. Everything works great, however it seems the default Flatpaks I specified are not installing. This is the case both for my regular system which was already set up, but also when I built an ISO and installed that in GNOME Boxes. Packages that I defined to be installed in rpm-ostree work fine. The interesting thing is that the GitHub Action does seem to handle the flatpaks, as I did get an error when I pointed to a flatpak from the fedora repository (it's not on Flathub with that name, so it couldn't find it). So it's not like the default flatpaks are ignored.
Is there something I'm doing wrong, or is this a bug perhaps with the new default-flatpak module?
For reference, I have my flatpaks defined in a seperate yaml file called
default-flatpaks.yml
default-flatpaks.yml
. Then I just point to that in my regular recipe like
- from-file: default-flatpaks.yml
- from-file: default-flatpaks.yml
The yml file with my default flatpaks is identical to the one in the example, but with different flatpaks of course.
Adds a check when flatpak list for the apps and runtimes is empty. Fixes an issue where the flatpaks wouldn't install when no runtimes or apps where installed in user-space, due to an empty...