On 3/14/16 1:25 PM, Sean Farley wrote: > > If I come off as arrogant, my apologies. I like to move fast and this > makes working with me difficult. > > For what it's worth, I'm testing a script that automatically updates a > port so we can (potentially) have a bot that tries to update every > outdated port and report what breaks. This caused me to miss your > comment. > > But I understand that not many people like working with me and my > efforts are rarely appreciated. Though I still think libgit2-glib is a > sorry excuse for a project. >
Sean, here's an update: I filed a ticket concerning this issue [1] and a number of updates have been committed to upstream git master in the last hour or so to fix the API break [2]. gitg has now been updated to require libgit2-glib 0.23.11 so a new release should be available soon [3]. [1]https://bugzilla.gnome.org/show_bug.cgi?id=76364 [2] https://git.gnome.org/browse/libgit2-glib/log/ [3] https://git.gnome.org/browse/gitg/commit/?id=d55ce1608d03fcdf31cd7c5a19e28dc2535b5929 Dave _______________________________________________ macports-dev mailing list [email protected] https://lists.macosforge.org/mailman/listinfo/macports-dev
