Bug 1348295 - Have metainfo.xml files, but addons not showing up in Gnome Software (until installed)
Summary: Have metainfo.xml files, but addons not showing up in Gnome Software (until i...
Keywords:
Status: CLOSED EOL
Alias: None
Product: Fedora
Classification: Fedora
Component: gnome-software
Version: 24
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: Richard Hughes
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks: 1342396
TreeView+ depends on / blocked
 
Reported: 2016-06-20 18:09 UTC by Colin Macdonald
Modified: 2017-08-08 14:53 UTC (History)
2 users (show)

Fixed In Version:
Clone Of:
Environment:
Last Closed: 2017-08-08 14:53:35 UTC
Type: Bug
Embargoed:


Attachments (Terms of Use)

Description Colin Macdonald 2016-06-20 18:09:39 UTC
I added metainfo.xml files to octave-symbolic and octave-doctest: they have both had them since at least January 2016.

But neither shows up in Gnome Software, unless I install them from the command line.


If I do install them on the command line, then they both appear under Octave and in searches, as expected.  This is true with either "gnome-software --prefer-local" or just "gnome-software".

*BUT* I think the desired user experience is that people can see the list of add-ons before they install them.

I waited patiently assuming all this would be fixed with a new Fedora release, but its not.  I assume there is some tool that runs periodically and gathers all the metadata so that it shows up for **uninstalled** applications.  Does that not run often enough?  Is there some other validation process other than `appstream-util`?

Comment 1 Colin Macdonald 2016-06-20 18:32:08 UTC
More info:

1. Seems the aggregator is/was called "appstream-builder".

2. Maybe I should've filed under "appstream-data"?

3. Gimp has various addons listed in Software without me first installing them, so its certainly *possible* to have the UX I describe above.

Comment 2 Colin Macdonald 2016-06-20 18:37:55 UTC
Hmmm, so I see there may be many more rules other than passing "appstream-glib validate":

https://github.com/hughsie/appstream-glib#guidelines-for-applications

In particular:

> AppData files MUST be installed into /usr/share/appdata

Well, the Fedora spec file does that for me... is that not sufficient?

Comment 3 Fedora End Of Life 2017-07-25 21:08:29 UTC
This message is a reminder that Fedora 24 is nearing its end of life.
Approximately 2 (two) weeks from now Fedora will stop maintaining
and issuing updates for Fedora 24. It is Fedora's policy to close all
bug reports from releases that are no longer maintained. At that time
this bug will be closed as EOL if it remains open with a Fedora  'version'
of '24'.

Package Maintainer: If you wish for this bug to remain open because you
plan to fix it in a currently maintained version, simply change the 'version'
to a later Fedora version.

Thank you for reporting this issue and we are sorry that we were not
able to fix it before Fedora 24 is end of life. If you would still like
to see this bug fixed and are able to reproduce it against a later version
of Fedora, you are encouraged  change the 'version' to a later Fedora
version prior this bug is closed as described in the policy above.

Although we aim to fix as many bugs as possible during every release's
lifetime, sometimes those efforts are overtaken by events. Often a
more recent Fedora release includes newer upstream software that fixes
bugs or makes them obsolete.

Comment 4 Fedora End Of Life 2017-08-08 14:53:35 UTC
Fedora 24 changed to end-of-life (EOL) status on 2017-08-08. Fedora 24 is
no longer maintained, which means that it will not receive any further
security or bug fix updates. As a result we are closing this bug.

If you can reproduce this bug against a currently maintained version of
Fedora please feel free to reopen this bug against that version. If you
are unable to reopen this bug, please file a new report against the
current release. If you experience problems, please add a comment to this
bug.

Thank you for reporting this bug and we are sorry it could not be fixed.


Note You need to log in before you can comment on or make changes to this bug.