/srv/irclogs.ubuntu.com/2016/10/16/#kubuntu-devel.txt

-kubuntu-ci:#kubuntu-devel- Project merger_kdesdk-thumbnailers build #96: FAILURE in 3 min 48 sec: http://kci.pangea.pub/job/merger_kdesdk-thumbnailers/96/00:03
-kubuntu-ci:#kubuntu-devel- Project mgmt_merger build #691: STILL UNSTABLE in 5 min 36 sec: http://kci.pangea.pub/job/mgmt_merger/691/00:05
-kubuntu-ci:#kubuntu-devel- Project mgmt_progenitor build #677: STILL UNSTABLE in 5 min 38 sec: http://kci.pangea.pub/job/mgmt_progenitor/677/00:05
-kubuntu-ci:#kubuntu-devel- Project merger_kdesdk-thumbnailers build #97: STILL FAILING in 16 sec: http://kci.pangea.pub/job/merger_kdesdk-thumbnailers/97/00:06
IrcsomeBot<marcinsagol> That is why nobody wants to use it :(00:13
IrcsomeBot<marcinsagol> But the channels exist00:13
yofelwell, point is that it doesn't scale, and gets very expensive with lots of users00:14
yofelthere's nothing technically wrong with it00:15
tsimonq2hai yofel :)00:15
yofelhey00:15
IrcsomeBot<marcinsagol> What is expensive?00:15
yofel"Slack" as in the service has a history limit, like 10k messages or so. To remove that you need a payed subscription, and that's per-user00:16
yofel*paid00:17
yofelThere's mattermost ofc. but then you again have the hosting problem on your hand00:18
tsimonq2Plus, I like Telegram. :)00:18
yofel(I personally love slack, but it's not without problems)00:18
IrcsomeBot<marcinsagol> For open source projects they make it free00:19
yofelhm... Telegram is.. okay. I don't like how the android app does notifications00:19
-kubuntu-ci:#kubuntu-devel- Project xenial_unstable_kgpg build #91: STILL FAILING in 12 min: http://kci.pangea.pub/job/xenial_unstable_kgpg/91/00:19
yofelit always shows me the oldest ones first, so I keep missing stuff unless I properly dismiss messages regularly00:19
IrcsomeBot<marcinsagol> There are also open source alternatives like mattermost00:21
tsimonq2yofel: File an issue here? :) https://github.com/DrKLO/Telegram00:21
tsimonq2Wait00:22
tsimonq2argh00:22
yofel^^00:23
-kubuntu-ci:#kubuntu-devel- Project xenial_unstable_kdesdk-kioslaves build #81: STILL UNSTABLE in 19 min: http://kci.pangea.pub/job/xenial_unstable_kdesdk-kioslaves/81/00:25
IrcsomeBot<CliffordTheBigRedDoggie> o/ yofel00:29
-kubuntu-ci:#kubuntu-devel- Project xenial_unstable_kppp build #7: STILL UNSTABLE in 26 min: http://kci.pangea.pub/job/xenial_unstable_kppp/7/00:32
-kubuntu-ci:#kubuntu-devel- Project yakkety_unstable_kdesdk-kioslaves build #42: STILL UNSTABLE in 32 min: http://kci.pangea.pub/job/yakkety_unstable_kdesdk-kioslaves/42/00:38
-kubuntu-ci:#kubuntu-devel- Project yakkety_unstable_kde-runtime build #201: STILL FAILING in 31 min: http://kci.pangea.pub/job/yakkety_unstable_kde-runtime/201/00:39
-kubuntu-ci:#kubuntu-devel- Project yakkety_unstable_kgpg build #91: STILL FAILING in 31 min: http://kci.pangea.pub/job/yakkety_unstable_kgpg/91/00:39
-kubuntu-ci:#kubuntu-devel- Project xenial_unstable_kgpg build #92: STILL FAILING in 22 min: http://kci.pangea.pub/job/xenial_unstable_kgpg/92/00:47
tsimonq2yofel: still around?00:55
ahoneybundo we want to put together a session at UOS about anything? Maybe making a new KCI or something?00:59
ahoneybunsince nothing it planned yet00:59
tsimonq2Whatever it is, I can't make it.01:00
tsimonq2Not to UOS/01:00
ahoneybun19:00?01:00
ahoneybunUTC01:00
ahoneybunthat's 3pm for me01:00
tsimonq220 is the absolute earliest I can go/01:00
ahoneybunmm01:01
-kubuntu-ci:#kubuntu-devel- Project yakkety_unstable_kgpg build #92: STILL FAILING in 16 min: http://kci.pangea.pub/job/yakkety_unstable_kgpg/92/01:01
ahoneybunclivejo acheronuk yofel valorie ovidiuflorin anything for UOS we need to plan for?01:02
-kubuntu-ci:#kubuntu-devel- Project yakkety_unstable_kppp build #84: STILL UNSTABLE in 1 hr 0 min: http://kci.pangea.pub/job/yakkety_unstable_kppp/84/01:06
-kubuntu-ci:#kubuntu-devel- Project xenial_unstable_kopete build #84: STILL UNSTABLE in 1 hr 0 min: http://kci.pangea.pub/job/xenial_unstable_kopete/84/01:06
-kubuntu-ci:#kubuntu-devel- Project yakkety_unstable_kopete build #61: STILL UNSTABLE in 1 hr 0 min: http://kci.pangea.pub/job/yakkety_unstable_kopete/61/01:06
-kubuntu-ci:#kubuntu-devel- Project xenial_unstable_kde-runtime build #195: STILL FAILING in 59 min: http://kci.pangea.pub/job/xenial_unstable_kde-runtime/195/01:06
-kubuntu-ci:#kubuntu-devel- Project xenial_unstable_kauth build #281: STILL UNSTABLE in 34 min: http://kci.pangea.pub/job/xenial_unstable_kauth/281/01:07
-kubuntu-ci:#kubuntu-devel- Project xenial_unstable_okular build #17: STILL UNSTABLE in 45 min: http://kci.pangea.pub/job/xenial_unstable_okular/17/01:18
-kubuntu-ci:#kubuntu-devel- Project yakkety_unstable_kde-runtime build #202: STILL FAILING in 34 min: http://kci.pangea.pub/job/yakkety_unstable_kde-runtime/202/01:18
-kubuntu-ci:#kubuntu-devel- Project yakkety_unstable_kdevelop-pg-qt build #18: STILL UNSTABLE in 19 min: http://kci.pangea.pub/job/yakkety_unstable_kdevelop-pg-qt/18/01:25
-kubuntu-ci:#kubuntu-devel- Project yakkety_unstable_kauth build #153: STILL UNSTABLE in 19 min: http://kci.pangea.pub/job/yakkety_unstable_kauth/153/01:26
-kubuntu-ci:#kubuntu-devel- Project yakkety_unstable_kidletime build #81: STILL UNSTABLE in 19 min: http://kci.pangea.pub/job/yakkety_unstable_kidletime/81/01:26
-kubuntu-ci:#kubuntu-devel- Project xenial_unstable_kde-runtime build #196: STILL FAILING in 22 min: http://kci.pangea.pub/job/xenial_unstable_kde-runtime/196/01:34
-kubuntu-ci:#kubuntu-devel- Project yakkety_unstable_okular build #95: STILL UNSTABLE in 27 min: http://kci.pangea.pub/job/yakkety_unstable_okular/95/01:34
-kubuntu-ci:#kubuntu-devel- Project xenial_unstable_kwallet build #288: STILL UNSTABLE in 9 min 55 sec: http://kci.pangea.pub/job/xenial_unstable_kwallet/288/01:44
-kubuntu-ci:#kubuntu-devel- Project yakkety_unstable_kwallet build #127: STILL UNSTABLE in 14 min: http://kci.pangea.pub/job/yakkety_unstable_kwallet/127/01:55
-kubuntu-ci:#kubuntu-devel- Project xenial_unstable_kcharselect build #226: FAILURE in 2 min 18 sec: http://kci.pangea.pub/job/xenial_unstable_kcharselect/226/02:09
-kubuntu-ci:#kubuntu-devel- Yippee, build fixed!02:24
-kubuntu-ci:#kubuntu-devel- Project xenial_unstable_kcharselect build #227: FIXED in 10 min: http://kci.pangea.pub/job/xenial_unstable_kcharselect/227/02:24
-kubuntu-ci:#kubuntu-devel- Project xenial_unstable_spectacle build #105: STILL UNSTABLE in 10 min: http://kci.pangea.pub/job/xenial_unstable_spectacle/105/02:30
tsimonq2!ninjas | Interesting guide that we may be able to adapt for KCI: https://wiki.ubuntu.com/UbuntuDevelopment/Merging/GitWorkflow02:33
tsimonq2argh you're no fun ubottu 02:34
tsimonq2clivejo, acheronuk, santa_ ^^^^02:34
-kubuntu-ci:#kubuntu-devel- Project yakkety_unstable_spectacle build #84: STILL UNSTABLE in 11 min: http://kci.pangea.pub/job/yakkety_unstable_spectacle/84/02:44
-kubuntu-ci:#kubuntu-devel- Project xenial_unstable_okteta build #113: STILL UNSTABLE in 19 min: http://kci.pangea.pub/job/xenial_unstable_okteta/113/02:50
-kubuntu-ci:#kubuntu-devel- Project xenial_unstable_umbrello build #91: STILL UNSTABLE in 19 min: http://kci.pangea.pub/job/xenial_unstable_umbrello/91/02:57
-kubuntu-ci:#kubuntu-devel- Project xenial_unstable_libkcompactdisc build #47: STILL UNSTABLE in 13 min: http://kci.pangea.pub/job/xenial_unstable_libkcompactdisc/47/02:57
-kubuntu-ci:#kubuntu-devel- Project xenial_unstable_ktp-common-internals build #207: STILL UNSTABLE in 18 min: http://kci.pangea.pub/job/xenial_unstable_ktp-common-internals/207/03:03
-kubuntu-ci:#kubuntu-devel- Project xenial_unstable_kstars build #256: STILL UNSTABLE in 26 min: http://kci.pangea.pub/job/xenial_unstable_kstars/256/03:04
-kubuntu-ci:#kubuntu-devel- Project xenial_unstable_akonadi build #267: STILL FAILING in 20 min: http://kci.pangea.pub/job/xenial_unstable_akonadi/267/03:04
-kubuntu-ci:#kubuntu-devel- Project xenial_unstable_kirigami build #33: STILL UNSTABLE in 17 min: http://kci.pangea.pub/job/xenial_unstable_kirigami/33/03:04
-kubuntu-ci:#kubuntu-devel- Project xenial_unstable_plasma-nm build #212: STILL FAILING in 17 min: http://kci.pangea.pub/job/xenial_unstable_plasma-nm/212/03:05
-kubuntu-ci:#kubuntu-devel- Project yakkety_unstable_umbrello build #76: STILL UNSTABLE in 22 min: http://kci.pangea.pub/job/yakkety_unstable_umbrello/76/03:13
-kubuntu-ci:#kubuntu-devel- Project yakkety_unstable_kstars build #124: STILL UNSTABLE in 23 min: http://kci.pangea.pub/job/yakkety_unstable_kstars/124/03:13
-kubuntu-ci:#kubuntu-devel- Project yakkety_unstable_plasma-nm build #117: STILL FAILING in 15 min: http://kci.pangea.pub/job/yakkety_unstable_plasma-nm/117/03:21
-kubuntu-ci:#kubuntu-devel- Project xenial_unstable_ktp-auth-handler build #181: STILL UNSTABLE in 17 min: http://kci.pangea.pub/job/xenial_unstable_ktp-auth-handler/181/03:21
-kubuntu-ci:#kubuntu-devel- Project yakkety_unstable_ktp-common-internals build #133: STILL UNSTABLE in 17 min: http://kci.pangea.pub/job/yakkety_unstable_ktp-common-internals/133/03:21
-kubuntu-ci:#kubuntu-devel- Project xenial_unstable_plasma-workspace build #3: STILL FAILING in 49 sec: http://kci.pangea.pub/job/xenial_unstable_plasma-workspace/3/03:21
-kubuntu-ci:#kubuntu-devel- Project xenial_unstable_plasma-workspace build #4: STILL FAILING in 44 sec: http://kci.pangea.pub/job/xenial_unstable_plasma-workspace/4/03:27
-kubuntu-ci:#kubuntu-devel- Project yakkety_unstable_kirigami build #37: STILL UNSTABLE in 22 min: http://kci.pangea.pub/job/yakkety_unstable_kirigami/37/03:27
-kubuntu-ci:#kubuntu-devel- Project xenial_unstable_plasma-nm build #213: STILL FAILING in 18 min: http://kci.pangea.pub/job/xenial_unstable_plasma-nm/213/03:28
-kubuntu-ci:#kubuntu-devel- Project yakkety_unstable_akonadi build #187: STILL FAILING in 30 min: http://kci.pangea.pub/job/yakkety_unstable_akonadi/187/03:28
-kubuntu-ci:#kubuntu-devel- Project yakkety_unstable_ktp-auth-handler build #134: STILL UNSTABLE in 12 min: http://kci.pangea.pub/job/yakkety_unstable_ktp-auth-handler/134/03:33
-kubuntu-ci:#kubuntu-devel- Project xenial_unstable_akonadi build #268: STILL FAILING in 24 min: http://kci.pangea.pub/job/xenial_unstable_akonadi/268/03:33
-kubuntu-ci:#kubuntu-devel- Project yakkety_unstable_akonadi build #188: STILL FAILING in 3 min 52 sec: http://kci.pangea.pub/job/yakkety_unstable_akonadi/188/03:34
-kubuntu-ci:#kubuntu-devel- Project xenial_unstable_akonadi build #269: STILL FAILING in 3 min 50 sec: http://kci.pangea.pub/job/xenial_unstable_akonadi/269/03:37
-kubuntu-ci:#kubuntu-devel- Project yakkety_unstable_plasma-nm build #118: STILL FAILING in 14 min: http://kci.pangea.pub/job/yakkety_unstable_plasma-nm/118/03:40
-kubuntu-ci:#kubuntu-devel- Project yakkety_unstable_plasma-workspace build #3: STILL FAILING in 48 sec: http://kci.pangea.pub/job/yakkety_unstable_plasma-workspace/3/03:40
-kubuntu-ci:#kubuntu-devel- Project xenial_unstable_akonadi build #270: STILL FAILING in 2 min 52 sec: http://kci.pangea.pub/job/xenial_unstable_akonadi/270/03:45
-kubuntu-ci:#kubuntu-devel- Project yakkety_unstable_plasma-workspace build #4: STILL FAILING in 50 sec: http://kci.pangea.pub/job/yakkety_unstable_plasma-workspace/4/03:46
-kubuntu-ci:#kubuntu-devel- Project yakkety_unstable_discover build #2: STILL UNSTABLE in 14 min: http://kci.pangea.pub/job/yakkety_unstable_discover/2/03:47
-kubuntu-ci:#kubuntu-devel- Project yakkety_unstable_akonadi-calendar build #2: STILL UNSTABLE in 9 min 53 sec: http://kci.pangea.pub/job/yakkety_unstable_akonadi-calendar/2/03:57
-kubuntu-ci:#kubuntu-devel- Project yakkety_unstable_kdepim-addons build #3: STILL FAILING in 41 sec: http://kci.pangea.pub/job/yakkety_unstable_kdepim-addons/3/03:58
-kubuntu-ci:#kubuntu-devel- Project xenial_unstable_akonadi-contacts build #38: STILL UNSTABLE in 12 min: http://kci.pangea.pub/job/xenial_unstable_akonadi-contacts/38/03:58
tsimonq2!info kdenlive unstable03:59
ubottukdenlive (source: kdenlive): non-linear video editor. In component main, is optional. Version 16.08.1-1 (unstable), package size 1915 kB, installed size 7428 kB03:59
-kubuntu-ci:#kubuntu-devel- Project xenial_unstable_kdepim-addons build #70: STILL FAILING in 38 sec: http://kci.pangea.pub/job/xenial_unstable_kdepim-addons/70/04:03
-kubuntu-ci:#kubuntu-devel- Project yakkety_unstable_kdepim-addons build #4: STILL FAILING in 1 min 8 sec: http://kci.pangea.pub/job/yakkety_unstable_kdepim-addons/4/04:04
-kubuntu-ci:#kubuntu-devel- Project xenial_unstable_kdepim-addons build #71: STILL FAILING in 1 min 5 sec: http://kci.pangea.pub/job/xenial_unstable_kdepim-addons/71/04:09
tsimonq2!info default-libmysqlclient-dev04:15
ubottuPackage default-libmysqlclient-dev does not exist in yakkety04:15
tsimonq2!info libmysqlclient-dev04:15
ubottulibmysqlclient-dev (source: mysql-5.7): MySQL database development files. In component main, is optional. Version 5.7.15-0ubuntu2 (yakkety), package size 1121 kB, installed size 6284 kB04:15
-kubuntu-ci:#kubuntu-devel- Project yakkety_unstable_plasma-desktop build #2: UNSTABLE in 35 min: http://kci.pangea.pub/job/yakkety_unstable_plasma-desktop/2/04:22
-kubuntu-ci:#kubuntu-devel- Project yakkety_unstable_akonadi build #189: STILL FAILING in 17 min: http://kci.pangea.pub/job/yakkety_unstable_akonadi/189/04:34
-kubuntu-ci:#kubuntu-devel- Project xenial_unstable_akonadi build #271: STILL FAILING in 19 min: http://kci.pangea.pub/job/xenial_unstable_akonadi/271/04:36
tsimonq2On Monday, I'll whip up a PPA and instructions for this ;)04:43
tsimonq2http://www.heliocastro.info/?p=29104:43
valoriewow04:47
valorieplease remember to blog about it so people can find it!04:47
IrcsomeBot<tsimonq2> Yep! :)04:47
IrcsomeBot<tsimonq2> Maybe I can even figure out how to spin up an ISO. :P04:48
valoriethere is a guide to making your own somewhere on the wikis04:49
valorie!iso04:50
ubottuTo mount an ISO disc image, type « sudo mount -o loop <ISO-filename> <mountpoint> » - There is a list of useful cd image conversion tools at http://wiki.linuxquestions.org/wiki/CD_Image_Conversion - Always verify the ISO using !MD5 before !burning.04:50
valorie!custom04:50
ubottuSorry, I don't know anything about custom04:50
valorie!custom iso04:50
ubottuSorry, I don't know anything about custom iso04:50
valoriehttp://askubuntu.com/questions/516687/how-do-i-make-a-custom-ubuntu-iso-for-fully-offline-installations04:52
-kubuntu-ci:#kubuntu-devel- Project yakkety_unstable_akonadi build #190: STILL FAILING in 17 min: http://kci.pangea.pub/job/yakkety_unstable_akonadi/190/04:56
tsimonq2valorie: Those no longer work.04:57
tsimonq2I've tried it before.04:57
-kubuntu-ci:#kubuntu-devel- Project xenial_unstable_akonadi build #272: STILL FAILING in 17 min: http://kci.pangea.pub/job/xenial_unstable_akonadi/272/04:59
valorieboo05:09
valoriesomehow jr made a neon one05:09
tsimonq2Well of course, maybe if I can't figure it out, I'll have to ask him.05:10
tsimonq2valorie: It would be nice if we could make a "Developer" image with kubuntu_stable that has "devel" in the sources.list.05:10
valoriehmmmm05:11
valorieI have to say that Clive's idea sounds more useful: a "professional" edition05:12
tsimonq2So then how would that work?05:12
valoriewith working kmail / kolab, libreoffice, and whatever else we think would be useful05:13
tsimonq2Heyyyyyy my fix was featured in LWN! https://lwn.net/Alerts/703321/05:13
valoriecool!05:13
tsimonq2valorie: What would be different compared to regular Kubuntu? Would we modify the existing Kubuntu to be only like a "users" or "enthusiasts" edition?05:14
valoriefor starters, we have no kolab05:14
tsimonq2kolab?05:15
* tsimonq2 DDGs05:15
valoriesecure email05:15
tsimonq2Hmm, this seems to be paid.05:16
valoriethe service is paid05:17
valoriethe server and client are free05:18
valorieafaik05:18
tsimonq2I don't like the idea of shipping something like that... :/05:18
valoriewe could offer Kube and trojita as alternatives I guess05:18
valorieanyway, ask clive05:19
tsimonq2Ok/.05:19
valorieit was his idea, not mine05:19
tsimonq2clivejo: Please elaborate on your idea of a "professional" edition of Kubuntu.05:20
tsimonq205:29
tsimonq2Ace Acer has sent you a message05:29
tsimonq2You can reply to this message by visiting your messages.05:29
tsimonq2Sorry to bother you but you manifested some interests for feedbacks about Kubuntu 16.10. 05:29
tsimonq2As you already know the reboot and shutdown make the system hangs on the Kubuntu logo. I heard that there is a newer kernel (4.8.1) and it's more stable that the current kernel in 16.10. Maybe upgrading Kubuntu kernel to 4.8 could solve some problems - it's just a guess of course but i think it's a possibility that worth exploring. 05:29
tsimonq2Now about the removal of plasmoids - using restricted drivers makes Plasma stalls at each attempt to remove a plasmoid - remember when i said i though the problem was fixed? well it seems that the problem is the nVidia drivers because all of them make Plasma stalls when removing a plasmoid. The mesa nouveau don't generate this problem. It's the first time i see the nouveau drivers being more stable05:29
tsimonq2 than the restricted drivers. On my PC(the one with the nVidia GPU and i'm using for testing new linux) it's usually the nouveau drivers that causes problems and the restricted ones are the ones being stable. I guess nVidia still need to improve their drivers. I'm not surprised because their drivers are giving me headaches on Windows as well. 05:29
tsimonq2The notification popup is also making Plasma stalls with the restricted drivers but everything returns to normal after a long time(from 5 to 10 mins) 05:29
tsimonq2One last thing. I have noticed that when installing new desktop themes they don't seem to install properly because most of them aren't showing in the themes list. 05:29
tsimonq2Since all the above already have a launchpad bug report active i don't see the need at the moment to file a new one. If you want i can keep you informed if other bugs occur or if the existing bugs are being fixed by updates or manual tweaks .05:29
tsimonq2Best Regards05:29
tsimonq2Sorry for the spam, but I just wanted to make y'all aware.05:30
tsimonq2This is a YouTube message...05:30
tsimonq2lol05:30
tsimonq2Night o/05:37
acheronukhmmm. no such problem with nvidia here07:13
soeeacheronuk: well than we shoudl test it more and release if all is fine10:40
soee5.7 is much improvement over 5.610:40
acheronuksoee: seeing what we can do with that is on my agenda for this week :)10:42
acheronuksorta got put on hold with YY etc10:43
acheronukand as said in #kubuntu, if 5.8 looks like it could be done in a reasonable time frame, I somewhat favour going straight for that10:44
soee+1 :)10:47
=== fregl_ is now known as fregl
mamarleyThat would be my preference too. :)11:20
BluesKajHey folks11:21
soeehiho BluesKaj11:34
soeemamarley: are yo familiar with nvidia-prime?11:35
BluesKajHi soee11:35
mamarleysoee: Not really.  This would likely be a better question for #ubuntu-x though.11:35
clivejotsimonq2: the idea was to have two editions of kubuntu (ie home and business/pro) have the home edition with a very light weight email client ie trojita  and apps only home users would want and the business edition with full PIM and office suites etc14:42
clivejobut as we dont have the person power to maintain one edition, it wouldnt be a smart move to try and provide two!14:43
* acheronuk nods14:46
clivejoshould be moved to wishlust14:46
clivejolist14:47
acheronukI prefer 'wishlust'14:47
BluesKaj_clivejo, yeah,  true enough , but a lighter home user edition would be welcome14:47
clivejoBluesKaj_: true, but moves us away from the default KDE experience we aim to give14:48
clivejoupstream want it installed by default14:49
BluesKaj_who needs a databased email system unless they´re in a work environment14:49
acheronukWTF is tomahawk and why am I in it's team?14:49
clivejoLOL14:49
clivejocongrats you are the new maintainer!14:50
BluesKaj_ hehe14:50
clivejoit was a good media player14:50
clivejo!info tomahawk14:50
ubottutomahawk (source: tomahawk-player): Multi source music player. In component universe, is optional. Version 0.8.4+dfsg1-0ubuntu3 (yakkety), package size 3608 kB, installed size 6366 kB14:50
acheronukwebsite looks nice. but that does not mean a lot14:51
BluesKaj_mpv is a good stand alone player ...i was using it until i decided to explore kodi more thoroughly than in the past ... itś really quite well desgned except for some clunkymess here an there14:53
acheronuksmplayer with mpv backend works nicely here :)14:54
BluesKaj_clivejo, my point about default kde is the PIM should be optional if that is possibel , but I suspect itś much too late14:56
clivejoBluesKaj_: I know your point, we've talked about it at length before14:56
BluesKaj_ right14:57
clivejowhich is why I suggested two editions14:57
clivejobut we do not have the people power to maintain two editions at present14:57
BluesKaj_and I agree , thatś a good concept14:57
BluesKaj_very unfortunate14:58
clivejohi DalekSec15:12
clivejohi DarinMiller15:12
DarinMiller\o clivejo!15:14
clivejohow are you?15:14
DarinMillervery good thanks.  15:15
DarinMillerI was really impressed by your valient effort to recover KCI.15:15
clivejohopefully we will get it patched up!15:16
clivejoif I can find someone to tell me how to add new packages now!15:16
DarinMillerI would like to understand exactly what  you did as I have no clue how a server such as KCI is setup.15:18
clivejoonce I get a better grip on it, Im planning to do a few BBB sessions on it15:19
DarinMillerexcellent15:19
clivejobasically Haruld accidently deleted the var/lib/jenkins folder on the master15:19
clivejothat held our keys for connction to our slaves15:20
clivejomy problem was that I was logging in as ubuntu and all jenkins stuff is owned by user jenkins15:21
clivejoand also on the slaves I was logging in as root, but there was another user called jenkins-slave that the master uses to control it15:22
DarinMillerthe kci server setup begs many questions: why australia, why not backed up, why not faster iron where at least one devleoper has physical access...15:24
DarinMillerdid a previous kubuntu dev used to live in Autralia?15:24
clivejoits owned by Blue Systems15:29
clivejoI have no idea why its in Australia 15:29
acheronukclivejo: I agree, I would like to go on BBB this week and get to grips with what you have done with KCI.15:32
acheronuk'this week' being tomorrow onwards15:34
clivejoacheronuk: do you know what julia is?15:35
acheronukan ex girlfriend?15:36
clivejoJulia , A high-level, high-performance dynamic programming language for technical computing , <http://julialang.org/>15:36
clivejo   Backend to use Julia with Cantor.15:36
acheronukyes, I have heard of that but never played with it15:37
clivejoseems to be synced from debian - https://launchpad.net/ubuntu/+source/julia15:38
acheronukout of date already15:41
acheronukpoint being?15:43
-kubuntu-ci:#kubuntu-devel- Project yakkety_unstable_cantor build #99: STILL FAILING in 43 min: http://kci.pangea.pub/job/yakkety_unstable_cantor/99/15:47
-kubuntu-ci:#kubuntu-devel- Project xenial_unstable_cantor build #197: STILL FAILING in 43 min: http://kci.pangea.pub/job/xenial_unstable_cantor/197/15:47
-kubuntu-ci:#kubuntu-devel- Project xenial_unstable_cantor build #198: NOW UNSTABLE in 16 min: http://kci.pangea.pub/job/xenial_unstable_cantor/198/16:09
-kubuntu-ci:#kubuntu-devel- Project yakkety_unstable_cantor build #100: NOW UNSTABLE in 23 min: http://kci.pangea.pub/job/yakkety_unstable_cantor/100/16:15
clivejohumm -- Julia not found (missing:  Julia_MAIN_HEADER) (found version "0.4.7")16:16
clivejomust need a more recent version16:17
-kubuntu-ci:#kubuntu-devel- Yippee, build fixed!16:26
-kubuntu-ci:#kubuntu-devel- Project yakkety_unstable_dolphin-plugins build #53: FIXED in 6 min 59 sec: http://kci.pangea.pub/job/yakkety_unstable_dolphin-plugins/53/16:26
-kubuntu-ci:#kubuntu-devel- Project yakkety_unstable_kdelibs4support build #89: STILL FAILING in 1 min 14 sec: http://kci.pangea.pub/job/yakkety_unstable_kdelibs4support/89/16:27
-kubuntu-ci:#kubuntu-devel- Project yakkety_unstable_kdelibs4support build #90: STILL FAILING in 1 min 27 sec: http://kci.pangea.pub/job/yakkety_unstable_kdelibs4support/90/16:34
tsimonq2o/16:34
tsimonq2clivejo: Ah ok, makes sense16:34
tsimonq2I agree with acheronuk, I want to get on BBB and get up to speed on your work with KCI16:35
clivejoonly problem is that you wont have proper access without kubuntu-dev16:36
tsimonq2Ohï¿¿16:36
tsimonq2*Oh?16:36
-kubuntu-ci:#kubuntu-devel- Yippee, build fixed!16:40
-kubuntu-ci:#kubuntu-devel- Project xenial_unstable_eventviews build #3: FIXED in 10 min: http://kci.pangea.pub/job/xenial_unstable_eventviews/3/16:40
clivejoone of you guys wanna look at kdelibs4support ?16:42
-kubuntu-ci:#kubuntu-devel- Yippee, build fixed!16:45
-kubuntu-ci:#kubuntu-devel- Project yakkety_unstable_eventviews build #3: FIXED in 11 min: http://kci.pangea.pub/job/yakkety_unstable_eventviews/3/16:45
tsimonq2clivejo: What's up with it?16:50
* tsimonq2 reads logs16:50
clivejopatch wont apply16:55
tsimonq2I see that, that's a weird patch name...16:55
clivejoneeds investigation if its just fuzz or its been applied upstream 16:56
DalekSecclivejo: Howdy.17:10
clivejohow are you?17:11
-kubuntu-ci:#kubuntu-devel- Project yakkety_unstable_kdelibs4support build #91: STILL FAILING in 22 min: http://kci.pangea.pub/job/yakkety_unstable_kdelibs4support/91/18:05
-kubuntu-ci:#kubuntu-devel- Yippee, build fixed!18:06
-kubuntu-ci:#kubuntu-devel- Project xenial_unstable_kdelibs4support build #199: FIXED in 22 min: http://kci.pangea.pub/job/xenial_unstable_kdelibs4support/199/18:06
tsimonq2Weird af...18:11
clivejotsimonq2: be careful with symbols, if they become MISSING, you need to find out why18:39
clivejothe ones marked (optional=gccinternal) shouldnt be removed as they might be used in different arch18:40
tsimonq2clivejo: ok18:40
clivejoalso see the way xenial is fixed and yakkety isnt?18:41
tsimonq2yeah18:41
clivejothat could be due to Qt versions18:41
tsimonq2I might have to reverse what I did18:41
tsimonq2oh?18:41
clivejoI believe santa_ has been marking them optional as well18:42
tsimonq2Ok18:47
tsimonq2good to know, thanks18:47
-kubuntu-ci:#kubuntu-devel- Project yakkety_unstable_kdelibs4support build #92: STILL FAILING in 37 min: http://kci.pangea.pub/job/yakkety_unstable_kdelibs4support/92/18:48
tsimonq2clivejo: and if you remember, we have the same Qt versions in KCI for both Xenial *and* Yakkety18:48
clivejoyes18:54
tsimonq2so "<clivejo> that could be due to Qt versions" doesn't explain it18:55
clivejobut xenial and yakkety have different gcc versions 18:55
clivejo!info gcc18:55
ubottugcc (source: gcc-defaults (1.163ubuntu2)): GNU C compiler. In component main, is optional. Version 4:6.1.1-1ubuntu2 (yakkety), package size 5 kB, installed size 56 kB18:55
clivejo!info gcc xenial18:55
ubottugcc (source: gcc-defaults (1.150ubuntu1)): GNU C compiler. In component main, is optional. Version 4:5.3.1-1ubuntu1 (xenial), package size 5 kB, installed size 44 kB18:55
tsimonq2ohhhhh ol18:55
tsimonq2*ok18:56
clivejowhich is why we use the (optional=gccinternal) tags18:56
tsimonq2Yeah, I see, ok18:56
tsimonq2So then what does that do?18:56
clivejoit will warn about them, but shouldnt fail the build over it18:57
tsimonq2Ok18:57
tsimonq2I'm attempting to fix jovie atm18:58
clivejowe are only building amd64 as well18:58
tsimonq2Yeah, that's a thing.18:58
clivejobut in this case you are comparing amd64 with the sam18:59
clivejothese MISSING symbols are probably due to gcc version18:59
clivejoso rather than removing them, you need to revert that commit and tag them as optional18:59
acheronukagreed. ditching symbols with only an amd64 build as justification is not a great idea19:00
tsimonq2Alright, well, I learned something new. Thanks guys. :)19:00
* acheronuk yawns19:01
clivejoif the symbol has private somewhere in the name, then its usually safe to remove19:01
clivejootherwise always investigate why they disappeared19:02
clivejoit usually indicates an ABI break19:02
tsimonq2clivejo: So if a package literally removes functions, is it safe to remove the symbols? Is there anything extra you have to do?19:03
acheronukas we found out, just because debian ditched them doesn't mean it's always ok19:03
clivejoonly if there is a SO bump19:03
tsimonq2clivejo: So please explain what that is.19:04
clivejodebian manual would be far better at explaining it19:06
clivejohttps://www.debian.org/doc/debian-policy/ch-sharedlibs.html19:06
tsimonq2Ok, I'll read this in a minute.19:07
acheronukand https://www.netfort.gr.jp/~dancer/column/libpkg-guide/libpkg-guide.html#upstreamconcerns19:07
tsimonq2So then my Akonadi symbol refresh needs to be redone19:10
acheronuk^^^ I would be happier if we at least had a look over it with santa_ clivejo etc19:11
tsimonq2Yeah, that would be a good example for this.19:11
acheronukthat is why a was a bit OMG!! when you did that the other week19:11
acheronukmay be right, but I want to make sure19:11
tsimonq2At least if one of them did it, we could see how they went about it.19:12
tsimonq2Yeah.19:12
clivejotsimonq2: whats this - https://git.launchpad.net/~kubuntu-packagers/+git/kubuntu-automation/commit/?id=f2af6875686a436dd47fae035a0208460fd115e119:12
tsimonq2I was getting annoyed at having to git clone and set up everything to work on a package that is FTBFS in KCI, so I scripted it.19:13
clivejojust dget the package from unstable PPA?19:14
tsimonq2It's not that simple.19:14
tsimonq2And it's a lot of typing when you do it over and over again.19:14
clivejowell there are a number of cases that wont work19:14
tsimonq2Example?19:14
clivejoplasma-discover for one19:14
tsimonq2Well hey, it's not meant to be complete.19:15
soeeo/19:16
tsimonq2o/ soee 19:16
acheronukneeds to be reasobaly tried and testing to be in KA though I suppose19:16
clivejohttps://git.launchpad.net/~kubuntu-packagers/+git/kubuntu-automation/tree/upstream-names.json19:16
acheronukas other people may assume it owrks19:16
clivejoif you wanted to make it smarter ^19:16
acheronukif not, that's what ~/bin/ is for19:17
tsimonq2acheronuk, clivejo: There, see my follow-up commit. :P19:18
clivejoId prefer you kept it locally, or in your own git repo until it was ready for team use19:20
-kubuntu-ci:#kubuntu-devel- Yippee, build fixed!19:20
-kubuntu-ci:#kubuntu-devel- Project xenial_unstable_kio build #283: FIXED in 22 min: http://kci.pangea.pub/job/xenial_unstable_kio/283/19:20
-kubuntu-ci:#kubuntu-devel- Yippee, build fixed!19:20
-kubuntu-ci:#kubuntu-devel- Project yakkety_unstable_kio build #153: FIXED in 32 min: http://kci.pangea.pub/job/yakkety_unstable_kio/153/19:20
-kubuntu-ci:#kubuntu-devel- Yippee, build fixed!19:20
-kubuntu-ci:#kubuntu-devel- Project xenial_unstable_jovie build #7: FIXED in 17 min: http://kci.pangea.pub/job/xenial_unstable_jovie/7/19:20
-kubuntu-ci:#kubuntu-devel- Yippee, build fixed!19:21
-kubuntu-ci:#kubuntu-devel- Project yakkety_unstable_jovie build #86: FIXED in 18 min: http://kci.pangea.pub/job/yakkety_unstable_jovie/86/19:21
-kubuntu-ci:#kubuntu-devel- Yippee, build fixed!19:46
-kubuntu-ci:#kubuntu-devel- Project yakkety_unstable_kcompletion build #76: FIXED in 26 min: http://kci.pangea.pub/job/yakkety_unstable_kcompletion/76/19:46
-kubuntu-ci:#kubuntu-devel- Yippee, build fixed!19:46
-kubuntu-ci:#kubuntu-devel- Project yakkety_unstable_kdoctools build #152: FIXED in 26 min: http://kci.pangea.pub/job/yakkety_unstable_kdoctools/152/19:46
clivejosgclark sitter shadeslayer_ yofel: if any of you have a few minutes to spare sometime to teach me how to deploy new jobs on KCI, it would be much appreciated :)19:55
tsimonq2^ same here19:56
acheronuk+1 as well19:56
acheronukback in a bit19:56
tsimonq2o/ acheronuk 19:56
acheronukI bet I miss it and have to read on logs or something :/19:57
tsimonq2clivejo: could you please take a look at plasma-sdk? that list-missing list is just too big to be misc. files...19:57
clivejo20:00 UTC on Sunday, I doubt it!19:57
tsimonq2clivejo: talking to me?19:57
clivejonope, Rik saying he'll miss it!19:58
acheronuktsimonq2: Neon's solution. Lol. https://packaging.neon.kde.org/plasma/plasma-sdk.git/commit/?h=Neon/unstable&id=1b9ccfc600165c72c6367779174c4ac395f02f9719:59
clivejothey are new files19:59
clivejoLOL19:59
tsimonq2LOOOOL19:59
acheronukone way to solve it!19:59
tsimonq2Hey, if it works!20:00
tsimonq2XD20:00
clivejopersonally I dont like it20:00
acheronukI saw that the other week and decided not to go that way!20:00
acheronukok. really back later....20:00
tsimonq2o/ acheronuk 20:01
clivejobut I cant give you a reason why I dont20:01
clivejojust doesnt feel very debian!20:01
tsimonq2clivejo: so should I try it? :P20:01
clivejotsimonq2: ask debian20:02
tsimonq2bah20:02
tsimonq2fine20:02
tsimonq2I won't20:02
tsimonq2I'll just do it properly20:02
clivejoit feels wrong to me, but I cant give you a reason20:02
clivejothey will give you the reason20:02
clivejoand you can tell me!20:02
tsimonq2It feels off to me too...20:02
clivejoseriously, ask20:03
-kubuntu-ci:#kubuntu-devel- Yippee, build fixed!20:03
-kubuntu-ci:#kubuntu-devel- Project xenial_unstable_kldap build #186: FIXED in 12 min: http://kci.pangea.pub/job/xenial_unstable_kldap/186/20:03
-kubuntu-ci:#kubuntu-devel- Yippee, build fixed!20:03
-kubuntu-ci:#kubuntu-devel- Project yakkety_unstable_kdelibs4support build #93: FIXED in 16 min: http://kci.pangea.pub/job/yakkety_unstable_kdelibs4support/93/20:03
tsimonq2HEY! Look at that! :D20:04
tsimonq2More green!20:04
clivejo:) 20:04
valorieweeee20:08
valorieis it really Sunday?20:08
tsimonq2Already, yeah.20:08
valorieand KCI is cooking again?20:08
valorieI love it20:09
tsimonq2If you mean that KCI is working, yep. :D20:09
-kubuntu-ci:#kubuntu-devel- Yippee, build fixed!20:17
-kubuntu-ci:#kubuntu-devel- Project xenial_unstable_calendarsupport build #3: FIXED in 13 min: http://kci.pangea.pub/job/xenial_unstable_calendarsupport/3/20:17
-kubuntu-ci:#kubuntu-devel- Yippee, build fixed!20:17
-kubuntu-ci:#kubuntu-devel- Project yakkety_unstable_kldap build #102: FIXED in 14 min: http://kci.pangea.pub/job/yakkety_unstable_kldap/102/20:17
clivejotsimonq2: by listing them in the install file, it allows you to see changes in future.  So if files are added or removed it gets flagged up at build time and we can decide what to do about them20:23
tsimonq2clivejo: Ok, so should I now be more specific and cite *exact* files or should I just do directories like I did in my fix a little bit ago>20:24
tsimonq2s/>/?/20:24
tsimonq2s/cite/list/20:24
clivejoif more files are added we might decide to create a new package and move some over20:24
tsimonq2Well see my question. Should I list each file individually or should I do directories?20:25
clivejowell in that particular example I would probably wildcard some of them20:25
clivejolike usr/share/kdevsavesystemview/qml/CommitsView/20:26
tsimonq2Ok, so how did I do on that commit?20:26
clivejoand usr/share/plasmate/templates/20:26
clivejobut for the binaries I would state them by name20:26
tsimonq2What is considered a binary?20:27
clivejothings that are built20:27
clivejousr/bin20:27
clivejousr/lib20:28
tsimonq2So anything in those two directories should be explicity defined, you're saying?20:28
clivejoI would have left usr/lib/*/qt5/plugins/ktexteditor/cuttlefishplugin.so20:28
clivejoI would like to know if that file ever changed location20:29
tsimonq2Ok20:31
tsimonq2When it builds in the PPA and we get the file list, I'll fix it.20:31
-kubuntu-ci:#kubuntu-devel- Project xenial_unstable_plasma-sdk build #225: NOW UNSTABLE in 21 min: http://kci.pangea.pub/job/xenial_unstable_plasma-sdk/225/20:32
-kubuntu-ci:#kubuntu-devel- Project yakkety_unstable_plasma-sdk build #119: NOW UNSTABLE in 21 min: http://kci.pangea.pub/job/yakkety_unstable_plasma-sdk/119/20:32
tsimonq2Ah great...20:32
clivejoits unstable due to the lintian warnings20:33
clivejohttp://kci.pangea.pub/job/yakkety_unstable_plasma-sdk/119/parsed_console/20:33
tsimonq2script-not-executable usr/share/applications/plasmate.desktop20:33
tsimonq2:/20:33
tsimonq2What do you suggest I do now?20:34
tsimonq2Attempt to create a debian patch *making* it executable?20:34
clivejoopen a bug upstream and suggest them make it executable20:35
tsimonq2Ok, will do.20:36
clivejobut I dont know what plasmate is!20:36
clivejoresearch in most cases20:36
clivejoyou could ask in kde-devel20:36
clivejoif its supposed to be executable or not20:37
tsimonq2Ok20:37
clivejoif it is not supposed to be, or doesnt need to be, then you could add a lintian ignore20:37
tsimonq2First20:37
clivejobut unstable isnt a problem20:37
clivejoits a warning20:37
tsimonq2If I do this, would this be sufficient?20:37
tsimonq2-usr/lib/*/qt5/plugins20:37
tsimonq2+usr/lib/*/qt5/plugins/kdevplatform/26/kdevplasmamanager.so20:37
tsimonq2+usr/lib/*/qt5/plugins/kdevsavesystemview.so20:37
tsimonq2+usr/lib/*/qt5/plugins/ktexteditor/cuttlefishplugin.so20:37
clivejoyeah, Id prefer that20:38
tsimonq2Ok, cool.20:38
clivejonow if a new plugin is added it will show us on a failed build20:38
clivejojust incase we need to do something about it20:38
-kubuntu-ci:#kubuntu-devel- Yippee, build fixed!20:39
-kubuntu-ci:#kubuntu-devel- Project yakkety_unstable_calendarsupport build #3: FIXED in 21 min: http://kci.pangea.pub/job/yakkety_unstable_calendarsupport/3/20:39
tsimonq2Ok20:39
tsimonq2clivejo: What should happen with kalarmcal?20:45
tsimonq223:27:29 KCI-E :: -./etc/xdg/kalarmcal.categories20:45
tsimonq223:27:29 KCI-E :: -./etc/xdg/kalarmcal.renamecategories20:45
tsimonq2Which package should those files go into?20:45
clivejowhat install files do you have?20:46
tsimonq2libkf5alarmcalendar5.install and libkf5alarmcalendar-dev.install20:46
valorie!info plasmate20:49
ubottuPackage plasmate does not exist in yakkety20:49
valoriepfff20:49
valorieafaik it is a little thing that helps you build and test plasma widgets20:49
valoriedunno why it isn't a plugin to kdevelop20:50
clivejowhat do you think those files are for?20:50
clivejodo they belong in a dev package?20:50
tsimonq2My guess is that these files should go in libkf5alarmcalendar-dev.install because it's similar to the other files in there.20:50
clivejoreally?20:51
tsimonq2At least it20:51
clivejo/etc/xdg are usually config files20:51
tsimonq2*it's my *guess*.20:51
tsimonq2Yes.20:51
tsimonq2clivejo: So the other one instead then?20:51
clivejomore associated to runtime config20:51
tsimonq2Ok, so I'll add to libkf5alarmcalendar5.install.20:52
-kubuntu-ci:#kubuntu-devel- Yippee, build fixed!20:52
clivejoI would put them in libkf5alarmcalendar5.install20:52
-kubuntu-ci:#kubuntu-devel- Project yakkety_unstable_kmime build #78: FIXED in 11 min: http://kci.pangea.pub/job/yakkety_unstable_kmime/78/20:52
-kubuntu-ci:#kubuntu-devel- Project xenial_unstable_plasma-sdk build #226: STILL UNSTABLE in 12 min: http://kci.pangea.pub/job/xenial_unstable_plasma-sdk/226/20:52
-kubuntu-ci:#kubuntu-devel- Project yakkety_unstable_plasma-sdk build #120: STILL UNSTABLE in 13 min: http://kci.pangea.pub/job/yakkety_unstable_plasma-sdk/120/20:53
clivejo-dev packages are for development stuff 20:53
tsimonq2clivejo: I'm bumping kleopatra's build deps to only grab GPGME 1.7.1 or greater, due to the new minimum requirement.20:58
clivejowhats the build dep?20:58
tsimonq2libgpgme11-dev20:59
tsimonq2clivejo: You got the email announcing that, right?20:59
tsimonq2So I just did this:20:59
clivejoringing a faint bell20:59
tsimonq2-               libgpgme11-dev,20:59
tsimonq2+               libgpgme11-dev (>= 1.7.1~),20:59
clivejo!info libgpgme11-dev20:59
ubottulibgpgme11-dev (source: gpgme1.0): GPGME - GnuPG Made Easy (development files). In component main, is optional. Version 1.6.0-3 (yakkety), package size 256 kB, installed size 1124 kB20:59
clivejo!info libgpgme12-dev20:59
ubottuPackage libgpgme12-dev does not exist in yakkety20:59
tsimonq2clivejo: https://mail.kde.org/pipermail/kde-distro-packagers/2016-October/000227.html20:59
clivejowho maintains it in Ubuntu21:00
tsimonq2clivejo: Apparently we just sync from Debian. who has a special team for that it seems.21:02
clivejohave they packaged the version we need?21:02
tsimonq2clivejo: Well according to upstream, 1.7.1 is not released yet, only 1.7.0.21:03
tsimonq2[2016-09-28] gpgme1.0 1.7.0-1 MIGRATED to testing (Debian testing watch)21:04
tsimonq2[2016-09-22] Accepted gpgme1.0 1.7.0-1 (source) into unstable (Daniel Kahn Gillmor)21:04
tsimonq2!info gpgme1.0 unstable21:04
ubottuPackage gpgme1.0 does not exist in unstable21:04
tsimonq2!info libgpgme11-dev unstable21:04
ubottulibgpgme11-dev (source: gpgme1.0): GPGME - GnuPG Made Easy (development files). In component main, is optional. Version 1.7.0-1 (unstable), package size 345 kB, installed size 1443 kB21:04
tsimonq2clivejo: ^^^21:04
-kubuntu-ci:#kubuntu-devel- Project xenial_unstable_kcoreaddons build #263: NOW UNSTABLE in 11 min: http://kci.pangea.pub/job/xenial_unstable_kcoreaddons/263/21:04
-kubuntu-ci:#kubuntu-devel- Yippee, build fixed!21:04
-kubuntu-ci:#kubuntu-devel- Project xenial_unstable_kcodecs build #269: FIXED in 11 min: http://kci.pangea.pub/job/xenial_unstable_kcodecs/269/21:04
-kubuntu-ci:#kubuntu-devel- Project yakkety_unstable_kcoreaddons build #107: NOW UNSTABLE in 11 min: http://kci.pangea.pub/job/yakkety_unstable_kcoreaddons/107/21:04
clivejocurious21:05
tsimonq2clivejo: I assume you have eyes on kcoreaddons?21:06
clivejoNeon have forked it21:06
clivejohttps://packaging.neon.kde.org/forks/gpgme.git/21:06
clivejotsimonq2: Im just scanning for stuff I know have issues21:07
tsimonq2Ok.21:07
tsimonq2clivejo: But for now, Kleopatra should automatically start building again once we get the new gpgme1.0 in KCI.21:08
-kubuntu-ci:#kubuntu-devel- Project xenial_unstable_kleopatra build #69: STILL FAILING in 3 min 52 sec: http://kci.pangea.pub/job/xenial_unstable_kleopatra/69/21:08
-kubuntu-ci:#kubuntu-devel- Project yakkety_unstable_kleopatra build #27: STILL FAILING in 3 min 55 sec: http://kci.pangea.pub/job/yakkety_unstable_kleopatra/27/21:08
clivejotsimonq2: you could grab the Neon packaging and build a temporary package, upload to your own PPA and copy it over to unstable when happy its building ok21:09
clivejoalso open a bug to have it updated21:09
tsimonq2clivejo: Well since it's not released upstream yet, it won't be easy to do that...21:09
tsimonq2Might have to live in experimental.21:10
clivejodo you know how to open a bug on debian21:10
tsimonq2Yep.21:10
clivejook open it upstream too21:10
clivejoand link it to LP21:10
tsimonq2I don't see the use in it because it's not in a tagged release yet.21:11
tsimonq2They'll release 1.7.1 soon enough.21:11
clivejowell thats what I thought about libdrumstick21:11
tsimonq2Give me a refresher on that?21:11
clivejoif you had time, you could go upstream, poke the maintainer and help get it into debian21:12
tsimonq2...an unreleased version?21:12
clivejosee if you can help getting it released21:13
clivejothe qt-kde guys will be interested in getting it sorted too I would think21:14
tsimonq2I just don't know if I should push upstream to release when this isn't a really big problem yet.21:14
-kubuntu-ci:#kubuntu-devel- Yippee, build fixed!21:14
-kubuntu-ci:#kubuntu-devel- Project xenial_unstable_kalarmcal build #85: FIXED in 9 min 58 sec: http://kci.pangea.pub/job/xenial_unstable_kalarmcal/85/21:14
tsimonq2It's only required on master.21:14
-kubuntu-ci:#kubuntu-devel- Yippee, build fixed!21:15
-kubuntu-ci:#kubuntu-devel- Project yakkety_unstable_kalarmcal build #69: FIXED in 10 min: http://kci.pangea.pub/job/yakkety_unstable_kalarmcal/69/21:15
-kubuntu-ci:#kubuntu-devel- Project xenial_unstable_kleopatra build #70: STILL FAILING in 3 min 49 sec: http://kci.pangea.pub/job/xenial_unstable_kleopatra/70/21:17
-kubuntu-ci:#kubuntu-devel- Project yakkety_unstable_kleopatra build #28: STILL FAILING in 3 min 55 sec: http://kci.pangea.pub/job/yakkety_unstable_kleopatra/28/21:17
-kubuntu-ci:#kubuntu-devel- Project yakkety_unstable_breeze-icons build #172: STILL FAILING in 4 min 10 sec: http://kci.pangea.pub/job/yakkety_unstable_breeze-icons/172/21:24
-kubuntu-ci:#kubuntu-devel- Project yakkety_unstable_breeze-icons build #173: STILL FAILING in 5 min 9 sec: http://kci.pangea.pub/job/yakkety_unstable_breeze-icons/173/21:34
valorietsimonq2: you could ask the devel when they plan to release?21:38
valorieif it's after April, then it's no problem21:39
valorieif before, it will be21:39
=== mwhudson_ is now known as mwhudson
tsimonq2YEAH BOI21:43
tsimonq2Plasma 5.8.1 landing in Sid!21:43
clivejonice21:45
clivejoits at times like this I dont like ubuntu's release cycle!21:45
SnowhogI've no idea exactly how many people are running Kubuntu Linux (who does, really?), but it's got to be a lot 'world wide'. I know I'm curious, even if most are not, but exactly how many people are actually responsible for making it available to 'the masses'?21:45
mamarleyIs there any reason why 5.8.x can't be staged?  Is KCI still too broken to do that?21:46
clivejomamarley: staging script works with dev version21:46
clivejoat the moment we dont have a dev version21:46
mamarleyCould it not be rejiggered to have the version selected at runtime?21:48
tsimonq2clivejo: I think we should really look at eliminating that rule.21:48
tsimonq2Like seriously.21:48
clivejorules or guidelines are usually there for a reason21:49
tsimonq2For this one, I don't see the reason...21:49
-kubuntu-ci:#kubuntu-devel- Yippee, build fixed!21:50
-kubuntu-ci:#kubuntu-devel- Project yakkety_unstable_knotifications build #78: FIXED in 8 min 54 sec: http://kci.pangea.pub/job/yakkety_unstable_knotifications/78/21:50
clivejojust because the reason isnt obvious, doesnt mean its valid!21:50
clivejoinvalid21:50
Snowhogclivejo: Also doesn't mean it is "still" valid.21:50
tsimonq2^^^^^^^^^^^^^^21:50
clivejoall I know is that its worked for many releases21:51
clivejoand you should plan your battles to win the war21:51
valoriewould be so great to be able to sync 5.8.1 and get it into releases though21:59
valorieI want it soooooo bad21:59
tsimonq2Yeah22:00
acheronukneed to to it properly, otherwise we makes ourselves bigger headaches down the line. we found that with yakkety.22:02
valorieamen22:02
acheronukas much as we may *want* it right now22:02
valoriewould be good to have yofel chime in about now......22:02
tsimonq2^22:02
DarinMillervalorie: what do you like about plasma 5.8.x?  I have it running a one of my boxes and other than the super key assigned to the menu, I do not notice much difference relative to 5.7.5.22:06
valoriebecause it's the newest!22:07
valorieand everybody else is getting it22:07
* valorie is just being childish22:07
valoriebut I do love running the latest22:07
acheronukthere are 2 more bug fix releases of 5.8 due this month 5.8.2 and 5.8.3 on Nov 1st 22:08
acheronukpersonally I think we should take a little time to plan and let kde fix some more release bugs on those22:09
valorieoh, I'm waiting22:10
valoriealthough I could install neon on my travel computer, just for testing22:11
DarinMillerI recommend waiting for at least 5.8.3 as plasma 5.8.9 in Neon still struggles with dual monitor/primary monitor assignments.22:11
acheronukour packaging is out of sync with debian, so that probably needs sorting before we leap and stage too much22:11
valorieacheronuk: amen to that22:13
valoriefirst things first22:13
valorieimo getting all of our packages into XX backports if appropriate and YY releases would be a good first step22:13
valoriesince we've already done the work22:14
tsimonq2Yeah.22:14
tsimonq2I really think we need a lot of improvements in our workflow.22:15
tsimonq2Yakkety wasn't a good release because we had to cram everything in at the last minute.22:15
tsimonq2That's not acceptable.22:15
acheronuknor is leaping to do something ad hoc just because you want something new and shiny22:16
acheronuka sustainable middle ground is needed22:17
mparilloDarinMiller: I know you are not asking me, but one plus for 5.8.1 that I saw on Manjaro Unstable (and now landed in Manjaro Testing): SuperKey brings up the Kicker.22:18
mparilloFrom the end-userYakkety as a much better relase for me than Xenial was.22:19
mparilloend-user's PoV, 22:19
acheronukin lieu a formal planning meeting, I would like to get on BBB one evening this week to have a chat about this22:19
valorietsimonq2: it's true that our workflow pretty much sucked at the end, but we've been working pretty hard to fix that22:20
valoriethe lack of Kubuntu Developers lately has hurt22:20
DarinMillermparillo: I totally agree with with the super key feature and the YY is much bettter than ZZ.22:20
tsimonq2Wasn't Xenial an even worse release on our side?22:20
valoriemparillo: I agree that Yakkety has been great, and even better then xenial22:21
valorieand xenial has been damn fine22:21
acheronukto me it was not so much the workflow, but the inability to apply it that hurt22:22
valorieright22:22
-kubuntu-ci:#kubuntu-devel- Project yakkety_unstable_kcrash build #150: NOW UNSTABLE in 6 min 53 sec: http://kci.pangea.pub/job/yakkety_unstable_kcrash/150/22:24
-kubuntu-ci:#kubuntu-devel- Yippee, build fixed!22:28
-kubuntu-ci:#kubuntu-devel- Project yakkety_unstable_kdgantt2 build #84: FIXED in 8 min 24 sec: http://kci.pangea.pub/job/yakkety_unstable_kdgantt2/84/22:28
-kubuntu-ci:#kubuntu-devel- Project yakkety_unstable_minuet build #25: STILL FAILING in 5 min 23 sec: http://kci.pangea.pub/job/yakkety_unstable_minuet/25/22:29
SnowhogWhat I 'hear' in this discussion, (assuming my hearing isn't going as is my sight) is a desire/need to change Kubuntu to a rolling release (as many users continually opine that is should be).22:29
valoriewell, I like the latest22:31
valoriebut I don't want to change us to rolling, no22:31
valoriethere is neon for that22:31
tsimonq2^22:31
valorieI want us to be excellent22:31
acheronukkubuntu as a flavour of ubuntu is not rolling.22:31
tsimonq2Me too.22:31
acheronuka rolling kubuntu would be something else22:32
acheronukwhy try to ape Neon, when we can't beat them at their game?22:32
tsimonq2Yeah.22:32
valoriethere are lots of reasons I love not just the distro, but the community here22:34
valorieI'm happy that neon is having success, but that's separate from us22:34
valorieI want us to have fun and be successful doing *our* thing22:35
SnowhogDon't get me wrong; I also find Kubuntu Linux to be my preferred OS. I do have KDE neon in a VM, and I keep it up to date, but Kubuntu is my primary OS.22:35
=== Squt is now known as Sput
acheronukSnowhog: I have Neon dev-unstable on my laptop and am typing from it now22:36
Snowhogacheronuk: Yes, Developer Edition of KDE neon in my VM also.22:36
acheronukI don't see a conflict there. 22:37
tsimonq2So acheronuk already has Plasma 5.8. :D22:37
acheronukI have plasma 5.8.90 :P22:37
tsimonq2oooOOOoo22:37
acheronukmy main PC is YY kubuntu though22:38
tsimonq2*16.1022:38
tsimonq2Shush with all the "YY" nonsense. :P22:38
SnowhogIf I may ask, what is going to (continue to) distinquish Kubuntu Linux from KDE neon? If one compares them side by side, they 'look' very similar.22:39
tsimonq2Neon is rolling, we have releases22:40
acheronukto be honest, so so most kde distros at the moment22:40
tsimonq2We focus on stability22:40
-kubuntu-ci:#kubuntu-devel- Project yakkety_unstable_minuet build #26: STILL FAILING in 6 min 23 sec: http://kci.pangea.pub/job/yakkety_unstable_minuet/26/22:41
tsimonq2Neon is about getting things out to users fast22:41
tsimonq2Also, afair, KDE Neon doesn't ship Apps, but we do.22:42
acheronukNeon is a dev tool that also has a user edition22:42
acheronukNeon does most of the kde apps now22:42
valorie"some"22:43
valorieperhaps most or all at some point22:43
mparilloBut speed in dropping KDE updates at the expense of supporting a wider variety of use cases. That is why they persist in claiming they are not a distro. What they mean is they do not support all the use cases a full-featured distro usually does.22:43
valoriethat isn't their focus unless the devel of the app ask, or users ask22:44
valoriemparillo: exactly22:44
acheronukindeed. a kubuntu user can pick what they like from the rest of ubuntu, and know it should work22:45
acheronukeven change DE without a reinstall or risk of big breakage22:45
tsimonq2Bah, let's just switch to Arch. :P22:45
-kubuntu-ci:#kubuntu-devel- Yippee, build fixed!22:45
-kubuntu-ci:#kubuntu-devel- Project yakkety_unstable_kwayland build #71: FIXED in 15 min: http://kci.pangea.pub/job/yakkety_unstable_kwayland/71/22:45
SnowhogI do understand that KDE neon was established for rapid testing of KDE, and that it isn't (even though many 'think' it is) a "distribution"; I keep telling those on our forum who believe otherwise, that it's a "repository".22:46
-kubuntu-ci:#kubuntu-devel- Yippee, build fixed!22:46
-kubuntu-ci:#kubuntu-devel- Project xenial_unstable_kwayland build #204: FIXED in 15 min: http://kci.pangea.pub/job/xenial_unstable_kwayland/204/22:46
tsimonq2Yeah.22:46
tsimonq2It's in a grey area.22:46
acheronukSnowhog: yes, the forumites do see a tad obsessed with neon at the moment22:46
acheronuk*seem22:47
valorieit's the hot new thing22:47
valorieand I wish them the best22:48
Snowhogacheronuk: Well, partly/entirely, because it has the 'latest/greatest' and they wonder why such ins't available in Kubuntu. KDE neon as such, is/has become a double-edged sword.22:48
valoriebut we have a large user base that we care about22:48
valorieSnowhog: yeah22:48
Snowhog"<valorie> but we have a large user base that we care about" -- And I/we really do appreciate that!22:49
-kubuntu-ci:#kubuntu-devel- Project xenial_unstable_breeze-icons build #288: STILL FAILING in 7 min 14 sec: http://kci.pangea.pub/job/xenial_unstable_breeze-icons/288/22:49
mparilloI disagree. It was a repository when you added it to Kubuntu sources and apt update'd. Now that it is an installable ISO, of course it is a distro. The important messaging point is that it is not full-featured. It is there to test the latest and greatest KDE S/W. Just as there are many other distros targeted at a single use case (Penetration Testing, Disk Recovery, Network Sniffing, etc.)22:52
mparilloAll of them are distros also, but they are not your daily 'runner'.22:53
Snowhogmparillo: Well, 'others' may claim it's a distro, but they who put it together insist it is not.22:53
acheronukpartly semantics and party politics22:54
SnowhogWhat KDE neon "is" is a tool.22:54
SnowhogA tool for their developers.22:54
-kubuntu-ci:#kubuntu-devel- Project xenial_unstable_kgpg build #93: STILL FAILING in 4 min 48 sec: http://kci.pangea.pub/job/xenial_unstable_kgpg/93/22:54
-kubuntu-ci:#kubuntu-devel- Project yakkety_unstable_kgpg build #93: STILL FAILING in 4 min 52 sec: http://kci.pangea.pub/job/yakkety_unstable_kgpg/93/22:54
acheronukit has a user editions, but that is not really it's point22:55
mparilloI assume the worry is that if they admit it is a kde distro, and since they are the only distro that is a KDE project, then there will be a perception that Neon is THE KDE distro. And they (and KDE) want to stay a million miles from there.22:58
-kubuntu-ci:#kubuntu-devel- Project xenial_unstable_kcrash build #274: UNSTABLE in 15 min: http://kci.pangea.pub/job/xenial_unstable_kcrash/274/22:58
-kubuntu-ci:#kubuntu-devel- Project xenial_unstable_breeze-icons build #289: STILL FAILING in 4 min 3 sec: http://kci.pangea.pub/job/xenial_unstable_breeze-icons/289/22:58
mparilloBut sorry for taking this -offtopic22:59
tsimonq2IMHO this is on topic enough.22:59
acheronukas I said the other day, I would actively like to do some stuff on Neon/KDE. hopefully for benefit going both ways 23:00
tsimonq2I would personally rather go the Debian route.23:01
acheronukI think any route you take is likely to be a bit circular in that respect anyway23:02
-kubuntu-ci:#kubuntu-devel- Project xenial_unstable_kgpg build #94: STILL FAILING in 12 min: http://kci.pangea.pub/job/xenial_unstable_kgpg/94/23:12
-kubuntu-ci:#kubuntu-devel- Yippee, build fixed!23:13
-kubuntu-ci:#kubuntu-devel- Project xenial_unstable_bluez-qt build #299: FIXED in 28 min: http://kci.pangea.pub/job/xenial_unstable_bluez-qt/299/23:13
-kubuntu-ci:#kubuntu-devel- Project yakkety_unstable_kgpg build #94: STILL FAILING in 13 min: http://kci.pangea.pub/job/yakkety_unstable_kgpg/94/23:13
clivejohi Vorap, shouldnt you be in bed?!?23:22
-kubuntu-ci:#kubuntu-devel- Project xenial_unstable_kgpg build #95: STILL FAILING in 3 min 46 sec: http://kci.pangea.pub/job/xenial_unstable_kgpg/95/23:22
-kubuntu-ci:#kubuntu-devel- Project yakkety_unstable_kgpg build #95: STILL FAILING in 3 min 49 sec: http://kci.pangea.pub/job/yakkety_unstable_kgpg/95/23:22
tsimonq2clivejo: shouldn't *YOU* be in bed?!? :P23:23
clivejoyes I should23:23
clivejotrying to get a few things sorted out23:24
tsimonq2OOH, what?23:24
clivejolist of stuff, cant remember23:25
valoriemparillo: any discussion of our mission and vision for Kubuntu is super-on-topic23:28
tsimonq2^^^23:28
tsimonq2clivejo: *can't23:28
valoriepffff23:30
-kubuntu-ci:#kubuntu-devel- Project xenial_unstable_kgpg build #96: STILL FAILING in 3 min 45 sec: http://kci.pangea.pub/job/xenial_unstable_kgpg/96/23:31
-kubuntu-ci:#kubuntu-devel- Project yakkety_unstable_kgpg build #96: STILL FAILING in 4 min 22 sec: http://kci.pangea.pub/job/yakkety_unstable_kgpg/96/23:32
tsimonq2clivejo: When you have a minute, could you please take a look at kde-baseapps?23:39
clivejowhat do I need to look at?23:39
clivejoDebian ABI manager?23:43
IrcsomeBot<tsimonq2> I'm unsure why it's FTBFS23:44
clivejosanta_ had to use the Debian ABI manager to fix an ABI breakage23:46
IrcsomeBot<tsimonq2> OK, so then how is that fixed?23:47
IrcsomeBot<tsimonq2> I mean the FTBFS.23:47
clivejowell they have done a lot of work upstream23:49
clivejohttps://quickgit.kde.org/?p=kde-baseapps.git23:49
acheronukkde-baseapps has now been ported AFAIK23:49
clivejoI would first of all remove the Debian ABI Manager23:49
acheronukso yes ^^^23:49
IrcsomeBot<tsimonq2> How is that done?23:50
acheronukdid we not go over this the other day?23:50
tsimonq2I'm unsure.23:52
acheronukI may have just been talking to clivejo 23:52
tsimonq2Ok, when?23:52
acheronukhttps://irclogs.ubuntu.com/2016/10/02/%23kubuntu-devel.html#t22:2623:55
acheronukI was talking to you :P23:55
clivejotsimonq2: great practice for you!23:56
tsimonq2acheronuk: that's not much23:57
clivejoI said it once and Ill say it again!23:57
tsimonq2clivejo: I thought you were talking about Akonadi symbols...23:57
clivejono, was talking about removing the ABI manager, I think23:57
acheronukNeon have already packaged the port, so you can have a loo at that if need be23:58
acheronuk*look23:58
clivejoif you dont know what the ABI Manager is, its worth a reading up on23:59

Generated by irclog2html.py 2.7 by Marius Gedminas - find it at mg.pov.lt!