On Monday, May 12, 2025 5:53:34 AM Mountain Standard Time Peter Blackman wrote: > Hi, > > I'm reopening this bug as I am still seeing > appstream-metadata-validation-failed in > https://udd.debian.org/lintian/?packages=cevomapgen > > I cannot see anything wrong with the metadata, > and cannot reproduce the issue locally. > > No issues with the package reported here. > https://appstream.debian.org/sid/main/issues/index.html > > > Regards, > Peter
In my experiences, this particular error has to do with inconsistencies between the appstream metadata file name, the appstream ID name, and the desktop file name. In my experience, the following always resolves the issue. 1. Use reverse DNS naming for the appstream metadata file appended by metainfo.xml. 2. Use reverse DNS naming for the appstream ID. 3. Use reverse DNS naming for the desktop file appended by .desktop. For example, see privacybrowser: 1. Reverse DNS naming for the appstream metadata file: com.stoutner.privacybrowser.metainfo.xml https://salsa.debian.org/soren/privacybrowser/-/blob/master/src/ com.stoutner.privacybrowser.metainfo.xml?ref_type=heads 2. Reverse DNS naming for the appstream ID: com.stoutner.privacybrowser https://salsa.debian.org/soren/privacybrowser/-/blob/master/src/ com.stoutner.privacybrowser.metainfo.xml?ref_type=heads#L26 3. Reverse DNS naming for the desktop file: com.stoutner.privacybrowser.desktop https://salsa.debian.org/soren/privacybrowser/-/blob/master/src/ com.stoutner.privacybrowser.metainfo.xml?ref_type=heads#L57 https://salsa.debian.org/soren/privacybrowser/-/blob/master/src/ com.stoutner.privacybrowser.desktop Running validate-tree on an installed binary checks these file name relationships, whereas a normal validate only checks the contents of the metainfo.xml file itself, but not the relationship of the file names. -- Soren Stoutner so...@debian.org
signature.asc
Description: This is a digitally signed message part.
