[00:00] valorie: sorry I forgot to tag you in my previous responses. see above [00:01] I always read backscroll [00:01] :-) [00:01] vertago1: very good to see you [00:02] one thing we lack is up-to-date packaging documentation/tutorial [00:02] new packagers keep saying they'll do it, and presumably take notes, but so far, that's as far as it has gotten [00:03] valorie: et al. anyone need kubuntu tasks put into the google code-in queue? [00:04] Is there an out of date wiki? [00:04] https://wiki.kubuntu.org/Kubuntu/GettingInvolved/Development ? [00:06] wxl: KDE is doing GCi too [00:06] valorie: oh yeah duh, nevermind :) [00:06] so .... [00:06] i remember noticing that early on but i kind of forgot [00:06] we're rather short of mentor time this year [00:06] it's been a real whirlwind of activity for me the last few days [00:07] vertago1: that is a good page [00:07] but not detailed enough, right? [00:07] wxl: same here [00:07] valorie: i would suggest mentioning #ubuntu-google as a support option for students. there's a lot of questions that don't necessarily require the help of an expert, i've found [00:08] our KDE students aren't all using *ubuntu [00:08] but sure, I'll keep that in mind [00:08] we have #kde-soc [00:09] and #kde [00:09] well, for kubuntu things at least :/ [00:09] etc. [00:09] right [00:09] haven't seen any students on #kubuntu yet [00:09] and honestly a lot of them just need help using the gci interface [00:11] we had one student abandon a task after asking a question FOUR MINUTES later [00:11] ! [00:11] valorie: yeah. I think some tutorials would be helpful. I am familiar with using apt source and adding a patch and rebuilding the package [00:11] but as I explained to the mentor -- this kid doesn't know that it's a world-wide community [00:11] or that it is a community at all [00:12] that there are real people involved, who work and sleep [00:12] and: [00:12] !patience [00:12] Don't feel ignored and repeat your question quickly; if nobody knows your answer, nobody will answer you. While you wait, try searching https://help.ubuntu.com or http://ubuntuforums.org or http://askubuntu.com/ [00:12] THIS is why we need the bot in #uubntu-google [00:12] *ubuntu [00:13] but to be fair: that's why there is such a contest [00:13] to introduce the students to the world of free software and the people who make it [00:13] yep [00:13] and it takes some work on our part [00:13] +1 [00:22] So if it fails because of a git exception don't troubleshoot it at the moment? [00:26] From looking at the output of those recent failures it looks like there might be an issue with the merger and the backports branch [00:28] right, and scarlett had to leave to the deathbed of her aunt before she could troubleshoot/finish the merger [00:28] life and death happens [00:31] If I were to look into it, where would I document what I find? [00:37] vertago1: I would either fix the doc you did find, or link new docs to it for specific topics, like : troubleshooting CI, Debian merges, Backporting [00:37] etc. [00:37] right there on teh wiki [00:37] also add missing links as you find them [00:38] hopefully at least the ones in the /topic of the chan are there..... [00:40] ouch, the wiki just blew up [00:40] openid.message.InvalidOpenIDNamespace [00:42] do you know who maintains the wiki? [00:42] or the server the wiki is on [00:43] oh it looks like it was moved [00:44] Here is probably the new location: https://community.kde.org/Kubuntu/Packaging [00:44] yeah [00:45] we stopped using the ubuntu wiki because it really sucks [00:45] oops, I should have looked at your URL more closely [00:45] sorry [00:57] so L10n is localization? [01:02] KCI supports 14.10 and later right? (Instead of just 14.10 and 15.04 dev) [01:14] hmm it looks like there was a build of mgmt_merger that was aborted [01:28] hello, could you please re-build all of libkf5* in xenial-proposed? [01:29] (which is against qt5.5, all the way up to kubuntu-dev, to get libreoffice-kde installable on s390x?) [01:29] otherwise nothing will migrate until that is done, and I shall be doing binNMUs of all the kubuntu things, until they build on s390x and migrate. [02:00] however that is drastic [11:57] 'Morning all [12:01] hiho BluesKaj [12:01] Hi soee [14:33] muon (master) v5.4.3-172-gbcc6f03 * Carlo Vanini: src/muonapt (2 files in 2 dirs) [14:33] Fix history dialog layout. [14:33] REVIEW: 126288 [14:33] BUG: 343992 [14:33] http://commits.kde.org/muon/bcc6f0334b9d3ffc6421571b758af5f84d90bb8c [14:33] bug 343992 in IPython "Overzealous introspection" [Undecided,Confirmed] https://launchpad.net/bugs/343992 [14:39] BluesKaj: do you tried maybe kos ? [14:40] they have Plasma 5.5 in latest release i think [14:40] *dev probably [14:43] soee, where? [14:44] http://kaosx.us/early-december-15-status/ [15:00] * yofel needs a "Slow down" button for the world -.- [15:24] soee, going to try kaos? [15:25] maybe in a free time [15:25] just for Plasma 5.5 [15:29] I have a spare partition, but I'll have a look at the live version first [15:30] not rolling release fan [15:31] shadeslayer: would you be so kind to remove the stuff you and Scarlett got done from the card? https://trello.com/c/TCAk2U9J/71-debian-merges [15:31] most of the frameworks IIRC? [15:31] all of them AFAIK [15:31] ah ok [15:31] then I'll just remove that checklist [15:31] thanks [15:32] cheers [15:34] any time line for Plasma 5.5 in the backports? [15:37] not really, though I hope I can say we have it in a ~week. From the order that's on the todo list, there's: apps 15.08.3 (WIP), frameworks 5.17 (releases on saturday), plasma 5.5 [15:39] as mentioned on #ubuntu-devel, two metric tons of packages are migrating to release pocket right now, so Qt 5.5 is finally done <- yofel, Riddell unping therefore regarding new big uploads [15:39] \o/ [15:39] I got a couple of plasma packages more to build on arm64 and that was one of the last things in addition to the multiple transitions in progress [15:40] Ok, perfect, thanks for your help with those. [17:30] yofel: are you around? [17:31] ovidiu-florin: yes, for a bit [17:32] yofel: 2 questions [17:32] 1. these kubuntu-ci messages, are here for logging purposes, does someone actually read them? [17:33] the status they present can be read from the CI itself, AFAIK [17:34] they are here for notification, and to remind people that there's stuff to fix (if $dev finds them so annyoing that he ends up fixing the failure, they serve their intended purpose) [17:34] 2. is it written somewhere what needs to be done for the FW and Plasma that you told me needs to be done [17:34] ? [17:34] I think I have some time in the weekend, and I'd like to take a look at it [17:35] documentation of that is done on the ninja notepad, the workflow is heavily underdocumented though and the readme that exists is partly wrong. [17:36] That was supposed to be one of the tasks for automation-ng, but santa is MIA lately and his scripts are far from done, so for now we're stuck with the old scripts. [17:37] I started improving those, but after years of under-maintenance, getting things into shape again is non-trivial. [17:37] bash or python scripts? [17:37] They do work though, as long as you know how to use them and what the pitfalls are (not documented) [17:37] Hi [17:37] Python mostly (some pieces require launchpadlib) [17:37] yofel: Did you get a resolution on the Server requirements from Michael ? [17:38] no [17:38] because I didn't do anything in that direction [17:38] Hmm, I see. Was a decision made.? [17:39] I understood that you and sgclark were discussing with mhall119 to make a decision whether to go with a JEnkins instance on Canonical [17:39] or to go with a Digital Ocean droplet ? [17:39] No. All I can still say is that sitter said that shell access is a requirement right now. [17:41] I'm honestly not sure how one would integrate our tooling into jenkins without shell access... [17:41] AFAIK, we're waiting to know if the current CI setup needs shell access to work, of it a hosted Jenkins setup could be used [17:41] but I'm not jenkins expert and I didn't have time to read the ci-tooling yet either [17:42] I've spoken to those who setup the jenkins-as-a-service in Canonical and have been told what we need to do in order to use it for Kubuntu [17:42] so it all hinges on whether or not it can be run in that kind of setup or not [17:42] is that kind of setup documented somewhere? [17:43] only our internal wiki I'm afraid [17:43] but from what I understand, it's a vanilla Jenkins with the ability to include Jenkins plugins [17:43] it actually uses one persistant control-node of Jenkins,and spins up build-nodes on demand [17:46] Ok. I probably won't have an answer for you this year. I want to replicate the CI in a VM over christmas so I actually know what I'm talking about [17:46] currently sgclark knows more about the CI than I do and she's on a trip [17:46] OK, [17:47] yofel: ack, I'll be off the weeks of christmas and new year's anyway, so we can revisit this in January [17:47] I think the only stumbling block on Kubuntu side is the shell access. [17:47] * mhall119 notes that "off" doesn't mean "offline", just not normal hours :) [17:47] I believe that we can upload scripts for Jenkins to run, but that needs testing to be sure. [17:48] So, we'll revisit this in January.. [17:48] probably. If we can integrate our ruby tooling using a jenkins plugin and figure whether/how docker is needed then the hosted instance would work [17:49] I add these notes to trello, and follow in the new year.. perfect thanks guys [17:49] * yofel spent some time reading "learn ruby the hard way" and still doesn't know why that's a language he wants to know.... [17:54] * yofel makes his way home. bbl [18:40] * yofel found a fun thing from 4.8 times while cleaning up the disk https://kyofel.de/owncloud/index.php/s/KQL9vo8C24oVqKe [18:40] how nostalgic [19:20] apt complained about a missing plymouth plugin file this morning after my normal dist-upgrade. The missing file is kubuntu-text.so. Apt suggest fixing this by installing plymouth-themes. That package is installed, and reinstalling the plymouth packages results in the same complaint, that kubuntu-text.so is missing. A search of my system confirms that it does not exist. ubuntu-text.so does. Anyone aware of this issue? This is on my [19:20] 16.04 64-bit Kubuntu installation. [19:22] I havent done an apt-get today [19:22] so I havent seen that [19:23] are you trying to run a Plymouth session? [19:24] or is it a default boot? [19:24] No, not that I am aware of. [19:25] like any customisations? [19:25] No customizations. [19:26] sorry, doing other stuff here and getting ready to leave, but Ill take a look later. Maybe yofel will be home soon and can shed some light on it [19:26] Appreciate that. Thank you. [19:28] I need to run as well, but please give a short step-by-step guide how you hit that error (or what commands one needs to enter to get the error message). I don't have an up-to-date xenial system around right now either [19:28] thanks [19:28] http://packages.ubuntu.com/xenial/plymouth-theme-ubuntu-text [19:28] apparently contains that file [19:28] the ubuntu one right, question is what requires the kubuntu one [19:29] could be that plymouth.hook that the changelog talks about [19:29] I'll look more into that later [19:29] duh Im being stupid [19:30] sorry, I better go! [19:30] bye [19:35] Some, but not all, plymouth packages are installed by default -- as far as I know. At least, I didn't specifically install any when I installed 16.04. It was after running dist-upgrade this morning that I sas the complaint by apt. To reproduce, just update your package cache and then run a dist-upgrade. The warning appears at the end of the process. [21:54] yofel: I remember that! [21:54] fun times [21:57] you hvae strange idea of fun :P [22:05] clivejo: yeah [22:05] lol [23:11] It looks like Plasma 5.4.3 is landing in Xenial? [23:13] ? that seems rather old.... [23:24] I had 5.4.2 ever since the first ISO (no PPAs etc.) [23:25] and there is 5.5 already released :) [23:27] :( Kmail is being a *beep* [23:27] everyday now it stops working [23:27] Unable to fetch item from backend (collection -1) : Unable to retrieve item from resource: Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broken. [23:27] :( [23:28] restart akonadi? [23:28] yeah and now our it mgr is freaking out ready to blame kubuntu for some gpu hangs he's having [23:28] argh [23:28] * wxl facepalms [23:28] I usually reboot and it fixes itself for a bit [23:28] rebooting seems a bit extreme [23:28] but Im building calligra and cant reboot for a while [23:28] Packagers are busy with other things. So I can save the time banging on 5.4.95 and just wait for 5.5. [23:29] but ya gotta do what ya gotta do [23:29] akonadi restart doesnt seem to fix it [23:29] clivejo: if you use ccache, you can reboot and resume building [23:30] its almost done [23:30] at dh_strip [23:40] famous last words [23:51] its still building :/ [23:54] hi Snowhog [23:54] As to plymouth on my installs; I 'did' manually install plymouth, plymouth-label, plymouth-theme-kubuntu-logo, plymouth-theme-kubuntu-text, plymouth-theme-ubuntu-text, and plymouth-xll. libplymouth4 was installed automatically at some earlier point in time. [23:55] hi clivejo [23:55] did you manage to fix the problem? [23:56] I installed those packages because I was noticing an inoccuous message during boot about plymouthd and something not being found. Didn't interfere with anything, but.... [23:58] No, but if I remove the plymouth* installed packages except libplymouth4, I won't see that complaint. See above.