[00:00]  * acheronuk tries to remember which bit of 5.8 needs it
[00:00] <clivejo> KCI is packaging it
[00:00] <clivejo> https://launchpad.net/~kubuntu-ci/+archive/ubuntu/unstable/+packages?field.name_filter=kirigami&field.status_filter=published&field.series_filter=
[00:00] <clivejo> discover @ acheronuk
[00:00] <clivejo> the new KDE Store
[00:01] <acheronuk> not in 5.8? in 5.8.90 
[00:02] <clivejo> oh I thought they said they would be trying to get it into 5.8
[00:02] <acheronuk> not 100% sure
[00:03] <clivejo> anyway, its bed time for me.  
[00:03] <acheronuk> can work that out later
[00:03] <clivejo> tsimonq2: if you look back at the release announcements for apps and compile a list of new packages
[00:03] <acheronuk> night clive :)
[00:04] <clivejo> santa_: can you can ping me tomorrow when you think the scripts are ready for testing?
[00:04] <acheronuk> santa_: and me please :)
[00:05] <tsimonq2> Yo necesito estudiar Español y escribo para la clase de ingles. ¡Hasta mañana!
[00:05] <clivejo> acheronuk: good night and get to bed yourself!
[00:05] <tsimonq2> o/ clivejo 
[00:05]  * acheronuk sheepishly looks at clock
[00:06] <santa_> clivejo, acheronuk: sure. mind if push that change to frameworks?
[00:06] <santa_> tsimonq2: que tengas suerte estudiando español
[00:07] <clivejo> tonight?
[00:07] -kubuntu-ci:#kubuntu-devel- Yippee, build fixed!
[00:07] -kubuntu-ci:#kubuntu-devel- Project mgmt_merger build #704: FIXED in 6 min 27 sec: http://kci.pangea.pub/job/mgmt_merger/704/
[00:07] -kubuntu-ci:#kubuntu-devel- Yippee, build fixed!
[00:07] -kubuntu-ci:#kubuntu-devel- Project mgmt_progenitor build #690: FIXED in 6 min 30 sec: http://kci.pangea.pub/job/mgmt_progenitor/690/
[00:08] <santa_> clivejo: yep, now, but I can wait if you prefer
[00:08] <clivejo> ^^^  Really wants to figure out how to add jobs to that thing!
[00:10] <acheronuk> zzzzzzzzzzzzz
[00:10] <acheronuk> night all
[00:10] <clivejo> santa_: ok, can you send an email to devel just saying what you have done etc
[00:11] <acheronuk> clivejo: when you figure it out, please show me 
[00:11] <clivejo> so everyone knows they need to pull to refresh local copies they might be working on
[00:11]  * clivejo is gone this time
[00:13] <mhall119> valorie: I'd be happy to help the peruse developer make a snap of their package if they're interested
[00:15] <tsimonq2_> santa_: Gracias.
[00:27] -kubuntu-ci:#kubuntu-devel- Project yakkety_unstable_kdesdk-kioslaves build #54: STILL UNSTABLE in 19 min: http://kci.pangea.pub/job/yakkety_unstable_kdesdk-kioslaves/54/
[00:27] -kubuntu-ci:#kubuntu-devel- Project xenial_unstable_kdesdk-kioslaves build #93: STILL UNSTABLE in 19 min: http://kci.pangea.pub/job/xenial_unstable_kdesdk-kioslaves/93/
[00:28] -kubuntu-ci:#kubuntu-devel- Project yakkety_unstable_kppp build #97: STILL UNSTABLE in 19 min: http://kci.pangea.pub/job/yakkety_unstable_kppp/97/
[00:28] -kubuntu-ci:#kubuntu-devel- Project xenial_unstable_ktouch build #99: FAILURE in 19 min: http://kci.pangea.pub/job/xenial_unstable_ktouch/99/
[00:28] -kubuntu-ci:#kubuntu-devel- Project yakkety_unstable_kmix build #96: FAILURE in 19 min: http://kci.pangea.pub/job/yakkety_unstable_kmix/96/
[00:28] -kubuntu-ci:#kubuntu-devel- Project xenial_unstable_palapeli build #43: FAILURE in 19 min: http://kci.pangea.pub/job/xenial_unstable_palapeli/43/
[00:28] -kubuntu-ci:#kubuntu-devel- Project yakkety_unstable_sweeper build #101: FAILURE in 19 min: http://kci.pangea.pub/job/yakkety_unstable_sweeper/101/
[00:28] -kubuntu-ci:#kubuntu-devel- Project xenial_unstable_libkdeedu build #105: FAILURE in 19 min: http://kci.pangea.pub/job/xenial_unstable_libkdeedu/105/
[00:28] -kubuntu-ci:#kubuntu-devel- Project xenial_unstable_kppp build #20: STILL UNSTABLE in 19 min: http://kci.pangea.pub/job/xenial_unstable_kppp/20/
[00:35] -kubuntu-ci:#kubuntu-devel- Project xenial_unstable_okular build #30: STILL UNSTABLE in 14 min: http://kci.pangea.pub/job/xenial_unstable_okular/30/
[00:35] -kubuntu-ci:#kubuntu-devel- Project yakkety_unstable_kde-runtime build #226: STILL FAILING in 25 min: http://kci.pangea.pub/job/yakkety_unstable_kde-runtime/226/
[00:44] -kubuntu-ci:#kubuntu-devel- Project xenial_unstable_kcoreaddons build #276: STILL UNSTABLE in 17 min: http://kci.pangea.pub/job/xenial_unstable_kcoreaddons/276/
[00:45] -kubuntu-ci:#kubuntu-devel- Project xenial_unstable_kopete build #97: STILL UNSTABLE in 36 min: http://kci.pangea.pub/job/xenial_unstable_kopete/97/
[00:54] -kubuntu-ci:#kubuntu-devel- Yippee, build fixed!
[00:54] -kubuntu-ci:#kubuntu-devel- Project xenial_unstable_ktouch build #100: FIXED in 20 min: http://kci.pangea.pub/job/xenial_unstable_ktouch/100/
[00:54] -kubuntu-ci:#kubuntu-devel- Yippee, build fixed!
[00:54] -kubuntu-ci:#kubuntu-devel- Yippee, build fixed!
[00:54] -kubuntu-ci:#kubuntu-devel- Yippee, build fixed!
[00:54] -kubuntu-ci:#kubuntu-devel- Project yakkety_unstable_kmix build #97: FIXED in 21 min: http://kci.pangea.pub/job/yakkety_unstable_kmix/97/
[00:54] -kubuntu-ci:#kubuntu-devel- Project xenial_unstable_palapeli build #44: FIXED in 20 min: http://kci.pangea.pub/job/xenial_unstable_palapeli/44/
[00:54] -kubuntu-ci:#kubuntu-devel- Project yakkety_unstable_sweeper build #102: FIXED in 20 min: http://kci.pangea.pub/job/yakkety_unstable_sweeper/102/
[00:54] -kubuntu-ci:#kubuntu-devel- Yippee, build fixed!
[00:54] -kubuntu-ci:#kubuntu-devel- Project xenial_unstable_libkdeedu build #106: FIXED in 20 min: http://kci.pangea.pub/job/xenial_unstable_libkdeedu/106/
[00:54] -kubuntu-ci:#kubuntu-devel- Project yakkety_unstable_okular build #108: STILL UNSTABLE in 20 min: http://kci.pangea.pub/job/yakkety_unstable_okular/108/
[00:54] -kubuntu-ci:#kubuntu-devel- Project yakkety_unstable_kdevelop-pg-qt build #30: STILL UNSTABLE in 33 min: http://kci.pangea.pub/job/yakkety_unstable_kdevelop-pg-qt/30/
[00:54] -kubuntu-ci:#kubuntu-devel- Project yakkety_unstable_kauth build #166: STILL UNSTABLE in 33 min: http://kci.pangea.pub/job/yakkety_unstable_kauth/166/
[00:54] -kubuntu-ci:#kubuntu-devel- Project xenial_unstable_kde-runtime build #220: STILL FAILING in 45 min: http://kci.pangea.pub/job/xenial_unstable_kde-runtime/220/
[01:02] -kubuntu-ci:#kubuntu-devel- Project yakkety_unstable_kde-runtime build #227: STILL FAILING in 22 min: http://kci.pangea.pub/job/yakkety_unstable_kde-runtime/227/
[01:12] -kubuntu-ci:#kubuntu-devel- Project yakkety_unstable_kopete build #74: STILL UNSTABLE in 1 hr 3 min: http://kci.pangea.pub/job/yakkety_unstable_kopete/74/
[01:21] -kubuntu-ci:#kubuntu-devel- Project xenial_unstable_kde-runtime build #221: STILL FAILING in 21 min: http://kci.pangea.pub/job/xenial_unstable_kde-runtime/221/
[01:27] -kubuntu-ci:#kubuntu-devel- Project yakkety_unstable_kcrash build #163: STILL UNSTABLE in 15 min: http://kci.pangea.pub/job/yakkety_unstable_kcrash/163/
[01:27] -kubuntu-ci:#kubuntu-devel- Project xenial_unstable_kauth build #294: STILL UNSTABLE in 14 min: http://kci.pangea.pub/job/xenial_unstable_kauth/294/
[01:27] -kubuntu-ci:#kubuntu-devel- Project xenial_unstable_kcrash build #287: STILL UNSTABLE in 15 min: http://kci.pangea.pub/job/xenial_unstable_kcrash/287/
[01:59] -kubuntu-ci:#kubuntu-devel- Project yakkety_unstable_kwallet build #141: STILL UNSTABLE in 11 min: http://kci.pangea.pub/job/yakkety_unstable_kwallet/141/
[02:00] -kubuntu-ci:#kubuntu-devel- Project xenial_unstable_kwallet build #302: STILL UNSTABLE in 11 min: http://kci.pangea.pub/job/xenial_unstable_kwallet/302/
[03:12] -kubuntu-ci:#kubuntu-devel- Project yakkety_unstable_spectacle build #95: STILL UNSTABLE in 10 min: http://kci.pangea.pub/job/yakkety_unstable_spectacle/95/
[03:17] -kubuntu-ci:#kubuntu-devel- Project yakkety_unstable_umbrello build #87: STILL UNSTABLE in 17 min: http://kci.pangea.pub/job/yakkety_unstable_umbrello/87/
[03:17] -kubuntu-ci:#kubuntu-devel- Project xenial_unstable_spectacle build #116: STILL UNSTABLE in 15 min: http://kci.pangea.pub/job/xenial_unstable_spectacle/116/
[03:23] -kubuntu-ci:#kubuntu-devel- Project yakkety_unstable_kstars build #135: STILL UNSTABLE in 24 min: http://kci.pangea.pub/job/yakkety_unstable_kstars/135/
[03:23] -kubuntu-ci:#kubuntu-devel- Project xenial_unstable_kstars build #267: STILL UNSTABLE in 23 min: http://kci.pangea.pub/job/xenial_unstable_kstars/267/
[03:24] -kubuntu-ci:#kubuntu-devel- Project xenial_unstable_umbrello build #102: STILL UNSTABLE in 23 min: http://kci.pangea.pub/job/xenial_unstable_umbrello/102/
[03:29] -kubuntu-ci:#kubuntu-devel- Project xenial_unstable_okteta build #124: STILL UNSTABLE in 16 min: http://kci.pangea.pub/job/xenial_unstable_okteta/124/
[03:33] -kubuntu-ci:#kubuntu-devel- Project yakkety_unstable_kolourpaint build #96: FAILURE in 9 min 12 sec: http://kci.pangea.pub/job/yakkety_unstable_kolourpaint/96/
[03:38] -kubuntu-ci:#kubuntu-devel- Project yakkety_unstable_kde-baseapps build #112: STILL FAILING in 3 min 57 sec: http://kci.pangea.pub/job/yakkety_unstable_kde-baseapps/112/
[03:39] -kubuntu-ci:#kubuntu-devel- Project yakkety_unstable_kirigami build #49: STILL UNSTABLE in 9 min 11 sec: http://kci.pangea.pub/job/yakkety_unstable_kirigami/49/
[03:39] -kubuntu-ci:#kubuntu-devel- Project xenial_unstable_ktp-common-internals build #218: STILL UNSTABLE in 15 min: http://kci.pangea.pub/job/xenial_unstable_ktp-common-internals/218/
[03:41] -kubuntu-ci:#kubuntu-devel- Project yakkety_unstable_kolourpaint build #97: STILL FAILING in 3 min 48 sec: http://kci.pangea.pub/job/yakkety_unstable_kolourpaint/97/
[03:44] -kubuntu-ci:#kubuntu-devel- Project yakkety_unstable_ktp-common-internals build #144: STILL UNSTABLE in 14 min: http://kci.pangea.pub/job/yakkety_unstable_ktp-common-internals/144/
[03:45] -kubuntu-ci:#kubuntu-devel- Project yakkety_unstable_plasma-mediacenter build #112: STILL UNSTABLE in 14 min: http://kci.pangea.pub/job/yakkety_unstable_plasma-mediacenter/112/
[03:49] -kubuntu-ci:#kubuntu-devel- Project yakkety_unstable_plasma-sdk build #131: STILL UNSTABLE in 9 min 35 sec: http://kci.pangea.pub/job/yakkety_unstable_plasma-sdk/131/
[03:50] <xor-freenet> the yesterday security updates of mysql broke akonadi/kontact/kmail completely on kubuntu 14.04... any idea in which channel a maintainer of one of those would hang out so i can notify them?  
[03:50] -kubuntu-ci:#kubuntu-devel- Project xenial_unstable_kolourpaint build #85: FAILURE in 10 min: http://kci.pangea.pub/job/xenial_unstable_kolourpaint/85/
 #ubuntu-hardened if the security team broke it
 Or #ubuntu-devel for normal issues
 Or #ubuntu-release if it broke everything
 Take your pick. :)
[03:51] <xor-freenet> thank you! :)
 No problem. :)
[03:54] -kubuntu-ci:#kubuntu-devel- Project xenial_unstable_libkcompactdisc build #58: STILL UNSTABLE in 14 min: http://kci.pangea.pub/job/xenial_unstable_libkcompactdisc/58/
[03:59] -kubuntu-ci:#kubuntu-devel- Project yakkety_unstable_discover build #13: STILL UNSTABLE in 10 min: http://kci.pangea.pub/job/yakkety_unstable_discover/13/
[03:59] -kubuntu-ci:#kubuntu-devel- Project yakkety_unstable_plasma-integration build #13: STILL UNSTABLE in 14 min: http://kci.pangea.pub/job/yakkety_unstable_plasma-integration/13/
[03:59] -kubuntu-ci:#kubuntu-devel- Project xenial_unstable_plasma-mediacenter build #195: STILL UNSTABLE in 18 min: http://kci.pangea.pub/job/xenial_unstable_plasma-mediacenter/195/
[04:00] -kubuntu-ci:#kubuntu-devel- Project yakkety_unstable_kde-baseapps build #113: STILL FAILING in 17 min: http://kci.pangea.pub/job/yakkety_unstable_kde-baseapps/113/
[04:00] -kubuntu-ci:#kubuntu-devel- Project xenial_unstable_kde-baseapps build #107: STILL FAILING in 5 min 50 sec: http://kci.pangea.pub/job/xenial_unstable_kde-baseapps/107/
[04:00] -kubuntu-ci:#kubuntu-devel- Project xenial_unstable_kolourpaint build #86: STILL FAILING in 4 min 44 sec: http://kci.pangea.pub/job/xenial_unstable_kolourpaint/86/
[04:05] -kubuntu-ci:#kubuntu-devel- Project yakkety_unstable_ktp-auth-handler build #145: STILL UNSTABLE in 20 min: http://kci.pangea.pub/job/yakkety_unstable_ktp-auth-handler/145/
[04:05] -kubuntu-ci:#kubuntu-devel- Project xenial_unstable_kirigami build #45: STILL UNSTABLE in 24 min: http://kci.pangea.pub/job/xenial_unstable_kirigami/45/
[04:05] -kubuntu-ci:#kubuntu-devel- Project xenial_unstable_ktp-auth-handler build #192: STILL UNSTABLE in 25 min: http://kci.pangea.pub/job/xenial_unstable_ktp-auth-handler/192/
[04:10] -kubuntu-ci:#kubuntu-devel- Project xenial_unstable_kde-baseapps build #108: STILL FAILING in 4 min 58 sec: http://kci.pangea.pub/job/xenial_unstable_kde-baseapps/108/
[04:10] -kubuntu-ci:#kubuntu-devel- Project xenial_unstable_discover build #15: STILL FAILING in 5 min 1 sec: http://kci.pangea.pub/job/xenial_unstable_discover/15/
[04:11] -kubuntu-ci:#kubuntu-devel- Project xenial_unstable_cantor build #202: STILL UNSTABLE in 31 min: http://kci.pangea.pub/job/xenial_unstable_cantor/202/
[04:11] -kubuntu-ci:#kubuntu-devel- Project yakkety_unstable_akonadi-calendar build #13: STILL UNSTABLE in 12 min: http://kci.pangea.pub/job/yakkety_unstable_akonadi-calendar/13/
[04:12] -kubuntu-ci:#kubuntu-devel- Project xenial_unstable_marble build #15: STILL FAILING in 21 min: http://kci.pangea.pub/job/xenial_unstable_marble/15/
[04:13] -kubuntu-ci:#kubuntu-devel- Project yakkety_unstable_marble build #15: STILL FAILING in 34 min: http://kci.pangea.pub/job/yakkety_unstable_marble/15/
[04:15] -kubuntu-ci:#kubuntu-devel- Project yakkety_unstable_kwin build #24: STILL UNSTABLE in 30 min: http://kci.pangea.pub/job/yakkety_unstable_kwin/24/
[04:16] -kubuntu-ci:#kubuntu-devel- Project xenial_unstable_plasma-sdk build #237: STILL UNSTABLE in 11 min: http://kci.pangea.pub/job/xenial_unstable_plasma-sdk/237/
[04:16] -kubuntu-ci:#kubuntu-devel- Project xenial_unstable_plasma-integration build #13: STILL UNSTABLE in 10 min: http://kci.pangea.pub/job/xenial_unstable_plasma-integration/13/
[04:16] -kubuntu-ci:#kubuntu-devel- Project xenial_unstable_akonadi-contacts build #49: STILL UNSTABLE in 10 min: http://kci.pangea.pub/job/xenial_unstable_akonadi-contacts/49/
[04:17] <xor-freenet> the most related bugtracker entry for the full kmail/kontact/akonadi breakage due to the mysql security update is https://bugs.launchpad.net/ubuntu/+source/akonadi/+bug/1633855  in case anyone is interested. i'll leave this channel now but continue to be online in case someone wants to privmsg me who the best person to contact about this would be.
[04:21] -kubuntu-ci:#kubuntu-devel- Project xenial_unstable_discover build #16: STILL FAILING in 5 min 56 sec: http://kci.pangea.pub/job/xenial_unstable_discover/16/
[04:27] -kubuntu-ci:#kubuntu-devel- Project yakkety_unstable_messagelib build #15: STILL FAILING in 4 min 56 sec: http://kci.pangea.pub/job/yakkety_unstable_messagelib/15/
[04:29] -kubuntu-ci:#kubuntu-devel- Project xenial_unstable_kwin build #22: STILL UNSTABLE in 23 min: http://kci.pangea.pub/job/xenial_unstable_kwin/22/
[04:33] -kubuntu-ci:#kubuntu-devel- Project xenial_unstable_marble build #16: STILL FAILING in 16 min: http://kci.pangea.pub/job/xenial_unstable_marble/16/
[04:36] -kubuntu-ci:#kubuntu-devel- Project yakkety_unstable_marble build #16: STILL FAILING in 17 min: http://kci.pangea.pub/job/yakkety_unstable_marble/16/
[04:38] -kubuntu-ci:#kubuntu-devel- Project yakkety_unstable_messagelib build #16: STILL FAILING in 5 min 54 sec: http://kci.pangea.pub/job/yakkety_unstable_messagelib/16/
[04:41] -kubuntu-ci:#kubuntu-devel- Project yakkety_unstable_mailcommon build #5: STILL FAILING in 2 min 48 sec: http://kci.pangea.pub/job/yakkety_unstable_mailcommon/5/
[04:41] -kubuntu-ci:#kubuntu-devel- Project xenial_unstable_messagelib build #13: STILL FAILING in 4 min 52 sec: http://kci.pangea.pub/job/xenial_unstable_messagelib/13/
[04:49] -kubuntu-ci:#kubuntu-devel- Project yakkety_unstable_mailcommon build #6: STILL FAILING in 2 min 47 sec: http://kci.pangea.pub/job/yakkety_unstable_mailcommon/6/
[04:49] -kubuntu-ci:#kubuntu-devel- Project yakkety_unstable_kdepim-addons build #17: STILL FAILING in 40 sec: http://kci.pangea.pub/job/yakkety_unstable_kdepim-addons/17/
[04:51] -kubuntu-ci:#kubuntu-devel- Project xenial_unstable_messagelib build #14: STILL FAILING in 4 min 52 sec: http://kci.pangea.pub/job/xenial_unstable_messagelib/14/
[04:55] -kubuntu-ci:#kubuntu-devel- Project xenial_unstable_mailcommon build #5: STILL FAILING in 3 min 43 sec: http://kci.pangea.pub/job/xenial_unstable_mailcommon/5/
[04:55] -kubuntu-ci:#kubuntu-devel- Project yakkety_unstable_kdepim-addons build #18: STILL FAILING in 39 sec: http://kci.pangea.pub/job/yakkety_unstable_kdepim-addons/18/
[05:02] -kubuntu-ci:#kubuntu-devel- Project xenial_unstable_mailcommon build #6: STILL FAILING in 2 min 42 sec: http://kci.pangea.pub/job/xenial_unstable_mailcommon/6/
[05:03] -kubuntu-ci:#kubuntu-devel- Project xenial_unstable_kdepim-addons build #84: STILL FAILING in 38 sec: http://kci.pangea.pub/job/xenial_unstable_kdepim-addons/84/
[05:09] -kubuntu-ci:#kubuntu-devel- Project xenial_unstable_kdepim-addons build #85: STILL FAILING in 37 sec: http://kci.pangea.pub/job/xenial_unstable_kdepim-addons/85/
[08:47] <acheronuk> morning :)
[08:56] <rbasak> clivejo: let me know if if you need any help with bug 1633855
[08:56] <rbasak> yofel: ^
[09:36] <Skuggen> clivejo: yofel: Do you need any assistance with LP: #1633855?
[10:05] <vip> Hi, do you have problems with virtualbox? Modules does not compiles (either packages or from upstream)
[10:06] <jimarvan> good morning
[10:06] <jimarvan> hi vip
[10:06] <jimarvan> hmm are you using the PPA vbox?
[10:06] <jimarvan> oh both
[10:07] <vip> I've had older version from virtualbox.org, tried to upgrade (added sources for apt)
[10:07] <jimarvan> hmm I am using the latest from virtualbox.org
[10:08] <vip> purged old, tried to install from repo, same problem
[10:08] <jimarvan> Version 5.0.26 r108824
[10:08] <jimarvan> works fine for me
[10:08] <jimarvan> let me check the website
[10:08] <vip> There's 5.1.8 now
[10:08] <jimarvan> oh my
[10:08] <jimarvan> hahaha
[10:08] <jimarvan> :D
[10:08] <jimarvan> ye just saw
[10:09] <jimarvan> downloading
[10:09] <vip> from .org compiles, but there's vboxdrv: Unknown symbol mcount (err 0) in dmesg
[10:09] <jimarvan> I will install the 64 bit version
[10:09] <jimarvan> hmm
[10:10] <soee> o/
[10:10] <jimarvan> hey soee :D
[10:10] <jimarvan> installing vip let me confirm the problem
[10:11] <jimarvan> hmm cannot satisfy dependencies...
[10:12] <jimarvan> vip: confirming issue
[10:12] <jimarvan> I will try with the xenial version
[10:13] <vip> maybe it is: "Ok, that's the reason for your problem. Your gcc version is outdated. Your kernel was compiled with gcc-4.8.1-10ubuntu9 while you are now trying to compile the modules with gcc-4.4.7. This will not work"
[10:13] <jimarvan> lol I forgot i still have xenial on my work laptop :P
[10:13] <jimarvan> hahaha :D sorry
[10:14] <jimarvan> awesome sounds plausible
[10:14] <vip> gcc on system 6.1.1, kernel compiled  with 6.2.0
[10:14] <jimarvan> :/
[10:15] <vip> oh sorry, kernel build with 5.2.1
[10:24] <jimarvan> sorry for the delay I was just installing 5.1.8 r111374 (Qt5.5.1) on Xenial
[10:25] <jimarvan> had no issues here vip :( probably it has to do with what you report
[10:25] <jimarvan> I will test it on my home's laptop with yakete in the afternoon
[10:28] <vip> I am thinking about temporary change version of gcc 
[10:35] <vip> jimarvan: I am also wondering, why there's no precompiled kernel module for packaged virtualbox
[10:35] <jimarvan> indeed that was always in issue with virtualbox
[10:36] <jimarvan> *an
 Ever consider installing Virt-manager? ;)
 I switched because I was having trouble with the kernel modules.
[10:43] <vip> does it run vbox images?
 You should be able to convert them if you don't.
 But I'm not 100% sure.
[10:45] <vip> ok, thanks
[10:45] <vip> Is there any way to get vbox module compiled with gcc 5.2.1?
 If anyone has time to look at the mysql bug please do so, I won't have time until this afternoon at least
 I don't think I'll have time either.
 Today is gonna be a hard day. I might just nap. :)
[11:29] <vip> ok, my problem was, too old kernel
[11:30] <vip> it was 4.2, where now is 4.8 :/
[11:30] <vip> something just did not upgrade from loong time ago
[11:32] <BluesKaj> Hiyas all
[11:46] <rbasak> clivejo, Skuggen, yofel: mdeslaur told me in #ubuntu-hardened that he's on it.
[11:50] <yofel> rbasak: sweet, please pass some thanks on
[12:09] <rbasak> yofel: I wonder how we might catch this sort of regression earlier in the future. It wouldn't have helped this time, but can we pretty please have some excellent dep8 tests for akonadi? Then when considering this kind of change we'd be in a place to be able to check reverse deps more effectively.
[12:10] <rbasak> Though that would need some process changes for the security pocket, in this case we did have some advance notice of the behavioural change, so might have had the opportunity to catch it.
[12:17] <yofel> uhm, if the debian team works on proper dep8 tests, maybe. I'm not going to promise anything considering we're already overworked as is.
[12:18] <yofel> yakkety was also a procedure fail on our side, needs looking at
 @CliffordTheBigRedDoggie, Have just got back from a quick pub lunch, so doubtful if I can.
 @tsimonq2, Good plan :)
[12:26] <mamarley> acheronuk: I installed FW 5.27 on several systems yesterday.  Everything looks good, no problems to report. :)
[12:27] <acheronuk> mamarley: great. there was not a huge packaging diff for most of it, so it should be a pretty smooth update
[13:28] <BluesKaj> mamarley, FW 5.27?
[13:28] <mamarley> BluesKaj: It is staged for Zesty
[13:29] <BluesKaj> ma yeah I'm on Zesty , but what is FW 5.27?
[13:29] <mamarley> KDE Frameworks 5.27
[13:30] <BluesKaj> mamarley ok thanks, I'll check it out
[13:36] <marco-parillo> FW 5.27 in Z-Archive? Can the topic take it? I canna change the laws of physics, man.
[13:48] <clivejo> ok, so where we up to Kubuntu peeps
[13:49]  * clivejo finally got sitting down in front of an actually computer for the first time today!
[13:55] <marco-parillo> Well, this morning I copied the ZZ ISO to a thumb drive. Might try to install it tonight.
[13:57] <BluesKaj> marco-parillo, ok , installed FW 5.27 on Zesty
[13:57] <BluesKaj> oops mamarley 
[13:57] <BluesKaj> too many mas around here :-)
[14:40] <clivejo> who is running zz?
[14:41]  * BluesKaj raises his hand
[14:42] <clivejo> but you dont use akonadi?
[14:47] <mamarley> clivejo: I am also running ZZ.
[14:49] <clivejo> https://launchpad.net/~clivejo/+archive/ubuntu/zesty/+packages?field.name_filter=akonadi&field.status_filter=published&field.series_filter=
[14:50] <clivejo> need akonadi installed and tested
[14:51] <mamarley> I don't use Akonadi though, sorry. :(
[14:51]  * clivejo rolls eyes
[15:00] <BluesKaj> mamarley, yeah, i have no use for that akonadi thing, don't think most home users do 
[15:06] <acheronuk> on the machines I use day to day, I have a dpkg-divert set up on /usr/bin/akonadiserver, so even if it is installed, the annoying thing can't run or get enabled by accident
[15:06] <acheronuk> a bit bad I know :/
[15:18] <clivejo> is there anyone on ZZ who can test akonadi for me?!?
 @clivejo, Me!
[15:20] <yofel> santa_: hi, as there was some discussion about who's in the changelog for scripted uploads to the archive, how about doing those as a team upload?
[15:25] <acheronuk> clivejo: just 'enabled' it, and it seems to start fine here without your package
 back later hopefully
[16:02] <jimarvan> see ya later peeps :)
[16:34] <santa_> brb
[18:07] <clivejo> for some reason, this past few weeks, my wifi keeps dropping for no reason.  Only way to get it back is to reboot.  Anyone know the cause or how to fix it?
[18:08] <davmor2> clivejo: try not joggling the shelf it's on pfff kids today ;)
[18:08] <clivejo> nothing has changed :/
[18:09] <davmor2> clivejo: what channel is the router on?
[18:10] <clivejo> 13
[18:10] <davmor2> clivejo: try switching it to channel 6 if that doesn't help start a bug against the wifi driver in the kernel
[18:10] <clivejo> 2472 MHz
[18:14] <clivejo> is channel 6 not the default for most routers?
[18:16] <davmor2> clivejo: it's a world standard and network manager is set to world for it's registration so it is works without dropping there then it is nm at fault which will hopefully get resolved soon, if it isn't that then it is an issue with the kernel driver possibly
[18:19] <clivejo> ok Ill see how I get on with this
 my laptop wireless tends to occasionally drop for 5s or so, then reconnect. not all that often, but every few hrs or so. that is some odd NM issue I think
[18:54] <clivejo> its only started recently
[19:27] <valorie> hi folks, am leaving to fly to Sunnyvale in less than an hour -- will be available via email and Telegram
[19:28]  * acheronuk does a doubletake at that place name
[19:29]  * clivejo notices that there are no placenames like that in Ireland
[19:30] <acheronuk> s/v/d and say hello to Buffy for us
[19:31] <acheronuk> here we have 'rainydampvale'
[19:33] <clivejo> yeah
[19:33] <clivejo> Fermanagh is basically men/people of the bogland
[19:43] <valorie> might rain a bit in Sunnyvale! packed my light rain jacket
[19:43]  * valorie will be inside the Googleplex
[19:44] <santa_>  <yofel> santa_: hi, as there was some discussion about who's in the changelog for scripted uploads to the archive, how about doing those as a team upload?
[19:44] <santa_> that is indeed a good sugestion
[19:45] <santa_> but unfortunately I couldn't reach an agreement about this
[19:45] <santa_> basically we have
[19:46] <santa_> a) Kubuntu Automation <kubuntu-devel@lists.ubuntu.com>
[19:46] <santa_> b) Kubuntu Developers <kubuntu-devel@lists.ubuntu.com>
[19:46] <santa_> c) the person who prepared the upload (in our case the person running gbp-archive and uploadind the resulting packages)
[19:47] <santa_> d) whoever did the first change in the changelog block or whoever did the initial staging
[19:48] <santa_> advantages of a) and b) - we will get mails for the build failures on the mailing list
[19:48] <santa_> advantages of c) it will make the gpg signing easier on KA
[19:48] <santa_> advantages of d) - none
[19:48] <santa_> yet we are doing d) (sigh)
[19:49] <santa_> maybe we should have a mini-technical committe to make decisions about this kind of thins
[19:49] <santa_> instead of me getting grumpy and such :)
[19:50] <santa_> s/getting/being/
[19:50]  * valorie heads out the door -- ciao all
[19:50] <santa_> bye valorie
[19:51] <santa_> that being said, lets move to other topic
[19:51] <santa_> !ninjas
[19:51] <santa_> are you up for a working sessions about debian merges
[19:51] <santa_> I have the tooling ready
[19:57] <clivejo> any idea how long it will take?
[20:01] <santa_> I don't know, but you can start reading the README.ng from KA, I have updated it with instructions for the debian merges
[20:01] <santa_> I also tested the thing with extra-cmake-modules
 Consider me afk tonight. I need a break and naps and such.
[20:03] <santa_> np
[20:04]  * acheronuk hands simon a pillow and bedtime milk & cookies
 Thanks Rik. :P
[20:06] <clivejo> acheronuk: can we go onto your container?
[20:06] <acheronuk> both yours keys should be enabled
[20:06]  * clivejo quickly throws some logs on the fire
[20:07] <santa_> ok, please before anything open the README.ng file
[20:07] <acheronuk> I am looking now...
[20:07] <santa_> go to the installation instructions and make sure you have the paths added in the $PATH
[20:08] <santa_> note that I have a added the check-and-fix directory
[20:12] <acheronuk> I have now :)
[20:13] <clivejo> can we type instructions here?
[20:14] <clivejo> terminal IRC is a bit hard to follow
[20:14] <santa_> yes, better
[20:14] <clivejo> yes Im here
[20:14] <santa_> I have 2 monitors
 Lucky! :P
[20:14] <acheronuk> plus this is logged, so can refer back
[20:14] <santa_> one with IRC, other with the shell :)
 Test
[20:15] <acheronuk> have konsole always on top, which works here
[20:16] <clivejo> so lets merge kservice which seems reasonably easy to handle, go to the frameworks dir with all the clones and lets try to do the steps from the section 4 of the README.ng
 (Photo, 800x600) https://irc-attachments.kde.org/q6bLpQHp/file_972.jpg
[20:17] <clivejo> can you delete filelist
[20:17] <clivejo> thanks
[20:17] <clivejo> ok
[20:18] <acheronuk> eek! 17" CRT?
[20:18] <santa_> lets cd into kservice/git?
[20:18] <santa_> yes, it's a CRT
[20:18] <acheronuk> retro :)
[20:18] <santa_> they were giving them for free @ the uni
[20:19] <acheronuk> cool.they do the job
[20:19]  * genii hugs his old IBM P200 CRT
[20:20] <clivejo> too many drivers at the wheel?
[20:21] <acheronuk> I either of you want to drive, feel free
[20:21] <clivejo> no no, you go ahead, its your car!
[20:22] <acheronuk> ha! you should see the dents!
[20:23] <clivejo> how are there changes from we updated that?
[20:23] <acheronuk> does cloneall at the remotes now?
[20:23] <acheronuk> *add
[20:24] <santa_> since a long time ago it does
[20:24] <clivejo> ah
[20:24] <clivejo> your VCS push
[20:24] <clivejo> forgot about that!
[20:24] <clivejo> dont mind me!
[20:25] <acheronuk> santa_: I had not noticed. whoops
[20:26]  * acheronuk kicks alioth to wake it up
[20:26] <clivejo> thats taking its time
[20:29] <clivejo> are debian still on Qt5.5?
[20:29] <tsimonq2> clivejo: 5.6
[20:29] <clivejo> or just update control when that package actually needs it?
[20:29] <tsimonq2> Getting 5.7.1 in time for Stretch.
[20:29] <acheronuk> no, but they have not dep bumped for a while clearly 
[20:31] <santa_> yep
[20:31] <acheronuk> so we have 5.8 vs 5.6
[20:31] <acheronuk> sv there I mean ^^
[20:31] <santa_> go on with the instructions
[20:32]  * clivejo pokes acheronuk with cattle prod
[20:32] <acheronuk> just that?
[20:32] <santa_> wait
[20:33]  * acheronuk waits
[20:34] <tsimonq2> wait
[20:34] <santa_> ok done
[20:35] <acheronuk> what is? change to tools I need to pull?
[20:35] <santa_> acheronuk: it was just a typo in the readme, its actually update-sv-field <value>
[20:36] <acheronuk> yep, I wondered if it needed that which was why I asked
[20:37] <acheronuk> so just append like that 'update-sv-field 5.8'
[20:37] <santa_> 3.9.8
[20:37] <santa_> that's the value from debian
[20:37] <tsimonq2> OH SHOOT, hmmmmmmmmmmm
[20:38] <acheronuk> sorry, getting distracted
[20:38] <tsimonq2> Do we have compat 10?!?
[20:40] <clivejo> we how does this work with backports?
[20:40] <clivejo> Xenial our LTS only supports up to 3.9.6
[20:40] <tsimonq2> No not Standards-version.
[20:41] <tsimonq2> I saw it in a commit the other day...
[20:43] <santa_> for now only merging for the unstable ubuntu dist is being taken into account
[20:43] <acheronuk> someone else drive for 5 mins, I have to deal with something
[20:43] <acheronuk> I'll catch up
[20:43] <santa_> probably you shouldn't merge for stable release but that's arguable
[20:43] <santa_> * stable releases
[20:44] <santa_> acheronuk: I would rather wait that 5 mins, pie me when you are back
[20:44] <clivejo> Ill wait too
[20:46] <santa_> s/pie/ping/
[20:50] <acheronuk> right, sorted. should be distraction free now
[20:51] <acheronuk> ok, in this case the debian revision is higher so run the bump?
[20:51] <acheronuk> oh.. ping santa_ clivejo 
[20:52] <santa_> yes, let's bump the revision 
[20:52]  * clivejo perks ears
[20:52] <acheronuk> bump-ubuntu-revision with any argument?
[20:53] <santa_> nope, it will work (hopefully) out of the box
[20:53] <acheronuk> seems it does :)
[20:54] <clivejo> is it intelligent?
[20:54] <santa_> so now comes the merge itself
[20:54] <santa_> ugh
[20:54] <santa_> something went wrong, please stand by..
[20:55] <acheronuk> didn't mean to run that. the copy in included the cr, which I didn't intend
[20:57] <acheronuk> we need a little spinning icon that says - santa (working.....)
[21:04] <clivejo> like windows installing something?
[21:04] <clivejo> so you dont think its crashed and reboot it
[21:04] <acheronuk> yep
[21:05] <santa_> WTF
[21:05] <santa_> I can reproduce it but I don't get it
[21:06] <acheronuk> is this a show-stopper?
[21:18] <santa_> I have to deal with it
[21:18] <acheronuk> ok. popping away for 5 mins or so to get food then
[21:18] <santa_> it's not reproducible
[21:18] <santa_> https://github.com/gitpython-developers/GitPython/issues/463
[21:19] <santa_> ↑ that's the thing
[21:19] <santa_> it's a bug on python-git /o\
[21:19] <tsimonq2> O__o
[21:20] <acheronuk> ick!
[21:20] <acheronuk> ok, as I said, back in 5 mins
[21:23] <ahoneybun> http://imgur.com/a/U6wPR
[21:23] <ahoneybun> one of the reasons I like KWin
[21:30] <santa_> acheronuk, clivejo: ok I have workarounded the python3-git bug in KA/master
[21:31] <clivejo> ok
[21:31] <clivejo> watching
[21:31] <santa_> acheronuk: so whenever you are up again "git merge --abort" and re-do the merge
[21:32] <acheronuk> done
[21:32] <santa_> git diff please
[21:33] <santa_> excellent
[21:33] <santa_> so about the first conflict, let's pick the debian version
[21:33] <santa_> note that it injects the -bin dep and that's a missing thing in our packaging
[21:34] <santa_> about the second one
[21:34] <clivejo> 5.20?
[21:34] <santa_> it's the same symbol and the debian revison is higher so let's pick th one from debian
[21:35] <santa_> clivejo: probably yhey updated the symbols later than us
[21:35] <acheronuk> 5.18+git in CI was probably really 5.20 anyway
[21:35] <santa_> maybe
[21:35] <acheronuk> or not far off?
[21:35] <santa_> just go ahead edit the file and pick the debian stuff
[21:37] <acheronuk> ok? 
[21:37] <santa_> yes
[21:38] <santa_> save and git diff again please
[21:38] <santa_> so git status, add the needed files and commit the result
[21:40] <acheronuk> Merge with debian/master. as per your readme?
[21:40] <santa_> saving that commit message will do that
[21:41] <acheronuk> I meant, amened to that simpler version or just leave it as we have there?
 Harmony - Music player compatible with Spotify, SoundCloud, Play Music and a lot more. … http://getharmony.xyz/
 anyone used?
[21:42] <santa_> acheronuk: leave the message as it is, then we will do other commit to update the changelog
[21:42] <acheronuk> ah. I see that now :)
[21:42] <santa_> i.e. dch "Merge with debian/master"
[21:43] <santa_> maybe you confused the commit message with the changelog entry ;)
[21:44] <acheronuk> ^^ yep, didn't read next intruction properly
[21:45] <acheronuk> so now clean and push?
 @marcinsagol I really really don't like that macOS look
[21:45] <santa_> yes
 @ahoneybun i thought you all in USA like it ;)
 heck no
 I burn Apple products in my spare time
[21:46] <acheronuk> ahoneybun: does it look like that on linux?
 :) i like to break and fix systems that is why I use *ubuntu. it's fun.
 I will have to install it and check tomorrow
[21:47] <acheronuk> santa_: ok. done
[21:48] <acheronuk> clivejo: you still there?
[21:48]  * clivejo nods
[21:48] <santa_> acheronuk: allright so rebuild in the ppa and let's hope everything gets right
[21:49] <santa_> damn
[21:49] <santa_> open the control file @ line 45
 @acheronuk I use Google Play Music Desktop Player
 bad name but it is a very cool webapp kinda
[21:51] <santa_> acheronuk: so indeed there's a dupe breaks, just join them in one
[21:52] <santa_> I think one of these days I will have to write a control merge driver
[21:52] <santa_> if there isn't one already
[21:53] <acheronuk> what dupe?
[21:53] <clivejo> why is it doing that?
[21:53] <santa_> because it didn't merge properly
[21:53] <santa_> shit happens
[21:54] <santa_> I think writing a control file merge driver would be a good thing
[21:54]  * clivejo nods
[21:54] <santa_> but for now we will have to deal with this manually
[21:54] <clivejo> I dont like the idea of 73 shits happening!
[21:55] <santa_> I will try to write a control merge driver, but keep in mind that might take a lot of time
[21:55] <santa_> hmm
[21:55] <santa_> even better
[21:55] <santa_> I could try to handle this at ka-debian2kubuntu-merge
[21:55] <santa_> as a quick solution
[21:58] <acheronuk> so that long list of breaks is to add to the single one?
[21:58] <santa_> yes
[21:59] <santa_> so we will have both ours and debian's
[21:59] <santa_> however I have my doubts about some debian breaks
[21:59] <santa_> but I will dig into that other day
[22:00] <santa_> it smells like someone not having a clue about how to solve a particular problem properly
[22:00] <acheronuk> libkf5service5 should really be 5.27 if we are being correct I take it?
[22:00] <santa_> nope
[22:01] <santa_> our breaks replaces is fine as it is
[22:01] <santa_> it comes from a file moving after 5.12 I guess
[22:01] <santa_> so it's fine as it is
[22:01] <acheronuk> ah. yes
[22:01] <santa_> not that out breaks is actually a breaks/replaces pair
[22:02] <santa_> * our
[22:02] <acheronuk> ok. try build again then I suppose
[22:02] <santa_> the bunch of debian breaks smell really bad. but yes, go ahead and rebuild
[22:02] <acheronuk> after commit
[22:03] <acheronuk> I take it
[22:03] <santa_> yep
[22:04] <santa_> ok, now it worked apparently but you have to sign the package
[22:05] <acheronuk> just sorting that
[22:06] <acheronuk> ok. signed
[22:06] <santa_> upload then?
[22:07] <acheronuk> uploadsource will pick the correct package, version and ppa I take it?
[22:07] <santa_> will take the correct ppa, the package and version are already there
[22:08] <acheronuk> off it goes
[22:08] <santa_> ok, so lets hope it gets built correctly
[22:09] <santa_> now that we are done (hopefully) I would like to point other things
[22:10] <santa_> regarding merges, to get the changelogs merged properly you need to have a debian/.gitattributes file with the driver configured
[22:11] <santa_> not all of our packages do
[22:11] <acheronuk> umm... https://launchpad.net/~kubuntu-ppa/+archive/ubuntu/staging-frameworks/+sourcepub/7065552/+listing-archive-extra
[22:15] <santa_> acheronuk: oh, wow, the control file was kind of corrupted due to a bad paste
[22:15] <santa_> as a suggestion, try to learn vim :P
[22:15] <santa_> copy-paste is easier
[22:15] <santa_> acheronuk: mind if I correct that and re-upload I would like to finish and move on to other topics
[22:16] <acheronuk> go for it
[22:16] <tsimonq2> O_____________O WHAT THE HELL
[22:16] <tsimonq2> https://launchpadlibrarian.net/291109977/buildlog_ubuntu-zesty-amd64.kservice_5.27.0-1ubuntu1~ubuntu17.04~ppa1_BUILDING.txt.gz
[22:16] <acheronuk> double changelog entry for me is also not right?
[22:16] <tsimonq2> Oh you guys got eyes on it?
 double changelog entry for me is also not right?
[22:18] <santa_> I will correct that also but I want you test something after that
[22:18] <santa_> to check your dch config
[22:19] <acheronuk> could be different on linode that I have locally
[22:22] <santa_> acheronuk: ok. please do a git pull in the kservice git repo
[22:23] <santa_> acheronuk: now dch "something"
[22:23] <santa_> ok, stand by please
[22:24] <santa_> acheronuk: make sure you have it configured like explained here http://pkg-kde.alioth.debian.org/changelogstandard.html
[22:26] <santa_> i.e.
[22:26] <santa_> DEBCHANGE_RELEASE_HEURISTIC=changelog
[22:26] <santa_> DEBCHANGE_MULTIMAINT_MERGE=yes
[22:26] <santa_> DEBCHANGE_MAINTTRAILER=yes
[22:26] <santa_> in /etc/devscripts.conf
[22:26] <santa_> acheronuk: ↑
[22:26] <acheronuk> yes, I was just looking
[22:29] <santa_> there we got it
[22:29] <acheronuk> I'll tidy that file later. It's quite large
[22:29] <santa_> case closed
[22:29] <santa_> :)
[22:30] <santa_> ok, going back to the other stuff about merges
[22:30] <santa_> like I mentioned not all of our repos had a debian/.gitattributes file
[22:31] <santa_> and apparently you need that to get the changelogs merged properly
[22:31] <santa_> so yesterday I pushed that file for ~ 6 frameworks
[22:31] <acheronuk> I saw
[22:32] <santa_> so I tought about creating kubuntu_zesty_archive branches for plasma and applications
[22:32] <santa_> and make sure that 
[22:32] <santa_> 1. the vcs field is updated
[22:32] <santa_> 2. they have the gitattributes file
[22:32] <santa_> so this way we will get it done in advanced
[22:33] <santa_> also this way i can change git-clone-all to be in the kubuntu_zesty_archive branch by default
[22:34] <santa_> (it's about time)
[22:35] <santa_> and about that massive changes, I could implement the git-clone-all -r other feature
[22:35] <santa_> but I can't give you an ETA for that
[22:35] <santa_> I have been investigating the launchpad api to do that and it's feasible
[22:36] <acheronuk> if I recall, we created the branches for apps and plasma? clivejo?
[22:37] <acheronuk> yep
[22:37] <santa_> are they already there?
[22:37] <tsimonq2> I think I might stop watching YouTube and actually nap now... :P
[22:37] <tsimonq2> o/
[22:39] <acheronuk> santa_: think so. we did a do-all over a full clone-all
[22:39] <santa_> ok
[22:39] <acheronuk> the "extra" ones are still to do
[22:39] <santa_> so are you ok guys if I push the Vcs and .gitattributes to these branches?
[22:40] <santa_> after that I will try to get the git-clone-all -r other working
[22:40] <acheronuk> ok I think with me, but let clivejo comment obviously
[22:40] <acheronuk> if he has not nodded off :P
[22:41] <fregl> santa_: where do you install Vc? how does the find macro need to be changed?
[22:42] <fregl> assuming this is krita requiring Vc
[22:42] <santa_> fregl: ?
[22:44] <fregl> santa_: not? then never mind :)
[22:44] <acheronuk> fregl: maybe should have been #kde-devel?
[22:44] <fregl> seeing Vc I thought you might be talking about the vectorization lib
[22:45] <acheronuk> oh
[22:45] <fregl> which krita requires since not so long ago
[22:45] <fregl> doesn't matter much, I was just curious if you had to patch stuff to find the Vc package, in which case I'd just push something into krita
[22:46] <santa_> ah no, we were talking about out Vcs-* fields
[22:46] <santa_> just packaging stuff
[22:46] <acheronuk> !info vc-dev
[22:47] <santa_> fregl: but now that you mention it it seems after a quick look our krita isn't built against vc-dev
[22:47] <santa_> fregl: so are you working on krita @ kde?
[22:48] <fregl> santa_: a bit, and the vc requirement will be for vc 1.0.0 and comming with krita 3.1
[22:48] <santa_> we have to update it
[22:48] <fregl> I just cleaned up a few bits of their build system
[22:48] <fregl> that would be nice :)
[22:48] <acheronuk> !info vc-dev unstable
[22:49] <santa_> we are still in the latest 2.9..x
[22:49] <santa_> so I presume 3.x are frameworks based
[22:49] <santa_> and I also presume it's safe to replace our current with that one
[22:51] <fregl> yes, it's getting there, so I don't think there's a big hurry, but it would be nice to get the frameworks based version :)
[22:52] <santa_> ok, I will dig into it if I have time
[22:53] <acheronuk> hmmm. vc has not been updated since utopic!
[22:55]  * acheronuk yawns
[22:56] <acheronuk> thanks for going through that santa_ 
[23:06] <acheronuk> I guess we are done here?
[23:21] <acheronuk> I guess we are. Night all :)
[23:22] <tsimonq2> o/ acheronuk 
[23:24] <santa_> I guess, I might poke you again tomorrow about a few things, but it won't be as "hard" as today
[23:24] <santa_> acheronuk: night
[23:26] <acheronuk> santa_: I may be busy tomorrow, but not 100% sure right this second
[23:26] <santa_> no prob
[23:27] <acheronuk> ping anyway, as I should pick it up one way or another
[23:27] <tsimonq2>