[08:08] <cjwatson> pleia2: done, thanks
[08:13] <cjwatson> jelmer: Sorry - done now.  I really must work out how to make questions against Launchpad itself not expire, since it's really not helpful
[12:04] <jelmer> cjwatson: thanks!
[13:53] <pleia2> thank you :)
[14:00] <cjwatson> pleia2: also I'd completely missed that you were joining the Z team - congrats, and interested to read that blog post once it's written
[14:02] <pleia2> cjwatson: thanks! it's a really great team, and fascinating stuff
[15:54] <marcustomlinson> cjwatson: hey, I have a feature request for LP :) Have a moment to mull it over?
[15:56] <cjwatson> I have a lot of feature requests for LP :)
[15:56] <cjwatson> But I mean sure
[15:56] <marcustomlinson> :)
[15:56] <marcustomlinson> https://gitlab.gnome.org/Community/Ubuntu/gnome-sdk/tree/gnome-3-32-1804
[15:57] <marcustomlinson> so this project incorporates two snapcraft.yamls. It needs to build the sdk one first, then the platform one stages the built sdk snap
[15:57] <cjwatson> I'm afraid this is outside my control
[15:57] <cjwatson> We were explicitly told not to support that
[15:57] <cjwatson> You'll have to discuss your use case with the snapcraft team
[15:58] <marcustomlinson> oh?
[15:58] <cjwatson> (That is: we were explicitly told not to support arbitrary configurable snapcraft.yaml paths)
[15:58] <marcustomlinson> hmm ok
[15:58] <cjwatson> Hopefully it's possible to do it in some other way, but I'm not enough of a snapcraft expert to know
[15:59] <marcustomlinson> I was thinking a SNAPCRAFT_COMMAND environment variable
[15:59] <cjwatson> There are various ways I could imagine implementing it, but we're forbidden to
[15:59] <marcustomlinson> yeah I understand
[15:59] <cjwatson> Talk to the snapcraft team and see if they can help :)
[15:59] <marcustomlinson> ok thanks
[16:01] <cjwatson> Couldn't you use multiple repositories?
[16:01] <cjwatson> And just build them successively
[16:03] <marcustomlinson> cjwatson: yeah was hoping for something less manual
[16:03] <marcustomlinson> could build one and forget the other sort of thing
[16:04] <cjwatson> marcustomlinson: One possibility might be to hook the two builds together using https://help.launchpad.net/API/Webhooks
[16:04] <cjwatson> It would require something that has the right permissions to request the second build, so you'd need to be careful, but should be possible
[16:05] <cjwatson> Once store_upload_status hits Uploaded, the first snap should be available from its target channel in the store
[16:06] <marcustomlinson> require "something" :)
[16:06] <marcustomlinson> Like run that as a service on my PC?
[16:06] <cjwatson> Or a Jenkins instance or some other kind of hosted CI
[16:07] <marcustomlinson> oh right
[16:07] <marcustomlinson> hmmmmmm
[16:07] <cjwatson> Something that runs the first build and polls for completion using the API would be possible too; it's less elegant because polling is always less elegant, though it avoids having to worry about opening up an authentication token on a web service
[16:08] <marcustomlinson> build takes like 4+ hours, I might hit timeouts
[16:08] <cjwatson> It's all pretty programmable using https://help.launchpad.net/API/launchpadlib
[16:08] <marcustomlinson> Maybe I can have a webhook trigger gitlab ci
[16:08] <marcustomlinson> not sure if I can wangle that
[16:09] <cjwatson> I haven't explicitly tried that but maybe it's possible.  Giving your launchpadlib credentials to gitlab ci might be unfortunate though
[16:09] <cjwatson> (Regrettably we don't yet have a way to construct credentials that can be constrained like "can only call this one API method")
[16:10] <marcustomlinson> yeah ok, I'll see what I can do with the LP API
[16:10] <marcustomlinson> thanks cjwatson
[16:12] <cjwatson> Let us know what you come up with
[16:12] <marcustomlinson> will do