[00:10] <zamazan4ik> hello. When will kdevelop5 package will appear in Kubuntu?
 there's no ETA yet
 we want to get 16.10 out the doors first
 then we can work on getting KDevelop 5 into the backports
[00:26]  * ahoneybun blames tsimonq2
[00:38] <zamazan4ik> IrcsomeBot: ty for answer
[03:04] <ahoneybun> mm plasmashell just shut down
[03:04] <ahoneybun> and is not starting up
[03:34] <tsimonq2> Hello again ninjas. Don't mind me, I'm just rebuilding mgmt_merger.
[03:34] <ahoneybun> why is it so red?
[03:34] <tsimonq2> because I made it red :P
[03:34] <ahoneybun> mm
[03:39] <ahoneybun> wow
[03:40] <ahoneybun> yofel: can we lower the limit of jobs for the KCI?
[03:41] <ahoneybun> it's hitting almost 100% CPU on the server
[04:02] <ahoneybun> mm I wonder if this has to do with that okular removal
[05:18] <acheronuk> WTF?
[05:18] <ahoneybun> ?
[05:20] <ahoneybun> what?
[05:20] <acheronuk> all the broken merges
[05:20] <acheronuk> then fixes
[05:21] <ahoneybun> yea a ton of fixes
[08:56] <acheronuk> plasma-sdk is now FTBFS as it can't find kirigami or kdevplatform. if they can be added by someone to KCI at some point that would be great
[11:23] <acheronuk> that LP publisher maintenance on Sunday mornings is a PITA. all those failures that aren't really
[11:31] <BluesKaj> Hiyas all
[11:31] <acheronuk> afternoon :)
[11:40]  * acheronuk switches to Grand Prix mode
[11:57] <BluesKaj> hi acheronuk
[12:55] <soee> http://www.phoronix.com/scan.php?page=news_item&px=SDDM-0.14-Released
[13:50] <ahoneybun> fun fact: don't update KDE Connect 
[14:02] <soee> wat happend ?
 I can't connect to my phone
 I think the phone version is too new
 nvm
[14:44] <clivejo> ahoneybun: Ive packaged kdeconnect 1.0 for yakkety - https://launchpad.net/~clivejo/+archive/ubuntu/kdeconnect-kde
[14:46] <clivejo> currently discussing going on regarding the need for Qt5.6 for it
[14:47] <ahoneybun> mm
[14:47] <ahoneybun> oh wow 14.04 too?
 Noo that was just a test
[20:54] <mitya57> tsimonq2, I tried to debug the qtquickcontrols / i386 failure and the news are quite bad
[20:54] <mitya57> First, for me it crashes not necessarily in test_windowHeight2(), but right after test_invisibleContentItemChildren()
[20:55] <mitya57> I.e. it should be test_minimumHeight(), but if I disable it, it crashes in the next test
[20:56] <mitya57> Then, the stack is damaged, so there is no useful stacktrace
[20:57] <mitya57> Finally, I spent some 30 minutes trying to debug stack corruption with memcheck and gdb, but got no luck
[20:58] <mitya57> So maybe the best way for you will be to not run the tests at all
[20:58] <mitya57> (note: I'm replying here because OFTC is not feeling good today)
[21:10] <tsimonq2> mitya57: hello :)
[21:10] <tsimonq2> mitya57: if you make the change upstream, I'll pull it in
[21:10] <tsimonq2> mitya57: (unless it doesn't affect Debian?)
[21:10] <tsimonq2> mitya57: (and by upstream I mean Debian)