Bug 1387681 - gedit won't build on 7.3
Summary: gedit won't build on 7.3
Keywords:
Status: CLOSED CANTFIX
Alias: None
Product: Red Hat Enterprise Linux 7
Classification: Red Hat
Component: glib2
Version: 7.3
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: rc
: ---
Assignee: Colin Walters
QA Contact: Desktop QE
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2016-10-21 14:28 UTC by Vitezslav Humpa
Modified: 2017-10-31 19:45 UTC (History)
4 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2017-10-31 19:45:27 UTC
Target Upstream Version:


Attachments (Terms of Use)

Description Vitezslav Humpa 2016-10-21 14:28:08 UTC
Description of problem:
Same issue as file-roller's https://bugzilla.redhat.com/show_bug.cgi?id=1378857 and 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:

rpmbuild --rebuild ...

...
plugins/externaltools/org.gnome.gedit.plugins.externaltools.gschema.xml:7:31  Error on line 7 char 31: Only one <summary> element allowed inside <key>.  --strict was specified; exiting.


The current version of gedit 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):
gedit-3.14.3-18.el7

Comment 1 Ray Strode [halfline] 2016-10-21 17:21:40 UTC
in 7.4 we'll rebase gedit, which should be fine.

If we do decide to do something for 7.3 it should be to revert

https://git.gnome.org/browse/glib/commit/?id=b2734d762f9b33c60575e835bbf9ef190315c79a

from glib, for backward compatibility.  Fixing all the apps doesn't make sense in 7.3

Comment 2 Tomas Pelka 2016-10-21 19:26:36 UTC
not urgent enough, does not deserve z-stream for 7.3 for sure

Comment 3 Matěj Cepl 2017-10-31 19:45:27 UTC
Problems with building glib2-2.46.2-2.el7 are long time obsolete.


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