[07:06] <acheronuk> x86 builders don't look well again. lots of 'cleaning'
[09:47] <cjwatson> acheronuk: no time to investigate properly, but stabbed
[14:28] <Ionic> hum, I'm having strange build errors
[14:29] <Ionic> https://code.launchpad.net/~x2go/+archive/ubuntu/ppa/+recipebuild/1488778 (more specifically https://code.launchpad.net/~x2go/+archive/ubuntu/ppa/+recipebuild/1488778/+files/buildlog.txt.gz - but affecting all Ubuntu series anyway) seems to want to checkout a git revision out of the bzr branch that doesn't exist and I have no idea where this might be coming from
[14:30] <cjwatson> It's probably a ghost revision - i.e. something that's listed as the parent of some revision, but that doesn't itself exist
[14:31] <cjwatson> Can't seem to reproduce it by branching it locally though
[14:32] <Ionic> the builders all run into that though; I made sure to re-run an import and check the upstream git repository for the commit SHA (which doesn't exist), so no idea what's going on there
[14:32] <cjwatson> The reason it's talking about git is that this branch was constructed using bzr-git
[14:33] <Ionic> right, I know that
[14:33] <cjwatson> I'm pretty confused too.  But is it worth just converting this to a git recipe build rather than wrestling with it?
[14:35] <Ionic> probably, since the upstream repository is a git repo anyway, though I guess there's no easy way to convert an existing repository to a different type (short of adding a new one + removing the old bzr branch)
[14:39] <cjwatson> no, just push/import it
[14:39] <cjwatson> the namespaces (mostly) don't overlap
[14:51] <Ionic> then again, I can't seem to find any link to import a new repository, hum
[14:52] <cjwatson> Ionic: https://help.launchpad.net/Code/Git#Mirroring_repositories_from_other_sites
[14:52] <Ionic> yes... it looks like the only option is to request an import (no 2)
[14:53] <cjwatson> if you want to push a new repository that only exists on LP, then you can just git push to an appropriate URL
[14:54] <cjwatson> but if it already exists somewhere else, then an import is more appropriate
[14:54] <Ionic> given that it's a clone of our upstream repository, an import makes most sense
[15:13] <Ionic> hum, it looks like git repository imports are not working like bazaar branches, but instead... are global to a project or team
[15:16] <cjwatson> Ionic: I think you misunderstand something, but I'm not exactly sure what.  Do you have an example?
[15:19] <Ionic> well, I seem to only be able to set the repository as backing a project... and that's not something I'd like to do with a code from a different project we're merely using as a dependency
[15:20] <Ionic> c.f., there's a "configure code" link on https://code.launchpad.net/x2go - but that's global for the whole project
[15:20] <cjwatson> Ionic: Looks like you only read half of the link that I gave you above.
[15:20] <cjwatson> Ionic: "2. This method is useful for other cases, such as importing repositories that are not the primary upstream repository for a project"
[15:21] <cjwatson> Ionic: Imports created in that way are not set to be the project default repository
[15:22] <cjwatson> Ionic: The "Configure code" link is option 1 on that page.
[15:23] <Ionic> right, I was confused because the code import page essentially queries the same data as the configure code page, I was probably wrong to assume it's doing the same thing
[15:23] <cjwatson> It indeed does not.
[15:23] <cjwatson> (not exactly; it's similar)
[15:23] <cjwatson> Looks like you created https://code.launchpad.net/~x2go/x2go/+git/python-wsgilog_master but then deleted it?
[15:24] <cjwatson> Oh, just renamed.
[15:24] <cjwatson> https://code.launchpad.net/~x2go/x2go/+git/python-wsgilog looks reasonable.
[15:24] <Ionic> yep, I created that, then deleted it, and now re-created as a proper import
[15:25] <Ionic> yep
[15:25] <Ionic> thanks, I'll have to see how the recipe takes it after the initial import :)
[15:28] <Saviq> hey guys, is it possible to prune PPAs up? say, https://launchpad.net/~mir-team/+archive/ubuntu/release/+packages has 7 source packages at 8MB, but almost 1k binaries at 6GB (for a 2GB-limited PPA that's quite a bit...), or should we ignore the size warning?
[15:33] <cjwatson> Saviq: Most of it's mir-test-tools-dbgsym I suspect
[15:34] <cjwatson> Saviq: I've bumped your quota a bit
[15:41] <Ionic> yeah, and it looks like a build directly from this newly imported git repository worked fine
[15:42] <Ionic> I guess I'll just drop the bzr branch for good
[15:43] <cjwatson> good good
[15:45] <Ionic> thank you again :)
[15:50] <cjwatson> np
[15:59] <Saviq> cjwatson: well, we'll fill it up soon enough anyway, are superseded binaries never pruned from PPAs?
[16:00] <cjwatson> Saviq: They're pruned roughly nightly
[16:00] <cjwatson> Saviq: Since just one instance of mir-test-tools-dbgsym is ~300MB, multiplying that by series and architectures accounts for most of the size you mentioned without having to theorise a pruning bug
[16:00] <Saviq> aha
[16:01] <Saviq> cjwatson: can you bump ppa:mir-team/dev and /rc, too, then? thanks
[16:01] <cjwatson> (actually every six hours I think)
[16:01] <cjwatson> Saviq: done
[16:24] <Saviq> thanks
[17:06] <rbasak> Does Launchpad use celery or something else? ISTR a different task runner name but I don't remember what it was.
[17:09] <cjwatson> rbasak: celery, with a variety of other bits and pieces glued above and below and on the side
[17:17] <rbasak> OK, thanks
[17:18] <cjwatson> rbasak: things you might be thinking of include ampoule and lazr.jobrunner
[17:19] <rbasak> Those don't ring a bell. But I may be mistaken entirely.
[17:19] <rbasak> But celery is the answer I was looking for, thanks.
[17:20] <rbasak> (though I might still try to avoid it as I don't want more infrastructure dependencies)