After an evaluation, GNOME has moved from Bugzilla to GitLab. Learn more about GitLab.
No new issues can be reported in GNOME Bugzilla anymore.
To report an issue in a GNOME project, go to GNOME GitLab.
Do not go to GNOME Gitlab for: Bluefish, Doxygen, GnuCash, GStreamer, java-gnome, LDTP, NetworkManager, Tomboy.
Bug 756607 - build fails during schema validation when using glib >= 1.45.1
build fails during schema validation when using glib >= 1.45.1
Status: RESOLVED FIXED
Product: file-roller
Classification: Applications
Component: general
3.16.x
Other Mac OS
: Normal critical
: ---
Assigned To: file-roller-maint
file-roller-maint
Depends on:
Blocks:
 
 
Reported: 2015-10-15 05:01 UTC by David Evans
Modified: 2016-05-08 09:25 UTC
See Also:
GNOME target: ---
GNOME version: ---

Attachments
depend on newer intltool and fix validation errors (20.68 KB, patch)
2016-05-05 09:21 UTC, David King 		none Details | Review

Description David Evans 2015-10-15 05:01:40 UTC 
Using glib >- 1.45.1, the file-roller build fails during schema validation as follows

Merging translations into org.gnome.FileRoller.gschema.xml.
CREATED org.gnome.FileRoller.gschema.xml
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.
make[3]: *** [org.gnome.FileRoller.gschema.valid] Error 1

Per glib 1.45.1 NEWS item:

  The GSettings schema compiler, glib-compile-schemas has been changed
  to reject schema xml that has duplicate <summary> or <description>
  elements. Such elements typically occur when translations are merged
  into the schema, with xml:lang attributes. This is not the correct
  way to translate schemas. Instead keep the translations in the .mo
  file and set the gettext-domain attribute on the <schemalist> element.

Please update the build to avoid this failure.
Comment 1 ilovezfs 2016-04-30 12:56:51 UTC 
Removing --strict works around it.

Here's how mate-utils fixed the same problem:

https://github.com/mate-desktop/mate-utils/commit/c4df12f12d21ea7d4bc0d656bd5f93539c078d93
Comment 2 David Evans 2016-05-04 17:59:57 UTC 
Yes, MacPorts has committed a similar fix:

https://trac.macports.org/changeset/141302
Comment 3 David King 2016-05-05 09:21:02 UTC 
Created attachment 327330 [details] [review]
depend on newer intltool and fix validation errors
Comment 4 Paolo Bacchilega 2016-05-08 08:50:30 UTC 
(In reply to David King from comment #3)
> Created attachment 327330 [details] [review] [review]
> depend on newer intltool and fix validation errors

push to master, thank you.
Comment 5 Paolo Bacchilega 2016-05-08 09:25:22 UTC 
Sorry, I meant: pushed to master