[11:10] <flexiondotorg> cjwatson, I realise opening network access during the snap build phase is a little way out.
[11:11] <flexiondotorg> Bit here is a bug I raised which you'll be able to close when the time comes.
[11:11] <flexiondotorg> https://bugs.launchpad.net/snapcraft/+bug/1642281
[11:11] <ubot5`> Ubuntu bug 1642281 in Snapcraft "Unable to build python based snap on Launchpad" [Undecided,New]
[11:41] <cjwatson> flexiondotorg: moved to the right place
[17:53] <mitya57> cjwatson, hi, is it by design that Git recipes do not clone submodules, or that's a bug?
[17:54] <cjwatson> mitya57: not sure
[17:54] <cjwatson> possibly a bug
[17:55] <mitya57> In my case the submodule is on a 3rdparty site (git.gnome.org), not on Launchpad
[17:57] <mitya57> So if the recipe builders have limited access to outside world, then maybe my chances on getting support for that are low :)
[17:58] <rbasak> I wonder if you could mirror in the submodule trees, and then somehow tell the recipe where your replacement is.
[17:58] <caraka> they trip over submodues and gpg sigs at the moment
[18:01] <mitya57> Yes, I'm thinking of using nest-part as a workaround
[18:07] <cjwatson> caraka: that's git-to-bzr imports; git-to-git imports don't suffer from that
[18:07] <cjwatson> caraka: hence also not git recipes
[18:07] <cjwatson> mitya57: yeah, I think that may actually be the right answer
[18:08] <mitya57> Ack!
[20:12] <mitya57> cjwatson, while trying to work around missing submodule support we ran into bug 1644640. I hope *that* is a bug :)
[20:12] <ubot5`> bug 1644640 in git-build-recipe "Cannot nest-part into an existing directory" [Undecided,New] https://launchpad.net/bugs/1644640
[20:49] <mitya57> Can somebody please respond to https://answers.launchpad.net/launchpad/+question/404131 ? It's upstream developer asking for rights for his projects on LP.
[21:04] <cjwatson> mitya57: done
[21:04] <mitya57> Thanks a lot!
[21:05] <cjwatson> and yes, that git-build-recipe thing seems like a bug though can't look hard now
[21:05] <mitya57> We have a workaround for now, but in a longer term it would be nice to have a fix