We are trying for a long time to get rid of libsecret USE flag in favor of "gnome-keyring" as explained here: https://wiki.gentoo.org/wiki/Project:GNOME/Gnome_Team_Ebuild_Policies#gnome-keyring_and_libsecret But it seems git ebuild had been changed in the reverse way (probably due to a mistake) Thanks
I'll take care of it tomorrow.
I'm a bit confused. I changed git ebuilds to use libsecret because of bug #610376. Now I wonder what is this bug about. Is just the name of the USE flag incorrect or should git (again) use gnome-base/libgnome-keyring instead of app-crypt/libsecret?
Is about the name of the USE flag, as the ebuild attached there, this should use "gnome-keyring" name for the USE flag even relying on app-crypt/libsecret https://bugs.gentoo.org/show_bug.cgi?id=610376#c7
Once this is fixed, bug 610920 will turn out to have been unnecessary as well.
commit 7ef9302c5539aa6ea229ed1aacca2f07cfeeecdb (HEAD -> master, origin/master, origin/HEAD) Author: Lars Wendler <polynomial-c@gentoo.org> Date: Wed May 24 10:48:43 2017 dev-vcs/git: Replace "libsecret" by "gnome-keyring" USE flag (bug #619484) Package-Manager: Portage-2.3.6, Repoman-2.3.2