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 743118 - error: ‘git_clone_options’ has no member named ‘remo te_name’ when compiling against libgit2-0.22.0
error: ‘git_clone_options’ has no member named ‘remo te_name’ when compiling ...
Status: RESOLVED NOTABUG
Product: libgit2-glib
Classification: Core
Component: General
git master
Other Linux
: Normal normal
: ---
Assigned To: gitg-maint
gitg-maint
Depends on:
Blocks:
 
 
Reported: 2015-01-18 10:08 UTC by Martin von Gagern
Modified: 2019-02-22 03:52 UTC
See Also:
GNOME target: ---
GNOME version: ---


Description Martin von Gagern 2015-01-18 10:08:43 UTC 
Since https://github.com/libgit2/libgit2/commit/1697cd6ff5d29c95106ff4b7bd56ebba5d51b8c1 the git_clone_options structure of libgit2 no longer has a member “const char *remote_name” but instead a callback “git_remote_create_cb remote_cb”. For this reason, libgit2-glib won't compile against libgit2-0.22.0. Libgit2-glib should react to this change in some reasonable way. Either by providing a compatibility layer, or by deliberately breaking backwards compatibility to follow upstream development.

Originally reported this as https://bugs.gentoo.org/show_bug.cgi?id=536952.
Comment 1 jessevdk@gmail.com 2015-03-08 10:34:14 UTC 
libgit2-glib follows libgit2 versioning strictly. If libgit2 breaks backwards compatibility, so does libgit2-glib. For now, the versions of libgit2 and libgit2-glib have to match.