Daniel Kahn Gillmor <d...@fifthhorseman.net> wrote: Josselin, which RC bug are you suggesting that i'm about to backport to jessie? I'm not proposing to set --use-standard-socket by default in jessie, if that's what you're worried about.
Yes, this is what I was worried about. Thanks for your explanations. Sorry for jumping in too fast with the “RC bug” wording, which was not mandated given what you have in mind - I guess the breakage in unstable did make me nervous. I’m not really sure your solution is worth deploying to jessie this way, though. Maybe a few words in the release notes would be enough. Talking about unstable: c) the ability to use gnome-keyring's passphrase-caching safely with gpg-agent pinentry upstream (the GnuPG upstream team) is working on a pinentry-gnome3 that should address (c) as well, but it's not even released yet, and it seems quite unlikely that we'll get that into a jessie point release. If gnome-keyring upstream agrees (I don’t know why they wouldn’t, but I haven’t looked at the architecture in detail), it looks like the long-term solution. But so far it isn’t there. It would be much appreciated if you could at least revert the --use-standard-socket change until this new pinentry has been uploaded to unstable and properly integrated in reverse dependencies wherever needed. Cheers, -- Joss -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org