How to let GNOME Software find a new AppStream metainfo file?

I’ve recently added the AppStream metainfo file to an editor called Frescobaldi. This file is available in Fedora 32 since version 3.1.2-2.
This editor cannot be found in GNOME Software. I hoped that adding the metainfo file would have fixed this but it didn’t.

IIUC (but I may be wrong) GNOME Software relies on the metadata generated by the distro with appstream-builder and distributed by the package appstream-data. But this package has not been updated for a month. I would expect metadata to be rebuilt if needed, or at least more often.
According to this message, metadata are built weekly. But it doesn’t seem true.

$ rpm -qa appstream-data
appstream-data-32-6.fc32.noarch

I’m missing something?
I hope someone can shed a light on this topic, as I cannot find any information.

2 Likes

AFAIK this package is only used on installation media, so that users can see package metadata in gnome-software and such even when offline.
Generating the metadata and incorporating them in the repository files is rather costly and I don’t know if it happens weekly or if Richard keeps on doing it manually. Better ask on devel.

1 Like

I’m quite sure it’s done manually:

https://src.fedoraproject.org/rpms/appstream-data/blob/f32/f/appstream-data.spec

Are you sure? The spec for the package does not show weekly updates.

A few things can go wrong here:

  • the metainfo file isn’t correctly installed, so best to verify that these are followed: https://docs.fedoraproject.org/en-US/packaging-guidelines/AppData/

  • if it is, then it should be included in gnome-software when the appstream-data is generated the next time: this is after the package hits stable, I don’t think packages in updates-testing are included in the appdata generation.

  • if both of these steps are correct, and it still doesn’t show, best to file a bug so that it can be debugged.

The release notes do not show weekly updates, that’s true. But the description says “The appstream data is built weekly with /usr/bin/appstream-builder…”, see here.

The doc page you linked makes a distinction between appdata.xml file for GUI apps and metainfo.xml file for add-ons. This doesn’t match current AppStream specification AFAICS. As you can read here and also here, appdata.xml name is still supported for historical reasons but it’s kind of deprecated.
I’ve opened an issue four months ago, but nobody replied so far.

For Frescobaldi (a GUI app) I’ve used only a metainfo.xml file. Is this a problem?

appstreamcli search frescobaldi was immediately able to find the application, as soon as the metainfo.xml file reached stable a few days ago.
So my feeling is that the problem is either the out-of-date appstream-data or GNOME Software.

If you want to debug it yourself, install the package:

sudo dnf install frescobaldi

(it will install a lot of dependencies though, as it depends on lilypond, which depends on texlive)

I stand corrected here. It’s actually in updates yet:

$ dnf info frescobaldi | grep -i repo
Repository   : @System
From repo    : updates

So when the package hits stable I should expect an update of appstream-data?

Thanks in advance for your help

No, if it’s in the updates repository, it is already a stable update. Otherwise, it would’ve been in “updates-testing”. More on this here:
https://fedoraproject.org/wiki/QA:Updates_Testing

As you see from bodhi here, it only reached the update repository 6 days ago:
https://bodhi.fedoraproject.org/updates/FEDORA-2020-a0e81551bc

As the appdata spec’s changelog will tell you, that package was updated on 13th April:
https://src.fedoraproject.org/rpms/appstream-data/blob/f32/f/appstream-data.spec#_49

So, when the appdata package is updated next, frescobaldi should be included in it.

1 Like

For the records, appstream-data has not been updated yet.

I’ve filed a bug, because appstream-data package description says that it’s updated weekly while in fact it seems to be updated every 2 or 3 months.

Two months have passed since the last update. I hope it will happen soon.

1 Like

This topic was automatically closed 28 days after the last reply. New replies are no longer allowed.