[02:35] <lifeless> where is the bug tracker for the laptop testing tracker?
[02:36] <lifeless> It keeps mutating bugs that are not part of Ubuntu, and I want to file a bug on it about that
[02:44] <blr> lifeless: noticed your name cropping up in relation to that in my email... sadly laptop testing is something I know nothing about. Perhaps cjwatson will know when he's about.
[02:45] <lifeless> blr: hmm, I haven't sent any email about that :) - just this ping here
[02:46] <lifeless> blr: I presume wgrant is on leave or something ?
[02:47] <blr> lifeless: you removed a tag from the qatracker supposedly
[02:47] <lifeless> blr: oh yeah, I did
[02:47] <lifeless> blr: from bug 10
[02:47] <mup> Bug #10: It says "displaying matching bugs 1 to 8 of 8", but there is 9 <laptop-testing> <lp-bugs> <Launchpad itself:Invalid> <https://launchpad.net/bugs/10>
[02:47] <blr> right
[02:47] <lifeless> blr: which is an old lp bug
[02:48] <blr> lifeless: stat holidays in au today and tomorrow
[02:50] <cjwatson> I know nothing about this either, despite not being able to sleep again.  A bit of googling finds https://wiki.ubuntu.com/Testing/Laptop which may be of some help
[02:50] <cjwatson> Possibly ubuntu-qa-website?
[02:53] <blr> lifeless: this appears to be the offending item? http://laptop.qa.ubuntu.com/qatracker/milestones/352/builds/108233/testcases/1479/results
[02:54] <cjwatson> blr: Are you planning to land https://code.launchpad.net/~blr/launchpad/bug-1536363-codereviewcomment-reply-git-oops/+merge/283382 today?
[02:54] <blr> lifeless: is it linking bugs from the comment field? i.e. "10."
[02:55] <blr> cjwatson: I would love to, but I've yet to resolve the gpg agent error I'm experiencing. :(
[02:55] <blr> cjwatson: is it possible to land that on my behalf?
[02:56] <cjwatson> Oh really?  Sure
[02:56] <cjwatson> You should at least be able to turn off the agent and type in your passphrase every time though
[02:56] <blr> yeah, quite perplexing, afaict, gpg is functioning perfectly fine, and the gpg-connect-agent responds to a health check
[02:57] <lifeless> https://bugs.launchpad.net/ubuntu-qa-website/+bug/1537587
[02:57] <mup> Bug #1537587: the bot "Ubuntu QA Website" keeps modifying bugs that are not Ubuntu bugs <Ubuntu QA Website:New> <https://launchpad.net/bugs/1537587>
[02:58] <lifeless> blr: I don't know, its been doing it for years, and well, sigh.
[02:58] <blr> cjwatson: if I enter my passphrase manually, bzr lp-land errors with: ERROR: Failed to GPG sign data with command "[u'gpg', '--clearsign', '-u', u'kit.randel@canonical.com']" - running clearsign manually is fine however.
[02:58] <cjwatson> urgh
[02:59] <cjwatson> blr: Anyway, edited the commit message to remove duplication with the tags that bzr lp-land will add, and sent to PQM.
[02:59] <lifeless> cjwatson: thanks for digging up a plausible project
[02:59] <blr> cjwatson: thanks for that. Hopefully can find the culprit this evening
[03:00] <cjwatson> blr: damnit, that won't pass due to a pending db-devel exception run on buildbot
[03:00] <cjwatson> blr: I've forced buildbot, will land that for you this coming morning
[03:00] <blr> great, thanks
[14:38] <daker> cjwatson: hi, is there a way to get the commit message from the webhook for bzr:push or git:push
[14:39] <daker> ?
[14:43] <cjwatson> daker: hm, not currently.  Could you file a bug explaining how you'd want to use this?  I don't think it would be too difficult to add - you can of course get hold of it using the information in the webhook payload but it would be more round-trips
[14:44] <daker> cjwatson: sure i'll do
[14:45] <cjwatson> At least in the git case we've already fetched that information immediately before dispatching the webhook, and I think that's true for bzr too
[14:48] <daker> cjwatson: yes, i am building a launchpad integration for slack using webhooks
[14:48] <cjwatson> neat!
[14:49] <daker> cjwatson: https://i.imgur.com/bQrcu6i.png
[14:49] <cjwatson> I've certainly got no problem including the information in the payload if it's going to be used.  We'd probably only send the new tip commit message though - is that sufficient?
[14:49] <cjwatson> (since we similarly only send the new tip commit ID)
[14:50] <daker> cjwatson: well that's enough but i would love to have the commit message
[14:50] <cjwatson> that's what I said ...
[14:51] <cjwatson> I meant the commit message only for the new tip commit, rather than for all commits between the previous state and the new state
[14:51] <cjwatson> the latter is a bit awkward and potentially very large indede
[14:51] <cjwatson> *indeed
[14:51] <daker> cjwatson: ah sorry yes!
[14:51] <daker> only the commit message for the new tip commit
[14:58] <daker> cjwatson: bug 1537780
[14:58] <mup> Bug #1537780: Provide the commit message in the webhook payload <Launchpad itself:New> <https://launchpad.net/bugs/1537780>
[15:02] <cjwatson> Ah yes, db_branch.getTipRevision().log_body and err I think bzr_branch.repository.get_revision(bzr_branch.last_revision).message ?  I never really got on with bzrlib
[15:06] <daker> cjwatson: i'll try that
[15:06] <daker> also i'll the add the author of the commit
[15:07] <cjwatson> well, that was more for my own reference
[15:07] <cjwatson> unless you fancy trying to write the patch
[15:07] <daker> cjwatson: no :D
[15:07] <cjwatson> daker: could you give a rationale in the bug?  we may need to refer back to this years later wondering who was using this thing and why
[15:08] <cjwatson> daker: so it's helpful to have more than a bare request
[15:08] <daker> cjwatson: sure
[15:16] <daker> cjwatson: good now bug 1537780 ?
[15:16] <mup> Bug #1537780: Provide the commit message in the webhook payload <Launchpad itself:New> <https://launchpad.net/bugs/1537780>
[15:18] <cjwatson> daker: yes, thanks
=== heroux_ is now known as heroux