diff options
| author | Pacho Ramos <pacho@gentoo.org> | 2025-12-17 19:02:20 +0100 |
|---|---|---|
| committer | Pacho Ramos <pacho@gentoo.org> | 2025-12-17 19:06:17 +0100 |
| commit | 2fe5e15b0ec3e8dc40b8d2e9b3916daa3b0affbd (patch) | |
| tree | 12fda24090c288996582a2fc570599ab28fed309 /dev-python/python-sqlparse | |
| parent | d6a3e11e268732c2cdcb0f73e97d22b1c9b34131 (diff) | |
| download | gentoo-2fe5e15b0ec3e8dc40b8d2e9b3916daa3b0affbd.tar.gz gentoo-2fe5e15b0ec3e8dc40b8d2e9b3916daa3b0affbd.tar.bz2 gentoo-2fe5e15b0ec3e8dc40b8d2e9b3916daa3b0affbd.zip | |
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@gentoo.org>
Diffstat (limited to 'dev-python/python-sqlparse')
0 files changed, 0 insertions, 0 deletions