I’m trying to understand how this happens. If you browse apps in Discover, you will notice that some apps are successfully grouped into one item entry and then you can choose which source you want to install it from, like:
On some other apps this won’t happen, resulting on duplicated entries like:
Is there a central database to map different sources like package-kit/apt, Flatpak and Snap? How to contribute to the app metadata on different sources? What exactly makes Discover to group them together?
Hi - If I had to guess without a deep-dive of Discover’s source code, it would be some sort of mismatch between how the application’s ID has been defined when packaged by your Linux distribution, vs. how the application’s ID has been defined when uploaded to Flathub as a Flatpak.
In this case, it looks like Ubuntu/Debian packaging shows Filezilla with the ID org.filezilla-project.FileZilla, including a dash. Flathub shows it as org.filezillaproject.Filezilla, with no dash (and different capitalization, FWIW).
It could be, of course, that the same developers or packagers are involved in both cases and just didn’t use the same name both times, but in this case with FileZilla it looks like the Flatpak was being maintained by someone outside the FileZilla project team (who was running into issues getting alerted to new versions), which will make it more likely for something to not match up quite correctly.
In this particular case, since the Flatpak on Flathub is out of sync and seems to be running behind on versions, a friendly request to the Flatpak maintainer to see what the status is might help? (Or if you’re particularly passionate about the software, perhaps to dive in and help as well with the Flatpak packaging?)
Hope this helps,
1 Like
Thanks for pointing that out, it seems there is already an issue open with the FlatPak repo about the id. (sorry can’t include links not sure why)
I’m not sure of the implications of changing a flathub id for existing installations of the software, but indeed it seems incorrect.