GNOME Bugzilla – Bug 742415
git master fails to build in continuous
Last modified: 2015-05-01 18:35:21 UTC
See http://build.gnome.org/continuous/buildmaster/builds/2015/01/05/44/build/log-gnome-calculator.txt More gtksourceview vala bindings issues? In the meantime, I'm going to do the same thing I did last time and remove gnome-calculator from the manifest.
Please revert https://git.gnome.org/browse/gnome-continuous/commit/?id=bee207ab5fd46b1e90538a66f7fb69c0292472bf when this is fixed.
The following fix has been pushed: 67ecaa4 Another gtksourceview bindings change...
Created attachment 293981 [details] [review] Another gtksourceview bindings change...
By the way, it is *really* suspicious to return uninitialized memory in an out parameter. I wonder why we override that function at all.
Nope: http://build.gnome.org/continuous/buildmaster/builds/2015/01/06/42/build/log-gnome-calculator.txt
Er sorry, that run hadn't done a git fetch becuase it wasn't in the manifest. Latest master builds after a resolve. Thanks!
I am building GNOME 3.14 and got this error. Maybe this fix should be pushed to gnome-3-14 too?
TBH I think gtksourceview should not have backported an API break (March 5, 2015) seven months after the 3.14 API freeze (August 18, 2014); best bet would be to downgrade gtksourceview.
How do you downgrade gtksourceview in jhbuild? Or now everyone who builds GNOME with jhbuild will need to deal with this manually?
TBH, it's a bit much to expect the gnome-3-14 jhbuild modulesets to work now that GNOME 3.16 has been released, but if you want to fix it, the options are (a) ask the gtksourceview developers to revert their vala API break, (b) ask the gtksourceview developers to work around the return value change in their vapi generation, or (c) have jhbuild build gtksourceview from a tarball release rather than from git (undesirable, so please only change that in the 3.14 moduleset). Or just upgrade to 3.16, where we already adapted to that API change.