Matthias Klumpp

Since AppStream may add new things in future, having its revision pinned to the runtime is probably unexpected - when it's a host dependency, Flatpak could say "require at least...

@barthalion The `appstreamcli compose` command will generate mostly legacy-free output - but nothing is stopping you from just adding a `mv /files/share/swcatalog /files/share/app-info` after the compose to keep things running...

@barthalion This was very helpful, thanks! The problem was that AppStream didn't expect that someone would set `--prefix=` to an empty string (which would mean "look in the current directory"...

@daharoni Yes, this is a known issue, I can definitely reproduce this here. I haven't looked into this in detail yet, but it's highly likely just like you said: Another...

> Very likely this is our software somewhat improperly using a UVC control channel to send number of frames received by the DAQ PCB. Potentially Windows has updated its UVC...

Yes, and AFAIK Elementary is using appstream-generator for everything already... For asgen, you also need a 64x64 (or larger) icon, but it will include 48x48px icons as well.

It's already extremely large on Debian too, and we don't have binary deltas for the icon tarballs yet. We do however have a CDN, and appstream-generator allows certain icon types...

Yes, looks like Flatpak hardcodes that, which isn't ideal... But also https://github.com/flatpak/flatpak-builder/pull/517 still isn't solved, so without that addressed there wouldn't even be other icon sizes that Flatpak could consider.

For a while there was still tools using `appstream-glib` - nowadays we could probably remove it from Linux distributions, but then again, if someone needs it to reproduce previous behavior...

> The alternative is to just run appstreamcli if the user types in appstream-util validate. @ximion any concerns about this? The two tools are not quite 100% compatible - wouldn't...