[02:20] <redir> thumper: should arm64, s390x, etc skip on azure provider tests?
[02:20] <thumper> NFI
[02:20] <thumper> perhaps it would be prudent to flick axw a quick email and ask
[02:21] <redir> OK.
[02:21] <redir> thanks
[02:21] <redir> is he at the sprint too?
[02:37] <thumper> yep
[02:40] <redir> bbiab
[05:52] <redir> g'nite
[11:11] <voidspace> off to hospital - back soon(ish)
[12:19] <deanman> Is it possible to kill jujud inside a controller and rerunning it?
[12:58] <hoenir> can someone take a look quickly on these ? https://github.com/juju/utils/pull/250 https://github.com/juju/juju/pull/6556
[12:58] <hoenir> it's just a move from juju/cert to juju/utils and import path updates.
[13:05] <hoenir> could someone tell me the exact procedure to move a core pkg to utils? There's something special to do? Or just update the dependencies.tsv and I'm done?
[13:05] <mgz> hoenir: one step that I think is not well written down anywhere
[13:05] <mgz> is probably just announcing it on the dev list
[13:06] <mgz> there are a few projects that actually depend on juju/juju and may need to be updated
[13:07] <perrito666> hoenir: announce it and then you have a shipit from me
[13:07] <perrito666> oh, axw instead has comments
[13:07] <perrito666> :p
[13:13] <hoenir> perrito666, checking now
[13:27] <hoenir> ping axw
[13:27] <axw> hoenir: pong. in a meeting, but what's up?
[13:27] <hoenir> axw, sorry for disturbing.
[13:27] <hoenir> could you take another peek on https://github.com/juju/utils/pull/250 when you have time?
[13:28] <axw> hoenir: sure
[13:31] <axw> hoenir: just one little thing and then it's LGTM
[13:32] <hoenir> axw, working now ! thanks !
[13:47] <hoenir> axw, can I hit the $$merge$$ https://github.com/juju/utils/pull/250 ?
[13:48] <axw> hoenir: yes, go ahead please
[13:48] <axw> not sure if the bot will listen though, I think it has to come from a juju org member
[13:48] <axw> we'll see...
[13:48] <axw> oh you're already added as a member
[13:51] <hoenir> axw, so satisfying to hit the $$merge$$ thing..
[13:51] <hoenir> http://i3.kym-cdn.com/entries/icons/facebook/000/006/077/so_good.jpg
[13:52] <axw> hoenir: :)
[15:15] <rick_h> dooferlad: able to join back to the standup?
[15:16] <dooferlad> rick_h: sorry, not today
[16:12] <mup> Bug #1639170 changed: openstack trusty:liberty deployment fails due to no relations and insufficient peer units <juju-core:Invalid> <juju-quickstart:New> <https://launchpad.net/bugs/1639170>
[16:12] <mup> Bug #1639494 changed: juju model-default no-proxy setting invalid for CIDR (172.16.0.0/16) <juju:New> <https://launchpad.net/bugs/1639494>
[16:12] <mup> Bug #1640113 changed: In LXD machines localdomain not resolvable <juju:New> <https://launchpad.net/bugs/1640113>
[16:42] <mup> Bug #1640079 opened: LXDs doesn't start after a reboot <juju-core:New> <juju (Ubuntu):Triaged> <https://launchpad.net/bugs/1640079>
[16:48] <mup> Bug #1640079 changed: LXDs doesn't start after a reboot <juju-core:New> <juju (Ubuntu):Triaged> <https://launchpad.net/bugs/1640079>
[16:57] <mup> Bug #1640079 opened: LXDs doesn't start after a reboot <juju-core:New> <juju (Ubuntu):Triaged> <https://launchpad.net/bugs/1640079>
[17:48] <redir> soo quiet
[17:53] <mgz> heyup redir :)
[17:54] <redir> mgz \o
[17:57] <redir> mgz: can you confirm https://github.com/juju/juju/pull/6557#issuecomment-259751567
[18:05] <mgz> let me have a look
[18:07] <mgz> redir: so, I agree with you on the selective arch skip maybe
[18:08] <mgz> but there's no real different between the github merge runs and the full revision test runs apart from that arch and many more runs happen
[18:22] <redir> mgz how about https://github.com/juju/juju/pull/6558 ?
[18:24] <mgz> redir: that looks sane to me
[18:25] <mgz> have you qaed it or do you need a pointer?
[18:29] <redir> i'd ned a pointer to qa on a read arm64/ppc64/s390 arch
[18:30] <mgz> okay, sinzui suggests the arm64 machine is the best option
[18:30] <mgz> the details of how to get to it are in the cloud-city repo, see ssh config in jenkins-ssh... config thingy
[18:30] <mgz> use the staging key from cloud city and either the vpn or bounce through with those ssh rules
[18:30] <mgz> poke me if you need help
[18:32] <mgz> you should be able to just ssh in as jenkins user, unpack source and run that unit test (to confirm it fails) then pull or apply your change
[18:38]  * redir looks
[20:50] <redir> phew
[20:50] <redir> QA'd https://github.com/juju/juju/pull/6558 ready for review, PTAL.
[20:50] <redir> Also should https://github.com/juju/juju/issues/6557 be reverted?
[21:09] <mgz> redir: lgtm, and probably, yes, maybe poke anastasia first?
[21:13] <redir> I'll send an email
[21:14] <redir> How do fixes targeted at 2.0 branch make it back to staging?
[21:15] <rick_h> redir: you submit a new PR against develop
[21:15] <mgz> you need to cherrypick that change
[21:15] <rick_h> redir: has to go through review/etc
[21:15] <mgz> and propose again, I'll be happy to stamp
[21:15] <rick_h> redir: the idea is trunk vs 2.0 will skew over time and it's not safe to just cherry-pick, needs to pass tests/etc over
[21:16] <redir> So that means 2.0 is long lived
[21:16] <redir> forever
[21:16] <redir> ?
[21:16] <rick_h> redir: yes, 2.0 is a release branch that lives on until we no longer support 2.0
[21:17] <redir> k thanks. just making sure I understand
[21:17] <redir> and support ends n time after 2.1
[21:25] <alexisb> babbageclunk, ping
[21:25] <babbageclunk> alexisb: pong
[21:25] <alexisb> heya babbageclunk, happy friday to you
[21:25] <alexisb> I wanted to check in on this bug: https://bugs.launchpad.net/juju/+bug/1640282
[21:25] <mup> Bug #1640282: upgrade-juju: manual-provider no matching tools available <ci> <manual-provider> <regression> <upgrade-juju> <juju:Triaged by alexis-bruemmer> <juju 2.0:In Progress by 2-xtian> <https://launchpad.net/bugs/1640282>
[21:25] <babbageclunk> alexisb: thanks!
[21:26] <alexisb> balloons, confirmed today that he can recreate on latest 2.0.2
[21:26] <veebers> sinzui: this is interesting ^^
[21:26] <babbageclunk> alexisb: I've been failing to reproduce it on the jenkins host.
[21:27] <alexisb> veebers, is tere some way we can get babbageclunk on the machine you guys use to test?  balloons did recreate today in front of me by re-running the test
[21:27] <babbageclunk> alexisb: using the binary from the report. I'll try uploading the latest 2.0.2 version and rebuilding.
[21:27] <alexisb> k
[21:28] <veebers> alexisb: yes, sinzui and I are talking about this. we're just OTP but will be in touch shortly
[21:29] <babbageclunk> alexisb: is balloons around? I'm probably doing something wrong, I'm just not clear what.
[21:29] <alexisb> babbageclunk, probably not it is late here
[21:29] <babbageclunk> alexisb: I tried pinging him this morning but I guess he's in the wrong timezone atm
[21:29] <alexisb> yeah :) he had team dinner for QA today
[21:29] <alexisb> all 2 of them
[21:30] <babbageclunk> alexisb: sounds intimate
[21:30] <alexisb> heh
[21:31] <babbageclunk> Hmm - if I want the same version as he used, where should I get the latest 2.0.2. develop?
[21:32] <babbageclunk> alexisb: or staging?
[21:32] <alexisb> tip off teh 2.0 branch
[21:32] <alexisb> not staging
[21:32] <redir> 2.0 branch babbageclunk
[21:32] <babbageclunk> alexisb: oh, duh - he said in the comment on the bug. Ok, thanks - building.
[21:33] <babbageclunk> alexisb: oh, no, just reread his comment - the comment revision is the one that works.
[21:34] <babbageclunk> alexisb: ok, using 2.0 branch
[21:35] <voidspace> perrito666: you still around?
[21:35] <voidspace> babbageclunk: you ever snapped juju?
[21:35] <perrito666> voidspace: sadly, I am
[21:35] <voidspace> perrito666: hah, me too...
[21:35] <voidspace> perrito666: I hear a rumour you've snapped juju before
[21:35] <perrito666> nah, I have snapped at juju
[21:35] <perrito666> common mistake
[21:35] <voidspace> perrito666: is the rumour true, is it easy, have you automated it? (providing a devel version for someone to try)
[21:35] <voidspace> hah
[21:36] <perrito666> voidspace: but honestly I have not but if what you want is to craft a juju snap should be easy
[21:36] <voidspace> voidspace: I'm off tomorrow and I need to provide a binary to a couple of users
[21:36] <voidspace> oops
[21:36] <voidspace> perrito666: ^^
[21:36] <perrito666> voidspace: coopy the snapcraft.yaml file to a folder
[21:37] <perrito666> then run snapcraft on it
[21:37] <perrito666> that will produce a snap of juju for your arch for master I guess
[21:37] <voidspace> "the" snapcraft.yaml...
[21:37] <voidspace> ah, there *is* a snapcraft of master
[21:37] <voidspace> I mean, snapcraft.yaml...
[21:37] <perrito666> voidspace: yes, snapcraft.yaml in our root folder of the repo
[21:38] <perrito666> voidspace: sadly that might give you master
[21:38] <perrito666> which is not what you want
[21:38] <voidspace> perrito666: that uses master from the repo -  I want to use a custom local binary
[21:38] <voidspace> perrito666: yeah, I'll work it out on Monday
[21:38] <voidspace> perrito666: I'll just zip up juju/jujud for today
[21:38] <perrito666> voidspace: there is a yaml attribute
[21:38] <perrito666> that will allow you to specify the checkout
[21:38] <perrito666> and then that will work
[21:39] <voidspace> right
[21:39] <voidspace> still, a task for Monday I think
[21:39] <voidspace> sounds easy enough
[21:39] <voidspace> but I want to get ready for bed :-)
[21:40] <voidspace> No command 'mkdur' found
[21:40] <voidspace> definitely too late to be working...
[21:41] <perrito666> voidspace: just ship the binary and go to sleep
[21:41] <voidspace> perrito666: hey, see you soon
[21:41] <perrito666> voidspace: sleep tight
[21:41] <voidspace> g'night
[21:43] <babbageclunk> voidspace: make sure to change the version, otherwise it could still match the one in the streams.
[21:43] <voidspace> babbageclunk: it's off staging
[21:43] <voidspace> babbageclunk: is the version number still the latest release
[21:44] <voidspace> babbageclunk: hmm... it could be
[21:44] <voidspace> goddammit
[21:44] <voidspace> what if I use develop?
[21:44] <babbageclunk> voidspace: not sure - best to check, otherwise you'll have a couple of roundtrips sorting it out.
[21:44] <babbageclunk> voidspace: just bump it locally before building and zipping your binaries.
[21:45] <voidspace> babbageclunk: building develop just to see
[21:45] <voidspace> develop should *always* have a bumped number, it should be part of the release process
[21:45] <babbageclunk> voidspace: develop should work though.
[21:45] <voidspace> about to find out
[21:45] <voidspace> babbageclunk: morning
[21:45] <voidspace> babbageclunk: you read my article yet?
[21:45] <babbageclunk> voidspace: evening!
[21:46] <voidspace> babbageclunk: yep, develop is good
[21:46] <babbageclunk> voidspace: I read the novel in ntoll's comments, haven't had a chance to comment yet
[21:46] <voidspace> babbageclunk: I turned it into an article, doesn't look so big then
[21:46] <voidspace> babbageclunk: interested in your comments
[21:46] <babbageclunk> voidspace: pretty fun - sounds like you're drifting towards excommunication though
[21:47] <voidspace> babbageclunk: it's only mental agility, but I like it
[21:47] <voidspace> babbageclunk: hah, I've been headed that way for years
[21:47] <voidspace> babbageclunk: the trouble is, they actually like me, so they're not keen to excommunicate me
[21:48] <babbageclunk> nice
[21:50] <voidspace> babbageclunk: they aren't keen to make me an official "leader" either (which is not even really a big deal) - I unofficially am, so they tolerate me in the leaders meetings, but won't make it official
[21:50] <voidspace> babbageclunk: truth be told, they're mostly a bit scared of me
[21:50] <babbageclunk> voidspace: aren't we all!
[21:50] <voidspace> babbageclunk: are you? ;-)
[21:51] <voidspace> I think that's fairly reasonable if you are...
[21:51] <voidspace> did you see the zombie day photos?
[21:53] <babbageclunk> alexisb: still no luck. My understanding of the test is that it bootstraps with the old juju binary it finds on the path, so really the version of the binary I'm running it with is irrelevant - it's the one that's on the path interacting with the stream. Do you know what versions he had on the path and which stream he ran it with?
[21:54] <babbageclunk> voidspace: only a bit, now that I'm on the other side of the world.
[21:54] <redir> mgz: if you're still about: https://github.com/juju/juju/pull/6560
[21:55] <babbageclunk> voidspace: yeah, looked good!
[21:55] <voidspace> babbageclunk: such fun!
[21:55] <voidspace> babbageclunk: moments of panic and terror
[21:55] <voidspace> very well done
[21:56] <voidspace> right, comments left and binary uploaded
[21:56] <voidspace> g'night all
[21:56] <voidspace> o/
[21:56] <babbageclunk> voidspace: \o
[21:58] <redir> voidspace: what article?
[21:58] <redir> or g'nite
[21:58] <voidspace> redir: :-)
[21:58] <voidspace> redir: http://www.michaelfoord.co.uk/2016/11/an-evolutionary-spirituality-goodness.html
[21:59] <voidspace> redir: reaching for synthethis of science, religion, psychology and philosophy
[21:59] <voidspace> redir: utterly un-work-related and merely my fetid musings
[21:59] <redir> ah ha, was looking at voidspace.uk...
[21:59] <mgz> redir: lgtm
[21:59] <redir> mgz: tx
[21:59] <voidspace> redir: I haven't done anything there for a very long time
[22:00] <voidspace> redir: I probably won't - as I'm not doing Python if I start a new blog I'll put it somewhere else
[22:00] <voidspace> redir: anything technical I do post, which is rare at the moment (shouldn't be) I tend to put on google+
[22:00] <voidspace> redir: although I'm moderately active on twitter too
[22:00] <redir> voidspace: I noticed
[22:01] <redir> I don't do much twitter.
[22:01] <voidspace> I enjoy twitter and facebook, I keep in touch with a lot of friends through them
[22:01] <voidspace> although some of my friends are too posh for facebook it seems
[22:01] <voidspace> *coff* katco *coff*
[22:02] <katco> lol
[22:02] <voidspace> :-)
[22:02] <katco> not posh, just feel it's a waste of time, and an energy drain, and an invasion of privacy
[22:02] <voidspace> I enjoy it :-)
[22:03] <voidspace> anyway
[22:03] <katco> at some point i got very tired of reading crappy political memes
[22:03] <voidspace> ah yeah, it's the psyche of humanity on full display
[22:03] <katco> at least my peers are on twitter
[22:03] <voidspace> full of crap and beauty in about equal measure
[22:03] <voidspace> staunch filters
[22:03] <redir> I don't do much facebook either
[22:03] <voidspace> I'm really off
[22:03] <voidspace> g'night all
[22:03] <voidspace> o/
[22:03] <katco> tc voidspace
[22:03] <voidspace> see you again on monday
[22:04] <redir> \o
[22:05] <perrito666> facebook, in my case, has the exact same contents hotmail had in the early 2000s when my mom got hold of mail
[22:05] <redir> perrito666: heh
[22:05] <perrito666> basically fake articles, inspirational power point like presentations, etc
[22:05] <perrito666> a bit low on cats though, which is odd
[22:05] <katco> lol
[22:06] <katco> i actually am on facebook. i've just enacted a big-data deep-ai filter to give me the truly important news. she is my wife
[22:06] <perrito666> katco: lol
[22:07] <redir> awesome. I think I might be that filter for M.
[22:07] <perrito666> katco: I usually get the truly important stuff from facebook, basically when my internet is down and I get the blank page
[22:08] <perrito666> I do laugh at people from high school treating everyone as sheeple while quoting articles from media of the journalistic quality of the onion
[22:10] <redir> Whelp, I guess I need to start getting on twitter to find out what our president elect thought about during midnight toilet runs.