commit: 2fe5e15b0ec3e8dc40b8d2e9b3916daa3b0affbd Author: Pacho Ramos <pacho <AT> gentoo <DOT> org> AuthorDate: Wed Dec 17 18:02:20 2025 +0000 Commit: Pacho Ramos <pacho <AT> gentoo <DOT> org> CommitDate: Wed Dec 17 18:06:17 2025 +0000 URL: https://gitweb.gentoo.org/repo/gentoo.git/commit/?id=2fe5e15b
gnome-base/gnome-keyring: Re-enable ssh-agent by default Re-enable the old gnome-keyring ssh-agent by default until we clarify with upstream the right way to auto-start (or start when needed) the newer gcr provided one. For now, no distribution manages to properly handle this: some have a broken setup due them disabling gnome-keyring one while not ensuring gcr one is launched; other distributions re-enabled gnome-keyring one as we are doing now until situation is clarified. For more information, please look into: https://github.com/gentoo/gentoo/pull/44265 You will find there all the bugs/references that I could find about this bug. Thanks-to: Florian Schmaus Bug: https://bugs.gentoo.org/964756 Closes: https://github.com/gentoo/gentoo/pull/44265 Bug: https://bugs.gentoo.org/964741 Signed-off-by: Pacho Ramos <pacho <AT> gentoo.org> gnome-base/gnome-keyring/gnome-keyring-48.0-r1.ebuild | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/gnome-base/gnome-keyring/gnome-keyring-48.0-r1.ebuild b/gnome-base/gnome-keyring/gnome-keyring-48.0-r1.ebuild index 81f6696887d1..ddfde1d9405a 100644 --- a/gnome-base/gnome-keyring/gnome-keyring-48.0-r1.ebuild +++ b/gnome-base/gnome-keyring/gnome-keyring-48.0-r1.ebuild @@ -12,7 +12,7 @@ HOMEPAGE="https://gitlab.gnome.org/GNOME/gnome-keyring"; LICENSE="GPL-2+ LGPL-2+" SLOT="0" KEYWORDS="~alpha amd64 arm arm64 ~loong ~mips ppc ppc64 ~riscv ~sparc x86 ~amd64-linux ~x86-linux" -IUSE="caps pam selinux ssh-agent systemd test" +IUSE="caps pam selinux +ssh-agent systemd test" RESTRICT="!test? ( test )" RDEPEND="
