Zum Inhalt der Seite gehen
Small reminder for anyone who doesn't read fully (or at all) release news yet is using our #nightly #flatpak for testing latest code: you need to uninstall then reinstall the nightly flatpak with the commands given in the RC2 news:
https://www.gimp.org/news/2024/12/27/gimp-3-0-RC2-released/#flatpak

If you don't do so, you will be stuck on an ancient build without ever getting an update since we changed the AppID (it allows to see both stable and nightly versions side by side in your desktop).

GIMP - GIMP 3.0 RC2 Released 🎁

Release news for version GIMP 3.0 RC2
www.gimp.org
#flatpak #nightly
Sturmflut
I've only come across this twice now, but IMO there would be merit in #Flatpak being able to handle AppID changes.
Leaflet
Flatpak does have a system for EOLing an app or runtime which can tell you information, such as the new appid. But I can’t remember if there’s a built in way to automatically transition users to the new package.
Sturmflut
You're right! It doesn't only support "--end-of-life=REASON", but also "--end-of-life-rebase=ID". The latter can actually point to a new AppID.

I've never seen it in action, but I found an app on Flathub that actually changed its AppID this way and tried it. Seems to work as expected.

@GIMP Might be worth a try.

@GIMP
GIMP
Hi! Our currently main packaging contributor tried but didn't succeed: https://gitlab.gnome.org/GNOME/gimp/-/issues/12685#note_2332639

If any of you have any further information on how this is supposed to work, we welcome contributions.

Thanks!

Marking org.gimp.GIMP//master flatpak branch as end-of-life pointing to the new App-ID (#12685) · Issues · GNOME / GIMP · GitLab

Apparently it is possible to mark a flatpak branch as being end-of-life and pointing it to the new branch name. It might be interesting to flag our old...
GitLab
⇧