Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

ublue-system-flatpak-manager uses the fedora repo instead of flathub #788

Closed
ispanos opened this issue Jan 4, 2024 · 2 comments
Closed

Comments

@ispanos
Copy link
Contributor

ispanos commented Jan 4, 2024

Describe the bug

When someone populates the flatpak/system/install list, flatpaks are installed using the fedora remote.

  • ublue-system-flatpak-manager removes the fedora remote with --user
  • L26 flatpak install --system --noninteractive flathub ${INSTALL_LIST[@]}
  • L41 flatpak remote-delete fedora --force

The flathub remote is never installed, thus flatpaks are installed from the fedora remote. Then it gets removed, which disables updates for those packages.

What did you expect to happen?

The expected behavior would either be to fail, since flathub is specified in L26 but it is not installed. This is probably a bug of the flatpak install command.

Output of rpm-ostree status

No response

Extra information or context

I can think of two solutions:

  1. Install the flathub repo with --system and remove the fedora repo with --system before installing flatpaks.

Unfortunately this causes all future flatpak installation to require --user, --system or user interaction for all installations in the terminal. If more that one remotes are installed, they need to be specified.

  1. Switch to system-wide flatpak installations and install the flathub remote with --user only for non-wheel users, who I believe can't install flatpaks system-wide.

Installing the flathub remote, install the packages, and then remove the flathub remote will not fix the issue of not getting updates.

@castrojo
Copy link
Member

castrojo commented Jan 4, 2024

Related: #789

@KyleGospo
Copy link
Member

#790

@ispanos ispanos closed this as completed Feb 7, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants