[00:34] wallyworld_: I think the bot is wedged [00:34] ffs. ok [00:56] wallyworld_: trust yours to be picked up first [00:56] i know right :-D [00:57] WTF? [00:57] the bot won't land my branch because it had trouble loading the prereq [00:57] FFS [00:57] thumper: if it's any consolation, i updated golxc yesterday and last night had to patch the lxc stuff in juju core for it to compile, pending your stuff landing [00:58] wallyworld_: all you had to do was 'cd ~/go/src/launchpad.net/golxc; bzr revert -r 7' [00:58] and it would have been fine [00:58] yeah i know === Tribaal_ is now known as Tribaal [00:58] was just trying to make you feel better === _mup__ is now known as _mup_ [01:00] oh, ok [01:00] thanks [01:05] fuck yeah! [01:06] * thumper pokes around a bit [01:08] hazmat: hey... [01:08] hazmat: wordpress works fine with aufs [01:08] hazmat: you had me all concerned about nothing [01:27] thumper, hmm [01:28] hazmat: talked with hallyn about it [01:28] hazmat: he suggested to use aufs if btrfs doesn't work [01:28] hazmat: sorry, if not btrfs backed [01:29] hazmat: and shake out bugs :-) [01:29] but should all be good [01:29] thumper, ah.. that's my issue.. i have btrfs under aufs [01:29] thumper, cool.. glad thats resolved [01:29] so, fast and small for all \o/ [01:44] thumper, so your able to install and relate wordpress to mysql? [01:44] thumper, i always get this error on aufs on the db relation.. 2014-03-12 01:41:35 INFO db-relation-changed rm: fts_read failed: Stale NFS file handle [01:44] hazmat: yep, and looked at the web on 10.0.3.x [01:44] thumper, cool [01:44] all good [01:50] umm, ubuntu@winton-02:~/src/launchpad.net/juju-core$ juju bootstrap -v --upload-tools [01:50] Flag --verbose is deprecated with the current meaning, use --show-log [01:50] 2014-03-12 01:50:08 WARNING juju.cmd.juju common.go:34 ignoring environments.yaml: using bootstrap config in file "/home/ubuntu/.juju/environments/local.jenv" [01:50] 2014-03-12 01:50:08 ERROR juju.cmd supercommand.go:296 environment has no bootstrap configuration data [01:50] this broke overnight [02:13] davecheney: i just tried bootstrapping local from trunk, seems to work [02:13] but i didn't have a jenv file lying around [02:14] i know that warning is new, but i don't know of any logic changes [02:19] ubuntu@winton-02:~/src/launchpad.net/juju-core$ juju status [02:19] ERROR Unable to connect to environment "local". [02:19] Please check your credentials or use 'juju bootstrap' to create a new environment. [02:19] Error details: [02:19] not bootstrapped [02:19] environment is not bootstrapped [02:25] davecheney, I can fix leankit [02:27] davecheney: you can try destroying your env and start again, that will clear any old jenv file [02:27] davecheney, you were definitely deleted [02:28] oh sweet, someone paid for more seats. There is not need to delete the old users [02:35] thumper: if you have a moment - https://codereview.appspot.com/74330044 === Ursinha is now known as Ursinha-afk [02:39] thumper: you're not having much luck with your branch :-( [02:39] no... === Ursinha-afk is now known as Ursinha [03:25] anyone able to give me a hint on "BadRequest - The affinity group name is empty or was not specified." when deploying to azure. I've created a storage group in East US and that's the location set in my env.yaml [03:28] ah, seems I'm hitting https://bugs.launchpad.net/juju-core/+bug/1259350 [03:28] <_mup_> Bug #1259350: juju bootstrap fails in Azure (BadRequest - The affinity group name is empty or was not specified.)

[03:33] https://bugs.launchpad.net/juju-core/+bug/1291165 [03:33] <_mup_> Bug #1291165: juju bootstrap local cannot bootstrap

[03:33] this has proved hard to unfuck [03:35] can you try removing the jenv file? [03:41] ubuntu@winton-02:~/src/launchpad.net/juju-core$ cat /home/ubuntu/.juju/environments/local.jenv [03:41] ubuntu@winton-02:~/src/launchpad.net/juju-core$ file /home/ubuntu/.juju/environments/local.jenv [03:41] /home/ubuntu/.juju/environments/local.jenv: empty [03:41] brilliant [03:42] wallyworld_: yup, that fixed it [03:42] davecheney: i would have hoped destroy-env would have been able to do that [03:43] maybe it can't handle an empty file [03:47] that sounds like a good resolution to the bug [03:47] --force should remove the .jenv, with prejudice [03:47] otherwise CTS will shank us [04:03] wallyworld_: when you have a moment, please: https://code.launchpad.net/~axwalk/gwacl/deleteservice-media/+merge/210534 [04:03] sure [04:06] axw: are you going to delete the obsolete delete code? [04:06] in juju [04:07] wallyworld_: I am going to in my new implementation [04:07] great [04:07] wallyworld_: actually, DestroyHostedService is in gwacl [04:07] which is what does all this manually [04:07] I will remove it once the Juju side is updated [04:07] do maybe add to your branch [04:07] ok [04:26] * thumper is starting to get real fucked off with the landing bot [04:26] no... [04:26] getting fucked off at that intermittent failing test [04:27] that fails more often than not [04:33] wallyworld_: you'll be happy to know that I came up with some good tests for this new code :) [04:33] * thumper is pretty happy with them [04:33] great [04:33] just running 'make check' before proposing [04:33] ok [04:36] * thumper waits with baited breath to see if the fucking test fails again [04:40] * wallyworld_ gets the popcorn [04:42] GRRRR!!!! [04:42] * thumper approves again [04:42] I think this branch is almost a record [04:58] * thumper taps his fingers... [05:03] * thumper approves it again [05:03] wallyworld_: https://codereview.appspot.com/74370044 if you have time [05:03] ok [05:03] * thumper wanders off for a bit [05:03] will check on the bot in about 20 minutes === thumper is now known as thumper-afk [05:45] thumper-afk: I think the bot has been failing because it failed enough to start running out of disk space [05:45] at least, it was at 6 out of 8GB consumed === jam1 is now known as jam === Ursinha is now known as Ursinha-afk === Ursinha-afk is now known as Ursinha [06:56] :( [06:57] jam: can I get you to email me the bot creds again? or point me to where to get them from? [06:57] that way I can look myself instead of annoying wallyworld_ [06:57] thumper-afk: sure, though I'm poking at it right now myself [06:57] thanks in advance [06:57] thumper-afk: FYI, just found this: https://bugs.launchpad.net/juju-core/+bug/1291207 [06:57] I'm trying to sort out the failures [06:57] <_mup_> Bug #1291207: juju-run symlink is broken after upgrade-juju

[06:57] :-( [06:58] will look tomorrow (most likely [06:58] looks like it'll be easy to fix. [06:58] thumper-afk: you hold the record [06:58] fcking permissions [06:58] wallyworld_: for annoying you? [06:58] \o/ [06:58] that too :-) === thumper-afk is now known as thumper [06:58] i mean for failed landing attempts [06:59] thumper-afk: I have to sort out the original creds for nova list, but for now the IP address is 10.55.61.118 and your launchpad SSH keys can log in as 'ubuntu' [06:59] I'm going to sign off now, but I'll keep poking the landing bot [06:59] kk [06:59] ta [06:59] bot is in limbo right now while I debug [06:59] kk [09:14] rogpeppe, hey [09:14] dimitern: yo! [09:14] rogpeppe, I decided to drop one of the incomplete fixes - the one about .jenv detection [09:15] dimitern: sounds like a good plan - it needed some more work [09:15] rogpeppe, after rummaging for a while in the code I realized you're right and it deserves its own CL as it'll blow up this out of proportion [09:30] rogpeppe, re registering a file:// protocol on utils/http by default [09:30] rogpeppe, it seems the manual provider is using "file:///var/lib/juju/storage/tools.tar.gz" in the provider-state-url file when provisioning [09:31] rogpeppe, and without that it fails to fetch the provider-state and claims it's not bootstrapped [09:31] rogpeppe, (or something similar - i'm testing again now to see if that's the case) [09:31] dimitern: how does it manage to work currently? [09:32] rogpeppe, it's quite fragile in my experience [09:33] dimitern: but how can it work at all if the file protocol isn't registered? [09:33] rogpeppe, i had to set up a vm with "ubuntu" user to make it work for example - it was always trying ubuntu@bootstrap-host and it was failing to use the bootstrap-user i specified [09:33] rogpeppe, well, that's the thing - simplestreams *does* register the file:// protocol for testing purposes [09:33] rogpeppe, in some init() func [09:34] dimitern: this isn't testing code though, is it? [09:34] rogpeppe, but that code path doesn't seem to run in some cases [09:34] rogpeppe, no it's production code [09:35] rogpeppe, simplestreams.go:379 [09:35] dimitern: in which dir? [09:35] rogpeppe, envs/ss/ [09:36] rogpeppe, but since RegisterProtocol there uses http.DefaultTransport it wasn't working when ssl-hostname-validation was set to false (and a non-validating tls transport was used) [09:36] dimitern: hmm, i start to see [09:38] rogpeppe: what is the command you want tested for 512-maas-bootstrap-bridge-utils? [09:38] rogpeppe, I'll run a series of tests of manual bootstrap and local bootstrap + manual provisioning to before reproposing without the file:// proto registration [09:39] wwitzel3: we need to check that we can deploy units to the bootstrap node and that we can connect to those units [09:40] dimitern: the fact that simplestreams is registering the file protocol seems a bit wrong. i need to think about it for a little bit. [09:40] rogpeppe, it *definitely* seems wrong like this, unconditionally [09:41] rogpeppe: ok, I'm on your branch and I've bootstraped a node in my maas .. so I can just deploy anything? [09:41] wwitzel3: try: juju deploy --to lxc:0 ubuntu [09:49] rogpeppe: ok, got it, when I "fixed" the lxc not being installed from cloud-tools before, I was testing not using --upload-tools. So my fix actually wasn't a fix and broke the CI build. [09:50] wwitzel3: good point [09:51] rogpeppe: so I'm actually fixing it now :P .. and I will test your branch with that test. [09:51] wwitzel3: thanks [09:52] rogpeppe: I also managed to get my maas configured in such away that I can easily destroy environ without having to rebuild the nodes from scratch. By snapshotting them at the right time, I can just restore to the snapshot. [09:52] rogpeppe: so testing is a lot faster now :) [09:52] wwitzel3: nice [10:17] rogpeppe, so without the file:// proto registration I get this: [10:17] rogpeppe, 2014-03-14 08:04:54 ERROR juju.cmd supercommand.go:296 cannot load state from URL "file:///var/lib/juju/storage/provider-state" (read from "/tmp/provider-state-url"): Get file:///var/lib/juju/storage/provider-state: unsupported protocol scheme "file" [10:17] rogpeppe, with manual bootstrap [10:20] rogpeppe, if you're against registering a file protocol handler, I can check for file:// schema in the environs/bootstrap LoadStateFromURL() and try to read it directly instead [10:20] dimitern: i'm still trying to think it through [10:24] dimitern: the thing that makes me most uncomfortable is the disconnected nature of the fix here - we have two places a long way apart in the code (utils/http vs environs/simplestreams) that are both intimately connected - that feels pretty sleazy [10:24] rogpeppe, it does, doesn't it [10:25] dimitern: i'd be happier if everything used a Client from utils/http [10:25] dimitern: then we could have a function to register schemes in there, rather than using http.DefaultClient [10:25] rogpeppe, in fact this error only seems to happen when you manual bootstrap with ssl-hostname-verification: false, tested just now [10:25] rogpeppe, and that's due to simplestreams [10:25] dimitern: that sounds right - if ssl-hostname-verification is true, we use http.DefaultClient [10:26] rogpeppe, so I'll drop the file:// proto registration for this CL and file a bug about unifying http clients [10:26] dimitern: doesn't that leave trunk broken? [10:26] dimitern: i guess it's already broken though [10:28] rogpeppe, yeah - it's no more broken than it was [10:31] rogpeppe: in juju-core/instance/instance.go where is Address defined? [10:31] is it a built-in type [10:32] voidspace: in instance/address.go [10:32] ah, same package name [10:32] just not the same file [10:32] voidspace: if in doubt, grep for 'type Foo' [10:32] gd doesn't work on my desktop machine either [10:32] must work out why [10:33] voidspace: yeah - i find it invaluable [10:33] voidspace: you could find out if it works ok just running it from the command line [10:33] rogpeppe: right, good call [10:36] voidspace: the only built-in types are mentioned here: http://golang.org/ref/spec#Predeclared_identifiers [10:36] rogpeppe: yeah, I just went there to check :-) [10:36] thanks [10:36] voidspace: (which is the definitive list of predeclared identifiers) [10:36] voidspace: if you haven't already, the spec is well worth a read [10:37] voidspace: being unusually readable for such things [10:40] rogpeppe: right, I haven't [10:40] rogpeppe: ok, so my godef wasn't properly installed in vim (the bundle wasn't working - I've now manually installed godef.vim) [10:41] rogpeppe: so now it is not working in much more interesting and potentially fixable ways... :-) [10:41] voidspace: lol [10:41] rogpeppe: it only looked like it was sort of working because "gd" is the default vim "goto local definition" vim command anyway [10:41] voidspace: so how's it failing now? [10:42] For example [10:42] parseLocalPackage error: no more package files found^@godef: no declaration found for Address [10:42] voidspace: that ^@godef thing is weird [10:44] rogpeppe: yeah, I'd better check godef.vim I guess [10:44] voidspace: godef has got a -debug flag, which might or not produce some useful info in this case [10:45] godef --help is "terse" [10:46] and [flags] expr does not explain the arguments it takes *particularly* well [10:46] rogpeppe, filed bug 1291292 [10:46] <_mup_> Bug #1291292: use a utils/http client for all HTTP(S) calls across the codebase

[10:47] voidspace: yeah, could do better :-) [10:47] voidspace: "expr" is a go expression [10:47] rogpeppe: so I did "godef instance.Address" [10:47] and got [10:47] godef: cannot read : open : no such file or directory [10:48] voidspace: try: godef -f somefile.go instance.Address [10:48] rogpeppe: cool, thanks [10:48] voidspace: where somefile.go is the file you're going from [10:48] right [10:48] voidspace: standup: https://plus.google.com/hangouts/_/canonical.com/juju-core?v=1394218410 [10:49] rogpeppe: and it works [10:49] hmmm.... [10:49] voidspace: hmm [10:49] rogpeppe: which is good news, just need to figure out the vim integration [10:49] voidspace: yeah [10:50] jam, mgz_, standup? [10:50] I'm here [10:56] rogpeppe: is this the canonical vim-godef? https://github.com/dgryski/vim-godef [10:56] voidspace: i think so [10:56] rogpeppe: thanks [11:02] rogpeppe: if I start vim from the launchpad.net directory it works - so it's not coping with shorter relative paths I think [11:02] voidspace: interesting [11:02] rogpeppe: if I start vim from launchpad.net/juju-core/worker (for example) it fails [11:03] rogpeppe: so yay, it works! :-) [11:03] voidspace:cool [11:09] rogpeppe: hmmm... maybe not, it works once and then the next call doesn't work :-/ odd [11:10] voidspace: i'd add some debug prints to the source [11:10] voidspace: see what arguments are actually being passed [11:10] rogpeppe: ok, outside work time I think [11:10] voidspace: then try calling godef directly with those arguments and see if you can repro the failure [11:10] voidspace: probsa [11:11] rogpeppe: my guess is that it's mainly a path issue [11:11] voidspace: it may well be [11:22] rogpeppe, last look over https://codereview.appspot.com/72860045/ before i land it? [11:22] dimitern: will do [11:39] vladk: It would seem that you made it to IRC, am I chatting to the right vlad ? [11:39] yes [11:40] mgz_: so I need coffee and then we should talk [11:41] voidspace: me too [11:42] vladk: welcome again to the team [11:43] natefinch: FWIW my last round of "If we get EOF, Refresh + Ping" seems to have landed cleanly, and allowed thumper's branch to land [11:43] it is possible that the fix was that I now *always* call Ping after replSetReconfig [11:43] to detect if we're actually going to get an EOF [11:43] that would otherwise have been missed [11:43] and then Refresh() and Ping again [11:44] natefinch: I'm not sure, but hey, 2 branches landed back to back is great news for thebot [11:50] so ever since we decided to shorten the standup to 15m it started getting 30-45m each time :) [11:51] jam: that's great. [11:53] jam: that may have been the fix... there seems to be a lot of chicken waving in getting the replicaset stuff working correctly [11:54] natefinch: given the "wait for us to wake up and be ready" it certainly does make you wave some chickens [11:54] rogpeppe, should be good to land, right? [11:55] * rogpeppe remembers to go back and look [11:56] dimitern: i don't think DetectionScript and CheckProvisioned should be exported - they could be added to export_test.go so that local tests can access them [11:57] dimitern: they aren't used in production code external to the package AFAICS [11:57] if people here could Ping when they set an MP to approved, I'd like to keep an eye on the bot, it looks like it is semi-healthy again [12:07] so in the case where a var of a package is private, but I want to use it in a test, do I just make it public .. seems not what I want to do. [12:08] the var is a slice that is modified by the package I am testing and I want to assert that those modifications are successful [12:09] wwitzel3: is the slice a global? [12:09] wwitzel3: are you doing this from another package, or from inside the package with the slice? [12:12] rogpeppe, natefinch: the slice is a global, it is being modified from side the functions of a struct in the same package. [12:12] s/side/inside [12:12] wwitzel3: in general I'm skeptical of functions that modify global state, but it may be ok in this instance [12:13] wwitzel3: what does the slice hold? [12:13] rogpeppe: fair, this is the requirePackages slice in the lxc/initalisation.go [12:13] requiredPackages .. helps if I could type this morning [12:14] wwitzel3: if your tests are in the same package as the slice, you can just modify it directly. THat is, put your tests in the same package (as opposed to _test) and then you can access non-exported data [12:14] natefinch: Ok, and that is not taboo? [12:14] wwitzel3: why does that slice need to be modified? [12:14] wwitzel3: it's a judgement call [12:15] rogpeppe: so that --target-release is passed to the AptGetInstall that consumes the slice [12:15] wwitzel3: it's not taboo, that's how you get nice limited-scope tests to verify specific behavior. [12:15] wwitzel3: the other approach is to have an export_test.go file in the same package that exports some variables just for tests [12:16] rogpeppe: I like the export_test approach [12:16] rogpeppe: export_test is an abomination... there seems to be no reason to do it other than "all the rest of my tests are external, and I don't want to make another file for internal tests" [12:16] natefinch: I like that it is explict [12:16] natefinch: i wouldn't word it so strongly [12:17] natefinch: there's a trade-off here [12:17] rogpeppe: it just means that your tests now use something that looks public that doesn't actually exist in the real package [12:17] rogpeppe: at least with internal tests, it's clear you're using package internals [12:17] natefinch: that's true [12:17] rogpeppe: there's nothing that says you can't have both internal tests and external tests [12:18] sorry, kids are up, I gotta go. I wanted to have this discussion last week, but it was too hard over the hangouts. [12:18] well it seems like there is less debate over just making the tests be part of the package, so I will go that route :) [12:18] natefinch: with internal tests, you can't tell whether any call is public or private [12:18] and then people can pick on me in the code review [12:18] wwitzel3: i think natefinch is about the only one with that particular view :-) [12:19] wwitzel3: although i don't mind internal tests much either [12:19] rogpeppe: maybe so, but I have to pair with him today, so he wins :P [12:19] wwitzel3: ha ha [12:20] wwitzel3: BTW, i think that modifying the global slice is almost certainly the wrong approach in this case [12:20] rogpeppe, agreed I changed that as you suggested [12:20] rogpeppe: yeah, I am actually going to send a different one instead of modifying [12:20] dimitern: thanks [12:20] rogpeppe, and I'm waiting for your LGTM [12:23] dimitern: i'm presuming you haven't re-proposed the changes yet [12:25] is it common when comparing two structs of the same type to get a runtime error "comparing uncomparable type" from c.Assert [12:25] https://pastebin.canonical.com/106327/ [12:26] dimitern: LGTM [12:26] voidspace: you probably want to be using gc.DeepEquals [12:26] rogpeppe: sounds good, thanks [12:27] voidspace: not all types in Go are comparable [12:27] voidspace: specifically, slices and function pointers aren't [12:27] rogpeppe: but you can compare type and compare members [12:27] rogpeppe: slices are uncomparable !? [12:27] that's the issue [12:28] DeepEquals is at least pointing me to the slices it can't compare [12:28] runtime error: comparing uncomparable type []instance.Id [12:28] voidspace: yes, slices are uncomparable because it's not clear how the comparison should work [12:28] compare length and if they're the same length compare members are equal [12:28] voidspace: there are at least three possible ways [12:28] what other way would make sense? [12:29] voidspace: slices also have additional values after the length [12:29] capacity [12:29] voidspace: yeah [12:29] hmmm [12:29] voidspace: and another possibility is to compare by pointer equality [12:30] an identity check [12:30] voidspace: yeah [12:30] that's a different check in my opinion [12:30] voidspace: it's not clear which one == should use though [12:30] voidspace: if i compare two pointers, it doesn't compare their contents [12:31] rogpeppe: that's an identity check not an equality check though right (using Python terminology) [12:31] voidspace: there's no distinction between the two in Go currently [12:31] rogpeppe, yeah, I wanted to address any comments with one proposal [12:32] rogpeppe, thanks! [12:32] rogpeppe: but the very idea of pointers introduces the distinction [12:32] voidspace: and if we compare members recursively, there's the possibility that we might get an infinite loop in an equality check [12:32] rogpeppe: only if you're equality implementation is dumb [12:32] :-) [12:33] rogpeppe: but yeah, maybe making arbitrary types automatically comparable is problematic [12:33] rogpeppe: how do you work around it for tests? [12:33] voidspace: DeepEquals [12:33] rogpeppe: except that doesn't work for types with slices as members [12:33] voidspace: sure it does [12:33] voidspace: DeepEquals is recursive [12:33] rogpeppe: hah [12:33] voidspace: (and deals with cycles too) [12:33] rogpeppe: the DeepEquals works [12:34] rogpeppe: and the error I *now* have is from the next Assert [12:34] I just didn't notice [12:34] so DeepEquals is fine and I'll stop complaining :-) [12:34] voidspace: if you use jc.DeepEquals (from testing/checkers) then it will tell you where the comparison failed too [12:34] yep [12:34] voidspace: which is great if you're comparing a large chunk of data [12:34] I'm using gc.DeepEquals (from gocheck) and it is giving me enough information at the moment [12:35] ah, but not the member name that failed, just the comparison that failed [12:35] voidspace: yeah [12:35] which for this type is sufficient as it only has two members [12:35] rogpeppe: thanks [12:36] voidspace: there's one other distinction between gocheck.DeepEquals (which uses reflect.DeepEqual) and checkers.DeepEquals - the former treats a nil slice as distinct from an empty slice; the latter does not. [12:36] voidspace: since in general we treat a nil slice exactly the same as an empty slice, the latter can be useful [12:36] rogpeppe: right, useful to know [13:44] wallyworld_, still there? [13:44] sorta [13:44] wallyworld_, so should i assign bug 1290684 to myself? [13:44] <_mup_> Bug #1290684: cannot perform multiple upgrades

[13:44] i have a mp up for that bug [13:45] https://code.launchpad.net/~wallyworld/juju-core/old-agentconf-datadir/+merge/210526 [13:45] wallyworld_, I can't see a linked branch [13:45] i haven't linked it sorry [13:45] will do so [13:46] wallyworld_, ok, so after yours lands, I can file a separate bug about migrating Jobs in 1.18 config? [13:46] yeah, and anything else that need doing [13:46] maybe it's just Jobs [13:46] can't recall right now [13:47] before i and i just want to ensure local provider is covered [13:47] sure [13:47] I also have some comments on your CL [13:47] ok [13:48] i'm off to bed, i'll look tomorrow [13:55] you guys ready for the UDS update? [13:55] jcastro: glad you reminded me [13:56] https://plus.google.com/hangouts/_/hoaevent/AP36tYdJ0WjYraULj4VVnIhg2-wan1zM_Q6nzudEY4WfC6p1-8aoWw?authuser=0&hl=en&hcb=0&lm1=1394632583536&hs=75&hso=0&heeid=tvJzNRrPTJA&ssc=WyIiLDAsbnVsbCxudWxsLG51bGwsW10sbnVsbCxudWxsLG51bGwsbnVsbCxudWxsLDc1LG51bGwsbnVsbCxudWxsLFsxMzk0NjMyNTgzNTM2XSxudWxsLFsiaG9hZXZlbnQiLCJBUDM2dFlkSjBXallyYVVMajRWVm5JaGcyLXdhbjF6TV9RNm56dWRFWTRXZkM2cDEtOGFvV3ciXSxbXSxudWxsLG51bGwsbnVsbCxudWxsLG51bGwsbnVsbCxudWxsLG5 [13:56] 1bGwsbnVsbCxbMF0sW10sbnVsbCwidHZKek5SclBUSkEiLG51bGwsW10sbnVsbCxudWxsLG51bGwsW10sbnVsbCxudWxsLFtdXQ.. [13:56] whoa! [13:56] https://plus.google.com/hangouts/_/hoaevent/AP36tYdJ0WjYraULj4VVnIhg2-wan1zM_Q6nzudEY4WfC6p1-8aoWw?authuser=0&hl=en [13:56] try that one [13:56] rogpeppe, mgz_, dimitern, jam: what the hell have we delivered and do we intend to deliver? [13:57] besides HA.... joyent provider, I guess [13:57] natefinch, for 1.18? [13:57] dimitern: uh sure, or trusty [13:58] natefinch, for trusty definitely more than for 1.18 [13:58] natefinch, for 1.18 mostly lots of critical/high bug fixes and regressions [13:59] dimitern: trusty is probably what people will care about [13:59]