Bug 1830709 - Invalid metainfo files
Summary: Invalid metainfo files
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Fedora
Classification: Fedora
Component: google-noto-fonts
Version: 34
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: Akira TAGOH
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
: 1922533 (view as bug list)
Depends On:
Blocks: 1946121
TreeView+ depends on / blocked
 
Reported: 2020-05-03 11:09 UTC by Mohamed Akram
Modified: 2021-05-17 03:08 UTC (History)
9 users (show)

Fixed In Version: google-noto-fonts-20201206-1.fc35 google-noto-fonts-20201206-1.eln110 google-noto-fonts-20201206-2.fc34
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2021-05-17 03:08:43 UTC
Type: Bug
Embargoed:


Attachments (Terms of Use)

Description Mohamed Akram 2020-05-03 11:09:50 UTC
Description of problem:
Metainfo files provided by the package are deemed invalid by appstream.

Version-Release number of selected component (if applicable):
20181223-7.fc32

How reproducible:
Always.

Steps to Reproduce:
1. appstreamcli validate /usr/share/metainfo/google-noto-sans-sinhala-vf.metainfo.xml

Actual results:
E: google-noto-sans-sinhala-vf:~: font-no-font-data
E: google-noto-sans-sinhala-vf:4: cid-is-not-rdns google-noto-sans-sinhala-vf
I: google-noto-sans-sinhala-vf:~: font-description-missing
E: google-noto-sans-sinhala-vf:~: component-summary-missing
E: google-noto-sans-sinhala-vf:~: component-name-missing
E: google-noto-sans-sinhala-vf:~: extends-not-allowed
I: google-noto-sans-sinhala-vf:4: cid-contains-hyphen google-noto-sans-sinhala-vf

Validation failed: errors: 5, infos: 2

Expected results:

Validation was successful.

Comment 1 Fedora Admin user for bugzilla script actions 2020-11-20 14:56:32 UTC
This package has changed maintainer in the Fedora.
Reassigning to the new maintainer of this component.

Comment 2 Ben Cotton 2021-02-09 15:15:01 UTC
This bug appears to have been reported against 'rawhide' during the Fedora 34 development cycle.
Changing version to 34.

Comment 3 Akira TAGOH 2021-04-05 07:28:59 UTC
*** Bug 1922533 has been marked as a duplicate of this bug. ***

Comment 4 Fedora Update System 2021-04-19 09:08:55 UTC
FEDORA-2021-9f2f8a78be has been pushed to the Fedora 35 stable repository.
If problem still persists, please make note of it in this bug report.

Comment 5 Fedora Update System 2021-04-20 01:33:30 UTC
FEDORA-2021-cb64515c14 has been pushed to the Fedora ELN stable repository.
If problem still persists, please make note of it in this bug report.

Comment 6 Alex 2021-04-27 12:37:55 UTC
Can this not be fixed in an update to Fedora 34? This is probably the cause of https://pagure.io/fedora-kde/SIG/issue/56

Comment 7 Rex Dieter 2021-05-10 15:54:20 UTC
Re-opening per comment #6

Comment 8 Fedora Update System 2021-05-13 03:46:22 UTC
FEDORA-2021-59b910a47a has been submitted as an update to Fedora 34. https://bodhi.fedoraproject.org/updates/FEDORA-2021-59b910a47a

Comment 9 Fedora Update System 2021-05-14 15:31:09 UTC
FEDORA-2021-59b910a47a has been pushed to the Fedora 34 testing repository.
Soon you'll be able to install the update with the following command:
`sudo dnf upgrade --enablerepo=updates-testing --advisory=FEDORA-2021-59b910a47a`
You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2021-59b910a47a

See also https://fedoraproject.org/wiki/QA:Updates_Testing for more information on how to test updates.

Comment 10 Fedora Update System 2021-05-17 03:08:43 UTC
FEDORA-2021-59b910a47a has been pushed to the Fedora 34 stable repository.
If problem still persists, please make note of it in this bug report.


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