[12:33] <bac> hey rick_h_, let's talk about bug 1287977 when you get a chance
[12:33] <_mup_> Bug #1287977: searching for rabbitmq locks the GUI up until all 400 results are loaded and rendered <juju-gui:Triaged> <https://launchpad.net/bugs/1287977>
[12:33] <rick_h_> bac: sure thing, let me grab my headphones
[12:34] <rick_h_> bac: https://plus.google.com/hangouts/_/7ecpjmmfgnbo8cqqqaqelr0j90?hl=en
[13:02] <bac> rick_h_: confirmed my rolled days have been added back.  thanks.  #shouldnotbethishard
[13:03] <rick_h_> bac: cool, thanks for checking up and glas we got it squared away
[13:07]  * bac reboots
[13:17]  * frankban lunches
[13:32]  * bac trusty vm is being uncooperative
[13:34] <rick_h_> bac: did you get trusty to run charmworld? I hit PPA issues when I tried.
[13:34] <bac> rick_h_: yeah, i can run cw...when i can log in
[13:34] <rick_h_> gotcha
[13:34] <bac> right now after typing my password into the ui login it locks up.
[13:35] <bac> can get in via ssh
[13:35] <rick_h_> cool, will be curious to hear what you used for the ppas in the build when it's running better.
[13:35] <bac> would that be unity-greeter?
[13:35] <rick_h_> bac: oh! sec. I saw someone post asking for a vmware fusion help with X issues (well unity?)
[13:35] <bac> rick_h_: was that barry yesterday?  his issue was crashes under weird circumstances
[13:35] <rick_h_> bac:  https://twitter.com/pumpichank
[13:35] <rick_h_> oh, ok
[13:36] <bac> but he'll be the first person i bug...
[13:36]  * rick_h_ tries it out with non-unity
[13:36] <bac> wait, how's that?
[13:37] <rick_h_> I run Awesome, curious to see if it hits the same issue
[13:37] <rick_h_> I can get in now, pulling the latest updates and will try again
[13:38] <bac> this is probably ungood
[13:38] <bac> [   15.985841] type=1400 audit(1394199451.466:74): apparmor="DENIED" operation="open" profile="/usr/lib/telepathy/mission-control-5" name="/var/lib/lightdm/.config/libaccounts-glib/accounts.db" pid=2352 comm="mission-control" requested_mask="rw" denied_mask="rw" fsuid=110 ouid=110
[13:39] <rick_h_> yea
[13:40] <bac> there was an update for unity-greeter that was "held back" from apt-get update.  manually installing it.  may help, may fry everything.
[13:40] <bac> i've never understoon the 'held back' stuff
[13:41] <bac> s/understoon/understood/
[13:42] <bac> whoo hoo
[13:42] <bac> not only does it work, the desktop is now watermarked '14.04 LTS' -- that'd been bugging me!
[13:43] <rick_h_> hah cool
[13:46] <bac> rick_h_: so i'm back. if you want to talk about charmworld ppa's let me know.
[13:46] <rick_h_> bac: not right now, I'll bug you about it later
[13:46] <bac> good answer.  :)
[14:15] <hatch> rick_h_ yeah two qa's would be fine
[14:16] <rick_h_> hatch: cool, I'm working on one right now
[14:33] <bac> benji: any idea why matt's cw branch didn't land?  https://code.launchpad.net/~makyo/charmworld/charm-urls/+merge/209556
[14:33]  * benji looks
[14:34] <bac> i see nothing there.  will look at jenkins
[14:35] <rick_h_> bac: http://<IP_ADDRESS>:8080/job/charmworld-autoland-lxc/313/console
[14:35] <rick_h_> jenkins is not having a good day? failed autolanding permission issue?
[14:36] <bac> rick_h_: and then it just gave up this morning?
[14:36] <rick_h_> bac: well looks like it's been running over and over
[14:36] <rick_h_> http://<IP_ADDRESS>:8080/job/charmworld-autoland-lxc/
[14:36] <bac> yeah but stopped at 03:38Z
[14:36] <rick_h_> about every 10min
[14:37] <rick_h_> oh hmm
[14:37] <bac> nothing in 9 hours
[14:37] <rick_h_> yea guess so.
[14:37] <bac> maybe that's built in
[14:37] <rick_h_> abentley: ^ any insight on the lander there? it's very unhappy on the autoland script
[14:37] <rick_h_> wonder if something got changed recently
[14:37] <abentley> rick_h_: otp
[14:37] <rick_h_> abentley: rgr, thanks
[14:43] <hatch> rick_h_ so I don't get held up I'm going to land this branch and we can get a few deep qa's after it's all done
[14:43] <rick_h_> hatch: rgr
[14:44] <hatch> only one more to go
[14:44] <hatch> *squeeee*
[14:45] <hatch> of course it's the biggest and most complicated lol
[14:45] <rick_h_> saved the best for last!
[14:45] <hatch> oh wait no there are two left
[14:45] <hatch> service relation and service overview
[14:46] <hatch> relation should be easy
[14:46] <hatch> famous last words!
[14:46] <rick_h_> hah
[14:48] <bac> rick_h_: the MP did not have an approved revid.  i've set it now.  can't get a build to kick off, though.
[14:49] <bac> abentley: jenkins for charmworld gave up and stopped processing jobs about 11 hours ago.  ideas on how to get it going again?
[14:49] <abentley> bac: otp
[14:49] <bac> np abentley.  ping me when you've got a sec.
[14:50] <benji> bac: I just added an approval since one was pending.  I think that'll get the bot to land the branch.
[14:50] <bac> benji: it looks like it got angry with us and now is on strike
[14:51] <benji> heh
[14:51] <benji> this should let it land once the scabs are bussed in
[14:56] <hatch> apparently you have to be careful what you search for on G+
[14:56] <rick_h_> hatch: s/G+/internet
[14:56] <hatch> lol - I was definitely not expecting NSFW photos when searching 'black pug'
[14:57] <bac> benji: i manually kicked off a build.
[14:57] <benji> k
[14:57] <luca> rick_h_: how comes the coming soon simulator doesn't show the landscape restart or security updates on the service block?
[14:58] <rick_h_> luca: ummm, I don't know. Should they? /me isn't up on the latest in landscape integration UI design.
[14:58] <abentley> rick_h_, bac: pong
[14:59] <bac> abentley: i figured out how to manually kick off a jenkins build.  will follow up if it fails again.
[14:59] <abentley> It looks like it's trying to merge charmworld into itself.  Also that it's trying to merge in a revision that does not exist.
[14:59] <bac> abentley: 314 was my mistake
[14:59] <abentley> bac: Okay, I'll leave it with you for now.
[15:00] <luca> rick_h_: I'm not sure, last I knew the restart and sec update should show on the service block, can anyone confirm if they show in the real environment?
[15:04] <benji> frankban: I think I've taken a wrong turn on this branch, do you have a minute to chat?
[15:04] <rick_h_> luca: so they show in the inspector with links for upgrade and reboot in the unit list
[15:04] <frankban> guihelp: I need two reviews (no QA) for https://github.com/juju/juju-gui/pull/167 . anyone available? thanks!
[15:05] <rick_h_> luca: I don't see anything on the service block
[15:05] <hatch> frankban on it
[15:05] <rick_h_> frankban: will look in a sec
[15:05] <frankban> benji: sure, give me a minute (coffee)
[15:05] <rick_h_> luca: so I'm not sure about the block level. It seems it got moved to units?
[15:05] <frankban> hatch, rick_h_ thanks
[15:06] <luca> rick_h_: last I knew it was in both places, no worries if it's moved :)
[15:06] <rick_h_> luca: yea trying to glance through the code quickl
[15:13] <frankban> benji: hangout?
[15:14] <benji> frankban: sure, I'll make one
[15:16] <benji> frankban: https://plus.google.com/hangouts/_/7acpiae8apl54n76eg0e0mr1ak?hl=en
[15:28] <frankban> hatch: interesting: is passing context to map more js idiomatic than self = this?
[15:29] <luca> rick_h_:  also, there are no hover states for the inspector
[15:32] <hatch> frankban so the difference is because the compiler has to keep the outer scope in memory because it's referencing that variable. If you pass it in, internally it binds the method to that context so it can properly clean up the wrapping method
[15:33] <frankban> hatch: makes sense
[15:33] <hatch> it's a pretty trivial performance gain hah, but it cleans the code up a bit imho
[15:33] <hatch> the compiler can then 'compile' the callback fn as well which can lead to some really big improvements in a loop
[15:36] <rick_h_> luca: k, sounds like perfect bugs to file for a new starter to hack on
[15:37] <luca> rick_h_: I'll file away
[15:38] <bac> benji: sadness http://<IP_ADDRESS>:8080/job/charmworld-autoland-lxc/315/console
[15:40] <benji> "npm ERR! Error: UNKNOWN, unknown error
[15:40] <benji> that's an odd error
[15:42] <rick_h_> benji: hmm, wonder if that's old npm issue
[15:42] <rick_h_> benji: we had to update npm in the ppa because of npm no londer allows downloading on the self-signed certs
[15:43] <rick_h_> forgot charmworld used npm at all
[15:43] <benji> the fact that it is the very first npm install in the run (as far as I can tell from scanning the output) suggests it might be
[15:43] <rick_h_> benji: yea, when we got it on the gui side we had a more helpful error
[15:43] <rick_h_> benji: but it's a know recent change
[15:44] <rick_h_> known that is
[15:56] <bac> jujugui meeting in 4
[15:57] <bac> benji: my irc client dropped out.  did you have ideas on the jenkins failure?
[15:57] <benji> bac: Rick and I think npm's recent global breakage because of the cert re-issue is a good first thing to check
[15:58] <benji> ...especially because the failure is the first time in the run that an npm package is installed
[15:59] <bac> benji: ok, perhaps we can chat after the meeting
[15:59] <benji> k
[16:00] <benji> oh, meeting
[16:03] <bac> jujugui: review of charm-proof - https://codereview.appspot.com/72170043
[16:06] <hatch> jujugui call in 9
[16:06] <hatch> jujugui call in 3
[16:07] <bac> whoa
[16:07] <rick_h_> jujugui call in 10
[16:07] <bac> irc has gone crazy for me.  just getting a lot of queued messages
[16:07] <rick_h_> jujugui call now
[16:07] <Makyo> Same
[16:09] <hatch> woah that was a lag lol
[16:11] <hatch> someone is probably DDOSing freenode again
[16:13] <luca> Makyo: hatch frankban benji bac rick_h_ https://docs.google.com/a/canonical.com/file/d/0B7XG_QBXNwY1SjJ5anNYblJva1E/edit
[16:13] <luca> Makyo: hatch frankban benji bac rick_h_ https://docs.google.com/a/canonical.com/file/d/0B7XG_QBXNwY1N2NHXzI5d0NBZ2M/edit
[16:14] <hatch> jujugui lf a really quick review/qa https://github.com/juju/juju-gui/pull/168
[16:14] <hatch> luca fyi `jujugui` pings the whole channel :)
[16:14] <luca> hatch: oh
[16:14] <hatch> well - we all have it set up to do so
[16:14] <luca> jujugui awesome
[16:14] <luca> did it work?
[16:14] <hatch> :)
[16:14] <hatch> yep
[16:15] <luca> I see
[16:15] <hatch> ugh more damn inspector design changes
[16:15] <hatch> lol
[16:15] <luca> lol
[16:15] <luca> I feel you
[16:15] <hatch> haha
[16:15] <hatch> I kind of wish the swooshes were part of the design
[16:16]  * hatch I like the new design though...looks 'tighter'
[16:16] <luca> thanks :)
[16:16] <hatch> and for whatever reason I love the deploy bar
[16:16] <hatch> lol
[16:17] <luca> haha
[16:17] <luca> it might change visually, spencer is working on the hard task of actually making it look good
[16:17] <hatch> really? I think it looks great now haha
[16:17] <hatch> this is why I'm not a designer I suppose :)
[16:17] <luca> ha
[16:18] <luca> most probably :P
[16:18] <luca> hehe
[16:18] <frankban> hatch: looking at your branch
[16:18] <hatch> frankban thanks!
[16:19] <frankban> bac: https://codereview.appspot.com/72170043 returns "No issue exists with that id (72170043)"
[16:19] <hatch> luca if I could....I'd like something which maybe pointed the 'configuration' button out to the user in the first panel
[16:20] <hatch> Just so they wan't like 'where do I configure this?'
[16:20] <hatch> oh man I can't type
[16:20] <hatch> just so they don't say 'where do I configure this?'
[16:20] <hatch> :)
[16:20] <hatch> or we could open it by default
[16:20] <hatch> that would probably be the best
[16:20] <luca> has Anyone Really Been Far Even as Decided to Use Even Go Want to do Look More Like?
[16:21] <hatch> lol
[16:21] <hatch> I'm actually laughing
[16:21] <hatch> ohh
[16:21] <luca> :)
[16:21] <hatch> English is hard
[16:21] <luca> haha
[16:21] <luca> when a user deploys a charm from the store
[16:21] <luca> the config panel will be open
[16:22] <hatch> +1
[16:22] <luca> they won't see the status panel unless they navigate to it or close and open the service
[16:22] <hatch> awesome
[16:22] <luca> but we want to add a little on boarding to the status panel to clue people in on what happens once they deploy, since some people may never deploy
[16:22] <hatch> yep that's a good idea
[16:29] <hatch> frankban sorry I totally forgot to do something in that branch
[16:30] <frankban> hatch: also have you seen the selenium failure?
[16:30] <hatch> yeah I did
[16:30] <hatch> I wonder why it's crashing so often
[16:32] <hatch> oh that's why I missed it....it's not even in trunk
[16:32] <hatch> heh
[16:35] <hatch> rick_h_ regression in master https://bugs.launchpad.net/juju-gui/+bug/1289469
[16:35] <_mup_> Bug #1289469: Remove relation button missing from relations tab in inspector <juju-gui:New> <https://launchpad.net/bugs/1289469>
[16:36] <rick_h_> hatch: k
[16:36] <hatch> rick_h_ maybe what we need to do is create a master list of functionality and interactions so before we do a release we can check each one as well as doing the exploratory qa
[16:42] <rick_h_> hatch: ugh, qa checklist... hatch well let's start by adding a test
[16:42] <rick_h_> it's the righ thing, bug escaped, write a test, fix it
[16:43] <hatch> rick_h_ well no it's not really a qa checklist it's more like 'these are the things that our application does' does it still do that
[16:43] <hatch> I mean...yes totally need tests :)
[16:44] <hatch> but this is more of a higher overview
[16:44] <rick_h_> hatch: right, so the thing to look at is qa vs tests. A lot of qa we can automate with functional tests
[16:44] <rick_h_> vs a checklist to run down
[16:44] <rick_h_> I do think we need to do more functional tests, but this one seems like just a bug
[16:44] <rick_h_> something we can test for
[16:44] <hatch> I think as we modularize things more then the tests will become a lot easier to write as well
[16:48] <rick_h_> hatch: definitely
[16:52] <rick_h_> hatch: frankban they released some new stuff with a new sauce connect and such in the last week. I wonder if we're hitting something in their upgrade
[16:52] <hatch> hmm well I hope not
[16:52] <hatch> :)
[16:53] <rick_h_> yea, not sure.
[17:10] <rick_h_> sorry for the delay frankban
[17:10] <rick_h_> frankban: +1 thanks for the machine view updates there.
[17:10] <frankban> rick_h_: thank you!
[17:15]  * rick_h_ runs for some grub
[17:35] <hatch> so confused...
[17:35] <rick_h_> look for the turtles
[17:35] <rick_h_> they'll lead you all the way down
[17:36] <hatch> we have events here which don't attach to anything or have callbacks
[17:36] <hatch> lol
[17:36] <hatch> how the heck didn't these throw errorsx
[17:36] <hatch> haha
[17:52] <marcoceppi> jcsackett: got a question about the queue and charmworld api
[17:53] <marcoceppi> jcsackett: as in, is the queue exposed int he charmworld api
[17:53] <marcoceppi> queue being review-queue
[17:53] <jcsackett> marcoceppi: i do not believe so, no.
[17:53] <marcoceppi> jcsackett: how hard would it be to have it added to the api?
[17:53] <marcoceppi> and who would I have to bug to get that worked lined up?
[17:54] <jcsackett> marcoceppi: i don't know off the top of my head; i haven't touched API code in some time.
[17:54]  * marcoceppi bugs rick_h_ ^
[17:54] <jcsackett> marcoceppi: to what end?
[17:55] <marcoceppi> jcsackett: I want to be able to get the charm review items (not the proof or au questions) as an api endpoint. So created, last updated, status, and link to review item
[17:55] <jcsackett> marcoceppi: i figured that; i'm just curious what you want to consume said endpoint.
[17:56] <rick_h_> marcoceppi: hmm, not sure at the moment. You can file the bug and we can see. We'd be happy to help mentor/review some code that did what you guys need :(
[17:56] <rick_h_> :)
[17:56] <rick_h_> that is
[17:57] <hatch> nananananananananana bug man....submitting bug man
[17:57] <marcoceppi> jcsackett: so, to start there's a charm review command in charm-tools that poorly re-implements the lp code in the review queue, then also some automation bits for the juju solutions team that reads data from teh queue
[17:58] <marcoceppi> rick_h_: I was hoping it would be a low level of effort, I'm happy to hack on it since it really only helps me
[17:58] <jcsackett> marcoceppi: ah, dig.
[17:59] <rick_h_> marcoceppi: ok, not a problem. We're currently under a crunch to get stuff ready for bundles announcement next week but can try to help look at it after that.
[17:59] <bac> frankban: (if you're still around) sorry, that RV got deleted due to chunk mismatch.  MP at https://code.launchpad.net/~bac/charm-tools/bundle-proof-warnings/+merge/209754
[17:59] <marcoceppi> rick_h_: cool
[18:00] <bac> marcoceppi: could you have a look at this extension to charm-proof? https://code.launchpad.net/~bac/charm-tools/bundle-proof-warnings/+merge/209754
[18:00] <marcoceppi> bac: can do, I need to finish this review for the same bundle announcment but after that (say, 30 mins) I can take a look
[18:00] <bac> marcoceppi: cool.  will take you just a jiffy.
[18:01] <marcoceppi> bac: actually, this lgtm, I'll pull and make test to verify
[18:01] <marcoceppi> bac: there will likely be a 1.2.10 release tonight of charm-tools that has this and the other fixes you submitted earlier
[18:01] <Makyo> jujugui review/QA for minor branch: https://github.com/juju/juju-gui/pull/169 (QA: drag and drop a charm with inspector open, ensure that there are no 'undefined' errors)
[18:01] <bac> marcoceppi: thanks.  note that the version of charmworld to generate those warnings isn't deployed yet, but proof doesn't care
[18:02] <marcoceppi> bac: right, cool, thanks for getting this in before that's live o/ appreciate it
[18:02] <rick_h_> Makyo: woot will look
[18:06] <hatch> what was the documentation make command to clear out the 'non documented' functions?
[18:06] <hatch> since they are now documented
[18:06] <hatch> make undocumented?
[18:06] <hatch> will try
[18:07] <Makyo> Yeah
[18:09] <hatch> 15 test failures for the overview switchover
[18:09] <hatch> not baaad
[18:11] <rick_h_> Makyo: thanks for that, not sure I would have seen that. The traceback was off a different area if I recall
[18:11] <rick_h_> Makyo: that's one big method, maybe we can break it up some to help down the road
[18:12] <Makyo> rick_h_, agreed.  Everything was 'working' in our code, it was d3 trying to assign attributes with undefined values through a callback.
[18:13] <rick_h_> Makyo: yea, I mean the UI worked just dumped errors. So it was a strange one to start with
[18:15] <hatch> my keureg machine broke :'-(
[18:16] <rick_h_> good, get some real coffee :P
[18:16] <hatch> but then I have to leave the house
[18:16] <hatch> IT"S COLD OUT THERE!
[18:16] <rick_h_> http://www.amazon.com/Primula-Aluminum-Stovetop-Espresso-Coffee/dp/B001J1L59E/ref=sr_1_2?ie=UTF8&qid=1394216192&sr=8-2&keywords=moka+pot
[18:16] <rick_h_> still make it at home
[18:16] <hatch> oh I'm not an espresso fan
[18:16] <hatch> drip or nothing
[18:17] <hatch> :)
[18:17] <rick_h_> ugh
[18:17] <hatch> :D
[18:18] <hatch> 9 failures.....
[18:18] <hatch> oo this one hasn't gone back up after I've fixed ones
[18:18] <hatch> this is unprecedented I'm not sure what to do...lol
[18:23] <mbruzek_> rick_h_, I see that my bug was indeed a duplicate.  Sorry about that.  I want to assure you I did search before I created it.
[18:23] <rick_h_> mbruzek_: it's all good
[18:24] <rick_h_> mbruzek_: we appreciate the feedback. I just want to keep the discussions together for ease of everyone working on things
[18:24] <mbruzek_> Yeah that makes sense, I wish I would have found it in my search.
[18:24] <rick_h_> don't worry about it. Can't know about all the bugs in all the projects and sometimes search-fu fails
[18:24] <rick_h_> appreciate you filing
[18:24] <mbruzek_> Really?
[18:25] <mbruzek_> I would imagine this issue has been talked about before.  I hope it did not reopen a long dead discussion.
[18:25] <rick_h_> yea, and deisgn is aware of it. I think most of us agree with you. The thing was that sometimes design is pulling standards from other places.
[18:26] <rick_h_> phone design, other website, and it takes some tweaking to get right
[18:26] <rick_h_> more people saying it's confusing helps us look into it more
[18:26] <mbruzek_> Sure and on the bug I opened I figured you already had a discussion and made a decision but I just didn't know where it was written down
[18:26] <mbruzek_> rick_h_, understood.
[18:27] <rick_h_> well in that bug luca mentions that they're working on it
[18:27] <rick_h_> so until they figure it out and do some testing/etc we're running with what we have
[18:27] <mbruzek_> Ok
[18:27] <mbruzek_> Have a good weekend rick_h_
[18:27] <rick_h_> you too
[18:27] <hatch> http://i.imgur.com/upi6iwF.png
[18:27] <hatch> bahahaha
[18:31] <hatch> jujugui lf a review on https://github.com/juju/juju-gui/pull/170 the final viewlet to view diff
[18:37] <bac> rick_h_: i think i know what is going on with search
[18:38] <bac> our input terms are tokenized.  so 'rabbitmq-server' gets split into parts and we return everything with any reference to 'server'
[18:39] <bac> rick_h_: http://paste.ubuntu.com/7051463/
[18:43] <rick_h_> bac: oooohhhhhhhhh
[18:44] <bac> do we really want stemming?
[18:44] <rick_h_> bac: wow, ok. What about the revisions ?
[18:44] <rick_h_> bac: well it was something requested yes. because of things like this. rabbitmq<enter>
[18:44] <bac> don't think revisions is an issue
[18:44] <rick_h_> bac: the dual cinder int he results for rev 17 and 19?
[18:45] <hatch> it shouldn't be returning the server ones unless they also match rabbit
[18:46] <bac> rick_h_: here are the charms and bundles returned by a search for 'rabbitmq-server' http://paste.ubuntu.com/7051502/
[18:46] <rick_h_> hatch: hmmm, so tokenize but treat them as an AND vs an OR?
[18:46] <rick_h_> bac looking
[18:46] <hatch> rick_h_ yeah
[18:46] <rick_h_> bac: right, so line 40/41
[18:47] <bac> so, yeah, cinder returns multi versions of the official charm.  other packages do not.  i missed that.
[18:47] <hatch> rick_h_ but it also needs the ability to backup....say if there are no matches for 'rabbitmq-server' but there is for 'rabbit' then it should show those (imho)
[18:47] <rick_h_> yea, it's not going to help us a ton
[18:47] <rick_h_> the revisions stuff
[18:48] <rick_h_> bac: do we get weighted scores back from search?
[18:48] <rick_h_> bac: can we tweak the threshhold on something to help cut out some of the noise?
[18:48] <bac> yes
[18:48] <rick_h_> or maybe there's a field we're weighing too highly
[18:48] <rick_h_> to get back so many 'server' results
[18:49] <bac> we can't know when we tokenize which of x,y,z is creating noise
[18:49] <hatch> maybe we can just use the google search thingy
[18:49] <hatch> :P
[18:49] <hatch> bac it should query on 'rabbitmq' 'server' 'rabbitmq-server'
[18:49] <bac> but i don't think this is due to a recent change.
[18:49] <rick_h_> bac: what do you think of checking on the revision issue (that seems like a bug bug) and maybe there's some suggestion for search we can add to help with the situation
[18:49] <hatch> then we should be able to weight them properly
[18:50] <rick_h_> bac: yes, it seems it's not directly a regression but getting more charms and search working too well :)
[18:50] <bac> hatch: full string gets more weight but you can't differentiate between the others
[18:50] <rick_h_> hatch: ES is doing that tokenizing, not us
[18:50] <rick_h_> we should be able to see if the scores cut off nicely at some point though
[18:50] <hatch> hmm I've never worked with ES....last project was with Solar and we were able to do what i mentioned
[18:51] <hatch> Is this a limitation of ES? because ES and Solar are both based on Lucene no?
[18:51] <rick_h_> and maybe adjust the weight of description or something that's catching so much 'server'
[18:51] <bac> ES is lucene based
[18:51] <rick_h_> hatch: solr and it depends on what you do. Right now, the tokenizing/scoring is done in ES land
[18:52] <hatch> hmm - I don't know enough about ES to say, but it sounds like we 'should' be able to do this
[18:52] <hatch> would kind of make for a crappy search tool if you couldn't tokenize and weight heh
[18:52] <bac> yes, i should hope we should
[18:53] <hatch> I'm sure there is some 800 page book you could read on it bac ;)
[18:53] <bac> i'll dig into the ES docs
[18:53] <rick_h_> heh yea
[18:53] <rick_h_> bac: ok, so you're ok moving forward then?
[18:53] <bac> there are too many 800 page books
[18:53] <hatch> haha :)
[18:53] <bac> this industry needs more 80 page books
[18:54] <bac> i remember looking through the index of a 1000+ page book on HTML or CSS or something and there was reference to the Dining Philosophers.  stupid editors.
[18:55] <hatch> moar pages = better right? :P
[18:55] <bac> must be
[18:56] <hatch> rick_h_ have a second for a quick hangout?
[18:56] <rick_h_> sure
[18:56] <hatch> https://plus.google.com/hangouts/_/76cpisv6qllekpbpm7ialobo28?hl=en
[19:03] <benji> bac and hatch: the _get_text_query method in charmworld/search.py generates queries with weights for the different fields; that might be a good place to start
[19:04] <hatch> Oh I don't really know enough about the ES functionality to contribute, I was just commenting on what we 'should' be able to do coming from my experience on a project with solr
[19:05] <benji> hatch: it sounds like you are now our ES expert
[19:05] <hatch> hahahaha
[19:05] <rick_h_> woot!
[19:06] <hatch> I'll add that on top of my Python and Go training
[19:06] <hatch> NO BIG DEAL
[19:06] <hatch> jujugui I still need a review on https://github.com/juju/juju-gui/pull/170 :)
[19:06] <rick_h_> hatch: working on it
[19:06] <hatch> awesome thanks
[19:07] <rick_h_> it's in one of these tabs here
[19:26] <rick_h_> it so much nicer that lxc containers come up in the same IP address each time. this VM keeps changing it's ip
[19:27] <hatch> the vagrant one keeps it's ip, my lxc's on my juju box changes the ips every time
[19:30] <hatch> I'm going to go grab some lunch
[19:35] <Makyo> Alright, that branch merged. Headed out.  Have a good weekend, see you all Tuesday.
[19:35] <rick_h_> Makyo: have a good weekend!
[20:14] <hatch> so I suppose I Should keep moving on this inspector business
[20:17] <rick_h_> hatch: :)
[20:36] <hatch> rick_h_ are you going to need me for UDS next week?
[20:36] <hatch> or are you handling it?
[20:36] <hatch> I just need to know if I should go get a spray tan and stuff.....
[20:37] <hatch> bahahaha
[20:37] <rick_h_> hatch: well I wanted to see if I could get a volunteer
[20:37] <rick_h_> hatch: I proposed we do a bundle/quickstart demo session
[20:37] <rick_h_> and answer any questions and such there
[20:37] <hatch> hmm well I'm stuck in osx land so I'm probably not the best person to demo
[20:37] <rick_h_> k
[20:37] <rick_h_> well I'll get someone and if I can't I'll do it
[20:37] <hatch> I can definitely be there to answer questions and the like
[20:38] <rick_h_> but my goal will be to get someone :)
[20:38] <hatch> I don't think a single proc is enough to stream a hangout :)
[20:38] <rick_h_> hah
[20:43] <rick_h_> ok, going to head out for the weekend. everyone have fun
[20:43] <rick_h_> thanks for all those views this week hatch
[20:43] <hatch> no problem, have a good weekend
[21:59] <hatch> jujugui hey anyone around still?
[21:59] <rick_h_> hatch: kinda
[21:59] <rick_h_> what's up?
[22:00] <hatch> oh just wondering if I am going to get a review on the card I'm working on :)
[22:00] <hatch> we put it at a day and it took me 2h so it'll catch me up :D
[22:00] <rick_h_> hah awesome
[22:00] <rick_h_> the base class?
[22:00] <hatch> yeppers
[22:00] <hatch> the others will take more time
[22:00] <rick_h_> ok cool
[22:00] <hatch> but this one is only a few lines heh
[22:00] <hatch> sometimes I love YUI
[22:01] <rick_h_> well take what we can get after all the bugs you've filed :P
[22:01] <hatch> haha
[22:01] <hatch> the inspector tests are going to be a ton of work once the setup switches to these classes I think
[22:02] <hatch> because I'm guessing they will all need to be rewritten.....hopefully they all use a single 'create inspector' method :)
[22:07] <hatch> rick_h_ it's super small https://github.com/juju/juju-gui/pull/171 :)
[22:07] <rick_h_> I guess I can put off laundy for a few more min :)
[22:08] <hatch> haha
[22:17] <rick_h_> hatch: hangout? I'm confused on two points
[22:17] <hatch> sure
[22:17] <hatch> I was chasing down your comments with my own heh
[22:17] <rick_h_> https://plus.google.com/hangouts/_/7ecpionjjtqfqdj7p7d097uc5g?hl=en


[00:00] <JontheEchidna> ah, that bug should be fixed in kubuntu 10.04
[00:00] <ejat> JontheEchidna: ok .. thanks ..
[00:00] <JontheEchidna> turning of translations for root should fix that
[00:00] <JontheEchidna> but that's a bit not nice :(
[00:01] <ejat> ic ..
[00:01] <ejat> is that a temp fix to that bugs ?
[00:02] <JontheEchidna> yeah
[00:02] <JontheEchidna> a real fix is in the software-properties-kde in 10.04
[00:03] <ejat> JontheEchidna: r u using lucid already ? :)
[00:03] <JontheEchidna> yeah :)
[00:04] <Lex79> ejat: me and JontheEchidna updated to Lucid when karmic was released :D
[00:05] <ejat> Lex79: i do it last time before karmic release .. ...
[00:05] <ejat> now my projects end .. thinking to upgrade to lucid next week :)
[00:05] <Lex79> :)
[00:05] <ejat> any big issues in lucid b4 i upgrade ? :)
[00:06] <JontheEchidna> not that I can recall. things have smoothed out
[00:06] <ejat> the most important is working with projector + krandrtray :)
[00:06] <ejat> JontheEchidna: c00l .. so no issue for me to upgrade :)
[00:07] <ejat> \0/
[00:07] <ejat> how about suspend n hibernate ?
[00:07] <JontheEchidna> let me see :P
[00:07] <ejat> JontheEchidna: :)
[00:08] <ejat> JontheEchidna: btw .. if ya dont mind asking .. will kde/kubuntu support thinkpad function key? :)
[00:09] <ejat> since in ubuntu all keys working out of the box .. just wondering if in kubuntu it also can work flawlessly .. ;p
[00:12] <JontheEchidna> works for me, your mileage may vary
[00:12] <ejat> wb JontheEchidna .. r u trying the suspend n hibernate ?
[00:12] <JontheEchidna> suspend
[00:12] <ejat> ok .. thanks
[00:13] <ejat> JontheEchidna: btw .. if ya dont mind asking .. will kde/kubuntu support thinkpad function key? :)
[00:13] <ejat> since in ubuntu all keys working out of the box .. just wondering if in kubuntu it also can work flawlessly .. ;p
[00:13] <JontheEchidna> dunno
[00:13] <ejat> its ok ..
[00:14] <ejat> anyway .. thanks for trying it for me .. either next week before the alpha3 release
[00:16] <Lex79> good, I need kleo_export.h to build kopete-cryptography, but it's in not-installed in kdepim :(
[00:19] <Lex79> btw kdepim-dev is empty
[02:48] <verbalshadow> is koffice-kde4 broken, rather krita-kde4 broken for anyone else?
[05:57] <shadeslayer> any triagers around?
[07:26] <apachelogger> JontheEchidna, Lex79: dpkg --compare-versions 4:2.0.3-kde4.4.0-0ubuntu1 gt 4:2.0.3really2.0.2-kde4.4.0-0ubuntu1; echo $?
[07:26] <apachelogger> when in doubt :)
[07:40] <markey> huhu apachelogger
[07:43] <apachelogger> ahoy markey
[08:06] <Xand3r> ahoy apachelogger
[08:10] <apachelogger> hoy Xand3r
[09:06] <Nightrose> apachelogger: update just killed my session for the 3rd time in 2 days :(
[09:07] <apachelogger> Nightrose: final kill that should have been
[09:07] <Nightrose> ok
[09:07] <Nightrose> hopefully
[09:07] <Nightrose> cause that's no fun tbh :(
[09:07] <apachelogger> postrm (the script responsible for all the killery) is used from the old package, so that last kill was necessary to get the new postrm that does not kill everything in ;)
[09:08] <Nightrose> i see
[09:08] <apachelogger> otherwise I would have to hack up the preinst script of the other thingy manually mangling the postrm script of the other thing, which is kind of dangerous to just think about :)
[09:17] <markey> aaaargs
[09:17] <markey> HARALD
[09:17] <markey> apachelogger: latest upgrade crashed my whole desktop
[09:17] <markey> used Synaptic
[09:17] <markey> same happened to Mamarok
[09:17] <Mamarok> markey: read above
[09:18] <markey> ah
[09:37] <apachelogger> JontheEchidna: I really think that you should use this when calling own methods
[09:37] <apachelogger> in cpp it gets easily confusing otherwise IMHO
[09:45] <apachelogger> JontheEchidna: fixed the cpp kfi up a bit
[09:54]  * Sput never uses the this pointer for calling methods, except when technically required
[09:54] <Sput> and I also don't see that in others' code
[09:54]  * jussi01 waits for the crash
[09:55] <jussi01> mind you may take a bit to get, only got a 3g connection here.
[09:59] <apachelogger> Sput: oh well, from looking at other's misuse of C I  must conclude that "others" are no good example to go by ;)
[09:59] <Sput> apachelogger: in C++ you are not supposed to have global methods, so anything that's not called via another object *is* a local method
[10:00] <Sput> no need for the this pointer
[10:00] <Sput> if you really need global methods, use ::myMethod()
[10:00] <apachelogger> Sput: true, maybe I am just too much of a C wrapper these days
[10:00] <Sput> wasting precious bytes for writing this-> all over the place is unnecessary :)_
[10:01] <Sput> and C doesn't have this-> !
[10:01] <apachelogger> JontheEchidna: letz reimplement kfi in nicely C ontained asm
[10:02] <apachelogger> Sput: I know, I meant the fact that I find methods in cpp without object preceeding it awful looking
[10:03] <Sput> apachelogger: don't ever look at Qt, KDE or any other cpp code then :)
[10:07] <apachelogger> Sput: nah, I'll just spend the next semester implementing some wacko SVG app in cpp, that should straighten me up again ;)
[10:47] <Tm_T> gah, it's a nightmare to try to find ppa repositories
[11:19] <apachelogger> ScottK: if you could take a glimps at bug 477922
[11:19] <apachelogger> Tm_T: how very true
[11:34] <apachelogger> a|wen: ping
[11:34] <a|wen> apachelogger: pong
[11:34] <apachelogger> a|wen: you were looking into iso mounting, werent you?
[11:37] <a|wen> apachelogger: jup; the best of existing options i could find is kfuseiso (but it only works for konqueror), so i'm thinking about simply going with some servicemenu shortcuts for it instead
[11:37] <apachelogger> a|wen: as long as we can get bugs fixed ... bug 66508 please :)
[11:37] <apachelogger> a|wen: why does kfuseiso only work with konqueror btw?
[11:41] <a|wen> apachelogger: it registers as a special protocol, and for some reason this is still only supported in konqueror
[11:43] <a|wen> apachelogger: I've added some service-menu shortcuts which makes sure to do things the same way as kfuseiso, so it works in dolphin (with less features) and mounted isos can then be seen and viewed in konqueror as if it was done using kfuseiso
[11:44] <a|wen> apachelogger: we could either distribute that as a whole; or it could be split up into two (having the service-menu entries by itself)
[11:46] <apachelogger> a|wen: your choice, if you think the servicemenu is enough, then we should just include that and save CD space :)
[11:46] <apachelogger> otherwise JontheEchidna has to go around porting python stuff to cpp and that is gonna be a bit more work than kfi ;)
[11:49] <a|wen> apachelogger: as dolphin is the default, not much point in having a lot of extra features in konqueror for this ... then comes the question if it should be a seperate source-package; and what we should name it (or if we simply should add it to dolphin and have it recommend fuseiso (needs MIR))
[11:50] <apachelogger> I still would just be rejecting the wish altogether :P
[11:50] <apachelogger> mount -o loop is not that much a hassle really :P
[11:50] <apachelogger> could do more useful things with the disc space
[11:51] <apachelogger> a|wen: kde-service-menu-iso or something probably is a good name
[11:53] <a|wen> apachelogger: heh; i have a wrapper for those as well (but some people don't like that they have to have admin access)
[12:28] <apachelogger> some people dont think that mounting a iso is a common task either :P
[13:13] <a|wen> apachelogger: true; well in any case http://revu.ubuntuwire.com/p/kde-service-menu-iso
[13:14] <apachelogger> a|wen: imho it should be non-native
[13:16] <apachelogger> a|wen: maybe -fuseiso is a better name after all ;)
[13:18] <apachelogger> a|wen: kde-open > xdg-open
[13:19] <apachelogger> descriptions exceed 80 chars/line
[13:27] <a|wen> then I should find somewhere to put it and all :P well i'll go make it non-native and change the name later today
[13:28] <a|wen> thx for the quick review
[15:53] <Guest65514> hello nixternal
[16:27] <apachelogger> Quintasan1: you were working on the input method stuff? ... http://primalcortex.wordpress.com/2010/02/12/kde-4-4-sc-kubuntu-backports-dead-keys-acentos-nos-caracteres-portugueses sounds like something related to that stuff
[16:31]  * apachelogger is wondering if this is positive for lucid too
[16:41] <jtechidna> apachelogger: confirming the kdm upgrade is fixed here
[16:42] <apachelogger> jtechidna: did you doubt my superior timelord intellect :P
[16:46] <jtechidna> nope
[16:46] <apachelogger> ok ^^
[16:51] <ryanakca> apachelogger: assuming you were asking if dead keys were broken with lucid's 4.4.0 ... not here, áőîñ :)
[16:51] <apachelogger> ryanakca: I hope you are using ibus as input method?
[16:52] <apachelogger> right click input field -> select im
[16:52] <apachelogger> should have ibus selected
[16:53] <ryanakca> apachelogger: Yes, looks like I am. Never played with it though...
[16:53] <apachelogger> ok
[16:53] <apachelogger> ryanakca: I'll prepare to revert the ibus-for-default-patch for karmic then
[16:54] <apachelogger> in case Quintasan1 chooses to agree with reverting
[17:10] <apachelogger> jtechidna: ping
[17:17] <shtylman> do we have something to manage encrypted folders in kubuntu?
[17:19] <apachelogger> I do not think so
[17:19] <apachelogger> unless KDE comes with something builtin
[17:19] <shtylman> apachelogger: gotcha
[17:27] <claydoh> eye <3 u guys!
[17:27] <claydoh> 4.4 is very nice
[17:49] <a|wen> apachelogger: http://revu.ubuntuwire.com/p/kde-service-menu-fuseiso <-- all points fixed; now it even uses cmake to install
[17:49] <Xand3r> moin apachelogger
[17:49] <mcguire> Hi everybody, I want to start to help development of Kubuntu specific software (programming, not packaging), could someone point me to the right documentation/wiki page that explain from where to checkout code, ...  I've only found https://wiki.kubuntu.org/Kubuntu/GettingInvolved/Development#Programming which is not really helpful in this case. Sorry if I missed something.
[17:59] <a|wen> apachelogger: have to run now; just leave a comment on revu if you find something missing
[18:16] <shtylman> ScottK: are we aware that our iso does not fit on a cd?
[18:32] <Lex79> apachelogger: thanks for the dpkg --compare-versions  command, it's usefull sometimes :)
[18:40] <mcguire> Riddell: esdaniel on #kubuntu tell me to ask you where/how to start with programming in Kubuntu specific software. Have you some time to help me?
[18:51] <jtechidna> apachelogger: pong
[18:52] <apachelogger> Lex79: yeah, it helps quite a bit with them fancy long version constructs :)
[18:52] <Lex79> :)
[18:53] <apachelogger> jtechidna: zander suggested that we get a group of kubuntu users to try koffice, any thoughts on that?
[18:54] <apachelogger> jtechidna: http://identi.ca/notice/21886573
[18:56] <apachelogger> mcguire: define programming kubuntu specific software?
[18:56] <apachelogger> usually I would suspect that you have some itch you want to scratch
[18:56] <apachelogger> it is not particular fun to get started with programming stuff someone else tells you to program ;)
[18:57] <jtechidna> apachelogger: would be quite interesting
[18:57] <jtechidna> sounds a bit like usability testing?
[18:57] <apachelogger> yes
[18:57] <apachelogger> though on a broarder scale than usability
[18:57] <apachelogger> I suspect
[18:58] <jtechidna> usability + functionality
[18:58] <apachelogger> also more casual
[18:58] <apachelogger> since we cannot really test specific cases at all
[18:58] <apachelogger> well, not not at all, but only limited ;)
[18:58] <jtechidna> so, we set up a wiki table, make an announcement on kubuntu.org and let the users go nuts?
[18:58] <jtechidna> mayhaps an announcement on kubuntu-users
[19:00] <mcguire> apachelogger: kubuntu specific software=developed for Kubuntu, not in Ubuntu nor KDE
[19:00] <claydoh> the forum would get more users than the puny amount in kubuntu-users :(
[19:01] <apachelogger> mcguire: yeah well, what in particular, what do you think is missing
[19:01] <claydoh> but I just answered a koffice -specific q in the list just now :)
[19:02] <apachelogger> jtechidna: I think we need more organization than that
[19:02] <apachelogger> claydoh: I expect we want to drain people from multiple resources
[19:03] <mcguire> apachelogger: no particular idea, I just just want to help other dev to create maintain and correct bugs in Kubuntu utilities, scripts and so on...
[19:03] <claydoh> drain away :) I think there would be good feedback from the few in there
[19:06] <apachelogger> jtechidna: how about ... prepare packages for all sorts of setups if necessary, prepare a questionnaire ("how did you like it? 0-4 points" "how did you like kword? 0-4 points" ...), aggregate general feedback in wiki or somewhere
[19:06] <apachelogger> jtechidna: use some forum for discussion and organization (in favor of mailing list as pointed out by claydoh)
[19:07] <apachelogger> claydoh: btw, how about that ppa policy discussion you started? ;)
[19:07] <apachelogger> mcguire: do you speak python?
[19:07] <claydoh> apachelogger: I forget that one, will look at it again
[19:08] <apachelogger> kthx
[19:10] <mcguire> apachelogger: I've read and patch some program in this language in my company, don't appear to be a complex language to learn
[19:12] <apachelogger> it isn't
[19:12] <apachelogger> to use it in a bug free way is impossible though ;)
[19:12] <apachelogger> mcguire: anyhow, you could look for bugs at launchpad
[19:13] <apachelogger> in the packages apturl and jockey and install-package and software-properties
[19:13] <shadeslayer> Xand3r: ping
[19:16] <mcguire> apachelogger: ok, I will look at these projects
[19:18] <apachelogger> omg jtechidna is not talking to me anymore
[19:19] <shadeslayer> apachelogger: maybe you went deaf? :P
[19:20] <apachelogger> more like blind in this particular case
[19:20] <apachelogger> claydoh: ping
[19:23] <claydoh> apachelogger: pong?
[19:24] <apachelogger> wanna be my new brainstorm buddy, jtechidna doesnt have any time for me :P
[19:24] <claydoh> apachelogger: I always do for you :)
[19:25] <apachelogger> claydoh: so, where do we organize that koffice review?
[19:25] <apachelogger> I suspect a wiki would be most appropriate
[19:26] <apachelogger> and I would go towards a KDE wiki because they support openid (hence one can login using launchpad stuff)
[19:26] <claydoh> a wiki , yes
[19:26] <apachelogger> question is ... techbase or userbase
[19:26] <apachelogger> former is probably more appropriate for organization, latter for execution?
[19:26] <claydoh> userbase? I dunno
[19:26] <claydoh> I need to look
[19:27] <apachelogger> or maybe use techbase for both
[19:27] <apachelogger> Nightrose: ping
[19:27] <apachelogger> claydoh: in any case I think using a kde wiki has loads of advantages over the ubuntu wiki
[19:27] <apachelogger> e.g. koffice devs can be included more easily in the preps
[19:27] <claydoh> apachelogger: true
[19:28] <claydoh> tho depending on the wiki, user input can be daunting for some folks
[19:28] <apachelogger> then again, usually when I try to use the powas of kubuntu to better kde I get bashed for treating kubuntu better or something ;)
[19:29] <apachelogger> claydoh: maybe get input via google spreadsheet or other means of questionnairing?
[19:29] <apachelogger> kind of depends on which information we want to aggregate I suppose
[19:29] <claydoh> apachelogger: that is key: what are we looking to find out?
[19:29] <apachelogger> how far along koffice is in terms of replacing ooo with it
[19:30] <apachelogger> i.e. how good does koffice match the home user use case at this point
[19:30] <claydoh> so doc import/export and usefulness
[19:30] <apachelogger> also overall usefulness vs. buggyness I suspect
[19:30] <claydoh> printing, etc
[19:30] <apachelogger> aight
[19:30] <apachelogger> the stuff a regular home user would want to do with his office
[19:32] <persia> Why not also the stuff a regular office user might want?
[19:32] <persia> (mostly the same, but usually involves more spreadsheets and presentations)
[19:32] <apachelogger> well
[19:33] <apachelogger> I would expect a regular office user to make use of advanced features ;)
[19:33] <apachelogger> though if indeed they do not, then koffice might also be an option there ;)
[19:33] <apachelogger> persia: there are very rough edges in presentation last I checked
[19:34] <apachelogger> spreadsheet and text processing are in pretty good shape for what a regular user wants to do
[19:34] <persia> At least from what I saw during the time I spent doing helpdesk in an office, most users in offices spend their time writing mail in Word, reading misformatted spreadsheets, and preparing presentations.  This may not have been a typical office, but I doubt it was that far off.
[19:34] <apachelogger> persia: yeah
[19:34] <persia> Ah, if presentation is still very rough, then yeah, probably not suitable for professional use (as it seems that sending presentations rather than documents or email has become popular)
[19:35] <apachelogger> though, as usual the question is if kubuntu actually targets business users :S
[19:35]  * persia inserts a missing "yet"
[19:35] <apachelogger> oh yeah, them darn presentation sending people ^^
[19:35]  * claydoh want koffice to replace ooo  so we can add more kde apps, like kmymoney :)
[19:36] <apachelogger> I did not manage to use kmymoney yet, so that is no good thing to consider :P
[19:36] <persia> the GNOME folks seem to be doing a parallel thing with the netbook flavour.
[19:36] <claydoh> apachelogger: kde4 version not quite there, but almost
[19:36] <apachelogger> persia: build the netbook flavour in ooo impress as presentation?
[19:36] <claydoh> or add more games by default :)
[19:37] <apachelogger> claydoh: yeah, one or two games couldnt hurt
[19:37] <apachelogger> and more translations
[19:37] <claydoh> yes
[19:37] <persia> apachelogger: Right.  It's much easier to get the nice glossy look if you don't need the software to work :)
[19:38] <persia> But no, my comment was about dropping OOo from the default install.
[19:38] <apachelogger> oh, especially for the netbook flavour I see a reason there
[19:38] <apachelogger> ooo is much to fat and clumsy for that use case IMHO
[19:38] <persia> (the little I've seen seems to imply use of abiword/gnumeric, which I thought were GNOME Office, which I thought would parallel KOffice)
[19:38] <apachelogger> yeah
[19:39] <apachelogger> persia: though I dont think it is officially gnome office
[19:39] <claydoh> darn techbase database errors!
[19:39] <persia> apachelogger: I think that the "officialness" of gnome office went away several years back.
[19:39] <apachelogger> back when they lost their presentation app I think
[19:39] <apachelogger> well
[19:39] <persia> apachelogger: But apparently I'm wrong: http://live.gnome.org/GnomeOffice
[19:39] <apachelogger> not particularimportant :D
[19:40] <persia> No ;)
[19:40] <apachelogger> persia: that is just a list of apps one might use in a office with gnome it seems
[19:40] <apachelogger> also not particular important
[19:41] <apachelogger> claydoh: thinking about it... in the fear of getting bashed again I do not think that using techbase is a good idea
[19:41] <apachelogger> people might come and whip my ass until I include more distros etc.
[19:43] <claydoh> yeah, how about this: we don't talk about kubuntu, just what works, doesn't, what needs help, and use that info for our ouwn purposes. Yhis does still give Koffice folks the useful info as well
[19:45] <claydoh> we are just looking to see if Koffice is worthy as a ooo replacement, right?
[19:45] <apachelogger> well, in a kubuntu context
[19:46] <claydoh> or are we trying to also help out the koffice team (which would e cool too )
[19:46] <apachelogger> I'll just use the kubuntu wiki for now to write down notes, we can always move stuff later on
[19:53] <apachelogger> claydoh: https://wiki.kubuntu.org/Kubuntu/KOfficeUserReview
[20:06] <ghostcube> o/
[20:09] <Riddell> hi mcguire, you can get our source code with apt-get source foo
[20:15] <mcguire> Riddell: thanks
[21:33] <bambule> hi, i have just updated my kubuntu 9.10 to kde 4.4. i now have the problem that the "kde menubar" gets shown twice.
[21:33] <bambule> both are at the bottom of the screen (as expected). one is a bit larger than the other
[21:34] <bambule> by clicking at the overlapping pixels i can bring one of them to the front
[21:34] <bambule> notifications are shown by both of them. so it get everything twice
[21:34] <bambule> any idea how i can get rid of this situation?
[21:35] <bambule> the bug is stable. restarting showed the same behaviro
[21:35] <bambule> r
[21:36] <claydoh> remove one of them
[21:36] <bambule> :-)
[21:36] <bambule> but how?
[21:36] <claydoh> right-clickmon one
[21:36] <claydoh> right-click on one
[21:37] <claydoh> but remember, support questions go to #kubuntu :)
[21:38] <bambule> claydoh: oh sorry. i thought i was in #kubuntu. the tab of quassel only shows the first bit....
[21:38] <claydoh> :)
[21:38] <bambule> how does right clicking help? btw.
[21:39] <claydoh> you get the option to remove panels, taskbars, etc
[21:39] <bambule> ok thanks!
[21:41] <claydoh> tho another way to remove it is to click the 'cashew' on the right side of a panel, select "more Settings" then 'remove this panel',
[21:42] <bambule> whats a "cashew"?
[21:42] <claydoh> the wierd golden icon on the very right side of the panel
[21:42] <claydoh> well, golden if you mouse over it
[21:48] <claydoh> anyone , what is up with this:
[21:48] <claydoh> https://wiki.kubuntu.org/Kubuntu/KnowledgeBase
[21:48] <ulysses> what the hell is this?
[21:49] <claydoh> and why is in the header as well?
[21:49] <yuriy_> i wondered that too when i saw it
[21:49] <jjesse> we talking about the linked wiki page?
[21:49] <ulysses> I think yes
[21:50] <claydoh> and https://edge.launchpad.net/~sakthievel
[21:50] <jjesse> what a silly page
[21:50] <claydoh> hmmm
[21:50] <jjesse> that page returs page not found
[21:51] <yuriy_> and there goes X!
[21:51] <claydoh> exactly, the user who edited it does not exist (anymore?)
[21:51] <claydoh> and why is it in the main kubuntu wiki header
[21:52] <jjesse> no idea
[21:55] <yuriy_> yeah looks like he created it too, no history, so it's not like an old real page that someone messed with
[21:56]  * ryanakca grumbles at debuild -S -sa making changes to upstream's source...
[22:00] <ryanakca> In bangarang's case, is it still appropriate to use 'dh --with kde $@' as I've been doing, even if it isn't a KDE SC app? I'm asking because of http://pastebin.ca/1795661 ...
[22:01] <JontheEchidna> yeah, that's ignorable
[22:01] <JontheEchidna> well, safe to ignore
[22:05] <persia> ryanakca: If that command is changing upstream source, fiddle more with debian/rules: clean
[22:05] <ryanakca> JontheEchidna: OK, and what about modifying upstream's source: http://paste.ubuntu.com/375754/ (1.0.1 is a bugfix release for 1.0, so this particular package will go into Debian and then I can sync it)
[22:05] <JontheEchidna> that field should be removed from upstream's .desktop file
[22:07] <ryanakca> JontheEchidna: Then should I add a lintian override for 'W: bangarang source: patch-system-but-direct-changes-in-diff data/bangarang_play_dvd.desktop'?
[22:08] <JontheEchidna> yeah. there's no harm done by modifying the source in this way
[22:08] <ryanakca> JontheEchidna: OK, thanks
[22:08] <JontheEchidna> It would be nice if the kubuntu l10n stuff didn't touch universe packages, but I suppose that's a bit hard to detect
[22:32] <nixternal> oi
[22:52] <Lex79> JontheEchidna: when you have time to sponsor some packages, they are in ninja wiki
[22:57] <ScottK> apachelogger: Looking at 477922
[22:57] <ScottK> shtylman: Generally, yes.  I didn't look recently at how bad it was (ISO size).  Riddell was working on it.
[23:23] <_Groo_> hi/2 all
[23:24] <_Groo_> is  dput still broken, i wanna contribute some new packages but i cant upload a 25k package!!!
[23:33] <_Groo_> anyone alive?
[23:34] <markey> apachelogger: ping


[03:15] <duflu> RAOF (I know you're away right now): Is this also your domain? - https://bugs.launchpad.net/mir/+bug/1499229
[04:20] <RAOF> duflu: Yeah, it is.
[10:52] <maikeul> Hello, I have a very basic question regarding running Xmir on an ubuntu phone (meizu), the connection is rejected by the server and I just cannot find a log or indications on how to allow this.
[10:53] <anpok> maikeul: you have to add a parameter --desktop_file_hint= iirc that tells unity8 which application it is dealing with
[10:53] <anpok> it otherwise tries to figure out the app id.. and that will fail
[10:53] <maikeul> ha thanks i will investigate this, i did not understood it was required
[10:53] <maikeul> undertand sorry
[10:54] <anpok> hm people at #ubuntu-unity shoud know more details
[10:54] <maikeul> thanks a lot
[10:54] <anpok> the parameter needs just one valid .desktop file..
[10:58] <maikeul> i'll just investigate this and eventually ask on the unity channel, thanks, so far i still get rejected
[10:59] <anpok> what parameter do you supply for mirSocket?
[11:00] <anpok> oh logs say rejcted..
[11:00] <anpok> nm, then it is the right one already..
[11:00] <maikeul> the one in /var/run
[11:22] <sturmflut> Does anybody know if GTK has a Mir backend? I think I read about it being patched for Mir, but that was a long time ago.
[11:29] <anpok> gtk3 has
[11:29] <anpok> yes and it is upstream
[11:31] <anpok> but on ubuntu-touch devices there are problems with the supported pixel formats.. none match the ones that cairo currently supports.. (I believe the backend currently tries to use software rendering)
[11:32] <anpok> or the opposite and that turns out to be a problem.. I havent looked in detail
[12:07] <sturmflut> anpok: Thanks for the detailed reply!
[12:07] <mcphail> sturmflut: if you get this working, can you let me know?
[12:12] <anpok> sturmflut: oh things have changed:
[12:12] <anpok> https://git.gnome.org/browse/gtk+/commit/gdk/mir/gdkmirwindowimpl.c?id=af5792f14126382705b2de328e4266f03ad1f824
[16:19] <maikeul> is there a repo/ppa where to get the latest builds for Xmir ?
[19:45] <bregma> maikeul, the latest version should be available in the vivid+overlay PPA, which should be in the sources on your device already
[19:47] <bregma> maikeul, just be aware there is no official support for running X11 apps directly on your phone


[11:52] <rmg51> Morning
[12:54] <InHisName> Morning, too
[13:26] <waltman> YAWN
[19:16] <InHisName> Afternoon