[00:09] <lfaraone> cjwatson: knownbug that pushing to a new remote branch on a private project hangs after "Total 3 (delta 0), reused 0 (delta 0)" or whatever, and never writes out the "To git+ssh://lfaraone@git.launchpad.net/~lfaraone/s3kr8t/+git/test" line?
[00:14] <lfaraone> eh, filed LP #1451107 anywayz
[12:03] <cjwatson> lfaraone: Not known.  Will have a look next week once we sort out the ability for developers to extract logs from the backend.
[12:04] <cjwatson> Thanks for the report.  It's probably the translatePath XML-RPC call crashing; not much else that can go wrong there
[16:23] <wxl> hey folks, does the email interface work? i got a "Signature couldn't be verified: (7, 8, u'Bad signature')"
[16:52] <cjwatson> wxl: Were you trying to do something that requires a signature, such as changing a bug task status?
[17:01] <wxl> cjwatson: yeppers
[17:02] <wxl> cjwatson: i think i've discovered the problem is not in launchpad. using mailvelope in gmail fails, but copying/pasting a gpg --clearsign works fine.
[17:03] <wxl> cjwatson: any ideas on how i could diagnose this further?
[17:03] <cjwatson> I was about to ask if you'd checked independently that your mail client actually signs mail correctly, indeed.
[17:04] <cjwatson> I'm afraid I don't use gmail significantly myself and not for signed mail.
[17:04] <wxl> i guess i can try to compare raw emails and go from there
[17:05] <wxl> thanks cjwatson :)
[17:35] <wxl> cjwatson: i notice that the default of mailvelope is sha256 while gpg is sha1. could that be the problem?
[17:36] <cjwatson> I'm sorry, I don't know.
[17:37] <cjwatson> Verify the output independently using a different mail client.
[17:37] <wxl> well it's the same email client— the one that worked and the one that didn't
[17:37] <wxl> what's different is what's doing the signing
[17:39] <cjwatson> Sure.  I'm suggesting that you could send a signed mail to a test account and use a different mail client to verify it, and maybe it would tell you what the problem is.
[17:40] <cjwatson> Or at the very least provide conclusive proof that it isn't a problem with Launchpad :-)
[17:41] <cjwatson> Also it would mean you had a copy of the message as seen by the recipient to use for debugging.
[17:42] <cjwatson> And if another client can verify it successfully, then you could attach that exact message to a Launchpad bug report.