Since b30ab47408a4, PackageKit has been embedding a severity code into the Package signal's info field. That change included updates to packagekit-glib2 that decode the two original values now embedded in that field, but it looks like PackageKit-Qt never got a corresponding update. Consequently, Qt clients expecting to find certain values in that field no longer work correctly.
For example, KDE Discover uses that field to distinguish security updates from normal updates. It can no longer do so, because it checks for an InfoSecurity value, but PackageKit sends (InfoSecurity << 16 | InfoSecurity) instead. Security updates are therefore no longer getting priority or special indicators to alert the user to their importance.
Shouldn't PackageKit-Qt be updated, for parity with packagekit-glib2 and to keep clients from remaining broken?
Since b30ab47408a4, PackageKit has been embedding a severity code into the Package signal's info field. That change included updates to packagekit-glib2 that decode the two original values now embedded in that field, but it looks like PackageKit-Qt never got a corresponding update. Consequently, Qt clients expecting to find certain values in that field no longer work correctly.
For example, KDE Discover uses that field to distinguish security updates from normal updates. It can no longer do so, because it checks for an InfoSecurity value, but PackageKit sends (InfoSecurity << 16 | InfoSecurity) instead. Security updates are therefore no longer getting priority or special indicators to alert the user to their importance.
Shouldn't PackageKit-Qt be updated, for parity with packagekit-glib2 and to keep clients from remaining broken?