default-flatpaks module, no flathub

in my recipe I have
- type: default-flatpaks
configurations:
- scope: user
notify: false
repo:
name: cosmic
title: COSMIC Flatpak
url: https://apt.pop-os.org/cosmic/cosmic.flatpakrepo
- type: default-flatpaks
configurations:
- scope: user
notify: false
repo:
name: cosmic
title: COSMIC Flatpak
url: https://apt.pop-os.org/cosmic/cosmic.flatpakrepo
but my image only has COSMIC Flatpak listed when using flatpak remotes -d When using scope system flathub is listed. Am I dong something wrong or is this intentional?
17 Replies
xyny
xyny4w ago
ublue images have system flathub by default, i think default-flatpaks module adds only remotes that it is configured to add the default values for repo configure flathub, but here you have overridden repo in your only configuration solution: add another configuration with scope: user but leave repo undefined
a64z
a64zOP4w ago
this is the result of
- type: default-flatpaks
configurations:
- scope: user
notify: false
repo:
name: cosmic
title: COSMIC
url: https://apt.pop-os.org/cosmic/cosmic.flatpakrepo
- scope: user
repo:
name: flathub
title: Flathub
- type: default-flatpaks
configurations:
- scope: user
notify: false
repo:
name: cosmic
title: COSMIC
url: https://apt.pop-os.org/cosmic/cosmic.flatpakrepo
- scope: user
repo:
name: flathub
title: Flathub
No description
a64z
a64zOP4w ago
- type: default-flatpaks
configurations:
- notify: false
scope: user
repo:
name: cosmic
title: COSMIC
url: https://apt.pop-os.org/cosmic/cosmic.flatpakrepo
- notify: false
scope: user
repo:
name: flathub
title: Flathub
url: https://dl.flathub.org/repo/flathub.flatpakrepo
- type: default-flatpaks
configurations:
- notify: false
scope: user
repo:
name: cosmic
title: COSMIC
url: https://apt.pop-os.org/cosmic/cosmic.flatpakrepo
- notify: false
scope: user
repo:
name: flathub
title: Flathub
url: https://dl.flathub.org/repo/flathub.flatpakrepo
Same effect
xyny
xyny4w ago
if you use the bluebuild-flatpak-manager to manually apply the user configurations, is there some error message or does it work then? you can also use the show command to see if the configurations are interpreted correctly it is possible that having the install array be empty causes an error with the current code of the module, since no checks are made before calling flatpak adding the repo happens before installation, though, so i don't know why that wouldn't work
a64z
a64zOP4w ago
I do not understand, using this on my recipe on a fresh install from iso, I still dont have the Flatpak User repo.
No description
xyny
xyny4w ago
did you try applying manually bluebuild-flatpak-manager apply user i think
a64z
a64zOP4w ago
yes, i also tried to disable and enable
xyny
xyny4w ago
what was the output of apply
a64z
a64zOP4w ago
No description
xyny
xyny4w ago
ah, it's trying to run the commands in interactive mode? that may or may not be a problem try piping to less so we see if flatpak is smart about it it might be trying to install an empty string to be honest
a64z
a64zOP4w ago
No description
xyny
xyny4w ago
i'm on my phone with 6% battery right now but i can add the change in a bit yeah, this is probably it
a64z
a64zOP3w ago
I ended up with - type: default-flatpaks
configurations:
- scope: user
repo:
name: flathub
title: Flathub
install:
- app.zen_browser.zen
- scope: user
repo:
name: cosmic
title: COSMIC
url: https://apt.pop-os.org/cosmic/cosmic.flatpakrepo
install:
- io.github.cosmic_utils.sysinfo-applet
- dev.cappsy.CosmicExtAppletLogoMenu
configurations:
- scope: user
repo:
name: flathub
title: Flathub
install:
- app.zen_browser.zen
- scope: user
repo:
name: cosmic
title: COSMIC
url: https://apt.pop-os.org/cosmic/cosmic.flatpakrepo
install:
- io.github.cosmic_utils.sysinfo-applet
- dev.cappsy.CosmicExtAppletLogoMenu
a64z
a64zOP3w ago
so now it will give an error unless a package is set to install?
xyny
xyny3w ago
no, it will work regardless of if you set any flatpaks to install or not
a64z
a64zOP3w ago
Ok great 👍🏻. Thanks for the fix

Did you find this page helpful?