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