[08:13] <caraka> low priority question: I manually cancelled some builds, and now they appear at the top of the list on the recipe page, meaning I cannot see the acutal current build status'. Methinks it is because the list is alphabetical. Any way to delete the canceled builds, or non alphabetise the list?
[10:15] <cjwatson> caraka: not alphabetical, a different sorting bug.  the only way to get rid of them is to fix https://bugs.launchpad.net/launchpad/+bug/746140
[10:15] <ubot5`> Ubuntu bug 746140 in Launchpad itself "Recipe superseded source builds get stuck at top of recent builds list forever" [High,Triaged]
[16:09] <mvo> just want to mention: I got two oopses in a row from LP when trying to report bug 1752635
[16:09] <ubot5`> bug 1752635 in python2.7 (Ubuntu) "[patch] Please add command-not-found hints" [Undecided,New] https://launchpad.net/bugs/1752635
[16:10] <cjwatson> OOPS IDs?
[16:10] <cjwatson> but it's probably the usual thing that goes away in 10min
[16:11] <mvo> cjwatson: meh, sorry, I don't have it anymore. but yeah, three times a charm and all that. it worked now
[16:11] <mvo> (just wanted to mention, if transient thats fine with me)
[16:15] <cjwatson> Yeah, unfortunately this happens with bugs from time to time
[16:15]  * mvo nods
[20:58] <ral> Any chance someone could help me with https://answers.launchpad.net/launchpad/+question/665102 ?
[21:03] <hloeung> ral: might be worth posting the output from dput as well, it might help
[21:04] <nacc> i do recall other users reporting similar silent failures when the gpg keys were 'wrong'
[21:05] <nacc> i'd need to trawl my logs to be sure
[21:05] <hloeung> ral: also, pretty sure LP uses keys from keyserver.u.c
[21:05] <nacc> cjwatson: had a branch in progress for this
[21:05] <hloeung> ral: https://keyserver.ubuntu.com/pks/lookup?op=vindex&fingerprint=on&search=0x779B22DFB3E717B7
[21:05] <hloeung> ral: nothing updated recently? Maybe you need to push up your new key?
[21:05] <hloeung> s/new key/changes to your key/
[21:21] <ral> hloeung: I pushed my key to another server earlier in the year, I thought they propagated.
[21:21] <ral> I've just pushed to k.u.c, I'll give it another try.
[21:22] <hloeung> right, depends on which servers keyserver.u.c talks to and what servers the keyserver you pushed to talks to
[21:38] <ral> hloeung: I'm afraid I'm mistaken, it was another gpg key that I updated
[21:38] <hloeung> heh ok, so that might be the problem then
[21:41] <ral> Well let's say there are two problems - launchpad shouldn't swallow these errors silently, and my key might have a problem :)
[21:42] <nacc> ral: yeah the first is 'known'
[22:00] <cjwatson> nacc: I think I landed that one already
[22:00] <cjwatson> that was https://code.launchpad.net/~cjwatson/launchpad/better-upload-error-notifications/+merge/311179
[22:01] <nacc> cjwatson: oh ok, i didn't have the link handy
[22:02] <nacc> i just remembered you were working on it before :)
[22:02] <cjwatson> can't get my VPN link to come up at the moment so can't check logs
[22:02] <cjwatson> oh wait, there it is, maybe it'll work
[22:03] <cjwatson> 2018-03-01 11:17:18 INFO        GPG verification of /srv/launchpad.net/ppa-queue/incoming/upload-ftp-20180301-111651-008775/~mosquitto-dev/mosquitto-ppa/mosquitto_1.4.15-0mosquitto1~xenial1_source.changes failed: Verification failed 3 times: ["(7, 153, u'Key expired')", "(7, 153, u'Key expired')", "(7, 153, u'Key expired')"]
[22:03] <cjwatson> ral: does that look like the right package name/version?
[22:03] <ral> cjwatson: yep
[22:10] <cjwatson> I'll have to experiment to see how we can pick out just that one error robustly
[22:11] <cjwatson> that's a little different from my earlier fix for deactivated keys, but I think it can come under basically the same heading
[22:14] <cjwatson> anyway, yes, pushing a non-expired key to LP should help
[22:14] <cjwatson> err, to keyserver.u.c
[22:27] <nacc> cjwatson: should i be able to specify a PPA without any packages in it yet as the source for a LP snap build? for some reason, it doesn't seem to find it
[22:34] <cjwatson> nacc: if it hasn't been published yet, it may not have any index files, which will cause apt etc. to not find it
[22:34] <cjwatson> nacc: you can either publish something and delete it shortly afterwards, or a more elegant trick: load the archive in the API and call the markSuiteDirty method on it
[22:34] <nacc> cjwatson: yeah i wasn't going to trigger a build yet, just wanted to set it up
[22:34] <cjwatson> https://launchpad.net/+apidoc/devel.html#archive-markSuiteDirty
[22:35] <nacc> cjwatson: to be clear, 'it' above was the launchpad web UI
[22:35] <cjwatson> oh
[22:35] <cjwatson> that should work regardless, yes
[22:35] <nacc> in the Source for automatic builds field
[22:35] <nacc> ok, i'll try again
[22:35] <cjwatson> I think.  Let me check the details
[22:35] <cjwatson> Perhaps the widget is clever
[22:36] <nacc> oh it expected a different ppa spec than i thought
[22:36] <nacc> ~sergiusens/ubuntu/snapcraft-lp1752481
[22:36] <nacc> rather than the normal sergiusens/snapcraft-lp1752481
[22:37] <cjwatson> "normal"
[22:37] <nacc> heh, the specifier you see on the ppa page
[22:37] <nacc> my own fault, i was able to find it by searching by user-prefix instead
[22:37] <cjwatson> so we can possibly update that now to the three-segment form
[22:38] <cjwatson> we had to delay a long time on that because old versions of add-apt-repository exist
[22:38] <nacc> oh of course
[22:38] <wgrant> Hm yeah, it's been nearly four years so probably.
[22:38] <cjwatson> however, the two-arg form should have worked in the search ...
[22:38] <cjwatson>             if len(query_split) == 3:
[22:38] <cjwatson>                 owner_name, distro_name, archive_name = query_split
[22:38] <cjwatson>             else:
[22:38] <cjwatson>                 owner_name, archive_name = query_split
[22:38] <nacc> cjwatson: and of course now it does
[22:39] <nacc> it didn't before, i swear :)
[22:39] <cjwatson> in fact distro_name isn't even used there
[22:39] <cjwatson> all right, I won't think about it too hard then :)
[22:39] <cjwatson> it wouldn't have worked with the ppa: prefix, which I think is a bug
[22:39] <nacc> cjwatson: yeah i'd assume PEBKAC for now
[22:39] <cjwatson> fortunately, easy to fix, will do
[22:40] <nacc> cjwatson: yeah it just feels like a 'nice to have' so that c&p works
[22:40] <cjwatson> I just missed that bit when adding support for that prefix to the API and such