[00:14] hello #juju-dev [00:16] hopefully a juju-core dev will see this soon but: i'm interested in running launchpad.net/juju-core/cmd/juju on plan 9, but there's currently some packages that import "syscall", which is inherently non-portable [00:17] but after removing some of these imports to syscall and fixing up the code, i have juju on plan 9. there's a few other bugs, but i was able to run wordpress/mysql on amazon from the binary i compiled [01:54] hey is 1.17.7 broken on Saucy? [01:55] bootstrapping on ec2 errors out with "error: --instance-id option must be set" [02:40] hatch: 1 sec, i'm attempting a bootstrap [02:41] hatch: it appears so i'm afraid :( [02:41] lazyPower cool thx - I switched to my precise box and it bootstrapped no problem [02:41] sounds like someone forgot a test :P [02:41] * hatch has no idea how juju testing works [02:41] :) [02:41] oh we test it? [02:41] rofl - I assumed so? [02:41] I'll file a bug [02:42] hatch: do you have a link to the tarball [02:42] tarball of? [02:42] ohh the juju tools one [02:43] sec [02:43] https://launchpad.net/juju-core/trunk/1.17.7/+download/juju-core_1.17.7.tar.gz ? [02:43] tools from https://juju-dist.s3.amazonaws.com/tools/releases/juju-1.17.7-precise-amd64.tgz downloaded: HTTP 200; time 0.364s; size 5260933 bytes; speed 14454184.000 bytes/s 259022021283f751a61482a53dc80a46d3e92a93d001c1173c8b581175f5f464 /var/lib/juju/tools/1.17.7-precise-amd64/tools.tar.gz [02:44] that's from the log [02:44] i don't have an ubuntu system currently [02:44] but i built juju command on debian [02:45] be aware i'm brand new to juju myself [02:45] but i do know go, and juju is written in go [02:45] go has a standard testing framework thats really easy to use [02:45] but you have to actually write the test of course ;) [02:46] there are definitely some errors in the tests! [02:46] https://bugs.launchpad.net/juju-core/+bug/1299671 [02:46] <_mup_> Bug #1299671: Juju 1.17.1 fails to bootstrap on Saucy ec2 === lazyPower is now known as lazypower_travel === vladk is now known as vladk|offline [20:47] fwereade: morning [20:47] thumper, hey dude [20:47] fwereade: around to chat? [20:47] thumper, did timezones change both ways? [20:47] no, not moved yet [20:47] thumper, ofc, but I'm pretty tired, it's nearly 11 here [20:47] not sure when actually [20:48] fwereade: we can make it short [20:48] thumper, sgtm :) [20:48] fwereade: just the hangout from the meeting [20:49] thumper, I'm the first one here? [20:49] so am i :-) [20:49] * thumper rejoins [20:50] fwereade: try this one https://plus.google.com/hangouts/_/72cpjvsv5ss5opllvep4g2ci4s?hl=en [22:05] o/ [22:09] o/ [22:09] mwhudson: welcome back [22:09] mwhudson: when you are through your copious email backlog [22:09] mwhudson: wondering if you could shed any light on this: https://bugs.launchpad.net/juju-core/+bug/1298085 [22:09] <_mup_> Bug #1298085: juju-core crash during bootstrap on arm64

[22:10] perhaps an strace could help... [22:10] logs not that useful in the bug [22:10] thumper: there is a known glibc bug that this _could_ be [22:11] davecheney: see bug above, this is a more generic golang thing, but could the co compiler at least tell us *which* C function it is in? [22:11] s/co/go/ [22:11] mwhudson: ok... [22:24] so, canonistack merges changes quickly when it's still sunday in most of the world [22:34] :) [22:44] thumper: thanks for taking a look at https://bugs.launchpad.net/bugs/1298708 [22:44] <_mup_> Bug #1298708: bzr: bzr unit tests are not properly isolated

[22:44] np [22:44] * thumper is just firing up a pristine container [22:52] oh crap, local provider is broken again [22:52] no, [22:52] wait [22:52] was just slow [22:52] hmm, still can't see into it [22:52] ssh [22:52] meh