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.

Sign up for GitHub

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

Jump to bottom

Flatpak doesn't allow automatic branch following for extension #4208

Open
hfiguiere opened this issue Apr 3, 2021 · 1 comment
Open

Flatpak doesn't allow automatic branch following for extension #4208

hfiguiere opened this issue Apr 3, 2021 · 1 comment

Comments

@hfiguiere
Copy link
Collaborator

Linux distribution and version

Fedora 33

Flatpak version

1.10.2

Description of the problem

Flatpak doesn't automatically update the extensions in their branch change at an update.

Steps to reproduce

  • An application (org.gimp.GIMP in that case) has an extension point defined with the version field set to 2-3.36.
  • This application gets updated to use the the GNOME 40 runtime. The version field for the extension point is changed to 2-40 because the runtime content is different and we assume the runtime are incompatible
  • The extensions org.gimp.GIMP.Plugins.* are updated to be on the branch 2-40
  • Everything is build
  • The user update org.gimp.GIMP

Expected

  • Flatpak notice a change in the extension version and will trigger an update of already installed extensions

Actual

  • Nothing else is updated and the user lost the plugins in GIMP.
@hfiguiere hfiguiere mentioned this issue Apr 3, 2021
Open
@hfiguiere hfiguiere mentioned this issue Apr 15, 2021
Closed
@vido89 vido89 mentioned this issue Jul 1, 2021
Open
@soredake soredake mentioned this issue Sep 12, 2022
Closed
@soredake
Copy link

It'll be nice if we can somehow link extensions/layers version to app versions to avoid situations like this flathub/org.freedesktop.Platform.VulkanLayer.MangoHud#17

@soredake soredake mentioned this issue Dec 3, 2022
Closed
2 tasks
@hfiguiere hfiguiere mentioned this issue Jan 27, 2023
Closed
7 tasks
@MatMaul MatMaul mentioned this issue Mar 16, 2023
Closed
@Perkolator Perkolator mentioned this issue Oct 18, 2023
Closed
@nurupo nurupo mentioned this issue Nov 5, 2023
Open
2 tasks
@nurupo nurupo mentioned this issue Apr 2, 2024
Closed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@hfiguiere @soredake