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 727112 - Does not Build on Arch Linux
Does not Build on Arch Linux
Status: RESOLVED OBSOLETE
Product: gnome-latex
Classification: Other
Component: general
2.12.x
Other Linux
: Normal normal
: unspecified
Assigned To: LaTeXila maintainer(s)
LaTeXila maintainer(s)
Depends on:
Blocks:
 
 
Reported: 2014-03-26 21:09 UTC by Bernd Prünster
Modified: 2014-04-29 20:28 UTC
See Also:
GNOME target: ---
GNOME version: ---


Attachments
make log (11.29 KB, text/plain)
2014-03-27 22:52 UTC, Bernd Prünster
Details
Generated Schema (102.72 KB, application/xml)
2014-03-28 11:23 UTC, Bernd Prünster
Details
Build log of LaTeXila 2.10 (169.81 KB, text/plain)
2014-03-28 11:47 UTC, Bernd Prünster
Details

Description Bernd Prünster 2014-03-26 21:09:22 UTC
This excerpt form the build log should suffice to identify the problem:

make[3]: Entering directory '<XXXXX>/latexila-2.12.0/data'
  ITMRG  latexila.appdata.xml
  ITMRG  org.gnome.latexila.gschema.xml
  ITMRG  latexila.desktop
  GEN      org.gnome.latexila.gschema.valid
org.gnome.latexila.gschema.xml: Error on line 19 char 31: attribute 'xml:lang' invalid for element 'summary'.  --strict was specified; exiting.
Makefile:795: recipe for target 'org.gnome.latexila.gschema.valid' failed
make[3]: *** [org.gnome.latexila.gschema.valid] Error 1
make[3]: Leaving directory '<XXXXX>/latexila-2.12.0/data'

Could this be due to the version of gsettings-desktop-schemas shipped with arch?
Comment 1 Sébastien Wilmet 2014-03-27 13:42:57 UTC
> --strict was specified

It's maybe that. Can you compile in verbose mode? so we can see the exact command. For example with:

$ make V=1
Comment 2 Sébastien Wilmet 2014-03-27 14:24:55 UTC
Here the command is:

> glib-compile-schemas --strict --dry-run  --schema-file=org.gnome.latexila.gschema.xml && mkdir -p . && touch org.gnome.latexila.gschema.valid

So --strict is used successfully.
Comment 3 Bernd Prünster 2014-03-27 22:52:28 UTC
Created attachment 273118 [details]
make log

make failing on Arch Linux
Comment 4 Sébastien Wilmet 2014-03-28 11:08:54 UTC
You have the same glib-compile-schemas command. Maybe a different version, but there is no --version or -v for glib-compile-schemas. What is your GLib version?

$ pkg-config --modversion glib-2.0

Can you also attach the generated org.gnome.latexila.gschema.xml?
Comment 5 Bernd Prünster 2014-03-28 11:23:13 UTC
Created attachment 273159 [details]
Generated Schema

$ pkg-config --modversion glib-2.0
  2.38.2
Comment 6 Sébastien Wilmet 2014-03-28 11:36:47 UTC
I have exactly the same generated org.gnome.latexila.gschema.xml.
But I use glib from jhbuild (version 2.39.91).

But with glib 2.38 it should also work, since it worked fine for latexila 2.10…

Can you try to rebuild latexila 2.10?
Comment 7 Bernd Prünster 2014-03-28 11:47:16 UTC
Created attachment 273163 [details]
Build log of LaTeXila 2.10

Works like a charm...
Comment 8 Sébastien Wilmet 2014-03-28 13:26:42 UTC
Then the problem most probably comes from this commit:
https://git.gnome.org/browse/latexila/commit/?id=633ae2cf438038d59fcd80885f993b9997f3337a

@INTLTOOL_XML_NOMERGE_RULE@ has been replaced by @INTLTOOL_XML_RULE@.

With the former (in latexila 2.10), the translations were not merged. No with the latter (in latexila 2.12), the translations are merged.

I think you need a more recent glib version.
Comment 9 Bernd Prünster 2014-03-28 14:00:43 UTC
I'm afraid that's not possible, as pulling a newer version would most certainly break *a lot* of applications.
So Arch will have to wait until glib 2.40 lands in the stable repositories.
Comment 10 Sébastien Wilmet 2014-03-28 16:19:56 UTC
There are anyway not a lot of changes between latexila 2.10 and 2.12.

There is no API/ABI break between glib 2.38 and 2.40. It should be safe to upgrade for Arch Linux users.

But upgrading to glib 2.40 is just a guess to fix the problem here. Maybe the problem comes from another dependency. If you test with glib 2.40, we would know if it fixes the problem, and if so I can update the dependency requirements for latexila and warn other packagers on the mailing list.
Comment 11 Sébastien Wilmet 2014-04-29 19:47:48 UTC
Does it work with glib 2.40?
Comment 12 Bernd Prünster 2014-04-29 19:51:25 UTC
Yes it does.
I forgot to mark it as resolved, doing so now.
Comment 13 Sébastien Wilmet 2014-04-29 20:28:31 UTC
Ok I've updated the glib version requirement.