[04:07] <valorie> oh, why wasn't I set away? grrrr
[04:07] <valorie> Etriaph: thank you for your attention to detail
[04:40] <Etriaph> valorie: I think promoting starts at ensuring that all of the mediums we can promote on are being used to the best of their ability.
[04:40] <valorie> I very much agree
[11:03] <BluesKaj> Hey folks
[11:14] <KDDA> hi BluesKaj
[11:15] <KDDA> Riddell: finally logged into ec2-54-159-117-153.compute-1.amazonaws.com
[11:15] <KDDA> what is that box for?
[11:16] <BluesKaj> hi KDDA
[11:18] <soee_> KDDA: i think its a fresh enironment to build packages
[11:18] <KDDA> they arent built on my local machine?
[11:19] <soee_> i think they can be, but than you have a lot of other packages that mght have negative influnace on builds. so when having fresh and clean environtment you are sure nothing interrupt it
[11:23] <sgclark> we dont typically use the amazon server to package, he uses it to train. They cost money..
[11:24] <sgclark> it is best practice to use chroot / pbuilder to get clean environment for packaging
[11:25] <KDDA> I see
[12:51] <soee_> yofel: ping
[13:00] <soee_> guys please confirm if you can: https://bugs.kde.org/show_bug.cgi?id=347795
[13:00] <soee_> iv added also video to demonstrate this behaviour
[13:00] <sgclark> confirming
[13:01] <soee_> thank you
[13:07] <soee_> sgclark: can you test one more thing?
[13:07] <soee_> this one: https://bugs.kde.org/show_bug.cgi?id=344867
[13:22] <KDDA> does anyone know how to lock the login to one screen?
[13:31] <sgclark> soee: confirming
[13:33] <soee> thank you 
[14:07] <soee> sgclark: 15.04.1 are building for Willy ?
[14:08] <sgclark> yeah
[14:09] <sgclark> stuck on ktp though
[14:11] <soee> sgclark: each time i see this packaging process we have i wonder why there are always building problems
[14:11] <sgclark> the wonderful world of packaging :p
[14:11] <soee> for example if there are app 15.04 ok - its fresh might be problematic, but bugfixes version in myopinion should be easy to package
[14:12] <soee> yes and i can't undersnatd this :)
[14:12] <sgclark> well that was my thought, this should be easy! just a point release!
[14:12] <soee> maybe because im a webdeveloepr and here upgrade process in some apps, frameworks etc. is much easier
[14:13] <sgclark> this error I am getting is wierd though.. does not happen in CI, and I am baffeled
[14:13] <soee> but still why this errors shows up :)
[14:13] <soee> *error
[14:14] <sgclark> if I knew the answer I would have it fixed..
[14:14] <soee> such packaging shudl be -> ad dpackages to build, done, they are ready :)
[14:15] <sgclark> well no, there are changes that have to be made when things change
[14:15] <soee> the most common problems are because of developers fault o ubutnu/debian packages need some extra stuff to be done around them ?
[14:18] <sgclark> well I would not say fault.. when developers change things to say fix a bug, then the package can change and it needs to be changed to accomodate those changes.
[14:19] <soee> ok but what problems it can cause, such change in package ?
[14:19] <soee> it can depend on something taht is not available in current release ?
[14:19] <sgclark> that can and has happened yes
[14:20] <sgclark> or a new feature will create new files that are not yet in the install file
[14:20] <sgclark> or in my case with ktp the build did not create the files at all...
[14:21] <sgclark> removing from install will surely break things so I need to sort out why the build did not build that component
[14:21] <sgclark> despite finding the needed libraries..
[14:23] <debfx> sgclark: I've replied on the list
[14:23] <sgclark> ty
[14:23] <sgclark> ah ha
[14:24] <soee> sgclark: so install file is not created by developer ?
[14:24] <sgclark> no that is packaging
[14:24] <sgclark> and something like the wrong version of another package can cause the probelm and did
[14:26] <soee> hmm for me this is a bit strange
[14:26] <soee> this all shoudl be somehow automated
[14:30] <sgclark> we are getting much closer to full automation... it used to be a ton harder to package all these. Obviously we have some kinks :)
[16:06] <sgclark> hmm anyone using wily yet? applications are ready to test, but I suspect there are not many using wily haha
[16:23] <soee_> sgclark: i think Bluskay does
[16:35] <mparillo> sgclark: I just dual-booted with wiley this morning
[16:37] <sgclark> cool, if your feeling adventurous the applications in the topic need testing.
[16:37] <mparillo> kinfocenter says I am still at Plasma 5.2.2 (I used the backports PPA) in Vivid to get to 5.3 on real hardware, but 5.3 did not work at all in a VMware VM. 
[16:38] <mparillo> sgclark: Dolphin, rekonq, and konsole all worked so far.
[16:39] <sgclark> particularily kdenlive and ktp* I think were the problem children of last release
[16:40] <mparillo> Okular seems to work.
[16:42] <mparillo> Those are the KDE apps I tend to use the most. KTP is a chat client?
[16:58] <mparillo> Firing up KTP. Anybody want to chat? 
[17:08] <mparillo> Might be user error on my part, but I have accounts on GTalk (now hangouts) and Yahoo Messenger. I have recently used the GTalk client successfully in Google Chrome, but it has been some years on YIM. In KTp, neither shows me as online.
[17:23] <sgclark> don't use yahoo, but I recall extra steps if you use 2 way auth with google
[17:27] <mparillo> sgclark: No, I do not use two way auth. 
[17:27] <sgclark> yeah I am having issues with google too... hmm
[17:29] <sgclark> ahh my problem was my firewall
[17:32] <mparillo> I do not run a firewall.
[17:32] <mparillo> I can install chrome and test my GChat from there.
[17:36] <mparillo> Yes, I am on-line when looking at the chat sidebar on Google Chrome, but not in KTp
[17:38] <sgclark> and you created the account and signed into google? also the top bar you need to pull down and select available
[17:43] <mparillo> That is it. I needed to set to available. YIM shows me available. I am having trouble authenticating to GChat.
[17:49] <mparillo> So YIM and AOL IM work for me (at least I show as available). GTalk and MSN Messaging do not.
[17:53] <mparillo> I do not thing I have been available on YIM or AOL IM in years.
[17:54] <mparillo> s/thing/think/
[17:54] <kubotu> mparillo meant: "I do not think I have been available on YIM or AOL IM in years."
[17:57] <vip> hello there
[17:58] <soee_> hiho
[17:58] <vip> anyone experienced unicode problems under vivid?
[18:12] <mparillo> Google hates KTp: http://paste.ubuntu.com/11170622/
[18:14] <mparillo> Google seems to be claiming that KTp uses weaker security?
[18:24] <KDDA> sgclark: ping
[19:11] <sgclark> KDDA: pong
[19:11] <sgclark> mparillo: woah that is wierd. I have never seen that.
[19:11] <KDDA> is there problem with kdepim with new apps?
[19:12] <sgclark> could you be more specific?
[19:13] <sgclark> did it crash?
[19:14] <sgclark> if you mean the red on that list, it is because it has a different version than the rest of the apps.
[19:14] <sgclark> they have some time yet before they will be kf5 ready.
[19:17] <KDDA> ah
[19:18] <KDDA> Im on wily, but dont want to mess up kontact
[19:19] <sgclark> I wish I could guarentee things will be splendid but pim is one that likes to break, and as such needs testing lol. No worries, I will recruit more testers after the weekend.
[19:20] <sgclark> I now have some real life to attend to, have a great weekend all.
[19:46] <gorgonzola> hello. me again witht he same question: What is the status of bluetooth in vivid? I understand that bluez is under transition, and bluedevil is being kept back. Does this mean there is no wasy way to get bluetooth working in plasma 5 for now?
[19:46] <gorgonzola> wasy=easy
[19:55] <Etriaph> https://launchpad.net/ubuntu/vivid/+source/bluez
[19:56]  * Etriaph is waiting for dolphin 15.04.1 to trickle down.
[20:22] <gorgonzola> Etriaph: I don't understand
[20:46] <valorie> gorgonzola: we're waiting on the Ubuntu folks who have blackballed the new bluez for now
[20:47] <valorie> because of the phone stuff or something
[20:47] <valorie> "folks" should have been devels
[20:52] <gorgonzola> valorie: thanks! so, just to understand on my end... bluez4 won't work with plasma 5, and we are waiting on bluez5 from ubuntu?
[20:54] <KDDA> valorie: are you on wily?
[20:54] <valorie> no, just vivid
[20:54] <valorie> gorgonzola: I believe that is right
[20:54] <valorie> unfortunately
[20:55] <valorie> I'm not sure what we can do on our end beyond commenting on the launchpad bug
[20:55] <gorgonzola> valorie would installing bluez5 locally help, or is that a recipe for disaster?
[21:15] <gorgonzola> valorie: never mind, I see that bluez5 is actually installed.. the problem is with libical1a etc. Thanks for the clarification
[21:16] <valorie> I guess it could be built from sources
[21:16] <valorie> and usually that doesn't cause disaster, but may cause more work as you have to also build this new thing, that new thing
[21:16] <valorie> etc.
[21:17] <valorie> and -dev versions of packages
[21:17]  * valorie builds amarok and has built phonon and phonon backend
[21:17] <valorie> s
[21:17] <valorie> no big deal realy
[21:23] <gorgonzola> valorie: yeah, i went that route with solid trying to get upnp to work... But in any case, as I said above, the problem seems to be elsewhere... not in bluez
[21:25]  * valorie is out for the next 24 hours or so
[21:40] <Etriaph> gorgonzola: I gave you the link because an update will end up there.
[21:40] <Etriaph> gorgonzola: That's how I track packages to determine when changes are coming down the pipe for me.
[21:42] <gorgonzola> Etriaph: Ah, ok. Thanks. So is there any point in using this ppa? https://launchpad.net/~ubuntu-desktop/+archive/ubuntu/transitions
[21:42] <Etriaph> gorgonzola: You are always free to try what's available and rollback if it doesn't work for you.
[21:43] <Etriaph> gorgonzola: Just keep ppa-purge handy at all times :D