[08:37] yofel: Riddell: if not critical, please try to hold on any big kde updates as we're trying to get Qt 5.5 migrated to release pocket. the pkg-kde-tools update broke half of the autopkgtests and they're now slowly being re-run after the fixed upload. [08:39] last evening it was starting to look promising, as me and xnox fixed the last failing autopkgtests. the migration is however tangled a bit with poppler transition which is tangled a bit with s390x architecture but... let's see [08:51] k [08:53] I assume, by the 376 of 376 broken packages that pkg-kde-tools is still broken? [08:54] in the CI? yes [09:57] clivejo: oh, I misread that. pkg-kde-tools is fixed, but the CI builds don't get auto-retried because of that. So unless they were part of the nightly re-run, they just need a retry or are broken for other reasons [10:03] yofel: which ones? [10:05] sitter: anything senile that failed with that undefined subroutine error [10:05] well, I can retry everything senile that failed if that helps [10:05] sure, not like anyone will get bothered by the wall of red [10:06] perhpas more motivating to get all of them fixed ^^ [10:07] if your's truly didn't forget to pause that would help [10:11] should be all queued up momentarily [10:11] except java is dying so I have no clue if they really are [10:21] what uses Java? [10:21] jenkins [10:21] * yofel is curious why it would die though [10:29] yofel: bottlenecking because of container windups I'd guess [10:29] :S [10:29] although I seem to recall jenkins not being very happy with getting 32 build requests at the same time [10:29] like in general [10:31] oohh shite [10:33] heh [10:43] poor lemmings [10:44] I thought KCI was in ruby, cause sitter loves ruby [10:47] clivejo: I also love java [10:48] in fact, the only language I do not love is python [10:48] I thought you would be more comfortable in assembly! [10:49] or just reading pure machine code [10:51] one of my favourite sitter quotes "that person is gonna suffer, really really terribly" [10:51] clivejo: you can't really do OOP in asm, so it's not really playing in the same league :P === greyback__ is now known as greyback [12:03] is plama 5.5 going to be backported to 15.10 ? [12:06] *plasma* [12:30] Yossarianuk: yes, without ETA. (The beta won't, that much I can say) [12:33] yofel: cheers - looking forward to it, each version is better than the previous one. [12:36] Hey folks === rdieter_ is now known as rdieter_work [13:05] hey folks === rdieter_work is now known as n === n is now known as rdieter_work [16:42] sgclark: your recent commit to kdeplasma-addons added git markers [16:42] (debian packaging) [16:42] bshah@archbox ..ea-tooling/git/plasma/kdeplasma-addons (git)-[kubuntu_unstable] % git grep HEAD [16:42] debian/control:<<<<<<< HEAD [16:42] debian/plasma-widgets-addons.install:<<<<<<< HEAD [16:44] * bshah goes to bed for today [17:08] clivejo: ping? [17:15] hmm, still no plasma 5.5 in the backports...guess it's going to take a while for Xenial [19:31] lots of lemmings saved! [19:32] ahoneybun ovidiu-florin is there a private telegram channel without porn spammers? [19:33] Riddell: pong [19:33] but not for long, got a meeting at 8pm [19:34] who fixed KCI? [19:35] ok, bored talking to myself, be back in couple of hours [21:17] sgclark: ping [21:17] yofel: ping [21:17] what is the status of plasma 5.5 in Kubuntu? [21:17] I understand it is not packaged [21:18] do you need someone to package it manually? [21:18] don't we have some sort of automation for this? [21:18] how can I help move this? [21:19] ovidiu-florin, yes, she asked if someone would package it since she was busy with family matters [21:19] clivejo: no. That's the only one. We're doing our best to kick them out in time [21:19] BluesKaj: I see [21:20] yesterday, you can check the logs if you wish [21:20] so it needs to be packeged manually? [21:20] i don't know , she didn't give any details [21:21] I'll wait for her or yofel 's input [21:21] yeah, probly a good idea [21:22] is it ready for Wily [21:27] ovidiu-florin: from my part its stuck on ENOTIME as I wanted to look at it after getting the wily stuff out. To get plasma done, someone first has to do the frameworks update and then we can look at plasma [21:28] we can scripts for that, but as the environments between CI and dev don't match there is still manual work involved [21:28] s/can/have [22:14] KCI is looking good :) [22:18] spoke too soon [22:31] well, seeing the fix count go down is certainly welcome [22:31] indeed, might be able to fix some of them now! [22:32] yofel: did you see that Paulo Dias asked some good questions on the ML? [22:32] I was hoping to see him here [22:33] ooo, green [22:33] nice to see [22:33] no, looks like kmail refused to fetch mail yesterday. How nice of it to give me a break.. again... [22:35] my kmail is actting the buck again [22:35] if that's the Paulo I remeber then his IRC nick was _Groo_ or so [22:35] cant connect to dbus errors [22:41] it would be helpful to me to know what the workflow for a packager is like. I can understand the tools fairly easily, but if I were to jump into it I think I would be inefficient at packaging something like plasma or kde [22:43] hi vertago1 [22:43] hi [22:45] well when everything is working right we have the Kubuntu Continuous Integration (KCI) [22:45] http://kci.pangea.pub/ [22:45] it takes the latest snapshot from KDE and packages it [22:46] Is something wrong with it? [22:48] theres been a few issues recently [22:49] Is the source code public? [22:49] I could look into setting up a local test bed for it [22:50] the CI is one half of our workflow, for it there's the ci-tooling somewhere on alioth under pkg-kde/ and the pangea tooling from blue systems on github. [22:51] vertago1: the packaging is here - http://anonscm.debian.org/cgit/pkg-kde/ [22:51] the other half is the kubuntu-automation tooling (on launchpad) which is used to generate the packages for the archive and PPAs, incorporating the work done in the CI [22:58] I don't really understand all the terms yet so pretty much KCI is a set of scripts which add the packaging information to the kde projects so they can be packaged on launchpad? [22:59] (the packaging information being the /debian folder) [23:00] yup [23:01] so would I be looking at xenial? [23:01] or would the backports be separate [23:02] nice video explaining what KCI is - https://www.youtube.com/watch?v=zhJQSpy3Luc [23:02] thanks [23:05] that is a fairly recent video [23:06] yup [23:08] at the moment the packaging is falling to mainly yofel and sgclark [23:08] so they are under a lot of pressure :( [23:10] yippeee [23:15] yofel: cantor FTBFS - Reversed (or previously applied) patch detected! Skipping patch. [23:15] does that mean the patch is now upstream? [23:16] do verify that it's true, but usually yes and the patch has to go. [23:16] just checking, Ill grab the packaging and test it [23:41] So are the issues with KCI solved? (I am guessing because of those irc bot messages) [23:54] vertago1: sitter paused CI last night and applied some fix [23:54] so yes, much better health today! [23:56] vertago1: are you Paulo Dias from the ML? [23:57] No I am a long time kubuntu user. I was looking into what it would take for me to be able to help with stuff like packaging [23:57] I just watched sitter's video on youtube about KCI [23:59] so the people who work on packaging pretty much fix errors caught by KCI, and bug reports?