Please read this before reporting a bug:
https://wiki.archlinux.org/title/Bug_reporting_guidelines
Do NOT report bugs when a package is just outdated, or it is in the AUR. Use the 'flag out of date' link on the package page, or the Mailing List.
REPEAT: Do NOT report bugs for outdated packages!
https://wiki.archlinux.org/title/Bug_reporting_guidelines
Do NOT report bugs when a package is just outdated, or it is in the AUR. Use the 'flag out of date' link on the package page, or the Mailing List.
REPEAT: Do NOT report bugs for outdated packages!
FS#40915 - [libgit2-glib] need rebuild against libgit2 0.21
Attached to Project:
Community Packages
Opened by Eric Belanger (Snowman) - Friday, 20 June 2014, 19:51 GMT
Last edited by Daniel Micay (thestinger) - Saturday, 21 June 2014, 05:09 GMT
Opened by Eric Belanger (Snowman) - Friday, 20 June 2014, 19:51 GMT
Last edited by Daniel Micay (thestinger) - Saturday, 21 June 2014, 05:09 GMT
|
DetailsDescription:
$ ldd /usr/lib/libgit2-glib-1.0.so.0 linux-vdso.so.1 (0x00007fff5cf5f000) libgio-2.0.so.0 => /usr/lib/libgio-2.0.so.0 (0x00007fc047317000) libgit2.so.0 => not found |
This task depends upon
Closed by Daniel Micay (thestinger)
Saturday, 21 June 2014, 05:09 GMT
Reason for closing: Fixed
Additional comments about closing: 0.21.0-1 -> 1:0.20.0-1, until libgit2-glib / pygit2 / subsurface are able to cope with the extensive API overhaul
Saturday, 21 June 2014, 05:09 GMT
Reason for closing: Fixed
Additional comments about closing: 0.21.0-1 -> 1:0.20.0-1, until libgit2-glib / pygit2 / subsurface are able to cope with the extensive API overhaul

Daniel: you should use checkpkg to help prevent this kind of issue.

Sorry about this. I was anxious to update to the new version for the data corruption fixes, and overlooked that there are packages in the repositories depending on this now. I'll downgrade it back to 0.20.0 with epoch=1 for now as new releases of pygit2 / libgit2-glib will be needed to deal with the extensive break in API compatibility.