Bug 1378857

Summary: file-roller won't build on 7.3
Product: Red Hat Enterprise Linux 7 Reporter: Vitezslav Humpa <vhumpa>
Component: file-rollerAssignee: David King <dking>
Status: CLOSED ERRATA QA Contact: Desktop QE <desktop-qa-list>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 7.3CC: jkoten, tis, tpelka
Target Milestone: rc   
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: file-roller-3.22.2-1.el7 Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2017-08-01 21:26:20 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Attachments:
Description Flags
add the backported upstream fix none

Description Vitezslav Humpa 2016-09-23 11:37:11 UTC
Description of problem:
I've started hitting the https://bugzilla.gnome.org/show_bug.cgi?id=756607

We now have newer glib2 in EL7.3 (glib2-2.46.2-2.el7 and up) which causes the build to break on schema compilation.

The current version of file-roller-3.14.2-10.el7 was built still with older glib, though any newer builds (if there are any for 7.4) will fail.

Version-Release number of selected component (if applicable):
file-roller-3.14.2-10.el7

How reproducible:
Attempt to build the srpm.

...

glib-compile-schemas --strict --dry-run  --schema-file=org.gnome.FileRoller.gschema.xml && mkdir -p . && touch org.gnome.FileRoller.gschema.valid
org.gnome.FileRoller.gschema.xml:41:31  Error on line 41 char 31: Only one <summary> element allowed inside <key>.  --strict was specified; exiting.

Comment 1 David King 2016-09-26 14:57:31 UTC
Created attachment 1204854 [details]
add the backported upstream fix

Comment 2 David King 2016-12-01 12:34:14 UTC
This will be fixed as a side effect of the rease to 3.22.2 in bug 1386857.

Comment 4 Vitezslav Humpa 2017-05-16 11:23:55 UTC
The file-roller builds on all arches. Verified.

Comment 5 errata-xmlrpc 2017-08-01 21:26:20 UTC
Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.

For information on the advisory, and where to find the updated
files, follow the link below.

If the solution does not work for you, open a new bug report.

https://access.redhat.com/errata/RHEA-2017:2125