Does that cover the case of yesterday?

[17:04] <cpaelzer> nacc: with git ubuntu from edge I can't build-source
[17:04] <nacc> cpaelzer: what happens?
[17:04] <cpaelzer> nacc: want to check with you if this is a known issue ... (pastebin incoming)
[17:05] <nacc> cpaelzer: and check if it happens with the test sap
[17:05] <nacc> *snap
[17:05] <cpaelzer> Edge: http://paste.ubuntu.com/25817428/
[17:05] <cpaelzer> stable running atm
[17:06] <cpaelzer> stable working http://paste.ubuntu.com/25817437/
[17:07] <cpaelzer> test-fixes running
[17:07] <nacc> bah
[17:07] <nacc> stderr: gpg: can't connect to the agent: IPC connect call failed
[17:08] <cpaelzer> me?
[17:08] <nacc> cpaelzer: i'll need to see why that happens, that's debsign calling gpg (and we ship gpg i the snap)
[17:10] <cpaelzer> and finally edge/test-fixes: http://paste.ubuntu.com/25817458/
[17:10] <cpaelzer> nacc: let me know if you need more
[17:11] <cpaelzer> nacc: I don't think it depends on the package - if anything on my laptp setup I'd think
[17:11] <cpaelzer> nacc: but then I don't remember anything arcane I could have done to gpg/debsign
[17:12] <cpaelzer> $ env | egrep -i 'gpg|sign' | pastebinit  => http://paste.ubuntu.com/25817471/
[17:12] <cpaelzer> oh yeah I'll join that rbasak
[17:12] <nacc> cpaelzer: cat .devscripts and ls -ahl ~/.gnupg
[17:13] <nacc> cpaelzer: and if you run debsign outside snap manually debsign ../mailman_2.1.16-2ubuntu0.3_source.changes, does it work?
[17:16] <cpaelzer> $ cat .devscripts 
[17:16] <cpaelzer> DEBSIGN_KEYID=8280B242
[17:16] <cpaelzer> http://paste.ubuntu.com/25817489/
[17:17] <cpaelzer> nacc: ^^
[17:17] <cpaelzer> debsign ../mailman_2.1.16-2ubuntu0.3_source.changes
[17:17] <cpaelzer> works fine
[17:17] <cpaelzer> nacc: ^^
[17:18] <nacc> cpaelzer: and cat .gnupg/gpg-agent-info-lap?
[17:28] <nacc> cpaelzer: also what is the host?
[17:28] <cpaelzer> $ cat .gnupg/gpg-agent-info-lap
[17:28] <cpaelzer> GPG_AGENT_INFO=/tmp/gpg-U33tMf/S.gpg-agent:5867:1
[17:28] <cpaelzer> Xenial
[17:28] <cpaelzer> nacc: ^^
[17:29] <nacc> cpaelzer: ah, that could be it too, the gpg in the snap is 2.2.1
[17:30] <nacc> cpaelzer: so i need to figure out if maybe there is an incompatibilty there, and we might need to run our own nagent?
[17:30] <cpaelzer> 1.4.20-1ubuntu3.1
[17:30] <nacc> yeah
[17:30] <nacc> a big jump
[17:30] <nacc> cpaelzer: ps aux | grep gpg-agent?
[17:31] <roaksoax> smoser: rharper howdy! has the dns bug landed in -proposed ?
[17:31] <cpaelzer> I have one "/usr/bin/gpg-agent --daemon"
[17:31] <nacc> cpaelzer: interesting
[17:32] <nacc> cpaelzer: let me see if i can reproduce it in a vm
[17:32] <nacc> cpaelzer: i thinnk that meanns your agent wasn't passing '--use-standard-socket'
[17:32] <nacc> (before)
[18:10] <nacc> cpaelzer: yeah, so i *think* gpg2 looks for the socket in agent-socket:/run/user/1000/gnupg/S.gpg-agent
[18:10] <nacc> (which comes from $SNAP/usr/bin/gpgconf --list-dirs
[18:45] <nacc> cpaelzer: for now, don't use --sign :) i'll keep trying to figure it out, i've reproduce it, at least
[18:52] <nacc> cpaelzer: what i need to be careful with is that the gpg in the snap does not break gpg outside the snap
[18:56] <nacc> cpaelzer: i don't think we want to put gpg1 in the snap as a workaround, because i'm not sure it'll be compatible with a gpg2 .gnupg