sidt4

FYI https://gitlab.gnome.org/GNOME/gnome-software/-/issues/1697#note_1837659

> Issues pages are always for the latest version found in a package archive. Yes, but displaying the version information helps in lot of places. I was asked which version...

> Awesome. Anyone else have Gnome 44 test results? Works fine after adding "44" to `metadata.json` in fedora rawhide GNOME Shell 44. Still facing https://github.com/paradoxxxzero/gnome-shell-system-monitor-applet/issues/784 though its not a blocker....

> So I guess we can simply update this `metadata.js` file to allow this nice add-on to run on newer GNOME versions. You probably meant `metadata.json`.

Could be https://github.com/flatpak/xdg-desktop-portal-gtk/pull/448. I don't have Fedora / silverblue to confirm this.

@matthiasclasen: this is a portal issue. Refer https://github.com/flatpak/xdg-desktop-portal-gtk/pull/448

Just FYI. 1. /usr/share/metainfo/org.gnome.DejaDup.metainfo.xml `(appstream-util:295440): As-WARNING **: 14:32:40.574: Unknown tag: ` 2. /usr/share/metainfo/org.inkscape.Inkscape.appdata.xml: `(appstream-util:295789): As-WARNING **: 14:32:42.416: Unknown tag: `

Yes, it seems like `appstreamcli` is better. But, then why keep the validator ? It's confusing.

Can we at least print a warning when using `appstream-glib` saying `"appstreamcli should be used etc."` ? Point here is that, it sounds good for those who are aware of...

Example: ```diff $ git diff data/metainfo/org.gnome.Software.metainfo.xml.in diff --git a/data/metainfo/org.gnome.Software.metainfo.xml.in b/data/metainfo/org.gnome.Software.metainfo.xml.in index 8cecc67ce..4f421b6db 100644 --- a/data/metainfo/org.gnome.Software.metainfo.xml.in +++ b/data/metainfo/org.gnome.Software.metainfo.xml.in @@ -66,7 +66,7 @@ Validate with `appstreamcli validate *.metainfo.xml` --> - + This...