Created attachment 185736 [details]
up to 3.26.0
This is not that easy, libgit2, libgit2-glib and all other libgit2 users need to be updated and checked.
gitg-3.24 cannot be built currently:
I guess there is no blockers anymore for updating this port?
Created attachment 188801 [details]
Up-to-date update to 3.26.0
A new translation was missing in the submitter patch. Fixed patch attached.
Build log available here:
Could you commit the update patch to the tree?
That unbreaks the port and I've been using 3.26.0 successfully for a while.
Created attachment 189791 [details]
An updated patch to 3.26.0 (diff against r459165)
Created attachment 189792 [details]
A poudriere testport log (releng/11.1 amd64)
libgit2 and libgit2-glib are already updated in ports effectively breaking current gitg version in ports, so update is required to fix the build.
I'll take it.
(In reply to Ruslan Makhmatkhanov from comment #8)
Thanks for picking this up!
I will look forward to an update.
A commit references this bug:
Date: Mon Jan 22 09:12:49 UTC 2018
New revision: 459639
devel/gitg: unbreak by updating to 3.26.0
Current version of libgit2 and libgit2-glib in ports were not supported by
gitg 3.24, so update this port to 3.26 to fix the breakage.
Submitted by: email@example.com (original patch)
romain (intermediate patch)
Hiroki Tagato <firstname.lastname@example.org> (committed patch)
With hat: gnome
Committed, thank you all for the patches!