Matthias Klumpp
Matthias Klumpp
Can you give examples of what such a "release name" would be? By being implemented as an XML attribute, there would be no way to translate it. Is that really...
This would definitely have to be a `name` element in a `release` though, and not an XML attribute... (for future-proofing and possibly localization).
This really can't just be my eyesight or my monitor, but are the AppStream-generated screenshot thumbnails really blurrier? They look exactly the same to me, only that the appstream-util one...
This is odd, I do not have the new version installed system-wide either (using the old libappstream), and I do not experience this bug. Is this on a pristine meson...
Oh, and: This is not a crossbuild. right? (doesn't look like it, but asking just in case)
Knowing the meson version would also be useful, as this might be a meson bug (there's nothing special that AppStream does here).
Can you check whether this works now with the recent Meson changes?
The only possible way this could happen is if your environment is unclean. Meson tries to guard against that by setting LD_LIBRARY_PATH, but that doesn't seem to be enough. So...
If we hide them, people wouldn't see any new ones and would just plainly apply "that flag that makes the validator shut up". What would be examples of hints that...
> Some maintainers don't want to use the new tag, because their upstream CI still uses, appstream-glib etc. I'd see that as a bug that they need to fix ;-)...