[10:20] <free> wgrant: hey there, around?
[10:22] <wgrant> free: Sorry, I've had your MP open for a day, but let me have a look at it now.
[10:22] <free> wgrant: ah, you noticed it, just wanted to mention it. No hurry from my side.
[10:23] <wgrant> free: Much less intimidating once I realised the majority of the diff was bootstrap.py.
[10:23] <free> wgrant: I'll be pushing a few txlongpoll branches at some point, I'm wondering if it'd make sense to make the Landscape team in LP member of the project (so I could get more reviewers). That code was originally written in Landscape and then extracted to txlongpoll by former LP devs
[10:24] <free> wgrant: yeah pretty much all of it, should have mentioned that in the MP description
[10:24] <wgrant> Yeah, I was part of that extraction project back in 2011.
[10:25] <free> wgrant: ah I had forgot
[10:25] <wgrant> free: I can add you to ~lazr-developers, which has commit access.
[10:25] <free> wgrant: thanks
[10:26] <wgrant> free: There's no tarmac or anything on these branches, so just merge directly.
[10:26] <free> wgrant: right, I'll make sure to run tests :)
[21:04] <Jasper> Is it possible to trigger a rebuilt of a previously-uploaded source package?
[21:04] <Jasper> If we try and trigger a rebuild the normal way, the package will fail to upload.
[21:09] <nacc> Jasper: is this in a PPA?
[21:09] <Jasper> Yes.
[21:09] <Jasper> It's a git import recipe thing.
[21:09] <nacc> Jasper: ah, i don't know much about that -- but did the previous build succeed?
[21:10] <Jasper> No.
[21:10] <Jasper> It was a test fail for other unrelated reasons.
[21:10] <nacc> Jasper: then i think you can submit the rebuild from the web interface, at least
[21:10] <nacc> Jasper: so it probably is possible via the API
[21:10] <Jasper> Where?
[21:10] <Jasper> We're not trying to do it from the API, only the web UI.
[21:10] <nacc> Jasper: i think if you view all builds, then click on the fialing build, there's a link
[21:11] <Jasper> Well, I could view all builds, if Launchpad just didn't die on us.
[21:11] <nacc> Jasper: i'm pretty sure i've done that in the past, i can try and look where i think it should be ... link?
[21:11] <Jasper> Launchpad is dead.
[21:11] <sarnold> launchpad feels unhappy, I got the "Uh oh! Something has gone wrong" page
[21:12] <nacc> yeah, it just stopped working for me too :/
[21:15] <dobey> seems to be a network issue to the data center. might be a DDoS or something
[21:16] <Jasper> Thank god. Now we might be able to switch to a CI system that's usable.
[21:16] <dobey> Jasper: but anyway, yes, you can request a rebuild for an individual target, if you go to the PPA's package details page, and then click on the failed build, there will be a "retry"
[21:17] <nacc> dobey: thanks (i was pretty sure it was there, but not an expert)
[21:19] <dopey_> is https://launchpad.net down at the moment?
[21:20] <wgrant> dopey_: Yes
[21:20] <beisner> i'm getting 'Uh oh!' too
[21:20] <rdhyee> any estimate of when launchpad.net will be back?
[21:21] <wgrant> Not at the moment. Still not sure exactly what's happened.
[21:23] <Gues_____> launchpad down?
[21:23] <gaughen> oh good it's not just me. I swear I didn't do anything!
[21:24] <rdhyee> wgrant: thanks for answering my question about estimated time.  Good luck to the sysadmins for bringing it back up.
[21:24] <sarnold> Gues_____: correct, down
[21:29] <Alives> git-core ppa 503: https://launchpad.net/~git-core
[21:29] <wgrant> topic
[21:30] <sarnold> thanks for publishing on twitter, too
[21:31] <bladernr> ack, that explains it.  Thanks wgrant
[21:35] <wgrant> We're back.
[21:38] <rdhyee> wgrant: thanks!
[21:40] <oeil> thank you!
[21:40] <wernerandrew> thanks!
[21:50] <Alives> thanks
[21:53] <cjwatson> Jasper: No; you need to arrange for a new recipe build that has a newer version number.  Your recipe will include various elements that go into building the version number, and you need to arrange that each time you want to build the package it has a newer version number.
[21:53] <Jasper> cjwatson, we fixed an issue with a dependency.
[21:53] <Jasper> We have no new source package.
[21:53] <cjwatson> Jasper: Link?
[21:54] <Jasper> To what?
[21:54] <cjwatson> Jasper: To your build
[21:54] <cjwatson> Or your recipe
[21:54] <cjwatson> Or *something*
[21:54]  * Jasper tries to find it
[21:54] <Jasper> https://launchpad.net/~endlessm/+archive/ubuntu/soma
[21:54] <Jasper> Start with that.
[21:55] <Jasper> I can't figure out how to navigate to anything else.
[21:55] <Jasper> We eventually just bumped it in the changelog.
[21:55] <Jasper> But it would be nice not to have to do that.
[21:55] <cjwatson> https://code.launchpad.net/~wgreenberg/+recipe/eos-shard-daily ?
[21:55] <Jasper> Yeah.
[21:56] <cjwatson> Looking for the older builds that actually failed, since they've now expired off the recipe listing page
[21:57] <Jasper> I can't navigate the Launchpad UI, sorry.
[21:57] <Jasper> I'd help you if I could.
[21:58] <cjwatson> Jasper: So the thing is that the builds preceding the "failed to upload" ones actually succeeded.  What "test failure" are you talking about?
[21:58] <cjwatson> CI in some other system?
[21:58] <Jasper> cjwatson, no, there was one that failed to build.
[21:58] <Jasper> Of eos-shard
[21:58] <nacc> Jasper: do you mean: https://launchpad.net/~endlessm/+archive/ubuntu/soma/+recipebuild/1149824 ?
[21:58] <Jasper> I have a build log but nothing else: https://launchpadlibrarian.net/262619453/buildlog_ubuntu-xenial-i386.eos-shard_1.4-1.5~114~ubuntu16.04.1_BUILDING.txt.gz
[21:59] <Jasper> Maybe?
[21:59] <cjwatson> Build log is enough.  One moment.
[21:59] <nacc> that would appear tob e: https://launchpad.net/~endlessm/+archive/ubuntu/soma/+build/9839401
[21:59] <nacc> i think?
[21:59] <cjwatson> Right, and that has a "Retry this build" link on it.
[22:00] <cjwatson> You could have used that.
[22:00] <Jasper> Aha, thanks.
[22:00] <Jasper> Out of curiosity, how did you find those pages?
[22:00] <nacc> Jasper: i got to that from https://launchpad.net/~endlessm/+archive/ubuntu/soma/+builds?build_text=&build_state=failed
[22:00] <Jasper> Cool, thank you.
[22:00] <nacc> Jasper: and i got there from 'view all builds' on https://launchpad.net/~endlessm/+archive/ubuntu/soma/+packages
[22:00] <wgrant> Jasper: They're also linked from +packages
[22:00] <Jasper> OK.
[22:00] <Jasper> I got to the recipe build page.
[22:00] <wgrant> When a build fails, there's an X in the relevant row with a link to each architecture that has failed.
[22:00] <Jasper> Where is it from there?
[22:01] <cjwatson> Under "Binary builds".
[22:01] <wgrant> eg. https://launchpad.net/~endlessm/+archive/ubuntu/soma/+packages?field.name_filter=&field.status_filter=&field.series_filter=
[22:01] <Jasper> "Binary builds: none"
[22:01] <Jasper> On https://launchpad.net/~endlessm/+archive/ubuntu/soma/+recipebuild/1149824
[22:01] <cjwatson> Then you're not looking at the right recipe build.
[22:01] <wgrant> That recipe build failed.
[22:01] <cjwatson> That recipe build was a *source package* build failure, not the binary build failure above.
[22:01] <Jasper> Ah, OK.
[22:01] <cjwatson> i.e. failure even to construct the source package
[22:02] <Jasper> OK, cool.
[22:02] <cjwatson> Recipes are all two-stage: first we build a source package from the various VCSes and such that you specify, and then we feed that source package into the usual package building machinery to get binary packages.
[22:02] <Jasper> I can't see it but that's probably a permissions issue.
[22:02] <Jasper> Yeah, yeah.
[22:30] <mwhudson> is there any way i can tell if this job is stuck? https://launchpad.net/~mwhudson/+archive/ubuntu/devirt/+build/9836839
[22:30] <mwhudson> it's gcc building on armhf so being very slow is hardly surprising but there has been no output for an hour or so now
[22:30] <mwhudson> oh wait, it's going now, never mind :)
[23:45] <nacc> what format does getPublishedSources' created_since_date take?
[23:47] <wgrant> nacc: ISO 8601
[23:48] <sarnold> <3
[23:48] <wgrant> eg. 2016-05-31T23:48:08
[23:48] <nacc> wgrant: thanks!
[23:48] <nacc> wgrant: i was thinking that as i looked through the logs
[23:48] <wgrant> nacc: But if you're using launchpadlib you can just pass in a datetime object
[23:49] <nacc> wgrant: ok, good to know!