For quite a while in neon we've been observing inconsistencies between desktop ids the same entity (e.g. org.kde.kdenlive) would sometimes be available as ID: org.kde.kdenlive and other times as ID: org.kde.kdenlive.desktop and as far as neon is concerned it would always have a superset of both.
The reason appears to be that when asgen autogenerates data from the desktop file it picks ID: org.kde.kdenlive whereas the actual upstream information is declaring it ID: org.kde.kdenlive.desktop client-side these two are not treated as equal resulting in duplicated entries.
Either the client should treat them as the same entity or the autogenerator ought to append .desktop I suppose.
$ appstreamcli search org.kde.kdenlive
Identifier: org.kde.kdenlive [desktop-application]
Name: Kdenlive
Summary: Nonlinear video editor by KDE
Package: kdenlive
Icon: kdenlive_kdenlive.png
---
Identifier: org.kde.kdenlive.desktop [desktop-application]
Name: Kdenlive
Summary: Nonlinear video editor for KDE
Package: kdenlive
Icon: kdenlive_kdenlive.png
The text was updated successfully, but these errors were encountered:
For quite a while in neon we've been observing inconsistencies between desktop ids the same entity (e.g. org.kde.kdenlive) would sometimes be available as
ID: org.kde.kdenliveand other times asID: org.kde.kdenlive.desktopand as far as neon is concerned it would always have a superset of both.The reason appears to be that when asgen autogenerates data from the desktop file it picks
ID: org.kde.kdenlivewhereas the actual upstream information is declaring itID: org.kde.kdenlive.desktopclient-side these two are not treated as equal resulting in duplicated entries.Either the client should treat them as the same entity or the autogenerator ought to append .desktop I suppose.
The text was updated successfully, but these errors were encountered: