[21:30] <blr> cjwatson: are you about?
[21:30] <cjwatson> little bit, what's up?
[21:31] <blr> cjwatson: interested in how you're testing snap builds locally
[21:32] <cjwatson> blr: running with http://paste.ubuntu.com/12517426/ (probably not all strictly necessary, but last bit definitely is)
[21:32] <cjwatson> and with the snap.allow_new feature flag set
[21:32] <cjwatson> that should be about all you need
[21:32] <blr> is the gpghandler related?
[21:32] <cjwatson> assuming you have an otherwise functional builder
[21:33] <cjwatson> I think that was a temporary hack for some other reason, ignore it
[21:33] <cjwatson> and default_batch_size was just to make it easier to see what was going on in some bits of UI
[21:34] <cjwatson> so basically, you just want
[21:34] <cjwatson> [snappy]
[21:34] <cjwatson> tools_source: deb http://ppa.launchpad.net/snappy-dev/snapcraft-daily/ubuntu %(series)s main
[21:34] <blr> thank you :)
[21:37] <cjwatson> blr: I also reasonably routinely just run launchpad-buildd slavebin scripts by hand rather than bothering to go through an LP master, if I'm just trying to work on buildd itself
[21:38] <cjwatson> blr: you can look for the RUN: lines in an existing build log and copy and paste them, just changing the build ID; you need to 'mkdir build-$YOUR_CHOSEN_BUILD_ID' (I usually just set the ID to 1 for less typing) in ~buildd first
[21:39] <cjwatson> and make sure to do the umount-chroot / remove-build steps at the end even if it fails, or you'll get confused
[21:39] <blr> cjwatson: what's the path to the slavebin scripts?
[21:39] <cjwatson> see e.g. https://launchpadlibrarian.net/218457654/buildlog_snap_ubuntu_vivid_ppc64el_wget_BUILDING.txt.gz
[21:40] <cjwatson> you have to decode the debug output, so:
[21:40] <cjwatson> RUN: /usr/share/launchpad-buildd/slavebin/unpack-chroot ['unpack-chroot', 'SNAPBUILD-9', '/home/buildd/filecache-default/a33a4a88601a2e76ec85f8a99d2254dbf2d0d1ac']
[21:40] <cjwatson> ->
[21:40] <cjwatson> /usr/share/launchpad-buildd/slavebin/unpack-chroot SNAPBUILD-9 /home/buildd/filecache-default/a33a4a88601a2e76ec85f8a99d2254dbf2d0d1ac
[21:40] <blr> excellent, thanks
[21:40] <cjwatson> file names in the filecache are sha-1s of the content
[21:40] <blr> right
[21:41] <cjwatson> and you'll want to have an appropriate chroot downloaded with manage-chroot and prepopulated in the filecache
[21:42] <cjwatson> a reason to do this for snaps is that it saves you from also having to have an appropriate local codehosting/git setup that the builder can talk to - that might be easy or it might not :)
[21:42] <cjwatson> sometimes it's easier not to have N different environments all running and working at once just to test one thing :)
[21:43] <blr> cjwatson: it certainly feels like quite a few balls to juggle at times :)
[21:43] <cjwatson> right, so I always prefer to figure out how to run stuff in isolation if I can
[21:44] <cjwatson> you can also start up the buildd and send xmlrpc requests to it by hand
[21:44] <blr> right
[21:47] <cjwatson> should be something like proxy.build('1', 'snap', 'sha-1 of chroot', {}, {"name": "blah", "arch_tag": "amd64", "archives": [list of sources.list lines including the snapcraft-daily PPA], "archive_private": False, "git_repository": "git repo URL", "git_path": "master"})
[21:48] <blr> right... and the build proxy endpoint
[21:48] <cjwatson> yeah, as in HowToRunSoyuzLocally
[21:49] <blr> I'm passing that through _extraBuildArgs in snapbuildhaviour which afaict is correct.
[21:49] <cjwatson> indeed
[21:50] <blr> thanks colin, will have more questions at the end of the day no doubt.
[21:50] <cjwatson> blr: all the primary web UI for snap building is in place now, so if you want to create a test build for yourself to dig sample information out of then you can start from Branch:+index or GitRef:+index
[21:50] <cjwatson> should be obvious from there
[21:55] <wgrant> Morning.
[21:56] <blr> morning wgrant