Bug 1591306 - AppData file installed in deprecated location
Summary: AppData file installed in deprecated location
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: Fedora
Classification: Fedora
Component: chromium
Version: 29
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: Tom "spot" Callaway
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2018-06-14 13:55 UTC by Mario Sanchez Prada
Modified: 2018-09-05 15:40 UTC (History)
5 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2018-09-05 15:40:05 UTC
Type: Bug
Embargoed:


Attachments (Terms of Use)

Description Mario Sanchez Prada 2018-06-14 13:55:16 UTC
Description of problem:

As far as I can see in [1], the chromium-browser.appdata.xml file is being installed in the old (and now deprecated) recommended location at /usr/share/appdata instead on /usr/share/metainfo, which is what the AppStream specification defines now as the right one: https://www.freedesktop.org/software/appstream/docs/chap-Quickstart.html

Indeed, a quick runtime check on my Fedora 28 machine confirms this:

  $ rpm -ql chromium | grep appdata
  /usr/share/appdata/chromium-browser.appdata.xml


I believe this has worked fine so far because software inspecting this kind of information is still likely checking both places, but it would be good to have it move to its right location at some point, thus this bug.

[1] https://src.fedoraproject.org/rpms/chromium/blob/9cdea2b9/f/chromium.spec#_1462

Comment 1 Phil Wyett 2018-07-24 02:28:49 UTC
Was fixed in commit:

https://src.fedoraproject.org/rpms/chromium/c/92b60dd6231b2b7bf1f5212720a5f423cc0417d8?branch=master

Should be indicated in changelog and this bug closed.

Comment 2 Jan Kurik 2018-08-14 09:58:04 UTC
This bug appears to have been reported against 'rawhide' during the Fedora 29 development cycle.
Changing version to '29'.


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