[08:19] <apachelogger> https://bugs.kde.org/show_bug.cgi?id=331867
[08:19] <apachelogger> akonadi is the best
[09:14] <apachelogger> yesterday I thought of something we need to do, but I forgot
[09:14] <apachelogger> was like 3 minutes before I fell asleep xD
[09:34] <kfunk> re. akonadi: "rm ~/.local/share/akonadi" helped
[09:34] <kfunk> (as always when anything odd happens)
[09:34] <kfunk> :)
[09:34] <kfunk> apachelogger: are you coming to randa as well?
[09:34] <kfunk> oh, you do. just checked 
[09:35] <apachelogger> I am darth vader, don't dare ask me silly questions
[10:04] <Riddell> "Timothy Pearson (kb9vqf) renewed their own membership in the Kubuntu Members" gosh the Trinity man still loves us
[10:51] <BluesKaj> Howdy folks
[10:54] <Riddell> yay, all of KF5 alpha 2 is done
[11:03] <Riddell> vHanda: morning, ping, the jungle is calling
[11:27] <Riddell> shadeslayer: baloo-widgets packaging up in ninjas, can you review it?
[11:53] <Riddell> hi sgclark 
[11:54] <sgclark> Riddell: good morning :)
[12:00] <sgclark> Riddell: is there anything I can work on?
[12:01] <Riddell> sgclark: we've got some bits on KDE SC 4.12.80 needing done if you're up for it
[12:01] <Riddell> https://notes.kde.org/p/kubuntu-ninjas
[12:02] <sgclark> Riddell: on it :)
[12:02] <Riddell> sgclark: it's being packaged in our ninjas PPA https://launchpad.net/~kubuntu-ninjas/+archive/ppa
[12:03] <Riddell> sgclark: first handy thing you could do is review my packaging of baloo and baloo-widgets for packaging perfection
[12:04] <Riddell> hi dougl 
[12:04] <sgclark> Riddell: ok, seems I have not worked with this PPA yet, setting it up
[12:05] <dougl> hi Riddell 
[12:06] <Riddell> sgclark: it's a private PPA so you'll need to copy the password for it
[12:06] <Riddell> into sources.list
[12:06] <sgclark> ok
[12:19] <Riddell> sgclark: kqtquickcharts also needs reviewed for packaging perfection
[12:19] <sgclark> k
[12:20] <Riddell> I have no idea if qtdeclarative4-kqtquickcharts-1 is a good .deb name, packaging qml libraries seems like a new art
[12:20] <sgclark> is there bazaar for this stuff or how do I submit to yyou?
[12:20] <Riddell> sgclark: yes, bzr in same place
[12:20] <sgclark> ty
[12:20] <Riddell> lp:~kubuntu-packagers/kubuntu-packaging/kqtquickcharts
[12:21] <Riddell> kbzr from kubuntu-dev-tools offers a nice shortcut
[12:21] <Riddell> Mirv: any thoughts? for a package which contains these files? http://paste.kde.org/pmblfsoe7  qtdeclarative4-kqtquickcharts-1
[12:24] <sgclark> Riddell: I show alot more copyright than what is in there, these are types I things that I fix right?
[12:26] <Mirv> Riddell: it doesn't sound wrong, but let's see if the Debian folks weigh in too. fun question is if qt quick 1 will live on via Qt 5's qtquick1 module or whether it's more probable Qt 4 will be used for QQ1 as long as needed
[12:35] <Riddell> sgclark: yep, which package are you looking at?
[12:35] <sgclark> Riddell: baloo
[12:36] <Riddell> sgclark: yeah all fixes welcome
[12:36] <sgclark> Riddell: fixing now
[12:37] <Riddell> Mirv: hmm interesting, does the package name need three version numbers? for the QQ version, for the Qt version and for the library API version?
[12:56] <Mirv> Riddell: good questions, I don't have definite answers though. maybe the 'declarative4' would be clearer that it means QQ1 in any case, even if in theory it could be used with Qt5's QQ1 module. it's not like upstream would be completely clear on the naming either (qtdeclarative == qt quick 1 module coming from qtquick1 source, qtquick = qt quick 2 module coming from qtdeclarative source...)
[12:57] <Riddell> messy messy
[13:02] <manchicken> Morning all.
[13:06] <dougl> So far that is 5 hours trying to manually config ip on 14.04 - is it possible I am still wondering
[13:11] <apachelogger> dougl: do what yofel said then?
[13:13] <dougl> apachelogger, are you tormenting me or can you help... I don't know what NM is or what it looks like?
[13:14] <apachelogger> http://i.imgur.com/98w6INT.png
[13:14] <apachelogger> login -> click on networkishy icon in system tray -> click on the connection you wish to statically assign an ip -> click on the wrench -> go to ipv4 -> configure ip -> reconnect the connection
[13:14] <apachelogger> takes like 10 seconds
[13:15] <dougl> I see part of a picture that looks familiar
[13:15] <Riddell> jmux: any idea what thiago is saying on https://codereview.qt-project.org/#change,80528 ? he says he would prefer it not to be merged as is but then says it looks good
[13:16] <dougl> apachelogger, ok I AM HERE NOW.... WHAT DO Ai DO?
[13:16] <apachelogger> dougl: login -> click on networkishy icon in system tray -> click on the connection you wish to statically assign an ip -> click on the wrench -> go to ipv4 -> configure ip -> reconnect the connection
[13:16] <apachelogger> also this is not the support channel
[13:16] <apachelogger> Riddell: that is an automatic label like "Won't fix" on bugzilla
[13:17] <Riddell> apachelogger: oh ok
[13:17] <dougl> I am looking for a solution to something missing in 14.04 where do I chat about that?
[13:17] <apachelogger> so what thiago is saying is: add test, get into qt5, then get into qt4 ^^
[13:17] <apachelogger> dougl: there is nothing missing
[13:17] <apachelogger> do what I told you
[13:19] <dougl> apachelogger, I am at ipv4 and there is nothing that inicates configure ip or reconnect the connection...?
[13:19] <jmux> Riddell: I'm currently on Qt5. State is this: http://paste.ubuntu.com/7073477/
[13:20] <jmux> Riddell: I'm also building Git Qt4, as it has the same test.
[13:21] <dougl> i see method other dns servers search domains DHCP client id apachelogger what are you trying to tell me to do?
[13:22] <apachelogger> dougl: replicate what you see in my screenshot?
[13:24] <jmux> Riddell: so my guess is the testcase is broken. But I couldn't find any real confirmation in the docs and the suggested waitForBytesWritten in the docs doesn't work either.
[13:25] <jmux> So probably there is even a deeper error in socket handling - I simply don't know.
[13:28] <Riddell> jmux: but the patch itself is good right?
[13:29]  * apachelogger thinks that for purposes of patch inclusion thiago should be asked
[13:30] <Riddell> he does say "Thanks, the patch looks good."
[13:30] <jmux> Riddell: Well - I know as much as you do. I didn't get any replies in the #qt-labs channel for my assumptions.
[13:30] <Riddell> so he just wants a change in the test and qt 5 patch
[13:31]  * apachelogger thinks that for purposes of patch inclusion thiago should be asked
[13:31] <Riddell> apachelogger: he was, see bug report!
[13:31] <jmux> I'll upload a new version of the patch including "fixes" to the Qt4 unit test. My build of Qt4 is still running.
[13:31] <apachelogger> Riddell: yet you have to ask what it meant, so I stand by my previous thinking :P
[13:34] <Riddell> apachelogger: but you told me the answer, it's a stock reply because he wants the test updated and qt 5 port done
[13:35] <apachelogger> Riddell: 'the patch looks good' is not 'a careful review of the patch yielded no concerns on upstream's part'
[13:36]  * dougl appreciates apachelogger's expertise = thanks
[13:37] <apachelogger> "Patches must not be taken from any bug tracker, without being reviewed by upstream or someone who is familiar with the source base." <- perhaps that needs to be clearified, but the point of it is to not take patches from random places and then under instrumentation of heavy hand waving argue that upstream approved it
[13:37] <apachelogger> upstream approves a patch when upstream says "I do hereby approve this patch, also I want cookies for it"
[13:40] <jmux> Well - in any case the Qt5 test case is broken, as it has the same result with and without the flag. Not sure if my "fix" is valid. Currently I'm waiting for the Qt4 test cases.
[14:05] <jmux> Riddell: Hmm - ok the same Qt4 test actually already fails and works with my patch :-)
[14:10] <Riddell> jmux: fails /and/ works?
[14:15] <jmux> Riddell: without my patch the Qt4 test already fails. With my patch applied it passes.
[14:18] <swex> hello everybody!
[14:18] <Riddell> jmux: oh nice :)
[14:18] <Riddell> hi swex 
[14:19] <swex> recently I've upgraded my kubuntu to 14.04 and logout dialog stopped working...
[14:19] <swex> not only logout, but
[14:19] <swex> all reboot, shutdown,switch user etc...
[14:19] <swex> how to debug such problem?
[14:20] <sgclark> Riddell: several more symbols-declares-dependency-on-other-package, but only one override for libbaloocore, override the others as well?
[14:23] <Riddell> swex: the dialog shows?
[14:24] <Riddell> sgclark: libbaloocore and libbaloofiles should have that, what else has it?
[14:24] <sgclark> Riddell: http://paste.ubuntu.com/7073789/
[14:25] <swex> Riddell: no.
[14:29] <Riddell> sgclark: symbols-declares-dependency-on-other-package that's all good, you can override them, but if you could make the .symbols file have only 1 option at the top that would be good
[14:29] <Riddell> sgclark: libbaloocore4.symbols is correct, some other ones have two options which is incorrect
[14:30] <Riddell> sgclark: intra-source-package-circular-dependency is more of a problem though, you can search through the contents of the baloo package to find out what depends on libbalooxapian4
[14:32] <sgclark> ok
[14:39] <Riddell> swex: what are you doing to try to get the dialog to show?
[14:39] <swex> Riddell: click on menu button)
[14:59] <manchicken> Now that I got the libqapt bugs fixed, should I switch to testing 14.04 or should I keep plugging away at kubuntu-debug-manager?
[15:07] <apachelogger> manchicken: whatever you feel like :P
[15:08] <manchicken> apachelogger: Have those changes been incorporated yet? I'm hoping that bug hasn't borked anybody's machine.
[15:09] <apachelogger> manchicken: they have not as far as I know
[15:47] <sgclark> Riddell: umm, baloo is saying aborting due to unexpected upstream changes... I have alot here, who else is working on this?
[15:47] <sgclark> Riddell: nevemind 
[16:15] <jmux> Riddell: After various tries to run the full Qt5 testsuite I pushed https://codereview.qt-project.org/80645 and https://codereview.qt-project.org/80644
[16:28] <Riddell> manchicken: should we be updating some package?
[16:29] <Riddell> sgclark: did you work it out?
[16:32] <sgclark> Riddell: So I created a baloo.symbols with all of the .so files in that package and removed baloo from the others, which stops all lintian errors and it looks like the depends are correctly being called now, but wierdness with dpkg-gensymbols. I am going to run to pbuilder to see what happens
[16:33] <Riddell> sgclark: how do you mean removed baloo from the others?
[16:34] <sgclark> Riddell: from the symbols files, aka baloo depends on them and not them on baloo, the source had alot of depends to the others from baloo
[16:35] <sgclark> hense the circular
[16:36] <sgclark> Riddell: this is an experiment at the moment trying to fix, nothing commited. If it does not work I can easily revert.
[16:40] <Riddell> sgclark: I suspect that baloo package needs split up somehow
[16:40] <Riddell> if only vHanda was around to tell us how
[16:40] <manchicken> Riddell: I committed a bug fix to prevent duplication within the sources.list-type files to the master on qapt.
[16:40] <sgclark> Riddell: that actually makes sense
[16:42] <sgclark> Riddell: but yeah I would need direction on how to spilt.
[16:48] <jmux> Anybody going to fix udisks2 USN (http://www.ubuntu.com/usn/usn-2142-1/) for Precise? I guess one just has to apply the patch from udisks2_2.1.0-4ubuntu0.1.
[16:49] <Riddell> jmux: I expect there's a reason why it hasn't been updated for precise
[16:49] <manchicken> Riddell: I suspect that the package should be updated to incorporate that change, the bug was pretty nasty.
[16:49] <jmux> It's just in kubuntu-backports
[16:50] <Riddell> jmux: ah right was going to say there is no udisks2 in precise https://launchpad.net/ubuntu/+source/udisks2
[16:50] <Riddell> jmux: ok I'll take a look at the package in backports
[16:50] <jmux> For the 4.2.13 packaging. Version is  2.1.0-4~ubuntu12.04~ppa1 
[16:50] <jmux> It in kubuntu-backports
[16:51] <jmux> Riddell: Thanks
[16:57] <sgclark> Riddell: http://paste.ubuntu.com/7074499/
[17:11] <Riddell> sgclark: mm yes I had the same issue in pbuilder today, I don't know what needs to be installed to make it work
[17:11] <Riddell> apt-transport-https of course but it must need something else too
[17:22] <kubotu> ::workspace-bugs:: [1290947] System go to sleep after a few minutes of inactivity. @ https://bugs.launchpad.net/bugs/1290947 (by Jaime Pérez)
[17:25] <sgclark> Riddell: yeah got the https. Unfortunately the tax man calls and I must break. Do you want what I have in Ubuntu one, or can this continue tomorrow?
[17:47] <sgclark> Riddell: nevermind, I have another hour or so, will keep trying
[17:53] <yofel> usually it's apt-transport-https and ca-certificates
[18:00] <sgclark> That worked, thanks yofel!
[18:48] <tester56> beta 2 has not been released yet, has it? Why is the following already accessible: https://wiki.edubuntu.org/TrustyTahr/Beta2/Kubuntu ?
[18:48] <tester56> stating: "Kubuntu 14.04 Beta 2 is available for testing. "
[18:53] <yofel> that's the beta2 release note draft page, I guess nobody put a "DRAFT" note at the top
[18:57] <tester56> yofel: is 4.13 ready soon?
[18:57] <tester56> can't wait to try it ... have unfortunately not the time to compile it myself
[18:58] <yofel> soon yes, but not all fixed yet http://qa.kubuntu.co.uk/ninjas-status/build_status_4.12.80_trusty.html
[18:58] <tester56> yofel: If I understand correctly the tarballs provided by KDE should build ...
[18:58] <tester56> yofel: So are those issues, issues with kubuntu specific patches?
[18:59] <tester56> or with unmet dependencies?
[18:59] <yofel> mostly issues with the packaging (new/removed file, new packages, ...)
[18:59] <yofel> *files
[19:00] <tester56> yofel: will you include nepomuk in the iso or will it be dropped completely?
[19:00] <yofel> it'll stay, only a few applications use baloo so far, everything else nepomuk
[19:01] <tester56> but baloo will be default?
[19:01] <yofel> both will be there by default
[19:01] <tester56> ah right ... they can coexist :D
[19:02] <tester56> yofel: thank you
[19:08]  * yofel throws a bucket of icy water at shadeslayer
[19:08] <yofel> for not writing changelog entries
[20:06] <shadeslayer> great, I was sick all day and now yofel throw's a bucket of cold water at me
[20:06] <shadeslayer> :P
[20:07] <yofel> lol
[20:07]  * yofel tries to figure out what's wrong with kde-runtime
[20:10] <shadeslayer> evening :)
[20:10] <yofel> shadeslayer: get better soon ;)
[20:10] <shadeslayer> yeah, the medication helped alot
[20:10] <yofel> oh lol
[20:10] <yofel> override_dh_autoconfigure:
[20:10] <yofel> that's dh_auto_configure, not dh_autoconfigure
[20:11] <shadeslayer> I thought I did fix that :O
[20:11] <yofel> not pushed maybe?
[20:11] <shadeslayer> well, either way, my changes are lost since I worked in /tmp for that package >.>
[20:12] <yofel> ah, nvm then, I'll fix it
[20:12] <shadeslayer> and for some reason my computer rebooted on it's own
[20:12] <yofel> -.-
[20:12] <yofel> yeah, I know that feeling...
[20:13] <shadeslayer> I was paranoid for about 30 minutes :P
[20:13] <shadeslayer> checking auth.log for funny stuff
[20:13] <shadeslayer> nothing stood out ...
[20:14] <yofel> a few days ago I had something like that at work. Notebook runs as usual and suddenly the screen goes black, but the fan was still running. Had to power it off for a few seconds until it booted again
[20:15] <yofel> I wonder if it overheated, but that shouldn't have been possible...
[20:15] <dougl> root kit
[20:16] <yofel> unlikely
[20:17] <shadeslayer> I had mine just randomnly reboot
[20:17] <shadeslayer> or well
[20:18] <shadeslayer> shutdown
[22:03] <valorie> http://linuxgrandma.blogspot.com/2014/03/prospective-gsoc-students-now-is-time.html
[22:13] <windows> hi