[00:02] <hatch> kewl single inspector stuff is done with a config factory
[12:41] <gary_poster> hey luca.  when you have a moment, I'd love to have a hangout with you on the scrolling behavior.  it sounds like you have something in mind that I will like a lot, but I just don't understand it yet.
[12:43] <luca> gary_poster: sure, I'll hopefully be free in a bit, trying to get the service blocks done
[12:43] <gary_poster> cool thanks luca
[12:59] <gary_poster> arosales, we still need to actually release the GUI so the contest's export instructions work.  Please let me know ASAP when you all have verified that it works as you need, so we can start the qa for making a release
[13:43] <rick_h> gary_poster: it looks like the updated staging isn't updating the css. I'm not getting my changes for the related charms stuff on there atm but it shows up in trunk and works locally.
[13:44] <gary_poster> rick_h, hm, ok, I'll dig for a sec
[13:48] <gary_poster> rick_h, poking at things and not sure what to look at to see if I did anything. :-) what do I check?
[13:50] <rick_h> gary_poster: so a manual force would be to rm build-shared/juju-ui/templates.js && make build-shared/juju-ui/templates.js
[13:50] <luca> gary_poster: did you want to discuss scroll bars?
[13:50] <gary_poster> rick_h, but what do I need to look on uistage at verify that the update happened?
[13:51] <gary_poster> luca, on call for the next 39 min.  Will you be available then?
[13:51] <luca> gary_poster: sure
[13:51] <gary_poster> thanks
[13:52] <rick_h> gary_poster: so the trouble. is that the juju-gui.css is out of date. I guess we can verify it's timestamp vs the lib/views/browser/*.less
[13:54] <rick_h> gary_poster: there should be a badge_approved_17.png in that combined css file coming from the lib/views/browser/charm-token.less file
[13:55] <rick_h> for a quick grep-able bit to look for
[13:55] <gary_poster> rick_h, ran out of time just forced.  fixed on uistage?
[13:55] <hatch> morning
[13:56] <rick_h> gary_poster: yes, thanks
[13:56] <gary_poster> cool welcome
[13:56] <rick_h> morning hatch
[14:10] <hatch> gary_poster: re your dec email - none are showing up for me in CA - should I do it or is it broken? :)
[14:11] <gary_poster> hatch, we have to add them ourselves in CA
[14:11] <hatch> ohh ok, I misunderstood
[14:15] <hatch> annnnd done
[14:16] <teknico> you can review a 4K lines diff in about 30 seconds! great opportunity, today only, don't miss it! https://codereview.appspot.com/10746043
[14:17] <hatch> teknico: can we really trust you? :)
[14:17] <hatch> maybe you put h4x0r code in there
[14:17] <hatch> *shifty eyes*
[14:17] <teknico> hatch: thaaat's the question, isn't it? ;-)
[14:18] <teknico> hatch: you have the tools to catch that, but it will turn the review into a 90 sec one ;-)
[14:19] <hatch> haha
[14:24] <teknico> hatch: thanks
[14:40] <arosales> gary_poster, I have tested a gui only / gui-wordpress-mysql / gui-wordpress-mysql-mongo-ceph
[14:40] <arosales> on aws
[14:41] <arosales> the yamls look correct, but I haven't yet been able to re-import with deployer just yet
[14:41] <arosales> gary_poster, I'll check on HP cloud this morning, and check the status of the deployer with hazmat and then sync up with your on our 1x1.
[14:42] <sinzui> orangesquad, I want to have another 15 minute chat in 20 minutes. We can reuse our standup hangout to discuss the big picture for July and maybe August
[14:42] <gary_poster> arosales, ok cool.  ideally I'd wait till we have that confirmation before we release, but I may start optimistically before then so we have enough qa time before eod.
[14:43] <gary_poster> luca, guichat?
[14:43] <gary_poster> hopefully fast :-)
[14:43] <arosales> gary_poster, agreed, from my testing it is looking good
[14:43] <gary_poster> great thanks arosales
[14:43] <luca> gary_poster: sure, let me grab a room
[14:43] <arosales> thanks for delivering that in a release no less :-)
[14:43] <gary_poster> cool thanks
[14:44] <gary_poster> arosales glad to help! thanks for promoting gui
[14:44] <arosales> literally its our pleasure
[14:44] <gary_poster> :-)
[14:48] <hatch> gary_poster: could you do me a favour and check out my branch to see if you can actually get the error you brought up?
[14:48] <hatch> I thought it wouldn't work either
[14:48] <hatch> but I can't make it break
[14:48] <gary_poster> hatch on call will try
[14:48] <gary_poster> later
[14:49] <hatch> thanks - I just want to be sure I'm not missing something obvious
[14:50] <gary_poster> jujugui call in 10, kanban now
[14:51] <arosales> hazmat, on that note is there a branch I can test the deployer import on charm store charms?
[14:52] <hazmat> arosales, ~hazmat/juju-deployer/python-env/
[14:52] <arosales> hazmat, thanks.
[14:53] <hatch> jujugui creating relations is broken in trunk
[14:54] <Makyo> hatch, works for me..
[14:54] <hatch> really?
[14:54] <Makyo> Yes.
[14:54] <hatch> hmm
[14:54]  * hatch clears caches
[14:55] <hatch> poo
[14:55] <hatch> looks like it's my branch and bad cache
[14:57] <hatch> darn and my branch doesn't appear to have any reason that would break
[14:59] <gary_poster> jujugui call now
[14:59] <gary_poster> ish
[15:02] <sinzui> rick_h, jcsackett, adeuring, https://plus.google.com/hangouts/_/cf491220dfb7736cee2876baf29110eeb52f5997
[15:23] <Makyo> So.
[15:23] <Makyo> Good thing I can hear everyone.
[15:23] <Makyo> closer to the new style, gary_poster, just minus some styling and checkboxes.  i.e. interaction.
[15:45] <rick_h> orangesquad: heads up that they're working on the power around here after the storms last night. Things are flickering and lost it twice now. I might come/go a bit
[15:46] <jcsackett> rick_h: ack.
[15:52] <hatch> rick_h: above ground power?
[15:53] <rick_h> hatch: well when I got back from the vet all the lights were out with trucks around the poles and power's gone out and hit the UPS twice so far.
[15:53] <rick_h> hatch: so yea...I guess it's above ground
[15:53] <rick_h> or it's the block's below ground, no idea.
[15:54] <hatch> ahh - around here the power is under ground in residential areas except where there is the transformers
[15:54] <hatch> usually it's those things that go in storms here
[15:54] <hatch> hah
[15:54] <hatch> ka------boooooooom
[15:54] <rick_h> hatch: yea, I mean they're clearly working on local power. We kept it through the storm, but a block away didn't. So I'm not sure what's up.
[15:56] <hatch> that video looked like it was a good storm too :)
[15:57] <rick_h> yea, I was surprised/happy we kept power tbh
[16:01] <jcsackett> rick_h: got a sec to hat on hangout?
[16:01] <jcsackett> s/hat/chat/
[16:02] <rick_h> jcsackett: sure thing
[16:07] <jcsackett> gary_poster: any chance we can get the templates rebuilt/recompiled on staging? they have not, and so despite the flag being gone the share button will not render.
[16:07] <jcsackett> which causes other fun problems for the sharing widget, as you might imagine. :-P
[16:07] <gary_poster> jcsackett, tell me what command to run and I will do so.  big extra points for figuring out what needs to be fixed in Makefile.  I'd look but other priorities atm
[16:07] <rick_h> jcsackett: I'd ping bac but I don't think he's around today. I wonder if someone else has access to the staging setup?
[16:08] <rick_h> gary_poster: that same command you ran for me needs running. What command is the staging server running on a new version update?
[16:08] <rick_h> gary_poster: rm build-shared/juju-ui/templates.js && make build-shared/juju-ui/templates.js
[16:09] <gary_poster> rick_h, jcsackett done
[16:09] <gary_poster> rick_h, make build-prod
[16:10] <hatch> oop another make error....time to switch to grunt /troll
[16:10] <rick_h> hatch: well I'm guessing some command wasn't moved to the new location when staging was split up.
[16:10] <rick_h> hatch: as it was working well on the old url for a long while
[16:10] <hatch> nope this is clearly a make error
[16:10] <rick_h> hatch: shush
[16:10] <hatch> haha
[16:11] <jcsackett> rick_h: huh, it's not fixed.
[16:11] <rick_h> before you get assigned to fix it
[16:11] <rick_h> jcsackett: yea, looking
[16:11] <hatch> so my insurance company lets us renew our insurance online.....but we have to go into the branch to set up an account :/
[16:11] <hatch> convenience gain.... 0
[16:12] <rick_h> gary_poster: any chance the command was on the wrong checkout?
[16:12] <rick_h> jcsackett: can you check if the css file has all the rules in your branch that was deployed out? http://uistage.jujucharms.com:8086/juju-ui/assets/juju-gui.css
[16:12] <rick_h> jcsackett: I'm guessing something is missing since the share widget has the li dots on it
[16:12] <jcsackett> rick_h: i can, but there aren't rules to make the share button not render.
[16:12] <gary_poster> rick_h, http://pastebin.ubuntu.com/5808236/
[16:12] <rick_h> jcsackett: right, but just checking if the file's up to date or not.
[16:13] <rick_h> gary_poster: thanks, will do a test here with that and see if there's a build step missing.
[16:13] <hatch> gary_poster: I'm going to switch to the settings page - so just let me know whwnever you have a moment to do that QA, no rush
[16:13] <gary_poster> thanks rick_h
[16:13] <gary_poster> hatch if someone else verifies for I am AOK with it
[16:13] <jcsackett> rick_h: looks like it.
[16:14] <rick_h> jcsackett: looks like it's up to date? or out of date?
[16:14] <jcsackett> that is to say, looks like all the rules are there.
[16:14] <rick_h> e.g. so the dots should be there?
[16:14]  * rick_h is confused
[16:15] <jcsackett> they get cut off by sizing, not decoration.
[16:15] <jcsackett> rick_h: and again, no css rules were changed in this branch, so even an out of date css file could have all the rules.
[16:16] <hatch> Makyo: bcsaller either of you guys have a moment for a quick QA?
[16:16] <hatch> https://codereview.appspot.com/10724043/
[16:21] <gary_poster> luca, try again in guichat? :-)
[16:21] <gary_poster> frankban, i privmsg'd you, in case it didn't ping
[16:25] <jcsackett> rick_h: what did you do? it's working.
[16:26] <rick_h> jcsackett: nothing atm. I don't have access to the staging server. I do see some issues though. Subapp tempaltes aren't part of the makefile's template list.
[16:26]  * jcsackett wonders if there's a delay between templates rebuilding us getting them, even with cache clearing...
[16:26] <rick_h> jcsackett: and not sure if there's a cache on the server side?
[16:26] <jcsackett> rick_h: there's almost certainly a server side cache, come to think of it.
[16:27] <jcsackett> rick_h: probably worth filing a bug about the subapp templates in makefile's template list.
[16:27] <rick_h> jcsackett: trying to see if the css files are keyed in the makefile as well since ours are in a subdir
[16:27] <rick_h> jcsackett: yea, trying to finish tracking down bits and maybe I can get my find-fu on to fix it. /me is spoiled by zsh **/*
[16:28] <rick_h> I never use find any more
[16:29] <rick_h> jcsackett: so there's en ETAG on the js file, but that sohuld have changed/updated when the source was updated.
[16:29] <teknico> why use find when you can F9-c-f? ;-)
[16:29] <rick_h> teknico: huh?
[16:30] <teknico> rick_h: no midnight commander, eh? :-)
[16:30] <rick_h> teknico: heh, no. ls app/**/*.(handlebars|partial)
[16:30] <Makyo> I always forget about midnight commander until I typo `mv`
[16:30] <rick_h> teknico: and I don't think out Makefile will be able to run mc
[16:31] <rick_h> /out/our
[16:31] <teknico> oh, ok, missed the context
[16:32] <rick_h> and man I can't wait until we get to scss and can ditch this treating the css files as a template build step. Just call scss on the files in the makefile themselves.
[16:32] <teknico> and I'm also going to miss you all for ten days: wish me a happy Europython! :-)
[16:32] <rick_h> teknico: jealous!
[16:33] <rick_h> jcsackett: well now that it's showing make sure to let jcastro see the sexy he's been wanting :)
[16:33] <jcastro> yeah!
[16:34] <jcastro> I just realized with the oscon reveal that that means I shouldn't take videos of deploying stuff with the gui?
[16:34] <rick_h> jcastro: I'd say not :/
[16:34] <rick_h> jcastro: http://uistage.jujucharms.com:8086/precise/ceph-11/ for your enjoyment
[16:35] <jcastro> rick_h: which part is different today?
[16:35] <rick_h> jcastro: share button
[16:36] <jcastro> I don't see it
[16:36] <rick_h> jcastro: next to add?
[16:36] <rick_h> jcastro: clear cache maybe?
[16:36] <jcastro> ah
[16:36] <jcastro> not in FFx
[16:36] <jcastro> weird
[16:37] <rick_h> jcastro: hmm, in FF here. Bet it's a cache issue
[16:37] <jcastro> k
[16:38] <rick_h> jcastro: ok, so the template list is incomplete and there's no actual make target on the css files so it doesn't rebuild when that's all that changes.
[16:38] <rick_h> oops, jcsackett ^
[16:43] <jcastro> gary_poster: oh hey, that Discourse charm gui bug, I'd like to demo it at oscon
[16:44] <jcastro> not a hard requirement, but dang it would be awesome
[16:45] <gary_poster> jcastro, I figured, but we haven't gotten to it.  probably no time before we have to make a release for you.  will see if I can squeeze it in.
[16:45] <jcastro> man, this drag and drop
[16:45] <jcastro> I am just sitting here dragging shit into the ui
[16:45] <jcastro> for no reason other than just doing it
[16:46] <hatch> lol
[16:46] <hatch> out of curiosity what's the discource gui bug?
[16:46] <jcastro> it doesn't deploy from ~marcoceppi/blah blah
[16:46] <hatch> ohh the local charm thing
[16:47] <jcastro> no I mean from cs:~marcoceppi blah blah
[16:47] <jcastro> it does work fine in the uistage though. ;)
[16:47] <jcastro> cheatin' uistage!
[16:47] <hatch> haha yup
[16:48] <hatch> you could demo on sandbox ;)
[16:48] <hatch> "look how fast servers spin up with juju"
[16:48] <hatch> haha
[16:48] <jcastro> hah yeah
[17:06] <sinzui> rick_h, jcsackett, do both of you have time to join my in the stand-up hangout?
[17:06] <rick_h> sinzui: rgr
[17:08] <gary_poster> jcastro, oh, you want discourse bug fixed for *OSCON*.  Yes, definitely plan on it.  I read it as fixed for Monday.
[17:09] <jcastro> oh ok, thanks!
[17:14] <benji> gary_poster: [I was lunching/relocating.] Sure, I'll get those entered before my EOD.
[17:14] <gary_poster> benji, cool thanks.  we need to countersign/countercountersign before then too.
[17:14] <jcsackett> sinzui: sure.
[17:15] <benji> gary_poster: oh, in that case I'll do it right now
[17:15] <gary_poster> cool
[17:17] <benji> gary_poster: is the target date 2014-04-01?
[17:18] <gary_poster> benji yes
[17:18] <benji> k
[17:20] <hatch> bcsaller: do we know what charm data is provided by default by the delta?
[17:22] <bcsaller> hatch: I *think* its just the reference id by default in the service data, I'd have to check
[17:23] <bcsaller> hatch: I think we use that Id to then go to one of the charm store apis, where that is currently the old one
[17:24] <hatch> alright so when we get a delta to create a new service we should go pull the charm data, then show the service in the UI
[17:24] <hatch> then we can get rid of the charm.loaded flag
[17:25] <benji> gary_poster: https://www.youtube.com/watch?feature=player_detailpage&v=ReJ3RltihME#t=309s
[17:25] <benji> I'm ready for simultanious key turn.
[17:26] <gary_poster> benji, lol cool
[17:27] <benji> I'm both proud and ashamed that it only took me 30 seconds from thinking of that clip to finding it.
[17:27] <gary_poster> heh
[17:27] <gary_poster> benji, I don't have it.  I think allhands is having issues.  I'll send an email to P&C about it
[17:27] <benji> :/
[17:28] <gary_poster> thank you for entering
[17:28] <gary_poster> yeah
[17:28] <gary_poster> four people have issues so far
[17:28] <benji> "Objective Sheet Submitted"
[17:45]  * hatch holds out hand for donations to buy faster machine to run lbox_check tests
[17:46] <hatch> rick_h: I hear you just got a new machine that you aren't using :P
[17:49] <rick_h> hatch: hah, I use it to run my lbox_check :P
[17:49] <hatch> lol
[17:49] <hatch> maybe I can push my changes to your box
[17:49] <hatch> lol
[17:50] <rick_h> the rick_h lbox service...wonder if I could turn that into a startup
[17:50] <hatch> lol
[17:51] <hatch> I have to admit I've heard worse startup ideas
[17:57] <hatch> bcsaller: mind taking a peek at the new code
[17:57] <hatch> the charm.loaded needs to stay - at least for a follow-up to fix the charm system later
[18:04] <rick_h> jujugui can I get a couple of sanity checks on the small makefile change please. QA instructions included. https://codereview.appspot.com/10756043
[18:04]  * benji looks.
[18:21] <hatch> gary_poster: if you get a moment mind taking a look at https://codereview.appspot.com/10724043/ for a followup LGTM
[18:22] <gary_poster> LGTM hatch
[18:23] <hatch> thanks!
[18:29]  * rick_h fears his 3 lines broken benji's computer
[18:29] <rick_h> broke, bah. come on EOD
[18:29] <benji> heh
[18:29] <benji> I got distracted by trying to get my tests to pass.
[18:29] <rick_h> benji: ah ok. I feared things were going bad.
[18:30] <benji> rick_h: nope, but the review is done with QA; I had a suggestion on the regex.
[18:31] <rick_h> benji: awesome. thanks for the suggestion.
[18:31] <benji> my pleasure
[18:33] <rick_h> gary_poster: landing the makefile update. Hopefully this fixes the issues we've seen today. Let me know if anyone runs across any others like it. /cc jcsackett
[18:33] <gary_poster> yay thanks rick_h
[18:40] <Makyo> bcsaller, or hatch, I'm having a hard time binding an event in a viewlet.  Either of you have time in ~5min for a quick chat?
[18:41] <bcsaller> sure
[18:41] <bcsaller> Makyo: in chat now
[18:50] <hatch> Makyo: in guichat
[18:50] <hatch> come on by
[18:51] <Makyo> hatch, just chatted with bcsaller, sorry.  Thanks though.
[18:51] <hatch> oh heh alright np
[18:52] <Makyo> Was defining the event on 'events', needed to be 'viewletEvents'
[19:09] <hatch> ahh
[19:09]  * hatch remembers now why he doesn't do CSS
[19:20] <gary_poster> sinzui, hi.  one more topic.  MS asked that uistage.ubuntu.com become comingsoon.jujucharms.com when OSCON starts.  May I ask you to add that to your IS coordination list?
[19:20] <gary_poster> sinzui, ideally uistage would redirect, but if they simply point to same machine that is OK
[19:20] <gary_poster> I suppose we could handle the redirect ourselves if they point to the same machine
[19:21] <sinzui> I think I understand
[19:22] <sinzui> gary_poster, anyone going to uistage.ubuntu.com -> comingsoon.jujucharms.com...and the reveal one or both domains become jujucharms.com?
[19:23] <hatch> do we have a card/ticket for removing all of the old unused css after the switchover?
[19:35] <gary_poster> sinzui, anyone going to jujucharms.com goes to stable production GUI.  anyone going to comingsoon.jujucharms.com sees equivalent of current uistage.jujucharms.com:8086.  (this one is different from what I said before) finally, anyone going to uistage.jujucharms.com is redirected to jujucharms.com (the stable version)
[19:35] <gary_poster> sinzui, we could have comingsoon turned on now
[19:36] <gary_poster> we could also control the uistage redirect if desired but probably better if dns points to production gui...we can implement a redirect later so that uistage actually changes the url
[19:38] <gary_poster> hatch no.  I'll make one.
[19:39] <sinzui> gary_poster, so as I am asking for the current stable charm and the stable code to be deployed to what will be jujucharmscom. If webops and I see no issues, we should do the DNS change now?
[19:40] <gary_poster> sinzui, +1 on comingsoon DNS change now.  -1 on the uistage DNS change now, but we can do that at or after OSCON
[19:40] <sinzui> okay. Thank you for clarifying.
[19:40] <gary_poster> thank you!
[19:42] <gary_poster> hey benji, I wanna make a release.  I want your branch in it.  what's the timeline?
[19:42] <hatch> gary_poster: thanks
[19:42] <gary_poster> thank you for mentioning it hatch
[19:42] <benji> gary_poster: I just submitted it for review; I'm looking over it before soliciting reviews
[19:42] <benji> s/just submitted/am submitting/
[19:42] <gary_poster> ok
[19:43] <gary_poster> cool
[19:43] <gary_poster> let's try to speed it through if we see no probs
[19:43] <benji> sounds good
[19:44] <gary_poster> Makyo, did frankban hand off to you for his constraints work?
[19:44] <Makyo> gary_poster, yes.  Still working on getting modifyUnits plugged in, though.  I have events properly firing now, at least.  I have his code already branched, though.
[19:44] <sinzui> orangesquad, gary_poster. The sun was just swallowed by a storm and I cannot hear the music over the thunder. I might loose power/net if this new house problems.
[19:45] <gary_poster> sinzui, ack.
[19:45] <gary_poster> cool Makyo thanks
[19:49] <benji> jujugui: I need two quick reviews so this branch can go into the pending release: https://codereview.appspot.com/10763043
[19:49] <Makyo> benji, on it.
[19:49] <benji> thanks
[19:49] <hatch> benji: i'll take one
[19:49] <benji> thanks hatch
[19:49] <hatch> needs QA?
[19:52] <hatch> gary_poster: http://www.sublimetext.com/blog/articles/sublime-text-3-public-beta
[19:53] <gary_poster> hatch QA yes
[19:53] <gary_poster> hatch sublime, already installed but haven't done much with it yet
[19:55] <hatch> benji: can I request that you add this functionality to the new deploy method in trunk?
[19:55] <benji> hatch: you can request anything your heart desires
[19:55] <hatch> well...I am asking becuase if I ask for that I won't lgtm it
[19:55] <hatch> :)
[19:56] <hatch> so depends if you want the lgtm or not haha
[19:56] <hatch> or follow-up
[19:56] <benji> I think gary_poster will want it in a follow-up.
[19:56]  * gary_poster vites for follow-up :-)
[19:56] <gary_poster> votes
[19:56] <hatch> alrighty then :)
[19:56] <Makyo> benji, LGTM.
[19:57] <Makyo> Closed Reitveld, will LGTM through there in a sec.
[20:00] <gary_poster> Oh btw Makyo did you look at those svgs from luca?
[20:00] <Makyo> gary_poster, Oh!  Yeah!  They should be fine, I think.  We'll have to re-jigger some of the margins and such, but that should be relatively easy, I think.  It helps that they don't have drop-shadows.
[20:00] <Makyo> Sorry, will email.
[20:01] <gary_poster> cool Makyo.  May I make a card and assign you?
[20:01] <hatch> lol re-jigger
[20:01] <Makyo> Yep!
[20:01] <gary_poster> cool Makyo  thanks
[20:01] <hatch> what show is that from
[20:01] <gary_poster> just a word for me
[20:01] <Makyo> It's kind of a south/south-central US idiom.  Friend from CA laughed at it last time I used it.
[20:03] <gary_poster> etymology http://www.etymonline.com/index.php?term=jigger<shrug>
[20:03] <gary_poster> http://www.etymonline.com/index.php?term=jigger that is
[20:03] <hatch> languages!
[20:04] <hatch> I'm gona speak in clicks from now on
[20:04] <gary_poster> _The Gods Must Be Crazy_
[20:04] <gary_poster> don't remember the movie but remember liking it
[20:05] <gary_poster> (he spoke in clicks)
[20:05] <hatch> oh haha
[20:06] <hatch> I was wondering where that was going
[20:06] <gary_poster> :-)
[20:06] <gary_poster> bushman discovers coca cola bottle; hilarity ensues
[20:06] <benji> the story of my life
[20:06] <gary_poster> lol
[20:09] <hatch> benji: fyi there is a conflict with trunk
[20:09] <hatch> in the less file
[20:09]  * benji looks
[20:10] <benji> hatch: fixed (pushing merged branch now)
[20:10] <hatch> yeah it's a super small thing
[20:14] <hatch> benji: lgtm'd I included the issues caused by the missing deploy method in the reply
[20:14] <gary_poster> benji, I need to be out of here in 20 minutes, fwiw.  I can do the release later this evening though.  hatch, are those qa issues?
[20:14]  * benji reads.
[20:14] <hatch> gary_poster: they are - but can only be fixed by the follow-up branch
[20:15] <gary_poster> :-(
[20:15] <hatch> unless we delay this branch to add those features
[20:15] <hatch> that feature*
[20:15] <gary_poster> ack
[20:17] <benji> hatch: I haven't QAed the branch after merging with trunk, are you saying that there is a new deploy method that I should be calling instead?
[20:17] <hatch> benji: under the flag yes
[20:17] <benji> ah
[20:18] <hatch> guichat about it?
[20:18] <gary_poster> hatch, this breaks the ghost inspector, but is fine outside of the feature flag?  or, it doesn't break anything under the feature flag but doesn't work either?
[20:18] <hatch> those qa issues were under the feature flag
[20:18] <hatch> sorry I wasn't clear there
[20:19] <gary_poster> gotcha
[20:19] <gary_poster> and it doesn't break anything pre-existing
[20:19] <gary_poster> but we need those changes in order to work with the inspector, right?
[20:19] <gary_poster> so fine to make a release with this
[20:19] <hatch> work with the inspector from deploying by dragging
[20:19] <hatch> yes a release is fine
[20:19] <gary_poster> right
[20:19] <gary_poster> cool
[20:19] <gary_poster> thanks
[20:19] <hatch> deploy by click still works with the flag
[20:20] <gary_poster> cool
[20:20] <gary_poster> benji, you good on this?  You can make a card and ask someone else to do it if you like :-)
[20:20] <benji> I'm cool doing a follow-up branch.
[20:21] <gary_poster> cool thanks benji.
[20:21]  * gary_poster brb
[20:21] <benji> I'll also address the review suggstions there, since we are in a rush.
[20:21] <benji> if that ^^^ is ok with hatch
[20:21] <hatch> benji: yep for sure - my comments were super trivial
[20:22] <benji> cool
[20:22]  * benji lands.
[20:22] <hatch> before the release is rolled someone should probably do a qa on it :)
[20:23] <gary_poster> hatch, was going to do that, but will be packing for trip tonight, so if you Makyo or bcsaller were willing to do the pre-release qa that would be much appreciated
[20:23] <gary_poster> if not I will do it
[20:24] <gary_poster> if you did the release that would be cool too! :-) the docs are pretty good I think
[20:24] <hatch> ok don't worry about it, one of us will be able to
[20:24] <hatch> I've never done it :)
[20:24] <hatch> not sure I want to go alone first time on a friday night haa
[20:24] <gary_poster> ok thank you.  shoot me a mail telling me how far it got
[20:24] <gary_poster> yeah friday is not the best :-/
[20:25] <gary_poster> ugh the resize is broken on the internal pages again :-/
[20:25] <gary_poster> fixed at least once before
[20:25] <gary_poster> if not twice
[20:25] <gary_poster> forgot what the deal was
[20:28] <gary_poster> darn.  I was going to talk to jeff and rick about reusing charm widget
[20:28] <gary_poster> hatch, guichat for 5?
[20:28] <gary_poster> if busy no problem
[20:29] <hatch> yup
[20:29] <gary_poster> thx
[20:35]  * benji waits for lbox sumbit to finish
[20:40] <rick_h> gary_poster: whats up?
[20:40] <gary_poster> rick, hey.  hatch will share evil plan.  must run. :-) thanks
[20:40] <rick_h> k
[20:40]  * gary_poster runs
[20:40] <hatch> rick_h: guichat plz
[20:41] <rick_h> hatch: can you invite me? on the tablet
[20:41] <hatch> sure one sec
[20:44]  * benji suspects lbox has frozen.
[21:11] <benji> branch landed, follow-up branch began, bug filed: time for EOW
[21:12] <benji> Have a good weekend all.
[21:36] <hatch> benji: you broke the build lol
[21:42] <benji>
[21:42] <benji> hatch: I'm looking at the test failure
[21:42] <hatch> benji: oh ok I just started on it too
[21:42] <benji> I wonder how that happened.
[21:42] <hatch> heh thought you went already
[21:42] <hatch> it only fails in FF
[21:42] <hatch> (repeated locally)
[21:43] <benji> hatch: maybe I should leave you to it.  Do you prefer one over the other?
[21:44] <hatch> I don't really know what the purpose of these asserts are
[21:44] <hatch> why does it 'need' to be 0
[21:53] <hatch> benji: I think I have fixed it
[21:53] <benji> cool!
[21:54] <benji> I am more and more of the opinion that an assert without an explanitory comment is a bug.
[21:54] <hatch> yeah sometimes it's just not very clear as to why the assert is necessary
[21:56] <hatch> ok yup fixed
[21:56] <hatch> proposing
[21:57] <hatch> benji: if you wouldn't mind sticking around for a bit to LGTM this for me so I can at least have a single reviewer :D
[21:58] <benji> hatch: sure
[21:58] <hatch> thanks I'll ping when lbox completes
[22:04] <hatch> jujugui could I get some reviews plz https://codereview.appspot.com/10769043
[22:04] <benji> hatch: looking
[22:04] <hatch> thanks
[22:04] <benji> hatch: oh, that's much better than what I had
[22:05] <benji> hatch: review done
[22:05] <hatch> haha well it's the same idea, just removed the cruft :)
[22:05] <hatch> thanks, landing
[22:06] <hatch> lol nice review
[22:07] <hatch> ok once that lands I'll QA and try and not screw up the release ;)
[22:09] <benji> the release docs are quite good
[22:09] <hatch> yeah they look like it
[22:09] <benji> ok, I really have to go now; bye!
[22:09] <hatch> cya :D
[22:23] <arosales> hopefully its just me but are other folks seeing the uistage load
[22:23] <arosales> http://uistage.jujucharms.com:8080/
[22:23] <arosales> canvas and charm store nav is not coming up for me.
[22:24] <hatch> checking
[22:24] <hatch> no store, canvas though
[22:24] <hatch> but the store isn't at that url
[22:24] <hatch> did you want this one? http://uistage.jujucharms.com:8086/
[22:25] <arosales> ah yes, that works better
[22:25]  * arosales was just looking for a working version.
[22:25] <hatch> :) the 8086 is the sekrit version ;)
[22:37] <arosales> hatch, thanks
[22:37] <arosales> pwd
[22:37] <hatch> no problem
[22:59] <hatch> jujugui - is the DD supposed to work on rapi? I don't get the (+) on the cursor and it doesn't drop
[22:59] <Makyo> DD?
[23:00] <hatch> drag and drop
[23:00] <Makyo> Oh,.
[23:00] <hatch> I'm trying to do the release but I can't release it if that's supposed to work heh
[23:01] <bcsaller> Thats very odd as thats just a UI specific way to call deploy, no?
[23:01] <hatch> that's what I thought
[23:01] <hatch> I'm investigating now
[23:02] <hatch> makedragstart handler is never called
[23:05] <hatch> hmm
[23:05] <hatch> odd
[23:05] <hatch> dragstart is fired but it's callback isn't called
[23:05] <hatch> that don't make no sense mang
[23:05] <hatch> oh
[23:06] <hatch> nope that's not it
[23:06] <hatch> heh
[23:12] <Makyo> Where does createServiceInspector live?
[23:12] <Makyo> I can't grep quickly because I have stuff in vim copy buffer.
[23:12] <hatch> yup 'drop' never fires
[23:13] <hatch> Makyo: environment.js
[23:13] <hatch> views/
[23:13] <Makyo> Wow, that sucks.
[23:13] <Makyo> Most of today's work is moot.
[23:13] <hatch> uh oh, why?
[23:14] <Makyo> Just surrounding event stuff, which got weird when I merged with trunk.
[23:14] <gary_poster> hey
[23:14] <Makyo> I'l ljust GUESS
[23:14] <hatch> oh hey gary
[23:14] <hatch> glad you're still here :)
[23:15] <gary_poster> so you said that dnd doesn't work with improv?
[23:15] <hatch> noope, the drop event doesn't fire
[23:15] <hatch> that's as far as I've gotten so far
[23:15] <gary_poster> wow that's pretty weird
[23:15] <hatch> yeah....I'm pretty blown away hah
[23:16] <hatch> if I change sandbox to true, I get a drop target, if it's false, I dont'
[23:16] <gary_poster> trying to dupe
[23:16] <Makyo> I can dupe.
[23:16] <gary_poster> ok
[23:16] <hatch> it's a D3 issue....it's makyo's fault
[23:16] <gary_poster> that sucks :-/
[23:16] <gary_poster> lol
[23:16]  * hatch runs away
[23:17] <hatch> haha
[23:17] <gary_poster> I doubt that
[23:17] <Makyo> Nah, not cool.
[23:17] <hatch> yeah actually it's in the YUI section
[23:17] <hatch> lol
[23:17] <hatch> OHHH
[23:17] <hatch> I KNOW!!!!
[23:17] <hatch> I KNOW!!!!!!!
[23:18] <Makyo> Do tell.
[23:18] <gary_poster> yeah I was kinda expecting a follow-up
[23:18] <gary_poster> :-)
[23:18] <gary_poster> and duped btw
[23:18] <hatch> lol
[23:18] <gary_poster> it drags very nicely fwiw
[23:18] <hatch> well my guess is that we are missing a yui module
[23:19] <hatch> oh wait
[23:19] <gary_poster> not so much wit hthe drop though
[23:19] <hatch> nm
[23:19] <hatch> nope the drop whitelist is there
[23:19] <hatch> damnnnnn
[23:19] <hatch> I was so excited
[23:19] <hatch> and now so let down
[23:19] <hatch> :'(
[23:20] <hatch> well darn
[23:21] <gary_poster> it looks so nice in the sandbox...
[23:22] <gary_poster> my chromium and chrome are broken for some reason :-(
[23:22] <gary_poster> they start flashing and wiggling
[23:22] <gary_poster> when I load a page with stuff going on
[23:23] <hatch> maybe it's checked out for the week
[23:23] <hatch> :)
[23:23] <gary_poster> heh, been that way for the whole week
[23:25] <hatch> benji is going to be very.....irritated
[23:29] <hatch> ahh getting closer
[23:30] <hatch> ok I lied
[23:30] <hatch> 'dragover' fires
[23:30] <hatch> so I suppose that's a little closer
[23:30] <gary_poster> I have a suspicion.  trying to verify
[23:31] <gary_poster> in show_environment
[23:31] <gary_poster> in app.js
[23:31] <gary_poster>             useDragDropImport: true, #this.get('sandbox'),
[23:31] <gary_poster> that is, I bet that something is configured in the environment that ben did
[23:31] <gary_poster> which benji needs
[23:31] <gary_poster> and assumed he already had
[23:33] <bcsaller> that would stop it
[23:35] <gary_poster> yes, hatch, bcsaller, that is the trick
[23:35] <hatch> haha damn
[23:35] <hatch> can that be on all the time?
[23:35] <bcsaller> so just never tested without
[23:35] <gary_poster> yup
[23:35] <bcsaller> it has to be now
[23:35] <gary_poster> well
[23:35] <bcsaller> thats the old version of a feature flag
[23:35] <hatch> :)
[23:35] <hatch> right on
[23:35] <bcsaller> but now its a real feature, all grown up
[23:36] <gary_poster> heh
[23:36] <hatch> good work gary :)\
[23:36] <gary_poster> thanks :-)
[23:36] <hatch> so.....who's gona fix? ;)
[23:37] <hatch> I can do it in a bit then do the release pending CI
[23:37] <hatch> well and any other obscure issues haha
[23:37] <bcsaller> I have to take off in a few minutes for something or I'd offer.
[23:38] <hatch> alright I have nothing to do tonight so I'll git-r-dun!
[23:38] <Makyo> Man, this reminds me of my last job in some pretty awful ways :P  Can I suggest no more Friday afternoon releases?
[23:38] <bcsaller> ha, have a good weekend
[23:38] <gary_poster> well, bcsaller, hatch, thank you.  mm
[23:38] <hatch> Makyo: bring it up on Friday
[23:38] <hatch> lol
[23:38] <bcsaller> ouch
[23:38] <gary_poster> Makyo, yeah, this was a extra special request for arosales
[23:39] <Makyo> gary_poster, Ah, alright!  I'm all for getting things out the door, just maybe not Fridays as standard practice :)
[23:39] <gary_poster> Makyo, huge +1
[23:39] <gary_poster> would not have done this otherwise
[23:39] <Makyo> Old job was Fridays at 11PM, on call until Monday at 5AM.
[23:39] <gary_poster> heh
[23:39] <gary_poster> yeah
[23:39] <Makyo> They had the QA people sleeping on cots in the bathrooms testing in 6hr shifts.
[23:39] <Makyo> It was nuts.
[23:39] <gary_poster> wow
[23:40] <hatch> ok great so I'll fix that, CI, QA, release 0.6.2
[23:40] <gary_poster> yeah, I was already kind of grimacing about how this might go
[23:40] <gary_poster> if this is the worst we've got...
[23:40] <gary_poster> we're lucky
[23:40] <gary_poster> hatch 0.7.0 pls
[23:40] <gary_poster> we actually have two real features that people will care about!
[23:40] <gary_poster> :-)
[23:41] <gary_poster> dnd and deployer format export
[23:41] <hatch> ahhh right ok cool
[23:42] <gary_poster> hatch other thoughts (bcsaller if you are around feel free to disagree):
[23:42] <gary_poster> (1) consider making card to rename importexport.js to dragdrop.js?
[23:43] <gary_poster> (2) consider passing the flag in to the import export module and disable the file part?
[23:43] <gary_poster> trying to see if it actually is separate...
[23:46] <hatch> 1 - agree, will make a card
[23:46] <hatch> 2 - not really sure why/when we would want to disable any of it
[23:48] <gary_poster> hatch, well tbh my first concern is that I still don't understand why the import export module needs to be there.  it only has two branches to handle a drop
[23:48] <gary_poster> and neither of them should be used for the charm drop
[23:49] <hatch> hmm
[23:49] <gary_poster> hatch, and then my second point is that neither of those branches are actually interesting if you are not using a sandbox
[23:50] <gary_poster> wow, yeah
[23:50] <gary_poster> you can comment out all of _handleFileDrop
[23:50] <hatch> throwing this out there - it might be the preventeDefault/stopPropogation
[23:50] <hatch> in _ignore on the dragover/enter
[23:51] <hatch> (sorry trying to feed the dogs right now, will test soon)
[23:51] <gary_poster> ok trying
[23:52] <gary_poster> hatch, yes that appears to be it
[23:53] <hatch> hmm that's odd
[23:53] <gary_poster> hatch, so all we need to get this to work is the
[23:53] <gary_poster>               dragenter: '_ignore',
[23:53] <gary_poster>               dragover: '_ignore',
[23:53] <gary_poster> registration
[23:54] <gary_poster> I'd prefer to move that out of the importexprt
[23:54] <gary_poster> into some generic module
[23:54] <hatch> yeah - I would like to know why that's required
[23:54] <gary_poster> agreed
[23:54] <gary_poster> hatch, you really cool with doing this?  I'll take the bullet if you need me to
[23:55] <hatch> nope that's fine - I don't have anything better to do :)
[23:55] <gary_poster> heh
[23:55] <gary_poster> ok hatch
[23:55] <gary_poster> thank you
[23:56] <gary_poster> I'll try to check in with you later
[23:56] <gary_poster> but thank you!
[23:56] <hatch> no problem :) have a good one


[00:04] <shadeslayer> apachelogger: please advise on how to merge changelog of kdegames
[00:04] <shadeslayer> ill then upload it to ppa
[00:05] <shadeslayer> apart from that kdegames is doen
[00:05] <shadeslayer> *done
[01:38] <MIH1406> Hi, I want to get pot (po template) files for KDE 4.5 and KDE 4.6
[01:52] <MIH1406> Hi, I want to get pot (po template) files for KDE 4.5 and KDE 4.6
[03:07] <JontheEchidna> blah, new libapt-pkg breaks ABI and makes libqapt throw deprecation errors :(
[03:07] <JontheEchidna> new beta for the ubuntu font looks nice
[03:07] <JontheEchidna> less blurry, more sharp
[03:19] <JontheEchidna> maco: seen http://lamarque-lvs.blogspot.com/2010/07/plasma-nm-modem-sony-md300-and-more.html ?
[03:38] <apachelogger> shadeslayer: I was talking about akonadi 1.4 which is not yet uploaded from what I have seen
[03:39] <apachelogger> crimsun: something about the pluseaudio-start-kde script things for which a report exists that is fixed in maverick but urgently needs SRUing in lucid because it essentially renders the phonon configuration module useless if used on a pulse setup
[03:39] <apachelogger> Nightrose: we'll see about stuttgart :S
[03:40] <apachelogger> shadeslayer: for merging 2 unreleased changlogs, just add the old changes to the new entry and remove the old entry (if necessary add changer identification such as [ Harald Sitter ]\n  * Did break things)
[03:41] <apachelogger> JontheEchidna: gotta love libapt :S
[03:56] <apachelogger> Quintasan, shadeslayer: please make sure the states in the wiki are correct
[03:56]  * apachelogger goes off to bed o/
[04:14] <crimsun> apachelogger: ugh, may as well roll in fixes for a few others, too.  sigh.
[04:59] <ScottK> What's the release day for 4.5.0?
[04:59] <ScottK> We need to decide if we're going to try and get it in before Alpha 3?
[06:44] <jussi> ScottK: according to kde.org, its set for the 19th.
[06:44] <ScottK> jussi: That seems pretty far off.  Thanks.
[06:44] <jussi> err
[06:44] <jussi> 14th
[06:44] <jussi> 4th
[06:44] <jussi> cripes I cant type
[06:44] <jussi> o read: http://techbase.kde.org/Schedules/KDE4/4.5_Release_Schedule
[06:45]  * jussi cries
[06:46] <jussi> ScottK: so 4th.
[10:58] <apachelogger> crimsun: :)
[10:58]  * apachelogger leaves a cookie on crimsun's desk
[11:07] <apachelogger> ScottK: we can upload a bit before to make it more suited for our freezes
[11:07] <apachelogger> we did that a couple of times already
[11:07] <apachelogger> not the best thing to do with a final release though (from a drumm roll POV)
[11:11] <apachelogger> eheheh
[11:12] <apachelogger> Quintasan: kdelibs got a wrong version no
[11:16] <apachelogger> debian/patches/security_01_CVE-2009-2702.diff
[11:16] <apachelogger> ?
[11:16] <apachelogger> eh?
[11:17] <apachelogger> from the description I gather that the patch is pointless now
[11:17] <apachelogger> yet it remains
[11:17] <apachelogger> yet it applies
[11:17] <apachelogger> so either KDE did other stuff to fix the issue or there is something very wrong
[11:25] <apachelogger> Quintasan: kdepimlibs also needs to be merged
[11:56] <CIA-98> [akonadi] Harald Sitter<EMAIL_ADDRESS>*<EMAIL_ADDRESS>* debian/changelog New upstream release.
[12:09] <shadeslayer> hmmm so weird
[12:09] <apachelogger> :O
[12:09] <shadeslayer> apachelogger: ssup?
[12:09] <apachelogger> is Qt 4.7 really still on beta2?
[12:10] <shadeslayer> apparently my quassel core account disconnected :S
[12:10] <shadeslayer> apachelogger: dude.. how do i merge kdegames changelog
[12:10] <apachelogger> you make it one
[12:10] <apachelogger> [04:41:34] <apachelogger> shadeslayer: for merging 2 unreleased changlogs, just add the old changes to the new entry and remove the old entry (if necessary add changer identification such as [ Harald Sitter ]\n  * Did break things)
[12:11] <shadeslayer> hmm ok...
[12:11] <apachelogger> ohm
[12:11]  * apachelogger is wondering if we should publish 4.5.0 to lucid and claim it stable even though Qt 4.7b2 is used
[12:14] <shadeslayer> apachelogger: do you see a quit message from me? ( in the logs )
[12:15] <shadeslayer> because i cant.....
[12:15] <apachelogger> shadeslayer: ping timeout
[12:15] <shadeslayer> hmm... jefferai ^
[12:15] <apachelogger> although a lot of people had a ping timeout around the same time
[12:15] <shadeslayer> but how come it didnt re connect :P
[12:16] <apachelogger> yeah, all people on jefferai's core went into timeout ^^
[12:16] <shadeslayer> lol
[12:18] <shadeslayer> apachelogger: so changelog looks like http://pastebin.com/UnfYw5nY
[12:18] <shadeslayer> did we release 4.4.95 kdegames?
[12:18] <apachelogger> oh dear qwebkit needs a backport -.-
[12:19] <apachelogger> shadeslayer: no, that is why the entry said UNRELEASED
[12:19] <apachelogger> and it is also the reason the should be merged
[12:19] <shadeslayer> ok then.. i think that is all good
[12:22] <shadeslayer> heh.. while uploading via SFTP to ninja ppa, i dont get the amount of data uploaded
[12:23] <shadeslayer> apachelogger: dude... how can you do this :P
[12:23] <shadeslayer> /usr/share/pkg-kde-tools/qt-kde-team/1/debian-qt-kde.mk:7: /usr/share/cdbs/1/rules/patchsys-quilt.mk: No such file or directory
[12:28] <apachelogger> shadeslayer: what?
[12:29] <shadeslayer> missing build dep on quilt for akonadi lucid
[12:29] <shadeslayer> or thats what i think it is
[12:29] <apachelogger> looks like it
[12:29] <apachelogger> a bit creepy though
[12:29] <shadeslayer> yeah ...
[12:30]  * apachelogger hates the cdbs
[12:30] <apachelogger> clearly I should have testbuilt
[12:31] <apachelogger> is that a general remark with lucid backports though?
[12:31] <apachelogger> we should mention that if so...
[12:31] <apachelogger> on the wiki page
[12:32] <apachelogger> so, should I conduct real live upgrade testing ^^
[12:37] <Quintasan> god damn
[12:38] <Quintasan> Please. how do I block WoW from my network T_T
[12:38] <shadeslayer> apachelogger: is everything done?
[12:39] <apachelogger> kdelibs got state ppa-bzr(not yet)
[12:39] <apachelogger> whatever that means
[12:39] <shadeslayer> plasma-scriptengine-googlegadgets
[12:39] <Quintasan> that means shadeslayer is to push the chages
[12:39] <apachelogger> plasma-addons got state ppa-bzr (w8 on edu)
[12:39] <Quintasan> without aspell
[12:39] <shadeslayer> yeah ill do that after i upload kdegames
[12:39] <apachelogger> shadeslayer: I will do that
[12:39] <apachelogger> ohohohoh
[12:39] <Quintasan> apachelogger: I have retried the build yesterday
[12:39]  * apachelogger still needs to resync pkg-kde-tools with KDE
[12:40] <apachelogger> what is with kdeartwork?
[12:40] <Quintasan> apachelogger: do we keep a different branch for lucid packaging?
[12:40] <shadeslayer> btw all of the stuff is built on older qt, we need rebuild with Qt lex uploaded
[12:40] <shadeslayer> Quintasan: nope
[12:40] <apachelogger> Quintasan: no, but we really should
[12:40] <Quintasan> apachelogger: kdelibs failed
[12:40] <apachelogger> Quintasan: supposedly I need to come up with a new set of batscripts
[12:40] <shadeslayer> what!!
[12:40] <Quintasan> shadeslayer: what's the status of import?
[12:40] <apachelogger> Quintasan: I noticed, needs more recent backpor to qtwebkit
[12:41] <shadeslayer> Quintasan: lemme poke jelmer.. although i really shouldnt
[12:41] <shadeslayer> Quintasan: you poke him
[12:41] <Quintasan> so don't do it
[12:41] <Quintasan> :P
[12:41] <apachelogger> anyone wanan do the honors of backporting qtwebkit? :P
[12:41] <apachelogger> shadeslayer: ? :P
[12:41] <Quintasan> apachelogger: I want the honor of doing pimlibs
[12:41] <shadeslayer> apachelogger: yeah its currently ftbfs.. working on it
[12:41] <apachelogger> Quintasan: do you have any informatin on kdeartwork
[12:41] <Quintasan> nope
[12:41] <shadeslayer> right now i need to get my noodles fixed first :P
[12:42] <Quintasan> and I imagine it is too big for me to upload
[12:42] <Quintasan> not to mention downloading
[12:42] <apachelogger> you cannot even download it Oo
[12:42] <shadeslayer> kdegames uploaded
[12:42] <apachelogger> stalcup: kdeartwork?
[12:42] <shadeslayer> now to work on webkit
[12:43] <shadeslayer> errr
[12:43] <shadeslayer> apachelogger: im working on webkitkde
[12:43] <Quintasan> apachelogger: that's what you get when you sister is a) older b) shouts all the time c) is nearer to cable d) is still playing WoW
[12:43] <Quintasan> weekends are nightmare when trying to use internet
[12:43] <apachelogger> whuz?
[12:43] <apachelogger> shadeslayer: where is webkitkde? Oo
[12:44] <apachelogger> Quintasan: ehm
[12:44] <apachelogger> Quintasan: dude
[12:44] <apachelogger> Quintasan: you are an IT geek
[12:44] <shadeslayer> apachelogger: dude.. they had a new release
[12:44] <shadeslayer> about a week back
[12:44] <apachelogger> the least you should be able is to reroute all your NW traffic through your machine and induce QoS
[12:44] <shadeslayer> and i didnt touch it since
[12:45] <apachelogger> shadeslayer: well I would appreciate if we could get the job at hand done first before we wonder off to do other things?
[12:45] <shadeslayer> im on for another 45 mins, then have to go out
[12:45] <apachelogger> well
[12:45] <apachelogger> me too
[12:46] <apachelogger> just I am here 30 mins longer ;)
[12:47] <shadeslayer> Launchpad failed to process the upload path '~rohangarg/kubuntu-ninjas/ubuntu': << wth
[12:47] <shadeslayer> oic
[12:47] <shadeslayer> that needs to be ~kubuntu-ninjas
[12:49] <Quintasan> apachelogger: the problem is
[12:49] <Quintasan> my router is pretty damn limited
[12:49] <Quintasan> :/
[12:52] <apachelogger> reroute through your machine!
[12:53] <Quintasan> apachelogger: upgrade on maverick is smooth
[12:53] <Quintasan> just pleasure hitting "g" in aptitude
[12:53] <apachelogger> Quintasan: upgade testing should be conducted using apt and/or kpackagekit
[12:56] <shadeslayer> errrr
[12:57] <shadeslayer> Riddell: around?
[12:58]  * apachelogger loves when kate decides to crash
[12:58] <shadeslayer> Riddell: did you upload kdevplatform from my PPA ?
[13:06] <apachelogger>   Uploading pkg-kde-tools_0.9.2ubuntu10_source.changes: done.
[13:06] <apachelogger> Successfully uploaded packages
[13:07]  * apachelogger notes that now kde qml files are processed properly \\o/
[13:07] <shadeslayer> apachelogger: btw are you backporting qtwebkit?
[13:07] <apachelogger> no
[13:07] <shadeslayer> or should i
[13:07] <shadeslayer> ok ill do it then
[13:15] <shadeslayer> apachelogger: btw webkitkde is done :P
[13:20] <shadeslayer> apachelogger: you need https://edge.launchpad.net/ubuntu/+source/qtwebkit-source backported right?
[13:20] <shadeslayer> i have 10 mins to do it :P
[13:35] <stalcup> apachelogger: almost
[13:38] <shadeslayer> apachelogger: qtwebkit uploaded
[13:44] <apachelogger> stalcup: cool
[13:44] <apachelogger> shadeslayer: please update the wiki
[13:44] <apachelogger> if you didnt already
[13:47] <apachelogger> shadeslayer, Quintasan: if you get a second, please check that everything requires akonadistuff >= 1.4
[13:59] <ximion> JontheEchidna: Hi!
[13:59] <JontheEchidna> ximion: hello
[13:59] <ximion> do you have time to look at the oxygen-molecule package agein?
[13:59] <ximion> ( http://revu.ubuntuwire.com/p/oxygen-molecule )
[14:01] <JontheEchidna> ximion: I'm actually at a hotel now and will have to get ready to go again in a few minutes, but I'll  try to look at it tonight
[14:01] <ximion> JontheEchidna: I finally reached upstream over his e-mail adress (I first only tried it via OpenDesktop), and he clearified the license stuff and gave me some background information about the theme.
[14:01] <ximion> okay.
[14:01] <JontheEchidna> I'm sure that some of the other kubuntu guys would be happy to revu :)
[14:01] <JontheEchidna> thanks for your work on the package
[14:01] <ximion> JontheEchidna: I'll be on holiday for two weeks starting on wednesday, so I can't look at the package then.
[14:02] <ximion> packaging themes is really easy :-P
[14:02] <ximion> thanks!
[14:02] <JontheEchidna> :P
[14:03] <ximion> Btw: Is someone of working on a Qt implementation of the Ubuntu Software center?
[14:04] <shadeslayer> ximion: id like to.. but i dont see any point...
[14:04] <JontheEchidna> I plan to start on one for 11.04 after Muon gets a stable release, but I've not started yet
[14:04] <shadeslayer> JontheEchidna: USC based on Muon?
[14:05] <shadeslayer> or from scratch
[14:05] <ximion> I started a project like this a long time ago, but then stopped working on it after Richard Hughes announced a cross-distro way of building a software-center like app.
[14:05] <muesli> love the new homepage
[14:06] <ximion> muesly: agree! it's beautiful! (kudos to the designer)
[14:07] <ximion> now since QApt has been created, it should be easy to create a Qt Software-Center.
[14:07] <ximion> ...if there are any plans, I'd like to help.
[14:08] <shadeslayer> ximion: idle here and you will get to know all our plans :P
[14:08] <shadeslayer> anyways.. im off
[14:09] <JontheEchidna> shadeslayer: I'll probably use the MuonMainWindow base class and write a custom GUI off of that
[14:09] <ximion> shadeslayer: I'll wait of courese :-P - bye.
[14:09] <JontheEchidna> ximion: I'll keep you in the loop. (But I have to go now too, bye)
[14:10] <ximion> bye.
[14:14] <debfx> could someone please sync gtk2-engines-qtcurve and kde-style-qtcurve from debian?
[14:20] <stalcup> debfx: did you file a sync-request?
[14:20] <stalcup> once approved, only archive admins can do those syncs
[14:21] <debfx> stalcup: no, but there is a syncpackage script in ubuntu-dev-tools
[14:22] <debfx> which allows anyone with upload privileges to sync
[14:22] <stalcup> hrm, must be a newer addition then
[14:23] <stalcup> or i've been away far too long :)
[14:25] <debfx> yeah it's only in maverick
[14:26] <stalcup> so I take it you are looking at 59.5-1 then?
[14:59] <debfx> stalcup: 59.5-1?
[15:11] <shadeslayer> apachelogger: retried kde4libs for lucid
[15:19] <shadeslayer> Quintasan: kde4libs for lucid needs fix0ring
[15:20] <shadeslayer> Quintasan: also can you upload webkitkde from https://edge.launchpad.net/~rohangarg/+archive/experimental
[15:56] <stalcup> Err http://archive.ubuntu.com/ubuntu/ maverick/main pkg-kde-tools 0.9.2ubuntu8 404  Not Found [IP: <IP_ADDRESS> 80]
[16:02] <shadeslayer> stalcup: superseeded
[16:02] <shadeslayer> bu ubuntu10
[16:02] <shadeslayer> *by
[16:02] <shadeslayer> so refresh sources ;)
[16:06] <Quintasan> shadeslayer: I belive I told you that my uploading powers are limited to 0 today
[16:06] <Quintasan> :/
[16:06] <shadeslayer> why?
[16:07] <shadeslayer> Quintasan: ^
[16:10] <shadeslayer> Quintasan-- for not uploading my packages to universe
[16:12] <Quintasan> shadeslayer: WoW Player inhouse
[16:12] <shadeslayer> dude
[16:12] <shadeslayer> universe >>>> WoW
[16:12] <Quintasan> She is near my ethernet cable
[16:12] <Quintasan> :<
[16:12] <shadeslayer> anyways.. ive got freeflying to sponsor the upload then :P
[16:13]  * Quintasan always wanted to do something about it but never got to
[16:13] <Quintasan> I'll buy a wireless card for my pc
[16:15] <shadeslayer> whee
[16:15] <shadeslayer> freeflying: its built.. can you sponsor it?
[16:19] <shadeslayer> well then... ill see you guys tmmrw
[16:31] <txwikinger> Any suggestions for a package for bugday?
[16:32] <DarkwingDuck> [16:32] <DarkwingDuck> BAH
[16:33] <DarkwingDuck> Anyone seen nixternal?
[17:21] <shadeslayer> DarkwingDuck: nope.. but i do see him tweeting
[17:22] <shadeslayer> txwikinger: hmm.. ill try to come up with something... :)
[17:22] <Quintasan> ping him then
[17:22] <Quintasan> txwikinger: KNetworkManager
[17:22] <Quintasan> :P
[17:22] <shadeslayer> heh
[17:26] <DarkwingDuck> shadeslayer: yeah, me too.. I'll get this move out of the way then sucker him in for some drinks
[19:22] <stalcup> ah! apt-transport-https
[19:24] <Riddell> shadeslayer: no I don't think I uploaded kdevplatform from your PPA, I think I synced from Debian
[19:29] <Riddell> apachelogger: if translations only get mangled on i386 won't that mean amd64 and whatnot have different .desktop files than i386 and might do things differently?
[19:29] <Riddell> ah it's not the mangling, it's the .pot generation only, that's fine
[19:33] <stalcup> How did I ever manage to package more than one source during a release before
[19:33] <stalcup> I am really out of shape packaging wise
[19:35] <Riddell> dual core processor is the secret :)
[19:37] <maco> Riddell: ive seen your laptop. i dont think dual core existed when you got that thing
[19:37]  * stalcup throws out his quad core
[19:38] <stalcup> so artwork will be ready in two shakes
[19:38] <stalcup> and I can start backporting
[19:38] <Riddell> quad core might sound useful but can you really work efficiently on four things at once?  I'm not convinced I want my computer to do more than I can hold in my head
[19:39] <stalcup> ha
[19:39] <crimsun> I keep chuckling at people who have these quad-core laptops who attempt to use them unplugged from AC.
[19:39] <stalcup> this is a desktop tyvm
[19:39] <stalcup> my macbook is a dualcore
[19:40] <stalcup> i really like my desktop though, made it myself
[19:40] <crimsun> I have six cores in /var/crash. I have six cores!
[19:40] <stalcup> AH!!!!! holy
[19:40]  * stalcup bows
[19:41] <stalcup> I'll have to dump the core to get us out of the grips of this black hole
[19:41] <crimsun> yeah, I was trying to avoid the blatant ST reference :P
[19:42] <stalcup> well, someone had to do it
[19:42] <crimsun> true
[19:42] <stalcup> i do love dolphin
[19:54] <sheytan> hey guys
[19:54] <sheytan> how do you like this: http://a.imageshack.us/img687/1636/whatiskubuntu.jpg
[19:59] <shadeslayer> sheytan: frickin awesome
[19:59] <shadeslayer> Riddell: well.. its FTBFS :P
[20:00] <sheytan> shadeslayer thank you :)
[20:00] <sheytan> what is FTBFS? :D
[20:01] <shadeslayer> Failed to build from source :)
[20:01] <shadeslayer> basically when a package fails to build
[20:01] <sheytan> oh, ok :D
[20:01] <shadeslayer> apachelogger: i might do a NMU for webkitkde to debian
[20:02] <shadeslayer> so we can sync/merge that.. although i do believe that it will fail with the dh_install --missing foo
[20:02] <Tscheesy> sheytan: very nice - although i would use english language and username like "kubuntu" in screenshot, also standard theme and background.. my2cents
[20:02] <shadeslayer> make that --fail-missing
[20:03] <maco> anyone think writing a wizard for mobile broadband in python and just having a button that launches it from knetworkmanager's config tool would be a bad way to do things? parsing xml in c++ seems ... unfriendly
[20:03] <shadeslayer> sheytan: yeah try to keep it as generic as possible :)
[20:04] <sheytan> Tscheesy it's still just a mockup, and replacing screenshots is just few minutes. I just put them these couse i had them done :)
[20:04] <sheytan> shadeslayer ^^ :D
[20:04] <shadeslayer> sheytan: btw the part in "Ready out of the box" needs some love
[20:05] <maco> alternatively, is it possible to have a single c++ program where a chunk of it is in python?
[20:06] <sheytan> shadeslayer, yep ;)
[20:08] <crimsun> maco: eh, not really unfriendly but not as nice as using Python, probably
[20:09] <crimsun> maco: and yes, it's possible
[20:09] <maco> crimsun: well knm is *already* c++
[20:09] <muesli> http://www.kubuntu.org/community <- links to a german support page which doesn't exist
[20:09] <maco> but writing a thing that reads xml to do the wizard in c++ is going to suck, so i want to know if i can do the logic for that piece in python
[20:10] <muesli> actually, none of the language support sites seem to work
[20:11] <maco> muesli: that was reported yesterday on the mailing list
[20:14] <maco> crimsun: do you have any links i could read on how to do that?
[20:16] <maco> oh nvm. Riddell just told me about qtxml. so im going to go learn about that and do my first patch with C++
[20:16]  * maco looks at knm's current code and whimpers
[20:17] <shadeslayer> muesli: can you post that to<EMAIL_ADDRESS>[20:19] <muesli> shadeslayer: maco just mentioned it was reported there already
[20:19] <shadeslayer> ah ok.. i didnt see that
[20:20] <shadeslayer> yeah seems neversfelde reported it
[20:21] <neversfelde> mhh
[20:21] <neversfelde> ah, the loco pages
[20:21] <shadeslayer> yep
[20:32] <stalcup> shadeslayer: neversfelde: could one of you two please pastebin me a copy of the ninja ppa dput info?
[20:33] <stalcup> pm of course :)
[20:34] <neversfelde> stalcup: done
[20:34] <stalcup> appreciated much!
[20:35] <neversfelde> :)
[20:35] <stalcup> well, hmm
[20:35] <stalcup> i tried that already
[20:36] <neversfelde> works for me
[20:36] <stalcup> I've been trying to unborkify my system
[20:43] <neversfelde> mhh, someone wanted to talk to Debian and upstream about minitube, I cannot remember who it was? :)
[20:46] <neversfelde> and we still have with plasma-widget-cwp and plasma-widget-customizable-weather cwp twice in the archive, I forgot again to work on it
[20:46] <neversfelde> someone else wants to do it, I am not available till End of August
[20:47] <stalcup> oh noes!
[20:49] <ScottK> Riddell: 4.5.0 before or after Alpha 3 freeze?
[20:49] <stalcup> after artwork is done, it will be ready
[20:50] <ScottK> Riddell: At the release team meeting on Friday, I said we hadn't decided.
[20:50] <ScottK> Also got dyfet to start looking at kdebindings on armel.
[20:50] <ScottK> AFAIK, no patches yet though.
[20:52] <debfx> the battery applet is gone from default settings :(
[20:52] <debfx> taking brightness osd with it
[20:54] <stalcup> yay!  finally uploading the last package Riddell
[20:54] <Riddell> ScottK: that is the question
[20:54] <Riddell> mostly depends if upstream would mind
[20:56] <Riddell> ScottK: is Sime aware of the kdebindings failure on ARM?  it's in his territory
[20:58] <Riddell> what does yellow mean on https://wiki.kubuntu.org/Kubuntu/Ninjas/Packaging ?
[20:59] <stalcup> I would assume "the stack"
[20:59] <stalcup> or not
[20:59] <stalcup>  /me spies kdeedu
[21:00] <Riddell> debfx: probably needs something fixed in /usr/share/kubuntu-default-settings/kde4-profile/default/share/apps/plasma-desktop/init/00-defaultLayout.js
[21:01] <debfx> oh, it's because I removed the battery from the laptop
[21:05] <Riddell> debfx: ah that would be it :)
[21:09] <ScottK> Riddell: I don't know about Sime and kdebindings.  dyfet indicated it looked more like a sip problem that was blowing up in kdebindings to him.
[21:10] <ScottK> I understand NC|Alaska will be NCommander again on Monday, so maybe he'll have suggestions.
[22:59] <neversfelde> I send a mail to Debian  and upstream about Minitube, so whoever wanted to do it, it is not necessary anymore
[23:05] <debfx> yay, ppa build on i386: Start 2010-08-04
[23:08] <Riddell> debfx: :(
[23:11] <neversfelde> shadeslayer: is there a reason, why we dropped source format 3.0 for choqok?
[23:12] <neversfelde> and other changes
[23:20] <NCommander> ScottK: I'm back
[23:21] <NCommander> ScottK: its NOT a sip problem, its someone broke the special rules handling calling sip on ARM.
[23:22] <Riddell> welcome back NCommander, how was Alaska?
[23:23] <NCommander> Riddell: lovely. I even got an opportunity to up to the Arctic Circle and jump into the Arctic Ocean
[23:26] <Riddell> see, it's not just me that's gets you cold and wet
[23:33] <ari-tczew> Riddell: could you check package https://launchpad.net/ubuntu/+source/koffice-l10n is it a merge or sync?
[23:34] <NCommander> Riddell: yes, but it has a higher statistical probability of happening while your around
[23:41] <Riddell> ari-tczew: probably a synz
[23:41] <Riddell> ari-tczew: probably a sync
[23:41] <Riddell> yes should be a sync
[23:41] <ari-tczew> ok thanks


[01:25] <marcoceppi> bdx: yes
[02:31] <bdx> marcoceppi: can you let me in on the secret?
[08:41] <jamespage> fginther, dpb1_: cs:~james-page/xenial/ceph-mon-gated-0
[08:41] <jamespage> testing myself atm
[09:39] <lazyPower> arosales icey  - also just fyi, you dont need to set defaults. juju bootstrap my-amazon-controller aws/us-west-1 would work equally as well.
[11:41] <Rajith> Hi,   I am facing issue while installing mariadb from charm store, install hook error is displayed in status and logs have 2016-05-17 10:42:46 INFO config-changed gpg: requesting key 1BB943DB from hkp server keyserver.ubuntu.com 2016-05-17 10:43:07 INFO config-changed gpgkeys: key CBCB082A1BB943DB can't be retrieved
[11:43] <lazyPower> Rajith - ah, seems like they may have updated their key. Their dev is west coast based, so there's a bit of a delay before i can get confirmation. Do you mind filing a bug against the charm? https://bugs.launchpad.net/charms/+source/mariadb
[11:44] <Rajith> sure will raise a bug
[11:44] <lazyPower> thanks Rajith
[11:55] <icey> lazyPower: that's what I ended up doing
[11:56] <lazyPower> right on.
[12:01] <magicaltrout> I appear to have opened a can of monitoring worms
[12:03] <lazyPower> magicaltrout you knew exactly what you were doing :) And i'm happy you did
[12:03] <magicaltrout> hehe
[12:03] <magicaltrout> its interesting to get all the different perspectives
[12:03] <lazyPower> you started the discussion, you can lay claim to the fact its gone further than expected, but dont be sad/upset at all. its a brilliant convo
[13:09] <fginther> jamespage, thanks, are you also porting that to trusty?
[13:09] <jamespage> fginther, yes but I was testing on xenial
[13:10] <fginther> jamespage, thanks
[13:20] <shewless_> Hello. I'm trying to bootstrap lxd on 16.04 and I'm getting this error: "ERROR cannot find network interface "lxdbr0": route ip+net: no such network interface". I tried adding the bridge using "sudo dpkg-reconfigure -p medium lxd"
[13:20] <shewless_> any ideas?
[13:26] <lazyPower> neiljerram - which charm from calico relates to etcd? (sorry i should have looked this up) - i have a patch re-introducing the proxy relation
[13:26] <lazyPower> shewless_ - ah that looks familiar. did you install a prior beta of juju?
[13:30] <shewless_> lazyPower: I just did a "sudo apt-get install juju"
[13:30] <shewless_> should I have added some ppa first or something?
[13:31] <lazyPower> shewless_ - installation instructions for the current beta is here: https://jujucharms.com/docs/devel/getting-started
[13:33] <shewless_> thanks I'll have a look
[13:33] <lazyPower> np, dont hesitate to ping back if you get stuck
[13:34] <jamespage> fginther, do you need that published to trusty for testing as well?
[13:45] <neiljerram> lazyPower, it's neutron-calico and neutron-api
[13:45] <fginther> jamespage, yes that would be great. I could start testing that today for trusty
[13:46] <lazyPower> neiljerram - yikes thats a big dep chain :D
[13:46] <neiljerram> lazyPower, for which one?
[13:46] <lazyPower> neutron - full stop
[13:46] <neiljerram> lazyPower, unfortunately yes.
[13:47] <lazyPower> that comes with an openstack dependency. for validation of this branch i think i'll hack together a simple charm consuming the interface and go from there
[13:47] <lazyPower> all we need is a mirror of the initial-cluster-string right?
[13:47] <jamespage> fginther, cs:~james-page/xenial/ceph-mon-bug1577519
[13:47] <jamespage> no not that one
[13:47] <jamespage> one sec
[13:48] <jamespage> fginther, cs:~james-page/trusty/ceph-mon-bug1577519
[13:49] <neiljerram> lazyPower, that sounds sensible to me.  Yes, a proxy just needs a valid value for ETCD_INITIAL_CLUSTER.
[13:50] <lazyPower> neiljerram - here's the interface code - i'm validating the reactive bits before pushing up - https://github.com/chuckbutler/interface-etcd-proxy
[13:50] <neiljerram> lazyPower, It would actually be quite nice to have a charm for an etcd proxy - perhaps just a different flavour of the normal etcd charm, if that would make sense?
[13:51] <lazyPower> would that be a subordinate then? as it needs to co-locate with another service right?
[13:51] <neiljerram> lazyPower, Then I could just install that alongside neutron-calico and neutron-api, instead of putting etcd stuff into those charms.
[13:52] <neiljerram> lazyPower, I'm not sure I completely understand, but I believe that "subordinate" is not exactly the same concept as "co-located"?
[13:53] <neiljerram> lazyPower, For example, my current bundle uses decls like "to: [ bird ]" to indicate co-location.  But I think that's different from being subordinate, isn't it?
[13:53] <lazyPower> well, yes and no. Subordinates will automatically deploy to every unit of the charm, occupying the same "containment" space as that charm. So if its in lxd, both will be installed in the same lxd container. Or of its on a bare metal server, both will be installed to that bare metal. Its effectively like using to, but different constructs. You can deploy a single unit of a different charm using the --to directive, and it has no notion of the
[13:53] <lazyPower>  supporting service
[13:54] <lazyPower> whereas subordinates gain some notion of another service that it is dependent/interacting with over that relation, and it also replicates to every unit of the charm.
[13:54] <neiljerram> lazyPower, ah OK, it sounds like subordinate is the right concept, then.
[13:55] <neiljerram> lazyPower, so if there was an etcd proxy charm, neutron-calico could say that it should have a subordinate etcd proxy; and similarly neutron-api.  Is that right?
[13:56] <neiljerram> lazyPower, or would it be the bundle that said that?
[13:56] <lazyPower> yeah, you'll still need to add the relationship bits to both charms, and whatever supporting data-pass that needs to happen
[13:57] <neiljerram> lazyPower, we could almost get away without any explicit relation at all ... with the proxy users just assuming http://<IP_ADDRESS>:2379.  But that would be a slight hack.
[13:58] <lazyPower> yep, deploy it without the sub and watch it break.
[13:58] <lazyPower> with no clear indicator as to why :/
[13:58] <neiljerram> lazyPower, OK, happy to defer to your experience on that point!
[13:58] <lazyPower> using the sub approach you can use status messaging to tell the user its incomplete
[13:59] <lazyPower> status_set('waiting', "Waiting on missing relation: etcd-proxy")   which is pretty clear whats happened, and not a fail.
[14:00] <neiljerram> lazyPower, Yes, on reflection I agree that it absolutely makes sense to have an explicit relation; independently of whether any config data is passed across it.
[14:25] <neiljerram> lazyPower, BTW - in case not already obvious to you - it would be super-easy to test an etcd-proxy charm: just deploy 1 etcd and 2 etcd-proxies; do etcdctl set /xxx yyy on one proxy, and etcdctl get /xxx on the other.
[14:27] <lazyPower> nice. Thanks for the tip
[15:55] <bdx> hello everyone. Does anyone know of a legitimate path around this -> https://github.com/juju/juju/issues/5411 ?
[15:58] <bdx> I've been battling it for a few days now, thought I would see whats up :-)
[15:59] <lazyPower> bdx - i cant say for certain but i think you're running into some assumptions the lxd provider is making on your behalf.
[16:00] <lazyPower> admittedly i haven't tried the lxd provider with a modified networking profile by default
[16:00] <lazyPower> I'm curious if it will work if you leave the default networking in-tact, and add your bridged network as a second nic on the container
[16:11] <bdx> lazyPower: yea, that works fine
[16:11] <lazyPower> bdx paydirt! thats a legitimate path around it
[16:11] <bdx> ha - I'm paying thats for sure
[16:12] <lazyPower> its a dirty hack, and i dont know what thats doing in terms of public-address/private-address
[16:12] <lazyPower> but theory states, so long as you're not binding to an interface, it should work for remote-access to your lxd resources on your laptop so you can share w/ a co-worker
[16:12] <lazyPower> ymmv
[16:14] <bdx> try to bootstrap lxd with the default profile set to use a bridge on an external interface ... then tell me your theory :-)
[16:16] <lazyPower> bdx - i mean *adding* that bridge on an external interface
[16:16] <lazyPower> not replacing
[16:17] <bdx> lazyPower: yeah ...
[16:17] <lazyPower> same result?
[16:17] <bdx> lazyPower: yeah
[16:17] <lazyPower> > [12:11:01] bdx:	lazyPower: yea, that works fine
[16:17] <lazyPower> i took that as "it works"
[16:18] <lazyPower> neiljerram - https://github.com/juju-solutions/layer-etcd/pull/13
[16:18] <bdx> oh .... so the problem is that you have to set the default lxd profile to use the bridge on the external interface too
[16:18] <bdx> lazyPower: bc the lxd controller gets created with the default profile
[16:18] <lazyPower> bdx something is getting lost in translation here. I'll TAL and see if i can beat it into submission later on
[16:18] <catbus1> Hi, what's the developer tool to discover the interfaces of other charms?
[16:19] <lazyPower> catbus1 - http://interfaces.juju.solutions
[16:19] <bdx> awesome, thx!
[16:20] <lazyPower> neiljerram - I'll push this up to my namespace. I based this off the Xenial branch so you can test w/o tls to start with as there's time there. This interface doesn't support the certificate exchange yet, we'll gate that all through at the same time when the tls-branch lands
[16:23] <catbus1> lazyPower: let's say I am developing a subordinate charm that will need to work with an OpenStack charm, how do I find out the interface names, attributes of the openstack charms? I remember from the first charmer summit, that is a tool developed to discover that and makes updates easier to manage.
[16:24] <lazyPower> catbus1 - ah that information is listed in the charm store itself, right hand side at the top of the charms listing. eg: https://jujucharms.com/neutron-api/  -- click "show more"
[16:24] <lazyPower> you'll get relation-name:interface
[16:26] <catbus1> I see that. I remember seeing a command line way of finding it out.
[16:28] <lazyPower> there's also charm show cs:xenial/neutron-api
[16:28] <catbus1> the interfaces are also defined in metadata.yaml. I remember it allows you to pull in the charms you are going to work with and show the interfaces. maybe it's charm compose.
[16:29] <catbus1> I think charm show is what I am looking for. Thank you!
[16:33] <lazyPower> np :)
[16:53] <Garyx> Hey is it a known issue with maas 2.0 + juju 2.0 that sshkeys that are saved in the maas gui is not being deployed to nodes?
[16:54] <Garyx> Using juju 2.0 beta 7
[16:54] <lazyPower> neiljerram - and its up at cs:~lazypower/etcd-8   https://jujucharms.com/u/lazypower/etcd
[16:54] <Garyx> Everything else seems to bo working fine, but cant log in with my key pair
[16:56] <lazyPower> Garyx - a skim through the bug tracker didn't surface anything that looked relevant. Thats certainly bug-worthy, as i know maas 2.0 + juju 2.0 has been a focus recently for the core team.  Any associated logs, steps to reproduce would be helpful   https://bugs.launchpad.net/juju-core/+filebug
[16:58] <Garyx> lazypower Thanks, haven't found anything in the logs yet that could help. Was wondering if anyone had seen the same before filing a bug.
[17:04] <Garyx> lazypower before I log a new bug the default user created is still ubuntu right?
[17:05] <lazyPower> Yep
[17:05] <Garyx> okies cannot see anything on my end then :/
[17:42] <jamespage> beisner, thedac: I think this will do the trick, but I've not tested yet...
[17:42] <jamespage> https://code.launchpad.net/~james-page/charm-helpers/fixup-service-running/+merge/294942
[17:46] <beisner> thedac, tldr;  SRU bug 1273462 caused bug 1581171.  bug 1582813 raised to ID it as a regression.    thx jamespage
[17:46] <mup> Bug #1273462: Users can mistakenly run init.d scripts and cause problems if an equivalent upstart job already exists <init> <sts> <trusty> <upstart> <verification-done> <lsb (Ubuntu):Fix Released> <upstart (Ubuntu):Fix Released by xnox> <lsb (Ubuntu Trusty):Fix Released by zhhuabj> <upstart (Ubuntu
[17:46] <mup> Trusty):Won't Fix by xnox> <lsb (Ubuntu Utopic):Fix Released> <upstart (Ubuntu Utopic):Fix Released by xnox> <upstart (Debian):Fix Released> <https://launchpad.net/bugs/1273462>
[17:46] <mup> Bug #1581171: pause/resume failing (workload status races) <landscape> <maintenance-mode> <uosci> <ceilometer-agent (Juju Charms Collection):In Progress by 1chb1n> <cinder (Juju Charms Collection):Fix Committed by thedac> <glance (Juju Charms Collection):Fix Committed by thedac> <keystone (Juju
[17:46] <mup> Charms Collection):In Progress by thedac> <https://launchpad.net/bugs/1581171>
[17:46] <mup> Bug #1582813: service --status-all always reports upstart managed daemons as running <amd64> <apport-bug> <ec2-images> <regression-update> <trusty> <lsb (Ubuntu):Confirmed> <https://launchpad.net/bugs/1582813>
[18:01] <mpjetta> I’m trying to setup a new MAAS 2.0 setup with juju 2.0 and running into an issue. I can add the hardware nodes just fine and I see them PXE boot and cloud-init and whatnot when commisioning. However when I go to actually bootstrap the juju CLI to the maas, the nodes PXE boot once, shutdown and then just hang at "Booting local disk. WARN: No MBR magic, treating disk as raw. Booting..."
[18:02] <mpjetta> any ideas?
[18:35] <bdx> mpjetta: format your disks
[18:36] <bdx> mpjetta: gpt + fat32
[18:36] <bdx> should do the trick
[18:36] <mpjetta> thanks, trying that now
[19:03] <thedac> beisner: jamespage. Ah that makes more sense. I'll try and take a look today
[19:03] <beisner> thedac, first - happy sprinting! :-)   2nd, i've got that sync'd into a couple of charms and testing where it was known failing w/out.
[19:04] <thedac> great
[19:07] <beisner> thedac, but plz do review that c-h change if you've got cycles
[20:27] <magicaltrout> hmmmmmm!
[20:27] <magicaltrout> maybe I should enhance my DC/OS mesos talk and head over to MesosCon
[20:27] <magicaltrout> http://events.linuxfoundation.org/events/mesoscon-europe/program
[20:32] <magicaltrout> http://events.linuxfoundation.org/events/linuxcon-europe
[20:32] <magicaltrout> and linuxcon \o/
[20:34] <lazyPower> magicaltrout - indeed you should!
[20:48] <marcoceppi> magicaltrout: hey, you've got a bunch of instances running for a while in cdp, do you need them still?
[20:50] <magicaltrout> juju status says I've got 1 failed node
[20:50] <magicaltrout> anything open to me marcoceppi tear it down
[20:50] <marcoceppi> magicaltrout: ack, there were leaks in earlier betas, will purge
[22:07] <anops> Hi
[22:08] <anops> I am unsure if juju is the right thing for me. I mainly do research and each project requires a custom and usually complex environment with a lot of dependencies. It's very important however to communicate, share and reproduce my environment
[22:09] <anops> with fellow researchers and to eventually deploy it to a server
[22:10] <anops> how can I create a custom juju app receipe/image/solution or however you call it? Do you think juju is the right thing for me? I run these projects on my local laptop.
[22:10] <magicaltrout> anops: depends, if the charms you require are available or you're willing to build it can be very helpful in that regard
[22:11] <anops> I would most likely need to build it, I work on machine-learning and web-development projects
[22:11] <magicaltrout> you can build a redeployable system that would work the same on your laptop or in the cloud, or on someone elses laptop assuming their running the same OS
[22:12] <magicaltrout> a charm is a single service, you're basically describing a bundle
[22:12] <anops> how complicated is it to build a juju app-solution... eh charm?
[22:12] <magicaltrout> https://jujucharms.com/openstack-base/bundle/42 bit like that ;)
[22:13] <magicaltrout> depends what the apps are and what they have to do, can you give me a clue?
[22:17] <anops> For example a topological analysis platform for data, anomaly detection via a deep learning framework, or just classic data-analyis. On the other hand there are isolated little projects involving haskell,java,c,c++ etc. each most preferrably in a container to keep dependencies isolated from the host syste
[22:17] <magicaltrout> okay well Juju has a new concept where you can use LXD on your local system
[22:18] <magicaltrout> so instead of building docker images for each one, you use a vanilla Xenial/Trusty etc image
[22:18] <magicaltrout> and install your stuff on it when its being spun up.
[22:18] <magicaltrout> so you have enacpsulation of your server within an LXD image
[22:18] <magicaltrout> but without having messed around creating a bunch of docker images and pushing them up to dockerhub etc
[22:19] <magicaltrout> at that point the charms understand the concept of relations
[22:20] <magicaltrout> so if you join various deep learning components together, they can configure themselves and get themselves up and running without users configuring them directly
[22:20] <magicaltrout> which is what those lines depict in a bundle
[22:20] <magicaltrout> relationships between different charms
[22:20] <anops> That sounds great, but wouldn't that make it extremely complicated to get running? Especially when you have to work on a hard research project and don't have too much time
[22:20] <magicaltrout> dunno, thats a choice you have to make :)
[22:20] <anops> don't want to sounds lazy, but sometimes you just need get work done :)
[22:22] <anops> magicaltrout: do you have an example?
[22:22] <magicaltrout> example of what?
[22:22] <magicaltrout> a charm?
[22:23] <magicaltrout> http://bazaar.launchpad.net/~spicule/charms/trusty/pentahodataintegration/trunk/view/head:/reactive/pdi.py thats the code that maintains my pentaho data integration charm
[22:23] <magicaltrout> just controls the installation, which services are started et
[22:23] <magicaltrout> c
[22:24] <anops> So juju is essentially something like ansible/salt/chef?
[22:24] <magicaltrout> 165 lines of code so i can do "juju deploy pentahodataintegration" on my local server, AWS cloud or anywhere else that takes my fancy is pretty good bang for your buck i'd have thought
[22:24] <magicaltrout> yerp
[22:24] <magicaltrout> sorta :)
[22:25] <magicaltrout> chef etc are generally lower level
[22:26] <anops> I would get  my hands dirty with that, but where is the part that creates "the container" to run your pentaho instance?
[22:26] <magicaltrout> i just run 'juju deploy ...' and if my local juju setup is configured to do LXD it will build the container and deploy it on the fly
[22:27] <magicaltrout> which takes the best part of about 15 seconds
[22:27] <magicaltrout> https://demo.jujucharms.com/ or you can use the gui
[22:27] <magicaltrout> which does the same thing
[22:28] <anops> hmm, ok but I don't deploy unless it works. Does it on-th-fly create containers localy and remove them when there's a bug in the python code?
[22:28] <anops> It would be harder to manage if I have 20 containers and need to find out which one was the working one..
[22:28] <magicaltrout> in my code above you can see me setting states
[22:29] <magicaltrout>   status_set('maintenance', 'PDI Installed')
[22:29] <magicaltrout>     set_state('pdi.installed')
[22:29] <magicaltrout> stuff like that
[22:29] <magicaltrout> so your charm would detect a failed bootstrap and set the state to failed
[22:29] <anops> does that result in a zfs snapshot or a state in a state-machine where you can rollback to?
[22:30] <anops> ah
[22:30] <magicaltrout> the containers themselves will allow you to take zfs snapshots if you so desire
[22:30] <magicaltrout> if a machine enters a failed state you can tear it down, login and fix it and mark it resolved
[22:30] <magicaltrout> whatever floats your boat
[22:30] <anops> Is the best way to start creating a charm setting up server 16.04 on my laptop?
[22:31] <magicaltrout> yeah
[22:31] <magicaltrout> marcoceppi: whats the best way to get charm tools? :0
[22:31] <magicaltrout> apt-get install charm-tools i believe anops
[22:32] <anops> is it possible to create a container with a personal desktop that runs on tty1? I'd like to keep the core, personal and work seperated so that snapshots are more granular
[22:32] <magicaltrout> then charm-create <charmname>
[22:32] <anops> also more secure
[22:32] <magicaltrout> https://jujucharms.com/u/kwmonroe/ubuntu-devenv/trusty/2
[22:32] <magicaltrout> something like that i suspect you want
[22:33] <magicaltrout> thats not GUI based but the idea is similar
[22:33] <magicaltrout> https://jujucharms.com/ubuntu/0 or that
[22:33] <anops> magicaltrout: oh you mean I should put the ubuntu-desktop into a charm too? I thought about lxc..
[22:34] <magicaltrout> you can do it direct in lxc
[22:34] <magicaltrout> lxc launch xenial
[22:34] <magicaltrout> or something like that
[22:34] <magicaltrout> lxc launch trusty
[22:34] <magicaltrout> depends what you want to bootstrap
[22:35] <magicaltrout> you might have some interesting issues with gfx though, although I did some ssh tunelling successfully
[22:36] <magicaltrout> https://github.com/ustuehler/lxc-desktop or something like that
[22:36] <magicaltrout> https://www.stgraber.org/2014/02/09/lxc-1-0-gui-in-containers/
[22:36] <anops> cool,eactly what I need
[22:45] <magicaltrout> alright i need to run anops, you'll probably find some life in this channel if you need more questions answered, if not, I'll be back in about 9 hours ;)
[22:46] <anops> magicaltrout: have a nice day/night thank you very much for your great help!
[22:46] <magicaltrout> no problem
[22:47] <anops> I'm just looking into sandstorm.io for the web-app part, maybe that's the way to share these and juju for the heavy stuff like machine-learning
[23:05] <jhobbs> is there a way to use a "charm: " option in a bundle to get the latest version of the charm for the series being used in the deployment (default-series)?
[23:05] <jhobbs> like "charm: cs:nova-compute"
[23:06] <jhobbs> if my default-series is trusty i want that to get the latest trusty nova-compute charm
[23:06] <blahdeblah> Quick Q: is there an overview showing which versions of juju2 are in stable/proposed/devel?  Or an easy way to obtain this information without having the repositories enabled on my machine?
[23:17] <anops> blahdeblah: https://launchpad.net/juju-core maybe
[23:18] <anops> or https://jujucharms.com/docs/stable/reference-releases
[23:19] <blahdeblah> anops: Looked at the first one - couldn't see any reference to the ppas there, although I may need more coffee
[23:20] <anops> the milestone timeline graphic
[23:22] <blahdeblah> That does't appear to have anything to do with which version is in which ppa...
[23:24] <blahdeblah> Looks like comparing https://launchpad.net/~juju/+archive/ubuntu/stable https://launchpad.net/~juju/+archive/ubuntu/proposed & https://launchpad.net/~juju/+archive/ubuntu/devel is easiest, but only the last has juju 2 packages...