GNOME Bugzilla – Bug 687323
e-contact-map breaks with API change on geocode-glib side
Last modified: 2014-03-12 13:06:34 UTC
Created attachment 227780 [details] [review] update for new geocode-glib api Here is a patch that replace removed geocode-glib geocode_object_new with g_object_new call as is done in geocode-glib itself.
With which geocode-glib version does this start?
There is no release with these changes yet. Bastien said he's reworking the API, so presumably more changes are coming. I think for the moment it would be better to lock into version 0.99.0 than try to chase unreleased API changes. Unfortunately geocode-glib's configure.ac still reports the version a 0.99.0, but I'll see if I can get Bastien to bump it forward so we can distinguish released versus unreleased changes.
Cannot tell the version right now , I am using jhbuild which pull master the commit is : 088f31d6c2eab04a2db871d7da2a665b322a9884 lib: Remove geocode_object_new() from the public API I bet I should reassign the bug to the gnome jhbuild moduleset for it to pull from a predefined version of geocode-glib ?
(In reply to comment #3) > I bet I should reassign the bug to the gnome jhbuild moduleset for it to pull > from a predefined version of geocode-glib ? Yes, that or else temporarily add --disable-contact-maps to evolution's configure command, which avoids the geocode-glib dependency altogether. Bastien gave me permission to bump the geocode-glib version number in git to 0.99.1, so I'm restricting Evolution's dependency to = 0.99.0 until the next geocode-glib release. http://git.gnome.org/browse/evolution/commit/?id=97115e6e0d136b1f47f55d171760927f23ab3b5d I'll leave this open for you to reassign to jhbuild.
Created attachment 231365 [details] [review] use geocode-glib 0.99.0 for jhbuild
Bastien already supplied a patch for newer geocode-glib API, but I'm holding off until I see a new geocode-glib tarball release. *** This bug has been marked as a duplicate of bug 689055 ***
Oh my bad, I didn't look at the patch close enough. Thought it was for Evolution. Sorry about that.
Hello Alban, This only affects 3.8 and seems to be resolved in 3.10 and 1.12 modulesets, so Im going to close this as obsolete. Thanks for the bug report!