Summary: | dev-libs/libgit2-glib-0.0.24 - In file included from ggit-cherry-pick-options.c:1:0: ggit-cherry-pick-options.h:56:7: error: unknown type name 'git_cherry_pick_options' | ||
---|---|---|---|
Product: | Gentoo Linux | Reporter: | Helmut Jarausch <jarausch> |
Component: | [OLD] GNOME | Assignee: | Gentoo Linux Gnome Desktop Team <gnome> |
Status: | RESOLVED FIXED | ||
Severity: | normal | CC: | gentoo-bugs, gentoo, guillaume.horel, ikelos, mail, markpariente, Martin.vGagern, phobosk, proteuss, seemantk |
Priority: | Normal | ||
Version: | unspecified | ||
Hardware: | All | ||
OS: | Linux | ||
Whiteboard: | |||
Package list: | Runtime testing required: | --- | |
Bug Depends on: | |||
Bug Blocks: | 530272 | ||
Attachments: | build log |
Description
Helmut Jarausch
2015-01-17 11:46:45 UTC
I think libgit2-glib-0.0.24 isn't compatible with libgit2-0.22.0 - will need upstream to release a new version that is, until then it should maybe be a blocker? Following the advice of Mark I can confirm that libgit2-glib compiles against libgit2-0.21.3 but not against libgit2-0.22 *** Bug 536952 has been marked as a duplicate of this bug. *** libgit2-glib 0.22.0 was released, I'll give it a try Build passes but the ssh patch needs updating. +*libgit2-glib-0.22.0 (20 Jan 2015) + + 20 Jan 2015; Rémi Cardona <remi@gentoo.org> +libgit2-glib-0.22.0.ebuild, + +files/libgit2-glib-0.22.0-automagic-ssh.patch: + Bump to 0.22.0, refresh automagic ssh patch, see bug #536830. + In portage. The API changed, this bump breaks gitg 3.14.1… @gnome: do we add a blocker on libgit2 in libgit2-glib to force the older version ? (PS, feel free to beat me to it) I start to think that gitg, libgit2 and libgit2-glib should be at least co-maintained by the same people as they are always mis-synced :S + 20 Jan 2015; Pacho Ramos <pacho@gentoo.org> libgit2-glib-0.0.24.ebuild, + libgit2-glib-0.22.0.ebuild: + Add a reference to upstream bug report and make the dependency of 0.0.24 + stricter + I'm happy to hand over maintenance of gitg to the gnome herd, particularly since it now appears to have adopted the numbering scheme and been pulled into the fold. @gnome herd, would that be ok? Some info from upstream https://bugzilla.gnome.org/show_bug.cgi?id=743118#c1: “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.” I guess the ebuilds should reflect this fact in their dependencies. |