[08:14] <mgz> morning all
[08:37] <hoenir> any more thoughts on this review? https://github.com/juju/juju/pull/6414
[08:39] <hoenir> morning mgz
[08:48] <mgz> hoenir: I'd be happy to look over as well, but seems you have addressed reviews from axw and katco already?
[08:49] <axw> hoenir mgz: I will take another pass, but nearly EOD so not until tomorrow
[08:55] <hoenir> axw, ok thanks !
[09:36] <jamespage> mgz, hey - we're hitting a juju ssh problem in a charm school at the openstack summit
[09:36] <jamespage> aware of any issues? basically the terminal is foobar'ed when you ssh to a ubuntu machine from a windows command prompt.
[09:37] <mgz> jamespage: hm, there have been some issues, let me see what I can find
[09:38] <mgz> jamespage: bug 1468752
[09:38] <mup> Bug #1468752: "juju ssh" adds an additional strings to all commands when used on Windows, in interactive mode <ssh> <windows> <juju:Triaged> <juju-core:Won't Fix> <juju-core 1.25:Triaged> <https://launchpad.net/bugs/1468752>
[09:38] <anastasiamac_> mgz: jamespage: there is this on.. https://bugs.launchpad.net/bugs/1635622
[09:38] <mup> Bug #1635622: 'juju ssh <unit> ...' fails with Permission denied (publickey), for only one or two machines in a deployment <juju:Triaged> <https://launchpad.net/bugs/1635622>
[09:39] <mgz> ...bug doesn't document a workaround as such, but does suggest spaces before and after the command
[09:47] <jamespage> anastasiamac_, ssh key is working ok - but shell is non-functional
[09:48] <mgz> jamespage: is terminal completely borked of does ` echo test ` actually output 'test' as well as errors?
[09:48] <mgz> -of+or
[09:49] <mgz> may also be work considering using `juju run` instead, if possible?
[10:38] <voidspace> finally online, one monitor still not working
[10:38] <voidspace> ah well
[10:39] <SimonKLB> whats the best way to include a local version of charmhelpers in the wheelhouse? right now i manually put it there and remove the one that gets downloaded in the build process
[11:14] <voidspace> SimonKLB: you're better off asking in #juju - there should be people there who can answer your questions (although maybe a bit later in the day when the Americans arise!)
[11:16] <SimonKLB> voidspace: whats the difference between #juju and this channel? i thought this was for the people developing juju / juju charms while #juju was for juju users
[11:17] <voidspace> SimonKLB: this channel is used by those developing juju itself. #juju is for those writing charms and using juju.
[11:18] <voidspace> SimonKLB: that's how it works in practise. I'm sorry that I don't know the answer to your question. There *maybe* someone here who can answer your question, but not at the moment it seems.
[11:18] <SimonKLB> voidspace: gotcha, so youre not involved with the charmhelpers and/or charm layers?
[11:18] <voidspace> SimonKLB: I don't have much experience with them myself, no.
[11:19] <SimonKLB> do you know of anyone awake at this hour that do? id like to have a quick discussion regarding an issue
[11:19] <voidspace> rick_h_: do you know who would be a good person to answer SimonKLB's question?
[11:21] <SimonKLB> that, but even more someone to discuss this: https://github.com/juju-solutions/layer-basic/issues/79
[11:23] <voidspace> SimonKLB: when more people are around I will ask again. It might be wise to ask on the mailing list as that gives people time to respond.
[11:23] <voidspace> SimonKLB: let me find you a link.
[11:24] <dimitern> SimonKLB: one of these people should be able to help: marcoceppi, lazyPower, arosales, jcastro
[11:24] <voidspace> SimonKLB: https://lists.ubuntu.com/archives/juju/
[11:24] <mgz> dimitern: do you have some time to help me with debugging today?
[11:25] <dimitern> mgz: sure - what's up?
[11:25] <SimonKLB> dimitern: yea, the only problem is the timezone difference with those guys.. :)
[11:25] <mgz> dimitern: hangout? maas/network fun mostly
[11:25] <dimitern> mgz: joining core now
[11:52] <perrito666> morning all
[11:56] <mgz> morning perrito666
[12:15] <dimitern> mgz: you got kicked out?
[12:25] <rick_h_> SimonKLB: https://pythonhosted.org/charmhelpers/getting-started.html#updating-charmhelpers-packages
[12:27] <SimonKLB> rick_h_: thanks!
[12:31] <SimonKLB> rick_h_: do you know if there is going to be any problems using this while also building the charm normally where the wheelhouse is getting populated?
[12:32] <SimonKLB> isnt the upstream version of the charmhelpers going to be installed as well in that case?
[12:35] <rick_h_> SimonKLB: sorry not sure. Will have to try it out.
[13:01] <dooferlad> rick_h_: 1:1 time
[13:02] <rick_h_> dooferlad: omw
[13:47] <mup> Bug #1589680 changed: Upgrading to cloud-archive:mitaka breaks lxc creation <canonical-bootstack> <juju-core:Incomplete> <juju-core 1.25:Incomplete by dimitern> <https://launchpad.net/bugs/1589680>
[13:52] <rick_h_> dimitern: so on that bug, you're doing an upgrade on the system so doing that install before bootstrap doesn't help?
[13:52] <rick_h_> dimitern: if you install post-bootstrap is there anything that could be done to get it to that working state?
[13:52] <dimitern> rick_h_: it's not an upgrade per se
[13:53] <dimitern> rick_h_: it won't work with xenial containers to begin with, without upgrading
[13:53] <rick_h_> dimitern: let's chat after the standup on it please
[13:53] <dimitern> rick_h_: ok
[13:56] <mup> Bug #1560487 opened: local provider fails to create lxc container from template <canonical-is> <local-provider> <juju-core:Triaged> <juju-core 1.25:Invalid> <OPNFV:Invalid> <juju-core (Ubuntu):Confirmed> <https://launchpad.net/bugs/1560487>
[14:01] <rick_h_> kadams54: voidspace ping for standup
[14:01] <rick_h_> oops, not kadams54, katco who, isn't here so tab complete fail
[14:01] <kadams54> lOl
[14:01] <kadams54> I was really befuddled
[14:01] <rick_h_> kadams54: :P you know you want to join us
[14:02] <kadams54> Guilty as charged
[14:02] <voidspace> rick_h_: omw
[14:11] <arosales> rick_h_: get SimonKLB all set?
[14:13] <SimonKLB> arosales: yea talked to lazyPower :)
[14:13] <arosales> SimonKLB: great, that lazyPower rocks
[14:14] <perrito666> well look at that, this code had a ton of nilptr derefs waiting to happen
[14:38] <natefinch> perrito666: obviously the answer is not to use pointers
[14:39] <perrito666> natefinch: wish it was so easy
[14:39] <natefinch> what, you just delete the little *, right?
[15:40]  * rick_h_ lunches
[15:52] <alexisb> babbageclunk, ping
[16:23] <perrito666> hi all, I desperately need a review on https://github.com/juju/juju/pull/6490 its a bit tricky sorry
[16:26] <natefinch> perrito666: oh man, dropping the need for our copied dependencies is awesome
[16:26] <perrito666> natefinch: heh sadly that is the last tag that will support juju until we move to 1.7
[16:27] <natefinch> perrito666: wow, they require 1.7?
[16:27] <perrito666> natefinch: next tag uses Context
[16:27] <perrito666> from context
[16:27] <natefinch> ahh, crappage
[16:28] <perrito666> We could revert it back to golang.org/x/context but maintaining such parallel code is very unwise
[16:30] <natefinch> you could file an issue and maybe they'd put it back to using that one
[16:35] <alexisb> perrito666, if we  are updating a dep we need a +1 from the tech board
[16:36] <perrito666> alexisb: technically we had that dep already
[16:36] <alexisb> the juju version was special because?
[16:36] <perrito666> alexisb: compatible with go 1.2
[16:37] <alexisb> o yuk, yeah ok I remember that
[16:37] <alexisb> ok we are good then thank you
[16:37] <perrito666> np, sorry for making the assumption there without asking
[17:05] <babbageclunk> alexisb: pong, sorry - missed your message!
[17:05] <alexisb> babbageclunk, no worries, was just going to touch base with you, otp atm
[17:07] <babbageclunk> alexisb: ok, give me a yell when you're free
[17:07] <perrito666> brb errand
[17:15] <babbageclunk> alexisb: actually, pausing for lunch - will ping when back.
[17:17] <alexisb> k
[17:28] <katco> i will probably miss the mobility, but for now: wow it is so nice to be back on a desktop with 8 fast cores and 16GB ram
[17:29] <rick_h_> katco: heh yea somtimes forget what real hardware can do
[17:30] <katco> i definitely did
[17:30] <katco> i did not know the pain i was in
[17:30] <katco> at least i did the experiment :) now i know better
[17:59] <babbageclunk> alexisb: back!
[18:00] <alexisb> babbageclunk, still otp
[18:00] <alexisb> :)
[18:00] <babbageclunk> alexisb: ok cool
[18:17] <perrito666> a lte modem is working better than my isp, this is so sad
[18:43] <alexisb> babbageclunk, I am free when you are
[18:44] <babbageclunk> alexisb: ok, jumping into the hangout
[18:44] <alexisb> meet you there
[18:45] <natefinch> man, recursive code screws with my head
[19:11]  * rick_h_ goes to get the boy from school
[19:12] <natefinch> rick_h_: aww... POC for openstack: http://pastebin.ubuntu.com/23375669/
[19:15] <lazyPower> super cool to juju update-clouds today and see the new AWS region show up
[19:15] <lazyPower> <3
[19:15] <natefinch> \m/
[19:16] <natefinch> lazyPower: while you're here, would love to get your impression of this working example of an interactive add-cloud for juju: http://pastebin.ubuntu.com/23375669/
[19:16] <lazyPower> interesting, can this be scripted wtihout the use of `expect`?
[19:17] <lazyPower> i assume it can with a config.yaml
[19:17] <natefinch> lazyPower: nope,  but if you want to script you can just pass in a yaml file like we do now
[19:17] <lazyPower> yep, sgm
[19:17]  * lazyPower +1's it
[19:17] <lazyPower> ship it
[19:18] <natefinch> cool
[19:18] <lazyPower> natefinch - i'm probably missing most of the context, the last time i setup an openstack controller was for OIL onboarding. but this looks straight forward.
[19:18] <lazyPower> and i'm +1 to straight forward data entry forms :)
[19:19] <natefinch> lazyPower: before this, the only way to add an openstack or maas or manual provider is to give juju a yaml file you had hand-written that you somehow mangically knew the correct format for
[19:19] <perrito666> natefinch: what, you dont?
[19:19] <lazyPower> natefinch - i recall, and it annoyed me
[19:19] <lazyPower> <3
[19:28] <babbageclunk> Anyone have an idea why this detects an error by looking for an error message in the header rather than for an error code? https://github.com/juju/juju/blob/staging/rpc/client.go#L103
[19:33] <babbageclunk> perrito666, natefinch: ^
[19:36] <natefinch> babbageclunk: I presume both are always set at the same time, not 100% sure though
[19:45] <babbageclunk> natefinch: Well, they weren't in some code I just wrote! :) Took me a while to track down.
[20:23] <katco> menn0: ping
[20:23] <menn0> katco: hi
[20:23] <katco> menn0: hey, hope your 3-day was good :)
[20:23] <katco> menn0: or 4-day? did you take friday off?
[20:23] <menn0> katco: 4 day!
[20:24] <katco> menn0: nice :D
[20:24] <katco> menn0: this is ready for review: https://github.com/juju/juju/pull/6469
[20:24] <menn0> katco: mostly spent doing hard labour in the garden mind you
[20:24] <katco> menn0: it always works out that way doesn't it?
[20:24] <katco> menn0: do you write about your garden anywhere? considering starting one
[20:24] <menn0> katco: yes, but it was kind of rewarding
[20:25] <menn0> katco: looking at that PR now
[20:25] <menn0> katco: github says there's a conflict
[20:25] <katco> menn0: ta. no rush on that other than i'd like to get it merged before it conflicts :)
[20:25] <katco> menn0: it's a very simple conflict at the top-level... not substantive
[20:25] <menn0> katco: ok
[20:26] <katco> menn0: cmd/juju/commands/main.go
[20:26] <katco> menn0: the review doesn't have to be now; i'm not blocked or anything. just when you have time. before i wake up tomorrow would be nice :)
[20:26] <menn0> katco: ok will do
[20:26] <katco> menn0: ta!
[20:26] <katco> menn0: so do you blog about your garden at all? what do you grow?
[20:27] <menn0> katco: no, not at all. I am a complete beginner. this weekend was a lesson in how much I suck at gardening.
[20:28] <katco> menn0: lol! any words of advice?
[20:28] <natefinch> katco: my wife and I have gardened a lot.  Our gardening blog is evidently down, which I should fix.  But I'll try to get it back up again.
[20:28] <menn0> katco: be careful when using a spade - there can be pipes where you don't expect them :)
[20:28] <natefinch> lol
[20:29] <menn0> I cut through an irrigation hose
[20:29] <katco> natefinch: awesome, thx!
[20:29] <katco> menn0: rofl
[20:29] <katco> menn0: what are you starting off with?
[20:29] <katco> natefinch: and what do you grow?
[20:29] <natefinch> katco: if you're going to be in this location through next july, plant garlic, it's super easy
[20:29] <katco> natefinch: with any luck we will not be. this is a future-looking thing :)
[20:29] <natefinch> katco: ok :)
[20:30] <katco> natefinch: maybe i could do some potted garlic
[20:30] <natefinch> katco: garlic grows like a flower bulb - plant in the fall, harvest next july-ish
[20:30] <katco> natefinch: that's perennial isn't it?
[20:30] <natefinch> not really, you uproot the whole plant when you harvest
[20:31] <katco> natefinch: oh. must have read that wrong... looked into that a month or so ago
[20:31] <natefinch> katco: my best piece of advice us to mulch mulch mulch.  Makes the garden look nice, keeps soil moister, and keeps the weeds down.
[20:31] <katco> natefinch: is mulch the same as compost?
[20:32] <natefinch> katco: nope.  Mulch is the stuff you put on top of the ground to keep weeds from growing.
[20:33] <katco> natefinch: oh didn't know mulch did that
[20:33]  * katco is going to challenge menn0 for garden newb status
[20:33] <natefinch> katco: for flower beds it's often bark, for garden beds my favorite is salt marsh hay... it's like regular straw, but straw has grass seeds in it, which are obviously not something you want in your garden
[20:34] <menn0> katco: what, like regular updates? :)
[20:34] <katco> natefinch: do you have to reapply? or once?
[20:34] <natefinch> katco: basically just once a season
[20:35] <katco> natefinch: what do you do with the old mulch?
[20:35] <natefinch> katco: it tends to start to break down.. if it hasn't broken down too much, you can reuse it, but often times I just till it back into the dirt.
[20:35] <katco> natefinch: ah ok. so you don't have to like rake it up or anything
[20:36] <natefinch> nah.  It's just plant matter... it's actually good for the soil after it breaks down
[20:36] <katco> cool
[20:37] <katco> menn0: natefinch: have you seen this? https://farmbot.io/
[20:37] <natefinch> oh oh oh.... if you're planting near a structure - get your soil tested for lead (among other things).  Sometimes lead paint can contaminate the ground near buildings.  you can get your local state extension office to test your soil - just grab a bag and mail it off.  It's like $15.  Totally worth it.
[20:38] <katco> natefinch: wow, does that end up in edibles?
[20:38] <natefinch> katco: it definitely can, especially if they're root vegetables.
[20:38] <katco> wow
[20:38] <menn0> katco: that's pretty awesome
[20:38] <natefinch> yeah, haven't seen that machine before.  That's amazing
[20:39] <menn0> katco: although this is almost certainly how the matrix begins... the robots start with plants but then move onto people
[20:39] <katco> natefinch: menn0: it's completely open too. plans, cad, etc.
[20:39] <katco> menn0: rofl
[20:39] <katco> menn0: i couldn't have a perfectly fine hobby that gets me away from computers to keep me away from computers.
[20:40] <menn0> haha
[20:42]  * menn0 counts Github reviews vs reviewboard votes
[20:44] <thumper> morning
[20:45] <katco> morning thumper, wb
[20:45]  * thumper is feeling a little sore
[20:45] <thumper> about 15 hours of BJJ over Thursday/Friday/Saturday
[20:45] <thumper> very good though
[20:45] <katco> thumper: what is BJJ?
[20:46] <thumper> brazillian jiu jitzu
[20:46] <katco> ahh
[20:46] <menn0> thumper: wow, that's a lot of walloping :)
[20:46] <perrito666> mm, so, if the test run fails it marks the PR as failed, if it doesn't will it mark it as success in some form?
[20:48] <thumper> why is our develop branch so screwed? and failing CI?
[20:49] <perrito666> katco: menn0 natefinch thumper  does any of you know the answer to my question??
[20:50] <katco> perrito666: i believe it will
[20:50] <thumper> perrito666: it gets a tick
[20:50] <perrito666> I see no tick, Ill try a build by hand
[20:54] <menn0> thumper: i've just been going through some of the recent failures
[20:54] <thumper> and?
[20:54] <menn0> thumper: i'll take this one since I've worked on this recently: https://bugs.launchpad.net/juju/+bug/1632485
[20:54] <mup> Bug #1632485: TestAgentConnectionDelaysShutdownWithPing fails <ci> <intermittent-failure> <unit-tests> <juju:Triaged by menno.smits> <https://launchpad.net/bugs/1632485>
[20:54] <menn0> thumper: some of the windows fails are the usual mongodb failing to come up
[20:55] <menn0> thumper: this looks quite strange and needs attention: http://reports.vapour.ws/releases/4522/job/run-unit-tests-race/attempt/2007
[20:59] <thumper> menn0: I'm pretty sure I have mentioned more than once that 40 minutes isn't good enough on a small VM
[20:59] <thumper> a success is ~36 minutes
[20:59] <thumper> a 10% variation can cause it to fail
[20:59] <thumper> ish
[21:00] <menn0> thumper: well there's that, but all the ssh unit test failures are interesting as well
[21:00] <thumper> ah
[21:00] <thumper> yeah
[21:00] <thumper> didn't scroll to that
[21:11] <menn0> thumper: this is a new failure that started happening on the 22nd: http://reports.vapour.ws/releases/issue/580bc1a0749a566f2d9176bf
[21:11] <thumper> heh
[21:12] <thumper> yes, using space constraints is dependent on the underlying maas configuration
[21:23] <menn0> thumper: any idea what we need to change to fix the failures? who owns this?
[21:24] <mup> Bug #1630737 changed: juju should use internal vpc network address space when connected to vpc  via vpn <juju:Triaged> <https://launchpad.net/bugs/1630737>
[21:26] <rick_h_> menn0: so that's something we need to work on the bigger "spaces on aws" picture
[21:26] <rick_h_> menn0: I just triaged it and we'll make it part of that work we're planning for 17.04
[21:27] <menn0> rick_h_: but what about the CI failures that are contributing to cursed develop tests now?
[21:27] <rick_h_> menn0: oh, not sure.
[21:28] <menn0> rick_h_: something spaces related was committed on the 22nd which started breaking a bunch of CI tests: http://reports.vapour.ws/releases/issue/580bc1a0749a566f2d9176bf
[21:29] <rick_h_> menn0: hmm, but that was on the 22nd and no code landed over the weekend I'm aware of
[21:29] <rick_h_> menn0: this smells like something else up?
[21:31] <menn0> rick_h_: not sure - maybe whatever it was landed on the 21st, or maybe there's something else going on. i'm just trying to raise visibility.
[21:31] <rick_h_> menn0: hmm, I wonder if this is related to mgz's new maas related tests he's been working to get going
[21:31] <mgz> menn0: I broke a bunch of things, and should now have fixed them
[21:31] <rick_h_> menn0: rgr, so that bug isn't related. It's something with aws and a vpn that's going on there.
[21:32] <rick_h_> mgz: k, if you get a sec can you check with menno on what he's seeing vs expectations?
[21:32]  * rick_h_ has to get the boy ready for violin lessons and then to join the release call
[21:32] <mgz> menn0: can do hangout quickly if you like?
[21:32] <menn0> mgz: sure
[21:33] <mgz> menn0: I'm in the hangout named core
[21:37]  * redir goes for late lunch and to run an errand
[21:37] <redir> bbiab
[21:39] <menn0> thumper: so those spaces failures are all in hand. mgz was making some changes to maas+networking related tests and the failures were teething problems. they shouldn't happen on the next run.
[21:40] <thumper> cool
[21:42] <mup> Bug #1636307 opened: cannot deploy to network space <juju-core:New> <https://launchpad.net/bugs/1636307>
[21:49] <babbageclunk> menn0: Hey, are you busy? Can I pick your brains about some more migration stuff?
[21:54] <alexisb> thumper, fyi this bug is still preventing blesses on CI: https://bugs.launchpad.net/juju/+bug/1625768
[21:54] <mup> Bug #1625768: github.com/juju/juju/state go test timeout <ci> <intermittent-failure> <regression> <unit-tests> <juju:Triaged by alexis-bruemmer> <https://launchpad.net/bugs/1625768>
[21:54] <thumper> yes
[21:54] <thumper> I know
[21:55] <thumper> and there isn't really much we can do to fix it
[21:55] <thumper> the state tests just take a long time
[21:55] <thumper> I have pointed this out many times
[21:55] <thumper> until we replace the DB
[21:55] <thumper> or move all the logic out into separate packages
[21:55] <thumper> this will continue to fail
[21:56] <thumper> there is no quick fix for this issue
[22:02] <alexisb> thumper, I am on bluejeans
[22:02] <thumper> ack
[22:07] <mgz> bdx: can you poke around in your machine-0.log and see what juju thinks it knows about spaces when it's deploying machines to the wrong places?
[22:08] <menn0> babbageclunk: hi, sorry was AFK
[22:08] <menn0> babbageclunk: can chat now
[22:09] <bdx> mgz: yeah omp
[22:11] <mgz> bdx: thanks!
[22:12] <mup> Bug #1560487 changed: local provider fails to create lxc container from template <canonical-is> <local-provider> <juju-core:Invalid> <juju-core 1.25:Invalid> <OPNFV:Invalid> <juju-core (Ubuntu):Confirmed> <https://launchpad.net/bugs/1560487>
[22:16] <babbageclunk> menn0: Sorry - now I'm AFK - organising burger order but back in 5?
[22:16] <menn0> babbageclunk: np, i'll be here.
[22:22] <babbageclunk> menn0: ok, jump into a-team hangout?
[22:22] <menn0> babbageclunk: ok
[22:23] <babbageclunk> menn0: oh, hang on, that's bluejeans now - core?
[22:24] <menn0> babbageclunk: yep :)
[22:34] <alexisb> wallyworld, we are on bluejeans
[22:34] <alexisb> I wil be right back
[22:35] <wallyworld> alexisb: oh, i was in the hangout from the meeting invite
[23:09] <babbageclunk> Oops, burgers just arrived - not going to make it to the standup, sorry! See you next week!
[23:16] <alexisb> anastasiamac, ping
[23:17] <alexisb> babbageclunk, ping
[23:17] <alexisb> veebers, ping
[23:17] <veebers> alexisb: pong o/
[23:17] <alexisb> are you joining the hangout
[23:17] <alexisb> standup
[23:18] <veebers> alexisb: ah right, yes I can join, but might need to leave early
[23:48] <axw> veebers: any idea what the deal is with http://juju-ci.vapour.ws:8080/job/github-merge-goose/17/console ?
[23:48] <axw> veebers: failing because of a missing dep... do they have to be added to the bot machine manually?
[23:49] <veebers> axw: hmm, wallyworld asked balloons the same thing. Let me have a look in a short moment
[23:49] <axw> veebers: ok, thanks
[23:52] <wallyworld> axw: veebers: i don't want the branch to land yet as I am pretty sure there's still a launchpad.net/gnuflag dep in there which needs to be culled
[23:52] <wallyworld> but we can still fix the other dep issue in preparation
[23:52] <axw> wallyworld: ok. yeah, i did see the bit just above where it grabbed launchpad.net/gnuflag
[23:52] <axw> sounds good
[23:52] <wallyworld> secgreoup-delete-all/main.go
[23:53] <veebers> wallyworld: the jenkins job has launchpad.net/gnuflag declared as a dep, that needs to change?
[23:54] <wallyworld> yes. to the github version
[23:54] <wallyworld> the job error shows the missing repo
[23:54] <veebers> ack
[23:54] <veebers> wallyworld: when you say you don't want it to land yet, do you want it crippled in some way?
[23:55] <wallyworld> no, just don't hit $$merge$$ once job is fixed
[23:55] <wallyworld> once launchpad.net/gnuflag is removed, it won't land anyway :-)
[23:56] <veebers> wallyworld: ack, I'll get the dep updated and you can merge whenever you wish
[23:56] <wallyworld> awesome, tyvm
[23:57] <veebers> wallyworld: nw, re-building now
[23:57] <wallyworld> noooo!
[23:57] <wallyworld> that's what  i didn't want :-)
[23:57] <wallyworld> but it should fail
[23:58] <veebers> wallyworld: carp, I can kill if needed
[23:58] <wallyworld> hopefully
[23:58] <wallyworld> we need to update to make consistent use of gnuflags dep
[23:58] <wallyworld> before landing again
[23:58] <veebers> wallyworld: rats, sorry about that :-\
[23:58] <wallyworld> no worries :-)
[23:58] <veebers> wallyworld: it succeeded :-\
[23:59] <wallyworld> ah, ok, we'll do another fix up branch
[23:59] <redir> thumper: when do you usually start?