On Wed, Dec 23, 2015 at 07:21:45PM +0100, Axel Beckert wrote: > Hi, > > Thorsten Glaser wrote: > > severity 796931 serious > > I agree with this severity. This issue breaks quite some automatic > stuff and is a severe and unexpected regression.
I assume this problem I'm having is the same thing: - I have a gpg-agent running in my normal desktop session - All development happens in an lxc container into which my home directory is bind mounted - When I ssh into this container, keychain is used to start a gpg-agent Previously this worked - I got a GPG_AGENT_INFO pointing to a socket under /tmp/gpg-XXXXXX. Now gpg-agent --daemon just bails out if it sees a socket under ~/.gnupg/ and so things fall back to using the pre-existing agent which they can't communicate with. Cheers, -- Iain Lane [ i...@orangesquash.org.uk ] Debian Developer [ la...@debian.org ] Ubuntu Developer [ la...@ubuntu.com ]
signature.asc
Description: Digital signature
