| Summary: | Discover flatpak runtimes are listed as "refresh" but are for "new" versions | ||
|---|---|---|---|
| Product: | [Applications] Discover | Reporter: | yizel7 |
| Component: | Flatpak Backend | Assignee: | Plasma Bugs List <plasma-bugs> |
| Status: | RESOLVED FIXED | ||
| Severity: | normal | CC: | aleixpol, EpicTux123, gmeligio, jgrulich, nate, prettyvanilla, travier |
| Priority: | HI | ||
| Version: | 5.26.5 | ||
| Target Milestone: | --- | ||
| Platform: | Arch Linux | ||
| OS: | Linux | ||
| See Also: | https://bugs.kde.org/show_bug.cgi?id=491328 | ||
| Latest Commit: | https://invent.kde.org/plasma/discover/commit/3d2006de8fdc8fd4d5e4976b5a0f478743fa85d5 | Version Fixed In: | 5.27 |
| Sentry Crash Report: | |||
| Attachments: | refresh | ||
|
Description
yizel7
2023-01-11 04:00:35 UTC
Created attachment 155202 [details]
refresh
Can confirm. in Arch linux, packages that have been rebuilt for the same version have a different appending number added like (version)-#. This could be a way to better convey the information to the user. example from pacman would be: flatpak 1:1.15.1-1 then if a rebuild has happened with a flag or config change it is still the same version of flatpak but in pacman the "new" package would now say flatpak 1:1.15.1-2 then another rebuild flatpak 1:1.15.1-3 A possibly relevant merge request was started @ https://invent.kde.org/plasma/discover/-/merge_requests/460 Git commit 2a7125cbb643daf57beff53fba70d75a86d66c05 by Aleix Pol. Committed on 31/01/2023 at 15:44. Pushed by apol into branch 'master'. flatpak: Make sure we are reading the correct metadata Also fetch the metadata for the apps that are available on the repo but have different branches to choose from. Since the branches model is not something appstream accounts for, so we all get confused. Therefore, we don't look for it in the metainfo file from the app and just add the bundle to it so it fits with the rest of components. M +22 -13 libdiscover/backends/FlatpakBackend/FlatpakBackend.cpp https://invent.kde.org/plasma/discover/commit/2a7125cbb643daf57beff53fba70d75a86d66c05 Git commit 3d2006de8fdc8fd4d5e4976b5a0f478743fa85d5 by Aleix Pol Gonzalez, on behalf of Aleix Pol. Committed on 31/01/2023 at 15:52. Pushed by apol into branch 'Plasma/5.27'. flatpak: Make sure we are reading the correct metadata Also fetch the metadata for the apps that are available on the repo but have different branches to choose from. Since the branches model is not something appstream accounts for, so we all get confused. Therefore, we don't look for it in the metainfo file from the app and just add the bundle to it so it fits with the rest of components. (cherry picked from commit 2a7125cbb643daf57beff53fba70d75a86d66c05) M +22 -13 libdiscover/backends/FlatpakBackend/FlatpakBackend.cpp https://invent.kde.org/plasma/discover/commit/3d2006de8fdc8fd4d5e4976b5a0f478743fa85d5 Hello, I'm reopening this issue because the main problem still exists. While I don't see any metadata problem anymore (which was fixed), the problem related to using the word "Refresh" for new versions is still present on Plasma 6.1.3. Without a screenshot that shows what you're seeing, it's not clear that it's really an old issue, or a new, slightly different one. Please open a new bug report that includes a screenshot that shows the issue, as well as the output of `flatpak update` to make sure it really is a Discover-specific issue and not caused by the app itself failing to increase its version number for the update. |