[00:00] <clivejo> here we go!
[00:00] <clivejo> take off
[00:00] <acheronuk> ooooooh
[00:01] -kubuntu-ci:#kubuntu-devel- Project merger_extra-cmake-modules build #797: STILL FAILING in 1 min 2 sec: http://kci.pangea.pub/job/merger_extra-cmake-modules/797/
[00:01] <acheronuk> 128 executors!
[00:01] -kubuntu-ci:#kubuntu-devel- Project merger_kdepim build #5: STILL FAILING in 1 min 15 sec: http://kci.pangea.pub/job/merger_kdepim/5/
[00:02] <clivejo> is that what we had before?
[00:02] -kubuntu-ci:#kubuntu-devel- Project merger_kio build #806: STILL FAILING in 1 min 0 sec: http://kci.pangea.pub/job/merger_kio/806/
[00:03] -kubuntu-ci:#kubuntu-devel- Project merger_kpimtextedit build #472: STILL FAILING in 1 min 17 sec: http://kci.pangea.pub/job/merger_kpimtextedit/472/
[00:04] <acheronuk> I admit that I honestly don't recall.
[00:04] <clivejo> we kinda just let it do its thing
[00:04] -kubuntu-ci:#kubuntu-devel- Project merger_plasma-framework build #782: STILL FAILING in 1 min 47 sec: http://kci.pangea.pub/job/merger_plasma-framework/782/
[00:05] -kubuntu-ci:#kubuntu-devel- Project mgmt_merger build #690: STILL UNSTABLE in 5 min 30 sec: http://kci.pangea.pub/job/mgmt_merger/690/
[00:05] -kubuntu-ci:#kubuntu-devel- Project mgmt_progenitor build #676: STILL UNSTABLE in 5 min 31 sec: http://kci.pangea.pub/job/mgmt_progenitor/676/
[00:06] <acheronuk> stage 2 prepare for separation
[00:06] <clivejo> ok so 5 to fix - http://kci.pangea.pub/view/merge%20FIX/
[00:06] <clivejo> tsimonq2: ^^
[00:07] <acheronuk> Build Queue (473)
[00:08] <clivejo> ok bed time!
[00:08] <acheronuk> Night
[00:08] <clivejo> lets see how it gets on with them while I zzzzz
[00:08] <clivejo> and congrats :)
[00:08] <acheronuk> ty :)
[00:09] <acheronuk> that was the easy one though!
[00:09] <clivejo> hopefully the next one you will have plenty of support
[00:10] <clivejo> study up on some stuff!
[00:10] <acheronuk> going to have to
[00:11] <acheronuk> ok. night all for a final time :)
 Congrats Rik
[00:29] -kubuntu-ci:#kubuntu-devel- Project xenial_unstable_kdesdk-kioslaves build #80: UNSTABLE in 22 min: http://kci.pangea.pub/job/xenial_unstable_kdesdk-kioslaves/80/
[00:37] -kubuntu-ci:#kubuntu-devel- Project xenial_unstable_palapeli build #30: FAILURE in 30 min: http://kci.pangea.pub/job/xenial_unstable_palapeli/30/
[00:37] -kubuntu-ci:#kubuntu-devel- Project xenial_unstable_kppp build #6: UNSTABLE in 30 min: http://kci.pangea.pub/job/xenial_unstable_kppp/6/
[00:37] -kubuntu-ci:#kubuntu-devel- Project yakkety_unstable_palapeli build #35: FAILURE in 31 min: http://kci.pangea.pub/job/yakkety_unstable_palapeli/35/
[00:37] -kubuntu-ci:#kubuntu-devel- Project yakkety_unstable_kppp build #83: UNSTABLE in 31 min: http://kci.pangea.pub/job/yakkety_unstable_kppp/83/
[00:47] -kubuntu-ci:#kubuntu-devel- Project yakkety_unstable_kdesdk-kioslaves build #41: UNSTABLE in 41 min: http://kci.pangea.pub/job/yakkety_unstable_kdesdk-kioslaves/41/
[00:47] -kubuntu-ci:#kubuntu-devel- Project yakkety_unstable_kauth build #152: UNSTABLE in 25 min: http://kci.pangea.pub/job/yakkety_unstable_kauth/152/
[00:56] -kubuntu-ci:#kubuntu-devel- Project yakkety_unstable_kopete build #60: UNSTABLE in 50 min: http://kci.pangea.pub/job/yakkety_unstable_kopete/60/
[00:56] -kubuntu-ci:#kubuntu-devel- Project yakkety_unstable_kde-runtime build #199: FAILURE in 50 min: http://kci.pangea.pub/job/yakkety_unstable_kde-runtime/199/
[00:56] -kubuntu-ci:#kubuntu-devel- Project yakkety_unstable_kdevelop-pg-qt build #17: UNSTABLE in 34 min: http://kci.pangea.pub/job/yakkety_unstable_kdevelop-pg-qt/17/
[00:56] -kubuntu-ci:#kubuntu-devel- Project yakkety_unstable_kwayland build #69: FAILURE in 34 min: http://kci.pangea.pub/job/yakkety_unstable_kwayland/69/
[00:57] -kubuntu-ci:#kubuntu-devel- Project yakkety_unstable_kidletime build #80: UNSTABLE in 34 min: http://kci.pangea.pub/job/yakkety_unstable_kidletime/80/
[00:57] -kubuntu-ci:#kubuntu-devel- Project xenial_unstable_kopete build #83: UNSTABLE in 51 min: http://kci.pangea.pub/job/xenial_unstable_kopete/83/
[00:57] -kubuntu-ci:#kubuntu-devel- Project xenial_unstable_kde-runtime build #193: FAILURE in 51 min: http://kci.pangea.pub/job/xenial_unstable_kde-runtime/193/
[01:02] -kubuntu-ci:#kubuntu-devel- Project xenial_unstable_palapeli build #31: STILL FAILING in 20 min: http://kci.pangea.pub/job/xenial_unstable_palapeli/31/
[01:03] -kubuntu-ci:#kubuntu-devel- Project yakkety_unstable_okular build #94: UNSTABLE in 26 min: http://kci.pangea.pub/job/yakkety_unstable_okular/94/
[01:03] -kubuntu-ci:#kubuntu-devel- Project xenial_unstable_kauth build #280: NOW UNSTABLE in 26 min: http://kci.pangea.pub/job/xenial_unstable_kauth/280/
[01:03] -kubuntu-ci:#kubuntu-devel- Project yakkety_unstable_palapeli build #36: STILL FAILING in 21 min: http://kci.pangea.pub/job/yakkety_unstable_palapeli/36/
[01:09] -kubuntu-ci:#kubuntu-devel- Project xenial_unstable_okular build #16: UNSTABLE in 32 min: http://kci.pangea.pub/job/xenial_unstable_okular/16/
 we have a review already: https://www.youtube.com/watch?v=QjrfLuDaxng
[01:24] <tsimonq2> good to know that our hacky tedious work actually seems stable :P
[01:24]  * tsimonq2 runs
[01:27] -kubuntu-ci:#kubuntu-devel- Project yakkety_unstable_kwayland build #70: STILL FAILING in 25 min: http://kci.pangea.pub/job/yakkety_unstable_kwayland/70/
[01:34] -kubuntu-ci:#kubuntu-devel- Project xenial_unstable_kde-runtime build #194: STILL FAILING in 32 min: http://kci.pangea.pub/job/xenial_unstable_kde-runtime/194/
[01:35] -kubuntu-ci:#kubuntu-devel- Project yakkety_unstable_kde-runtime build #200: STILL FAILING in 33 min: http://kci.pangea.pub/job/yakkety_unstable_kde-runtime/200/
[01:35] -kubuntu-ci:#kubuntu-devel- Project yakkety_unstable_kwallet build #126: UNSTABLE in 15 min: http://kci.pangea.pub/job/yakkety_unstable_kwallet/126/
 for someone who reviews Linux he seems to not understand the release cycle of distros...
[01:51] -kubuntu-ci:#kubuntu-devel- Project xenial_unstable_kwallet build #287: UNSTABLE in 9 min 53 sec: http://kci.pangea.pub/job/xenial_unstable_kwallet/287/
[02:00] <Snowhog> Given the issues with KCI, is it 'safe' to download the 16.10 iso's from cdimage.ubuntu.com/kubuntu/releases/16.10/releases/ that are date/time stamped 13-Oct-2016 20:17 (amd64)?
[02:00] <tsimonq2> Snowhog: KCI has nothing to do with the Ubuntu archive.
[02:00] <tsimonq2> Snowhog: Yes, it's safe. In fact, I recommend it. ;)
[02:00] <Snowhog> Thank you.
[02:01] <tsimonq2> Snowhog: No, scratch that, torrent it then seed it for others. :D
[02:05] -kubuntu-ci:#kubuntu-devel- Project yakkety_unstable_kio build #149: FAILURE in 58 sec: http://kci.pangea.pub/job/yakkety_unstable_kio/149/
[02:11] -kubuntu-ci:#kubuntu-devel- Project yakkety_unstable_kio build #150: STILL FAILING in 44 sec: http://kci.pangea.pub/job/yakkety_unstable_kio/150/
[02:22] -kubuntu-ci:#kubuntu-devel- Project xenial_unstable_kio build #279: FAILURE in 53 sec: http://kci.pangea.pub/job/xenial_unstable_kio/279/
[02:26] -kubuntu-ci:#kubuntu-devel- Project yakkety_unstable_kactivitymanagerd build #113: FAILURE in 15 min: http://kci.pangea.pub/job/yakkety_unstable_kactivitymanagerd/113/
[02:28] -kubuntu-ci:#kubuntu-devel- Project xenial_unstable_kio build #280: STILL FAILING in 53 sec: http://kci.pangea.pub/job/xenial_unstable_kio/280/
[02:46] -kubuntu-ci:#kubuntu-devel- Project yakkety_unstable_kdenlive build #133: FAILURE in 19 min: http://kci.pangea.pub/job/yakkety_unstable_kdenlive/133/
[02:48] -kubuntu-ci:#kubuntu-devel- Project xenial_unstable_kactivitymanagerd build #113: FAILURE in 19 min: http://kci.pangea.pub/job/xenial_unstable_kactivitymanagerd/113/
[02:54] -kubuntu-ci:#kubuntu-devel- Project yakkety_unstable_kactivitymanagerd build #114: STILL FAILING in 22 min: http://kci.pangea.pub/job/yakkety_unstable_kactivitymanagerd/114/
[02:54] -kubuntu-ci:#kubuntu-devel- Project yakkety_unstable_spectacle build #83: UNSTABLE in 24 min: http://kci.pangea.pub/job/yakkety_unstable_spectacle/83/
[02:56] -kubuntu-ci:#kubuntu-devel- Project yakkety_unstable_kdelibs4support build #87: STILL FAILING in 1 min 11 sec: http://kci.pangea.pub/job/yakkety_unstable_kdelibs4support/87/
[03:00] -kubuntu-ci:#kubuntu-devel- Project xenial_unstable_spectacle build #104: UNSTABLE in 9 min 51 sec: http://kci.pangea.pub/job/xenial_unstable_spectacle/104/
[03:01] -kubuntu-ci:#kubuntu-devel- Project xenial_unstable_kactivitymanagerd build #114: STILL FAILING in 7 min 43 sec: http://kci.pangea.pub/job/xenial_unstable_kactivitymanagerd/114/
[03:02] -kubuntu-ci:#kubuntu-devel- Project yakkety_unstable_kdelibs4support build #88: STILL FAILING in 59 sec: http://kci.pangea.pub/job/yakkety_unstable_kdelibs4support/88/
[03:07] -kubuntu-ci:#kubuntu-devel- Project yakkety_unstable_kpimtextedit build #97: FAILURE in 12 min: http://kci.pangea.pub/job/yakkety_unstable_kpimtextedit/97/
[03:10] -kubuntu-ci:#kubuntu-devel- Project yakkety_unstable_plasma-framework build #138: FAILURE in 9 min 8 sec: http://kci.pangea.pub/job/yakkety_unstable_plasma-framework/138/
[03:12] <tsimonq2> clivejo, acheronuk, santa_: can you guys please work out what's left to get what's in Yakkety Archive to Xenial Backports ASAP?
[03:15] -kubuntu-ci:#kubuntu-devel- Project yakkety_unstable_kdenlive build #134: STILL FAILING in 23 min: http://kci.pangea.pub/job/yakkety_unstable_kdenlive/134/
[03:15] -kubuntu-ci:#kubuntu-devel- Project yakkety_unstable_kstars build #123: UNSTABLE in 27 min: http://kci.pangea.pub/job/yakkety_unstable_kstars/123/
[03:15] -kubuntu-ci:#kubuntu-devel- Project yakkety_unstable_libkcompactdisc build #52: FAILURE in 13 min: http://kci.pangea.pub/job/yakkety_unstable_libkcompactdisc/52/
[03:15] -kubuntu-ci:#kubuntu-devel- Project yakkety_unstable_okteta build #108: FAILURE in 27 min: http://kci.pangea.pub/job/yakkety_unstable_okteta/108/
[03:15] -kubuntu-ci:#kubuntu-devel- Project yakkety_unstable_umbrello build #75: UNSTABLE in 27 min: http://kci.pangea.pub/job/yakkety_unstable_umbrello/75/
[03:16] -kubuntu-ci:#kubuntu-devel- Project yakkety_unstable_akonadi build #185: FAILURE in 21 min: http://kci.pangea.pub/job/yakkety_unstable_akonadi/185/
[03:16] -kubuntu-ci:#kubuntu-devel- Project xenial_unstable_kdenlive build #284: FAILURE in 21 min: http://kci.pangea.pub/job/xenial_unstable_kdenlive/284/
[03:16] <valorie> tsimonq2: when I asked about that earlier, it was decided to talk about this tomorrow (their time)
[03:17] <tsimonq2> ok
[03:17] <tsimonq2> valorie: when I pinged Rik a few days ago, he said he had to ask them
[03:17] <valorie> we also have a bunch of uploaded Applications packages that should be put into -updates, as I understand it
[03:17] <tsimonq2> oh?
[03:17] <valorie> right, it would be good to get this stuff cleared before Z opens
[03:18] <tsimonq2> Right now my priority is getting QtWebEngine OUT THE DOOR!
[03:18] <tsimonq2> Because we really need that.
[03:19] <valorie> for pim, for sure
[03:19] <tsimonq2> Yeah.
[03:19] <tsimonq2> Let's see what Debian has, so we can see what we need to get uploaded.
[03:19] <tsimonq2> !info package blahblah
[03:19] <tsimonq2> ok good
[03:20] <valorie> what does neon have?
[03:20] <tsimonq2> I don't think that matters at the moment.
[03:20] <tsimonq2> Debian is our upstream.
[03:20] <valorie> it would be nice to chose which one is best
[03:20] <valorie> Debian is their upstream as well
[03:20] -kubuntu-ci:#kubuntu-devel- Project yakkety_unstable_plasma-framework build #139: STILL FAILING in 4 min 57 sec: http://kci.pangea.pub/job/yakkety_unstable_plasma-framework/139/
[03:21] <tsimonq2> valorie: we're a sister project
[03:21] <tsimonq2> !info akonadi unstable
[03:21] <valorie> your point?
[03:21] <tsimonq2> valorie: We upload things to Debian, they come to Ubuntu automatically. We somehow get things in Neon, they don't touch Ubuntu.
[03:22] <tsimonq2> We can get things from Neon into Debian, then sync down, but not from Neon to Ubuntu.
[03:22] <tsimonq2> (at least that's how it *should* be)
[03:22] -kubuntu-ci:#kubuntu-devel- Project yakkety_unstable_ktp-common-internals build #132: UNSTABLE in 22 min: http://kci.pangea.pub/job/yakkety_unstable_ktp-common-internals/132/
[03:22] <tsimonq2> !info akonadi-server unstable
[03:23] -kubuntu-ci:#kubuntu-devel- Project xenial_unstable_plasma-framework build #274: STILL FAILING in 5 min 49 sec: http://kci.pangea.pub/job/xenial_unstable_plasma-framework/274/
[03:23] <tsimonq2> ok that's not good
[03:23] <valorie> if they already have it packaged and working, why on earth would we re-do the work?
[03:23] -kubuntu-ci:#kubuntu-devel- Project yakkety_unstable_cantor build #97: FAILURE in 21 min: http://kci.pangea.pub/job/yakkety_unstable_cantor/97/
[03:23] <tsimonq2> valorie: Well we get that in Debian.
[03:23] -kubuntu-ci:#kubuntu-devel- Project xenial_unstable_okteta build #112: UNSTABLE in 22 min: http://kci.pangea.pub/job/xenial_unstable_okteta/112/
[03:23] <tsimonq2> Why should Debian have to redo the work?
[03:23] -kubuntu-ci:#kubuntu-devel- Project xenial_unstable_kdelibs4support build #197: STILL FAILING in 1 min 4 sec: http://kci.pangea.pub/job/xenial_unstable_kdelibs4support/197/
[03:23] <tsimonq2> So QtWebEngine is a priority so 16.08.2 can land ASAP/
[03:23] <valorie> according to Riddell, he would like Debian to sync from Neon if they want
[03:24] <valorie> however it can happen, I think it's good
[03:24] <tsimonq2> Then that's that decision.
[03:24]  * valorie is no packager, so it is not up to me
[03:24] <tsimonq2> But I'm uncomfortable directly syncing from Neon unless it's on a case-by-case basis.
[03:24] <valorie> and naturally it has to get to Debian too
[03:24] <tsimonq2> Which is my point.
[03:25] <tsimonq2> !info bluedevil unstable
[03:25] <tsimonq2> Ok, they need 5.8.1.
[03:26] <tsimonq2> !info attica unstable
[03:28] <tsimonq2> !info baloo unstable
[03:28] <tsimonq2> Ok, so they are still on 5.26 there as well/.
[03:28] <tsimonq2> s/\//
[03:29] -kubuntu-ci:#kubuntu-devel- Project xenial_unstable_kdelibs4support build #198: STILL FAILING in 42 sec: http://kci.pangea.pub/job/xenial_unstable_kdelibs4support/198/
[03:30] -kubuntu-ci:#kubuntu-devel- Project xenial_unstable_kstars build #255: UNSTABLE in 22 min: http://kci.pangea.pub/job/xenial_unstable_kstars/255/
[03:30] -kubuntu-ci:#kubuntu-devel- Project yakkety_unstable_kde-baseapps build #100: STILL FAILING in 7 min 13 sec: http://kci.pangea.pub/job/yakkety_unstable_kde-baseapps/100/
[03:30] -kubuntu-ci:#kubuntu-devel- Project xenial_unstable_umbrello build #90: UNSTABLE in 23 min: http://kci.pangea.pub/job/xenial_unstable_umbrello/90/
[03:30] -kubuntu-ci:#kubuntu-devel- Project yakkety_unstable_libkcompactdisc build #53: STILL FAILING in 9 min 55 sec: http://kci.pangea.pub/job/yakkety_unstable_libkcompactdisc/53/
[03:31] -kubuntu-ci:#kubuntu-devel- Project yakkety_unstable_kpimtextedit build #98: STILL FAILING in 18 min: http://kci.pangea.pub/job/yakkety_unstable_kpimtextedit/98/
[03:31] -kubuntu-ci:#kubuntu-devel- Project yakkety_unstable_kirigami build #36: UNSTABLE in 10 min: http://kci.pangea.pub/job/yakkety_unstable_kirigami/36/
[03:36] -kubuntu-ci:#kubuntu-devel- Project yakkety_unstable_kldap build #100: FAILURE in 13 min: http://kci.pangea.pub/job/yakkety_unstable_kldap/100/
[03:36] -kubuntu-ci:#kubuntu-devel- Project xenial_unstable_plasma-framework build #275: STILL FAILING in 8 min 51 sec: http://kci.pangea.pub/job/xenial_unstable_plasma-framework/275/
[03:37] -kubuntu-ci:#kubuntu-devel- Project xenial_unstable_kpimtextedit build #182: FAILURE in 14 min: http://kci.pangea.pub/job/xenial_unstable_kpimtextedit/182/
[03:37] -kubuntu-ci:#kubuntu-devel- Project xenial_unstable_ktp-common-internals build #206: UNSTABLE in 21 min: http://kci.pangea.pub/job/xenial_unstable_ktp-common-internals/206/
[03:37] -kubuntu-ci:#kubuntu-devel- Project yakkety_unstable_plasma-pa build #102: FAILURE in 16 min: http://kci.pangea.pub/job/yakkety_unstable_plasma-pa/102/
[03:37] -kubuntu-ci:#kubuntu-devel- Project yakkety_unstable_ktp-auth-handler build #133: UNSTABLE in 14 min: http://kci.pangea.pub/job/yakkety_unstable_ktp-auth-handler/133/
[03:38] -kubuntu-ci:#kubuntu-devel- Project yakkety_unstable_plasma-nm build #115: FAILURE in 17 min: http://kci.pangea.pub/job/yakkety_unstable_plasma-nm/115/
[03:38] -kubuntu-ci:#kubuntu-devel- Project yakkety_unstable_plasma-mediacenter build #101: FAILURE in 17 min: http://kci.pangea.pub/job/yakkety_unstable_plasma-mediacenter/101/
[03:38] -kubuntu-ci:#kubuntu-devel- Yippee, build fixed!
[03:38] -kubuntu-ci:#kubuntu-devel- Project yakkety_unstable_kate build #134: FIXED in 17 min: http://kci.pangea.pub/job/yakkety_unstable_kate/134/
[03:39] -kubuntu-ci:#kubuntu-devel- Project yakkety_unstable_kwin build #1: FAILURE in 1 min 34 sec: http://kci.pangea.pub/job/yakkety_unstable_kwin/1/
[03:42] -kubuntu-ci:#kubuntu-devel- Project xenial_unstable_kdenlive build #285: STILL FAILING in 21 min: http://kci.pangea.pub/job/xenial_unstable_kdenlive/285/
[03:43] -kubuntu-ci:#kubuntu-devel- Project yakkety_unstable_akonadi build #186: STILL FAILING in 22 min: http://kci.pangea.pub/job/yakkety_unstable_akonadi/186/
[03:44] -kubuntu-ci:#kubuntu-devel- Project yakkety_unstable_okteta build #109: STILL FAILING in 23 min: http://kci.pangea.pub/job/yakkety_unstable_okteta/109/
[03:44] -kubuntu-ci:#kubuntu-devel- Project yakkety_unstable_kwin build #2: STILL FAILING in 48 sec: http://kci.pangea.pub/job/yakkety_unstable_kwin/2/
[03:45] -kubuntu-ci:#kubuntu-devel- Project yakkety_unstable_libkleo build #58: FAILURE in 14 min: http://kci.pangea.pub/job/yakkety_unstable_libkleo/58/
[03:49] -kubuntu-ci:#kubuntu-devel- Project xenial_unstable_libkcompactdisc build #46: UNSTABLE in 20 min: http://kci.pangea.pub/job/xenial_unstable_libkcompactdisc/46/
[03:50] -kubuntu-ci:#kubuntu-devel- Project yakkety_unstable_cantor build #98: STILL FAILING in 21 min: http://kci.pangea.pub/job/yakkety_unstable_cantor/98/
[03:50] -kubuntu-ci:#kubuntu-devel- Project yakkety_unstable_kde-baseapps build #101: STILL FAILING in 14 min: http://kci.pangea.pub/job/yakkety_unstable_kde-baseapps/101/
[03:50] -kubuntu-ci:#kubuntu-devel- Project xenial_unstable_akonadi build #265: FAILURE in 27 min: http://kci.pangea.pub/job/xenial_unstable_akonadi/265/
[03:50] -kubuntu-ci:#kubuntu-devel- Project yakkety_unstable_plasma-sdk build #117: FAILURE in 19 min: http://kci.pangea.pub/job/yakkety_unstable_plasma-sdk/117/
[03:53] -kubuntu-ci:#kubuntu-devel- Project yakkety_unstable_marble build #1: FAILURE in 23 min: http://kci.pangea.pub/job/yakkety_unstable_marble/1/
[03:56] -kubuntu-ci:#kubuntu-devel- Project xenial_unstable_cantor build #195: FAILURE in 27 min: http://kci.pangea.pub/job/xenial_unstable_cantor/195/
[03:56] -kubuntu-ci:#kubuntu-devel- Project xenial_unstable_kirigami build #32: UNSTABLE in 19 min: http://kci.pangea.pub/job/xenial_unstable_kirigami/32/
[03:57] -kubuntu-ci:#kubuntu-devel- Project xenial_unstable_plasma-mediacenter build #184: FAILURE in 20 min: http://kci.pangea.pub/job/xenial_unstable_plasma-mediacenter/184/
[03:57] -kubuntu-ci:#kubuntu-devel- Project xenial_unstable_plasma-nm build #210: FAILURE in 20 min: http://kci.pangea.pub/job/xenial_unstable_plasma-nm/210/
[03:59] -kubuntu-ci:#kubuntu-devel- Project yakkety_unstable_plasma-workspace build #1: FAILURE in 1 min 49 sec: http://kci.pangea.pub/job/yakkety_unstable_plasma-workspace/1/
[04:00] -kubuntu-ci:#kubuntu-devel- Project xenial_unstable_kde-baseapps build #95: STILL FAILING in 10 min: http://kci.pangea.pub/job/xenial_unstable_kde-baseapps/95/
[04:01] -kubuntu-ci:#kubuntu-devel- Project yakkety_unstable_libkleo build #59: STILL FAILING in 10 min: http://kci.pangea.pub/job/yakkety_unstable_libkleo/59/
[04:02] -kubuntu-ci:#kubuntu-devel- Project xenial_unstable_ktp-auth-handler build #180: UNSTABLE in 25 min: http://kci.pangea.pub/job/xenial_unstable_ktp-auth-handler/180/
[04:02] -kubuntu-ci:#kubuntu-devel- Project yakkety_unstable_plasma-pa build #103: STILL FAILING in 19 min: http://kci.pangea.pub/job/yakkety_unstable_plasma-pa/103/
[04:02] -kubuntu-ci:#kubuntu-devel- Project yakkety_unstable_kldap build #101: STILL FAILING in 20 min: http://kci.pangea.pub/job/yakkety_unstable_kldap/101/
[04:02] -kubuntu-ci:#kubuntu-devel- Project xenial_unstable_kpimtextedit build #183: STILL FAILING in 20 min: http://kci.pangea.pub/job/xenial_unstable_kpimtextedit/183/
[04:04] -kubuntu-ci:#kubuntu-devel- Project xenial_unstable_kwin build #1: FAILURE in 1 min 47 sec: http://kci.pangea.pub/job/xenial_unstable_kwin/1/
[04:05] -kubuntu-ci:#kubuntu-devel- Project yakkety_unstable_plasma-workspace build #2: STILL FAILING in 59 sec: http://kci.pangea.pub/job/yakkety_unstable_plasma-workspace/2/
[04:09] -kubuntu-ci:#kubuntu-devel- Project xenial_unstable_kldap build #184: FAILURE in 19 min: http://kci.pangea.pub/job/xenial_unstable_kldap/184/
[04:09] -kubuntu-ci:#kubuntu-devel- Yippee, build fixed!
[04:09] -kubuntu-ci:#kubuntu-devel- Project yakkety_unstable_kcalutils build #61: FIXED in 19 min: http://kci.pangea.pub/job/yakkety_unstable_kcalutils/61/
[04:09] -kubuntu-ci:#kubuntu-devel- Project yakkety_unstable_kalarmcal build #67: STILL FAILING in 19 min: http://kci.pangea.pub/job/yakkety_unstable_kalarmcal/67/
[04:10] -kubuntu-ci:#kubuntu-devel- Project yakkety_unstable_plasma-mediacenter build #102: STILL FAILING in 26 min: http://kci.pangea.pub/job/yakkety_unstable_plasma-mediacenter/102/
[04:10] -kubuntu-ci:#kubuntu-devel- Project yakkety_unstable_plasma-nm build #116: STILL FAILING in 26 min: http://kci.pangea.pub/job/yakkety_unstable_plasma-nm/116/
[04:10] -kubuntu-ci:#kubuntu-devel- Project xenial_unstable_plasma-sdk build #223: FAILURE in 13 min: http://kci.pangea.pub/job/xenial_unstable_plasma-sdk/223/
[04:10] -kubuntu-ci:#kubuntu-devel- Project yakkety_unstable_plasma-sdk build #118: STILL FAILING in 14 min: http://kci.pangea.pub/job/yakkety_unstable_plasma-sdk/118/
[04:10] -kubuntu-ci:#kubuntu-devel- Project yakkety_unstable_kleopatra build #25: STILL FAILING in 9 min 36 sec: http://kci.pangea.pub/job/yakkety_unstable_kleopatra/25/
[04:11] -kubuntu-ci:#kubuntu-devel- Project xenial_unstable_kwin build #2: STILL FAILING in 1 min 19 sec: http://kci.pangea.pub/job/xenial_unstable_kwin/2/
[04:11] -kubuntu-ci:#kubuntu-devel- Project xenial_unstable_libkleo build #45: FAILURE in 8 min 41 sec: http://kci.pangea.pub/job/xenial_unstable_libkleo/45/
[04:13] -kubuntu-ci:#kubuntu-devel- Project yakkety_unstable_kdepimlibs build #1: FAILURE in 10 min: http://kci.pangea.pub/job/yakkety_unstable_kdepimlibs/1/
[04:13] -kubuntu-ci:#kubuntu-devel- Project xenial_unstable_kde-baseapps build #96: STILL FAILING in 8 min 11 sec: http://kci.pangea.pub/job/xenial_unstable_kde-baseapps/96/
[04:15] -kubuntu-ci:#kubuntu-devel- Project xenial_unstable_discover build #1: FAILURE in 5 min 24 sec: http://kci.pangea.pub/job/xenial_unstable_discover/1/
[04:15] -kubuntu-ci:#kubuntu-devel- Project xenial_unstable_akonadi build #266: STILL FAILING in 20 min: http://kci.pangea.pub/job/xenial_unstable_akonadi/266/
[04:16] -kubuntu-ci:#kubuntu-devel- Project yakkety_unstable_discover build #1: UNSTABLE in 19 min: http://kci.pangea.pub/job/yakkety_unstable_discover/1/
[04:16] -kubuntu-ci:#kubuntu-devel- Project xenial_unstable_plasma-workspace build #1: FAILURE in 1 min 18 sec: http://kci.pangea.pub/job/xenial_unstable_plasma-workspace/1/
[04:21] -kubuntu-ci:#kubuntu-devel- Project yakkety_unstable_kleopatra build #26: STILL FAILING in 5 min 22 sec: http://kci.pangea.pub/job/yakkety_unstable_kleopatra/26/
[04:21] -kubuntu-ci:#kubuntu-devel- Project xenial_unstable_libkleo build #46: STILL FAILING in 4 min 56 sec: http://kci.pangea.pub/job/xenial_unstable_libkleo/46/
[04:21] -kubuntu-ci:#kubuntu-devel- Project xenial_unstable_marble build #1: FAILURE in 24 min: http://kci.pangea.pub/job/xenial_unstable_marble/1/
[04:22] -kubuntu-ci:#kubuntu-devel- Project xenial_unstable_cantor build #196: STILL FAILING in 20 min: http://kci.pangea.pub/job/xenial_unstable_cantor/196/
[04:22] -kubuntu-ci:#kubuntu-devel- Project xenial_unstable_plasma-mediacenter build #185: STILL FAILING in 19 min: http://kci.pangea.pub/job/xenial_unstable_plasma-mediacenter/185/
[04:22] -kubuntu-ci:#kubuntu-devel- Project xenial_unstable_plasma-nm build #211: STILL FAILING in 19 min: http://kci.pangea.pub/job/xenial_unstable_plasma-nm/211/
[04:22] -kubuntu-ci:#kubuntu-devel- Project xenial_unstable_plasma-workspace build #2: STILL FAILING in 1 min 0 sec: http://kci.pangea.pub/job/xenial_unstable_plasma-workspace/2/
[04:24] -kubuntu-ci:#kubuntu-devel- Project yakkety_unstable_marble build #2: STILL FAILING in 25 min: http://kci.pangea.pub/job/yakkety_unstable_marble/2/
[04:24] -kubuntu-ci:#kubuntu-devel- Project yakkety_unstable_kdeplasma-addons build #1: FAILURE in 18 min: http://kci.pangea.pub/job/yakkety_unstable_kdeplasma-addons/1/
[04:25] -kubuntu-ci:#kubuntu-devel- Project xenial_unstable_discover build #2: STILL FAILING in 5 min 2 sec: http://kci.pangea.pub/job/xenial_unstable_discover/2/
[04:25] -kubuntu-ci:#kubuntu-devel- Project yakkety_unstable_kdepimlibs build #2: STILL FAILING in 6 min 57 sec: http://kci.pangea.pub/job/yakkety_unstable_kdepimlibs/2/
[04:25] -kubuntu-ci:#kubuntu-devel- Project xenial_unstable_kleopatra build #67: STILL FAILING in 4 min 13 sec: http://kci.pangea.pub/job/xenial_unstable_kleopatra/67/
[04:27] -kubuntu-ci:#kubuntu-devel- Project xenial_unstable_kalarmcal build #83: FAILURE in 11 min: http://kci.pangea.pub/job/xenial_unstable_kalarmcal/83/
[04:27] -kubuntu-ci:#kubuntu-devel- Yippee, build fixed!
[04:27] -kubuntu-ci:#kubuntu-devel- Project xenial_unstable_kcalutils build #100: FIXED in 11 min: http://kci.pangea.pub/job/xenial_unstable_kcalutils/100/
[04:27] -kubuntu-ci:#kubuntu-devel- Project xenial_unstable_kldap build #185: STILL FAILING in 13 min: http://kci.pangea.pub/job/xenial_unstable_kldap/185/
[04:27] -kubuntu-ci:#kubuntu-devel- Project yakkety_unstable_kalarmcal build #68: STILL FAILING in 13 min: http://kci.pangea.pub/job/yakkety_unstable_kalarmcal/68/
[04:27] -kubuntu-ci:#kubuntu-devel- Project yakkety_unstable_libkgeomap build #1: FAILURE in 3 min 47 sec: http://kci.pangea.pub/job/yakkety_unstable_libkgeomap/1/
[04:28] -kubuntu-ci:#kubuntu-devel- Project xenial_unstable_plasma-sdk build #224: STILL FAILING in 12 min: http://kci.pangea.pub/job/xenial_unstable_plasma-sdk/224/
[04:34] -kubuntu-ci:#kubuntu-devel- Project xenial_unstable_kdeplasma-addons build #1: FAILURE in 11 min: http://kci.pangea.pub/job/xenial_unstable_kdeplasma-addons/1/
[04:34] -kubuntu-ci:#kubuntu-devel- Project xenial_unstable_kdepimlibs build #1: FAILURE in 7 min 2 sec: http://kci.pangea.pub/job/xenial_unstable_kdepimlibs/1/
[04:37] -kubuntu-ci:#kubuntu-devel- Project xenial_unstable_kleopatra build #68: STILL FAILING in 6 min 52 sec: http://kci.pangea.pub/job/xenial_unstable_kleopatra/68/
[04:38] -kubuntu-ci:#kubuntu-devel- Project yakkety_unstable_libkgeomap build #2: STILL FAILING in 4 min 59 sec: http://kci.pangea.pub/job/yakkety_unstable_libkgeomap/2/
[04:38] -kubuntu-ci:#kubuntu-devel- Project yakkety_unstable_akonadi-contacts build #42: STILL FAILING in 13 min: http://kci.pangea.pub/job/yakkety_unstable_akonadi-contacts/42/
[04:38] -kubuntu-ci:#kubuntu-devel- Yippee, build fixed!
[04:38] -kubuntu-ci:#kubuntu-devel- Project yakkety_unstable_kmailtransport build #76: FIXED in 13 min: http://kci.pangea.pub/job/yakkety_unstable_kmailtransport/76/
[04:44] -kubuntu-ci:#kubuntu-devel- Project xenial_unstable_marble build #2: STILL FAILING in 17 min: http://kci.pangea.pub/job/xenial_unstable_marble/2/
[04:45] -kubuntu-ci:#kubuntu-devel- Project xenial_unstable_kalarmcal build #84: STILL FAILING in 12 min: http://kci.pangea.pub/job/xenial_unstable_kalarmcal/84/
[04:46] -kubuntu-ci:#kubuntu-devel- Project xenial_unstable_kdepimlibs build #2: STILL FAILING in 7 min 0 sec: http://kci.pangea.pub/job/xenial_unstable_kdepimlibs/2/
[04:46] -kubuntu-ci:#kubuntu-devel- Project yakkety_unstable_kdeplasma-addons build #2: STILL FAILING in 17 min: http://kci.pangea.pub/job/yakkety_unstable_kdeplasma-addons/2/
[04:48] -kubuntu-ci:#kubuntu-devel- Project xenial_unstable_libkgeomap build #1: FAILURE in 3 min 47 sec: http://kci.pangea.pub/job/xenial_unstable_libkgeomap/1/
[04:52] -kubuntu-ci:#kubuntu-devel- Project yakkety_unstable_libkdepim build #1: FAILURE in 14 min: http://kci.pangea.pub/job/yakkety_unstable_libkdepim/1/
[04:52] -kubuntu-ci:#kubuntu-devel- Project yakkety_unstable_akonadi-calendar build #1: UNSTABLE in 14 min: http://kci.pangea.pub/job/yakkety_unstable_akonadi-calendar/1/
[04:53] -kubuntu-ci:#kubuntu-devel- Project yakkety_unstable_kdepim-runtime build #1: FAILURE in 50 sec: http://kci.pangea.pub/job/yakkety_unstable_kdepim-runtime/1/
[04:53] -kubuntu-ci:#kubuntu-devel- Project xenial_unstable_kdeplasma-addons build #2: STILL FAILING in 14 min: http://kci.pangea.pub/job/xenial_unstable_kdeplasma-addons/2/
[04:56] -kubuntu-ci:#kubuntu-devel- Project xenial_unstable_libkgeomap build #2: STILL FAILING in 2 min 53 sec: http://kci.pangea.pub/job/xenial_unstable_libkgeomap/2/
[04:58] -kubuntu-ci:#kubuntu-devel- Project yakkety_unstable_akonadi-contacts build #43: STILL FAILING in 14 min: http://kci.pangea.pub/job/yakkety_unstable_akonadi-contacts/43/
[04:58] -kubuntu-ci:#kubuntu-devel- Yippee, build fixed!
[04:58] -kubuntu-ci:#kubuntu-devel- Project xenial_unstable_kmailtransport build #90: FIXED in 12 min: http://kci.pangea.pub/job/xenial_unstable_kmailtransport/90/
[04:58] -kubuntu-ci:#kubuntu-devel- Project xenial_unstable_akonadi-contacts build #37: NOW UNSTABLE in 12 min: http://kci.pangea.pub/job/xenial_unstable_akonadi-contacts/37/
[04:59] -kubuntu-ci:#kubuntu-devel- Project yakkety_unstable_kdepim-runtime build #2: STILL FAILING in 51 sec: http://kci.pangea.pub/job/yakkety_unstable_kdepim-runtime/2/
[05:08] -kubuntu-ci:#kubuntu-devel- Project yakkety_unstable_libkdepim build #2: STILL FAILING in 10 min: http://kci.pangea.pub/job/yakkety_unstable_libkdepim/2/
[05:08] -kubuntu-ci:#kubuntu-devel- Project xenial_unstable_libkdepim build #1: FAILURE in 10 min: http://kci.pangea.pub/job/xenial_unstable_libkdepim/1/
[05:09] -kubuntu-ci:#kubuntu-devel- Project xenial_unstable_kdepim-runtime build #1: FAILURE in 47 sec: http://kci.pangea.pub/job/xenial_unstable_kdepim-runtime/1/
[05:12] <tsimonq2> calligra 1:2.9.11+dfsg-2 is marked for autoremoval from testing on 2016-11-20
[05:12] <tsimonq2> It is affected by these RC bugs:
[05:12] <tsimonq2> oh god...
[05:13] <tsimonq2> 840071: calligra: calligra FTBFS, failure to find postgresql.
[05:15] <valorie> !info calligra
[05:15] <valorie> !
[05:15] -kubuntu-ci:#kubuntu-devel- Project xenial_unstable_kdepim-runtime build #2: STILL FAILING in 41 sec: http://kci.pangea.pub/job/xenial_unstable_kdepim-runtime/2/
[05:15] <valorie> lies
[05:15] <valorie> ubuntustudio got ours IN
[05:15] <tsimonq2> !info calligra yakkety-updates
[05:16] <tsimonq2> !info calligra yakkety-proposed
[05:16] <tsimonq2> valorie: ^^^^^^^^^^^^^^^^^^^^
[05:17] -kubuntu-ci:#kubuntu-devel- Project yakkety_unstable_pimcommon build #1: FAILURE in 9 min 6 sec: http://kci.pangea.pub/job/yakkety_unstable_pimcommon/1/
[05:17] -kubuntu-ci:#kubuntu-devel- Project yakkety_unstable_mailimporter build #1: FAILURE in 9 min 6 sec: http://kci.pangea.pub/job/yakkety_unstable_mailimporter/1/
[05:18] <valorie> gah
[05:18] <valorie> why do we have an old one
[05:18] <valorie> :(
[05:22] -kubuntu-ci:#kubuntu-devel- Project xenial_unstable_libkdepim build #2: STILL FAILING in 8 min 51 sec: http://kci.pangea.pub/job/xenial_unstable_libkdepim/2/
[05:32] -kubuntu-ci:#kubuntu-devel- Project xenial_unstable_mailimporter build #1: FAILURE in 9 min 48 sec: http://kci.pangea.pub/job/xenial_unstable_mailimporter/1/
[05:32] -kubuntu-ci:#kubuntu-devel- Project xenial_unstable_pimcommon build #1: FAILURE in 9 min 48 sec: http://kci.pangea.pub/job/xenial_unstable_pimcommon/1/
[05:32] -kubuntu-ci:#kubuntu-devel- Project yakkety_unstable_mailimporter build #2: STILL FAILING in 9 min 55 sec: http://kci.pangea.pub/job/yakkety_unstable_mailimporter/2/
[05:38] -kubuntu-ci:#kubuntu-devel- Project yakkety_unstable_pimcommon build #2: STILL FAILING in 15 min: http://kci.pangea.pub/job/yakkety_unstable_pimcommon/2/
[05:47] -kubuntu-ci:#kubuntu-devel- Project yakkety_unstable_libgravatar build #1: FAILURE in 8 min 55 sec: http://kci.pangea.pub/job/yakkety_unstable_libgravatar/1/
[05:48] -kubuntu-ci:#kubuntu-devel- Project xenial_unstable_mailimporter build #2: STILL FAILING in 10 min: http://kci.pangea.pub/job/xenial_unstable_mailimporter/2/
[05:48] -kubuntu-ci:#kubuntu-devel- Project xenial_unstable_pimcommon build #2: STILL FAILING in 10 min: http://kci.pangea.pub/job/xenial_unstable_pimcommon/2/
[05:48] -kubuntu-ci:#kubuntu-devel- Project yakkety_unstable_kdepim-apps-libs build #1: FAILURE in 9 min 52 sec: http://kci.pangea.pub/job/yakkety_unstable_kdepim-apps-libs/1/
[05:52] -kubuntu-ci:#kubuntu-devel- Project yakkety_unstable_libksieve build #1: FAILURE in 13 min: http://kci.pangea.pub/job/yakkety_unstable_libksieve/1/
[05:58] -kubuntu-ci:#kubuntu-devel- Project xenial_unstable_kdepim-apps-libs build #1: FAILURE in 9 min 51 sec: http://kci.pangea.pub/job/xenial_unstable_kdepim-apps-libs/1/
[05:58] -kubuntu-ci:#kubuntu-devel- Project xenial_unstable_libgravatar build #1: FAILURE in 9 min 51 sec: http://kci.pangea.pub/job/xenial_unstable_libgravatar/1/
[06:03] -kubuntu-ci:#kubuntu-devel- Project xenial_unstable_libksieve build #1: FAILURE in 14 min: http://kci.pangea.pub/job/xenial_unstable_libksieve/1/
[06:03] -kubuntu-ci:#kubuntu-devel- Project yakkety_unstable_kdepim-apps-libs build #2: STILL FAILING in 9 min 51 sec: http://kci.pangea.pub/job/yakkety_unstable_kdepim-apps-libs/2/
[06:03] -kubuntu-ci:#kubuntu-devel- Project yakkety_unstable_libgravatar build #2: STILL FAILING in 10 min: http://kci.pangea.pub/job/yakkety_unstable_libgravatar/2/
[06:09] -kubuntu-ci:#kubuntu-devel- Project yakkety_unstable_messagelib build #1: FAILURE in 6 min 5 sec: http://kci.pangea.pub/job/yakkety_unstable_messagelib/1/
[06:14] -kubuntu-ci:#kubuntu-devel- Project xenial_unstable_libgravatar build #2: STILL FAILING in 10 min: http://kci.pangea.pub/job/xenial_unstable_libgravatar/2/
[06:14] -kubuntu-ci:#kubuntu-devel- Project xenial_unstable_kdepim-apps-libs build #2: STILL FAILING in 10 min: http://kci.pangea.pub/job/xenial_unstable_kdepim-apps-libs/2/
[06:14] -kubuntu-ci:#kubuntu-devel- Project yakkety_unstable_calendarsupport build #1: FAILURE in 10 min: http://kci.pangea.pub/job/yakkety_unstable_calendarsupport/1/
[06:14] -kubuntu-ci:#kubuntu-devel- Project yakkety_unstable_libksieve build #2: STILL FAILING in 16 min: http://kci.pangea.pub/job/yakkety_unstable_libksieve/2/
[06:18] -kubuntu-ci:#kubuntu-devel- Project xenial_unstable_messagelib build #1: FAILURE in 4 min 0 sec: http://kci.pangea.pub/job/xenial_unstable_messagelib/1/
[06:20] -kubuntu-ci:#kubuntu-devel- Project yakkety_unstable_messagelib build #2: STILL FAILING in 6 min 3 sec: http://kci.pangea.pub/job/yakkety_unstable_messagelib/2/
[06:24] -kubuntu-ci:#kubuntu-devel- Project xenial_unstable_libksieve build #2: STILL FAILING in 15 min: http://kci.pangea.pub/job/xenial_unstable_libksieve/2/
[06:24] -kubuntu-ci:#kubuntu-devel- Project yakkety_unstable_mailcommon build #1: FAILURE in 3 min 46 sec: http://kci.pangea.pub/job/yakkety_unstable_mailcommon/1/
[06:28] -kubuntu-ci:#kubuntu-devel- Project xenial_unstable_messagelib build #2: STILL FAILING in 5 min 0 sec: http://kci.pangea.pub/job/xenial_unstable_messagelib/2/
[06:31] -kubuntu-ci:#kubuntu-devel- Project xenial_unstable_mailcommon build #1: FAILURE in 2 min 47 sec: http://kci.pangea.pub/job/xenial_unstable_mailcommon/1/
[06:33] -kubuntu-ci:#kubuntu-devel- Project yakkety_unstable_mailcommon build #2: STILL FAILING in 3 min 58 sec: http://kci.pangea.pub/job/yakkety_unstable_mailcommon/2/
[06:38] -kubuntu-ci:#kubuntu-devel- Project yakkety_unstable_calendarsupport build #2: STILL FAILING in 18 min: http://kci.pangea.pub/job/yakkety_unstable_calendarsupport/2/
[06:39] -kubuntu-ci:#kubuntu-devel- Project xenial_unstable_mailcommon build #2: STILL FAILING in 2 min 49 sec: http://kci.pangea.pub/job/xenial_unstable_mailcommon/2/
[06:39] -kubuntu-ci:#kubuntu-devel- Project xenial_unstable_calendarsupport build #1: FAILURE in 25 min: http://kci.pangea.pub/job/xenial_unstable_calendarsupport/1/
[06:52] -kubuntu-ci:#kubuntu-devel- Project yakkety_unstable_eventviews build #1: FAILURE in 14 min: http://kci.pangea.pub/job/yakkety_unstable_eventviews/1/
[06:52] <acheronuk> old what? calligra?
[06:53] -kubuntu-ci:#kubuntu-devel- Project xenial_unstable_calendarsupport build #2: STILL FAILING in 8 min 58 sec: http://kci.pangea.pub/job/xenial_unstable_calendarsupport/2/
[06:53] <acheronuk> tsimonq2: yes, we need qtwebengine. also new git repos for kdepim split :P
[06:56] <acheronuk> tsimonq2: yes, want to get back ports done, but as previously said need to check a few things and test in landing for at least a short while. I don't think any tester has been extensively testing the xenial staging builds
[07:02] -kubuntu-ci:#kubuntu-devel- Project xenial_unstable_eventviews build #1: FAILURE in 8 min 51 sec: http://kci.pangea.pub/job/xenial_unstable_eventviews/1/
[07:09] -kubuntu-ci:#kubuntu-devel- Project yakkety_unstable_eventviews build #2: STILL FAILING in 12 min: http://kci.pangea.pub/job/yakkety_unstable_eventviews/2/
[07:17] -kubuntu-ci:#kubuntu-devel- Project yakkety_unstable_incidenceeditor build #1: FAILURE in 8 min 3 sec: http://kci.pangea.pub/job/yakkety_unstable_incidenceeditor/1/
[07:18] -kubuntu-ci:#kubuntu-devel- Project xenial_unstable_eventviews build #2: STILL FAILING in 10 min: http://kci.pangea.pub/job/xenial_unstable_eventviews/2/
[07:19] -kubuntu-ci:#kubuntu-devel- Project xenial_unstable_kdepim-addons build #68: STILL FAILING in 42 sec: http://kci.pangea.pub/job/xenial_unstable_kdepim-addons/68/
[07:22] -kubuntu-ci:#kubuntu-devel- Project xenial_unstable_kdepim build #1: FAILURE in 4 min 5 sec: http://kci.pangea.pub/job/xenial_unstable_kdepim/1/
[07:24] -kubuntu-ci:#kubuntu-devel- Project xenial_unstable_kdepim-addons build #69: STILL FAILING in 40 sec: http://kci.pangea.pub/job/xenial_unstable_kdepim-addons/69/
[07:31] -kubuntu-ci:#kubuntu-devel- Project xenial_unstable_kdepim build #2: STILL FAILING in 4 min 2 sec: http://kci.pangea.pub/job/xenial_unstable_kdepim/2/
[07:38] -kubuntu-ci:#kubuntu-devel- Project yakkety_unstable_incidenceeditor build #2: STILL FAILING in 14 min: http://kci.pangea.pub/job/yakkety_unstable_incidenceeditor/2/
[07:38] -kubuntu-ci:#kubuntu-devel- Project yakkety_unstable_kdepim-addons build #1: FAILURE in 42 sec: http://kci.pangea.pub/job/yakkety_unstable_kdepim-addons/1/
[07:41] -kubuntu-ci:#kubuntu-devel- Project yakkety_unstable_kdepim build #1: FAILURE in 3 min 8 sec: http://kci.pangea.pub/job/yakkety_unstable_kdepim/1/
[07:44] -kubuntu-ci:#kubuntu-devel- Project yakkety_unstable_kdepim-addons build #2: STILL FAILING in 41 sec: http://kci.pangea.pub/job/yakkety_unstable_kdepim-addons/2/
[07:49] -kubuntu-ci:#kubuntu-devel- Project yakkety_unstable_kdepim build #2: STILL FAILING in 3 min 6 sec: http://kci.pangea.pub/job/yakkety_unstable_kdepim/2/
[08:36] <acheronuk> in Xenial ubuntu-release-upgrader-qt is not installed by default which is breaking GUI upgrades to 16.10
[08:37] <acheronuk> https://www.kubuntuforums.net/showthread.php?70938-16-10-Upgrade-being-flagged-but-nothing-happens
[08:38] <acheronuk> used to be a dependency of muon-updater, but seems it got dropped when switched to plasma-discover-updater
[09:18] <acheronuk> https://bugs.launchpad.net/ubuntu/+source/plasma-discover/+bug/1633692
[09:31] <To24> Hi! Like someone said, Okular is not installed by default in Kubuntu 16.10.
[09:31] <To24> Are we supposed to install Okular or to use other program?
[09:36] <acheronuk> To24: it was removed from the iso due to causing kde4 dependency problems when building that. go ahead and install it :)
[09:38] <To24> So using Okular is still recommended.
[09:38] <To24> Thank you, acheronuk!
[09:38] <acheronuk> yes, though obviously other choices are available
[09:45] -kubuntu-ci:#kubuntu-devel- Project mgmt_docker » master build #1036: STILL FAILING in 2.9 sec: http://kci.pangea.pub/job/mgmt_docker/label=master/1036/
 How did KCI get on?
 @CliffordTheBigRedDoggie, a big list of yakkety fixes and a dead exectutor it seems
 Are they genuine fails?
 Ie packaging fixes needed
 that is next on my list to check
 looks mostly so from a very quick check
 some patches with failed for fuzz. a few actual build failures on the code, which is probably incomepete unstream changes etc
[10:50] <acheronuk> mgmt_docker failed in a painful looking way :(
[11:29] <clivejo> I think mgmt_docker is looking for scaleway slave and freaking out when it cant find it
[11:43] <clivejo> looks like Simon didnt get time to look at the merges!
[11:50] -kubuntu-ci:#kubuntu-devel- Yippee, build fixed!
[11:50] -kubuntu-ci:#kubuntu-devel- Project merger_extra-cmake-modules build #798: FIXED in 18 sec: http://kci.pangea.pub/job/merger_extra-cmake-modules/798/
[11:51] <mamarley> It is nice to see those messages again. :)
[11:53] <clivejo> o/ sick_rimmit
[11:54] <clivejo> mamarley: it sure is!
[11:59] -kubuntu-ci:#kubuntu-devel- Project merger_kpimtextedit build #473: STILL FAILING in 11 sec: http://kci.pangea.pub/job/merger_kpimtextedit/473/
[11:59] -kubuntu-ci:#kubuntu-devel- Yippee, build fixed!
[11:59] -kubuntu-ci:#kubuntu-devel- Project merger_plasma-framework build #783: FIXED in 20 sec: http://kci.pangea.pub/job/merger_plasma-framework/783/
[12:02] -kubuntu-ci:#kubuntu-devel- Yippee, build fixed!
[12:02] -kubuntu-ci:#kubuntu-devel- Project merger_kpimtextedit build #474: FIXED in 19 sec: http://kci.pangea.pub/job/merger_kpimtextedit/474/
[12:03] -kubuntu-ci:#kubuntu-devel- Project xenial_unstable_kpimtextedit build #184: STILL FAILING in 40 sec: http://kci.pangea.pub/job/xenial_unstable_kpimtextedit/184/
[12:03] -kubuntu-ci:#kubuntu-devel- Project yakkety_unstable_kpimtextedit build #99: STILL FAILING in 42 sec: http://kci.pangea.pub/job/yakkety_unstable_kpimtextedit/99/
[12:03] -kubuntu-ci:#kubuntu-devel- Project xenial_unstable_plasma-framework build #276: STILL FAILING in 4 min 51 sec: http://kci.pangea.pub/job/xenial_unstable_plasma-framework/276/
[12:03] -kubuntu-ci:#kubuntu-devel- Project yakkety_unstable_plasma-framework build #140: STILL FAILING in 4 min 55 sec: http://kci.pangea.pub/job/yakkety_unstable_plasma-framework/140/
[12:03] -kubuntu-ci:#kubuntu-devel- Yippee, build fixed!
[12:03] -kubuntu-ci:#kubuntu-devel- Project merger_kio build #807: FIXED in 18 sec: http://kci.pangea.pub/job/merger_kio/807/
[12:05] <soee> o/
[12:05] <soee> KCI is back ? :D
[12:08] -kubuntu-ci:#kubuntu-devel- Project xenial_unstable_kio build #281: STILL FAILING in 43 sec: http://kci.pangea.pub/job/xenial_unstable_kio/281/
[12:09] -kubuntu-ci:#kubuntu-devel- Project yakkety_unstable_kio build #151: STILL FAILING in 47 sec: http://kci.pangea.pub/job/yakkety_unstable_kio/151/
[12:14] -kubuntu-ci:#kubuntu-devel- Project xenial_unstable_kio build #282: STILL FAILING in 42 sec: http://kci.pangea.pub/job/xenial_unstable_kio/282/
[12:14] -kubuntu-ci:#kubuntu-devel- Project yakkety_unstable_kio build #152: STILL FAILING in 44 sec: http://kci.pangea.pub/job/yakkety_unstable_kio/152/
[12:15] -kubuntu-ci:#kubuntu-devel- Project xenial_unstable_kpimtextedit build #185: STILL FAILING in 40 sec: http://kci.pangea.pub/job/xenial_unstable_kpimtextedit/185/
[12:15] -kubuntu-ci:#kubuntu-devel- Project yakkety_unstable_kpimtextedit build #100: STILL FAILING in 43 sec: http://kci.pangea.pub/job/yakkety_unstable_kpimtextedit/100/
[12:15] -kubuntu-ci:#kubuntu-devel- Yippee, build fixed!
[12:16] -kubuntu-ci:#kubuntu-devel- Project merger_kdepim build #6: FIXED in 18 sec: http://kci.pangea.pub/job/merger_kdepim/6/
[12:20] -kubuntu-ci:#kubuntu-devel- Project xenial_unstable_plasma-framework build #277: STILL FAILING in 5 min 55 sec: http://kci.pangea.pub/job/xenial_unstable_plasma-framework/277/
[12:20] <acheronuk> \o/ can sftp to my ubuntu webspace dir
[12:20] -kubuntu-ci:#kubuntu-devel- Project yakkety_unstable_plasma-framework build #141: STILL FAILING in 5 min 58 sec: http://kci.pangea.pub/job/yakkety_unstable_plasma-framework/141/
[12:24] -kubuntu-ci:#kubuntu-devel- Project xenial_unstable_kdepim build #3: STILL FAILING in 4 min 4 sec: http://kci.pangea.pub/job/xenial_unstable_kdepim/3/
[12:25] -kubuntu-ci:#kubuntu-devel- Project yakkety_unstable_kdepim build #3: STILL FAILING in 4 min 9 sec: http://kci.pangea.pub/job/yakkety_unstable_kdepim/3/
[12:33] -kubuntu-ci:#kubuntu-devel- Project yakkety_unstable_kdepim build #4: STILL FAILING in 3 min 9 sec: http://kci.pangea.pub/job/yakkety_unstable_kdepim/4/
[12:33] -kubuntu-ci:#kubuntu-devel- Project xenial_unstable_kdepim build #4: STILL FAILING in 4 min 4 sec: http://kci.pangea.pub/job/xenial_unstable_kdepim/4/
[12:36] <clivejo> soee: yes its back
[12:36] <clivejo> but not fully
[12:36] <clivejo> acheronuk: is it using that file ok?
[12:37] <acheronuk> the log parsing rules? I think so. did not see any complaining in the ones I checked and seems to have parsed
[12:38] <clivejo> so it found the file ok
[12:43] <acheronuk> seems so
[12:45] <clivejo> nice one!
[12:45] <clivejo> do you know how to add new packages to KCI?
[12:51] <acheronuk> I know you add them in /ci-tooling/data/projects/kci.yaml
[12:51] <acheronuk> what you have to do in addition to that? no idea
[12:55] <ahoneybun> the KCI is back!
[12:55]  * ahoneybun hugs everyone who is comfortable with hugs!
[12:57] <ahoneybun> mm a user on G+ asks where are the Calligra and Krita packages
[12:58] <ahoneybun> I can't find them with apt search
[12:58] <ahoneybun> only the language packs for Calligra
[13:02] <acheronuk> ahoneybun: I replied to this one if it's the same person? https://plus.google.com/u/0/+MarkFraser74/posts/WHhs6vBLAyA
[13:04] <yofel> clivejo: regarding mgmt_docker: all matrix jobs will block on their slave jobs, so one configured slave being down holds everything up
[13:07] <To24> ahoneybun: We can see that, for (K)ubuntu nobody has packaged Krita and Calligra: http://packages.ubuntu.com/calligra
[13:07] <To24> http://packages.ubuntu.com/krita
[13:07] <To24> For the latest (K)ubuntu, as we can see
[13:08] <To24> Ok, I see that acheronuk has answerec before me
[13:11] <acheronuk> To24: yes, we discussed it with the ubuntu release prior to release, and decided to temporarily demote calligra to the proposed pocket. There is a new/fixed version in proposed that will hopefully be an update in short order.
[13:12] <To24> Great!
[13:12] <ahoneybun> acheronuk: so it's been pulled from the archive?
[13:12] <ahoneybun> acheronuk: it was the post about a smooth upgrade to 16.10
[13:13] <ahoneybun> https://plus.google.com/+KristerHallergard/posts/95aF1hJweNA
[13:13] <acheronuk> ahoneybun: it's only in proposed for now. so in the archive, but not available in release until it becomes an update
[13:13] <ahoneybun> same person though
[13:13] <ahoneybun> oh so not visible?
[13:14] <acheronuk> ahoneybun: aha. yes, it is
[13:14] <ahoneybun> I know it's a bit crazy to do but should we annonce it? (crazy since we would have to do it for all packages)
[13:16] <acheronuk> calligra? ummmm... if any more people ask about it, then maybe. Should at least go in the release notes as errata or similar I think.
[13:17] <ahoneybun> errata?
[13:18] <acheronuk> ahoneybun: santa_ is just asking the release team about calligra. if it can go in as updates
[13:18] <ahoneybun> does anyone wonder about having a poll to see how many users use calligra over libreoffice
[13:18] <ahoneybun> ?
[13:20] <acheronuk> errata: a list of corrections or soon to be made corrections. i.e. in written works, sofware etc.
[13:20] <acheronuk> I never much liked calligra
[13:26] <mparillo> ahoneybun: I think JR asked around maybe 2-3 years ago. The consensus was that (1) LO was a bit less clunky and (2) LO can save in MS Formats, which is a must-have function for people sharing outside the Linux world, so many of our day-to-day users would install LO anyway. So, basically the argument for Calligra was to try to showcase KDE Apps and the argument for LO was to do what our end-users were likely to prefer. And LO
[13:26] <mparillo> won. IIRC, it was not even close.
[13:29] <mparillo> On one of my laptops, I will need to install Calligra anyway until this is sorted: https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-video-intel/+bug/1625595
[13:30] <BluesKaj> Hiyas all
[13:36] <mparillo> Hiyas BluesKaj. Can  you share the link of the bug you filed on kate profiles?
[13:44] <BluesKaj> mparillo, it must have been a dupe since it's not in my launchpad bug list, or it's been deleted. It's well over a yr ago
[13:46] <mparillo> OK, then I will work on creating a new one.
[14:00] <acheronuk> clivejo santa_: do you think plasma-discover is the right package for this? https://bugs.launchpad.net/ubuntu/+source/plasma-discover/+bug/1633692
 Steam is not working for me
[14:39] <acheronuk> doesn't connect here
[14:41] <soee> Steam ?
[14:43] <acheronuk> now it does. ignore me :P
[15:33] <santa_> acheronuk: probably yes
[15:45] -kubuntu-ci:#kubuntu-devel- Project mgmt_docker » master build #1037: STILL FAILING in 2.4 sec: http://kci.pangea.pub/job/mgmt_docker/label=master/1037/
[16:00] <buovjaga> hi, anyone with edit rights to https://wiki.ubuntu.com/YakketyYak/ReleaseNotes/Kubuntu ? I think the upgrading steps could be made more explicit, enumerated. Even listing, which tab you must enter in Discover.
[16:08] <steve-_-2> so I think this wiki could be tweaked: https://wiki.ubuntu.com/YakketyYak/ReleaseNotes/Kubuntu
[16:08] <steve-_-2> the update steps in the left section are confusing. it's not a good idea to offer "or" steps. Just have a clear path that works and be done. list steps as in 1. 2. 3. and so forth and be precise in descriptions
[16:09] <steve-_-2> and besides that should http://kubuntu.org/ forward to https://kubuntu.org/ ?
[16:09] <steve-_-2> kubuntu KInfocenter still lists the non https URL so that should be updated
 You mean http
 That would be upstream KDE
[16:38] <mparillo> OK, BluesKaj I opened Bug #1633748
[17:19] <soee> urgh...
[17:19] <soee> planetkde.org is blocked by filter ... "Category: Adult Material: adult content, sex, nudity"
[17:26] <mparillo> I picked the wrong week to quit reading Planet KDE.
[17:27] <tsimonq2> Afternoon
[17:28] <tsimonq2> Stayed up until 1 AM working on QtWebEngine
[17:28] <tsimonq2> (to be fair, I was going to go to bed at 10 PM :P)
[17:29] <soee> :p
[17:31]  * acheronuk scans planet KDE without much luck
[17:32] <tsimonq2> acheronuk: dude I've been working on QtWebEngine
[17:32] <acheronuk> good :)
[17:32] <acheronuk> are debian any closer to getting it in their archive?
[17:33] <tsimonq2> I facepalmed at it because it was FTBFS due to a simple typo
[17:33] <acheronuk> I saw that
[17:34] <acheronuk> sorry. back in a bit. food cooking!
[17:34] <tsimonq2> acheronuk: KDE PIM split is going on the top of my priority list after QtWebEngine.
[17:42] <tsimonq2> acheronuk: you got a response from Mark! :D
[17:43]  * tsimonq2 hugs ahoneybun back
[17:44] <acheronuk> tsimonq2: I saw that. I presume his PA or a script does those.
[17:45] <tsimonq2> ...
[17:45] <tsimonq2> No
[17:45] <tsimonq2> He is a human who cares...
[17:46] <acheronuk> wasn't implying he isn't and doesn't. just that he may be a busy one
[17:46] <tsimonq2> acheronuk: I've had conversations with him before. It's not like his schedule is THAT tight that he can't send a quick email saying congrats...
[17:47] <tsimonq2> It's not like it was a 5 page email either
[17:47] <acheronuk> tsimonq2: even better than :)
[17:47] <acheronuk> then
[17:48]  * acheronuk glances at blog
[17:48] <acheronuk> z-series still
 I blame Rik
 Taking up marks time when he's trying to pick a name!
[18:40] <tsimonq2> lol
[19:55] <valorie> does someone have access to edit this page?
[19:55] <valorie> https://help.ubuntu.com/community/YakketyUpgrades/Kubuntu
[19:55] <valorie> there's no such thing as muon-updater in 16.04, it appears it's been replaced by plasma-discovery-updater
[19:56] <valorie> according to a response on the Kub-users list
[19:56] <valorie> I can get into the regular ubu-wiki, but the help pages just send me back to login
[20:01] <acheronuk> just hangs forever on "waiting for help.ubuntu.com" for me
[20:20] <mparillo> valorie: I can edit it. Unfortunately, I cannot easily re-do all my pictures, as I was bit with https://bugs.launchpad.net/ubuntu/+source/kubuntu-meta/+bug/1627348 in VMware.
[20:21] <valorie> :(
[20:22] <mparillo> Plus, for my personal use cases, a fresh install always was better than an upgrade. But for now, want me to just paste plasma-discovery-updater in place of Muon?
[20:23] <valorie> if you can get in, please do
[20:24] <ScottK> acheronuk: that was from him personally.
[20:25] <acheronuk> ScottK: so I now realise :)
[20:25] <acheronuk> which is very cool
[20:25] <acheronuk> and nice
[20:26] <acheronuk> valorie: on refreshing the page, I seem to be logged in
[20:27] <valorie> nice!
[20:28] <acheronuk> mparillo has it locked for editing, so I'll not touch it for now
[20:30] <mparillo> I should be out. I replaced Muon with plasma-discovery-updater, 15.10 with 16.10, and Plasma 5.whatever with Plasma 5.7.5
[20:30] <mparillo> Off to the market.
[20:30] <valorie> thanks mparillo
[20:30] <mparillo> My pleasure
[20:53] -kubuntu-ci:#kubuntu-devel- Project mgmt_docker » master build #1038: STILL FAILING in 2.5 sec: http://kci.pangea.pub/job/mgmt_docker/label=master/1038/
 clivejo: regarding mgmt_docker: all matrix jobs will block on their slave jobs, so one configured slave being down holds everything up
[20:55] <clivejo> what does that mean?
[20:55] <clivejo> Ive brought the scaleway slave up
[20:55] <clivejo> but its still failing on master
[20:58] <valorie> clivejo: the other day you referenced Launchpad bug 1571019 in nootka (Ubuntu) "Nootka package needs update" [Undecided,New] https://launchpad.net/bugs/1571019 and I did some research
[20:58] <clivejo> I did
[20:58] <valorie> although this project calls themselves part of KDE, they are not on KDE infra
[20:59] <valorie> therefore not part of our packageset I believe
[20:59] <valorie> so I responded to the BR (because I could find no other way to write to them) suggesting how they could move into the KDE community
[20:59] <clivejo> https://launchpad.net/ubuntu/+source/nootka
[21:00] <clivejo> the dev wrote to me
[21:00] <valorie> yes, I connected the source to the project
[21:00] <valorie> oh cool
[21:00] <valorie> you might write back and suggest they read the response on the BR
[21:00] <clivejo> Maintainer: Kubuntu Developers<EMAIL_ADDRESS>[21:00] <clivejo> XSBC-Original-Maintainer: Howard Chan<EMAIL_ADDRESS>[21:00] <valorie> also that they give folks a way to contact 'em!
[21:01] <valorie> well, howard might have packaged it
[21:01] <valorie> but I'm pretty sure he is not the devel
[21:01] <valorie> it is a spanish devel
[21:01] <valorie> interesting
[21:01] <valorie> I wonder how that got into our packageset
[21:02] <valorie> the source is on sourceforge
[21:02] <valorie> they should move to KDE
[21:02] <valorie> sourceforge sucks
[21:02] <clivejo> I dunno
[21:03] <clivejo> but it would be good experience for someone
[21:03] <clivejo> get the new version packaged and put a debdiff on that BR and get someone to sponsor it
[21:03] <valorie> "someone" with time and interest, such as tsimonq2?
[21:04] <clivejo> anyone looking to contribute!
[21:05] <clivejo> even you valorie
[21:05] <clivejo> we can go on BBB and Ill guide you :P
[21:05]  * tsimonq2 ignores ping, sees the word "contribute," and automatically raises hand
[21:05] <clivejo> have you churning out packages left, right and centre
[21:06]  * valorie is actually somewhat busy atm
[21:06] <clivejo> sgclark: ping
[21:06] <clivejo> LOL
[21:06] <valorie> and might be offine in a bit when the giant storm hits
[21:06] <valorie> https://www.windytv.com/?43.747,-122.827,6
[21:06] <valorie> so far, it's still hanging off the coast
[21:06] <clivejo> me too, Im a woodchopper in the Sahara
[21:07] <clivejo> oh thats pretty
[21:07] <clivejo> look at the pretty colours
[21:07] <valorie> you can put in your own location
[21:07] <valorie> it's an awesome site
[21:07] <valorie> or even look at the whole world
[21:08] <tsimonq2> clivejo: meet on Big Blue Button?
[21:08] <clivejo> yeah, Matthew seems to be heading this way!
[21:09]  * clivejo blows in a south westly direction to knock Matthew off track
[21:09] <tsimonq2> clivejo: BBB?
[21:10] <clivejo> big beautiful blonde?
[21:10] <clivejo> sure, why not!
[21:10] <tsimonq2> Count me in!
[21:11] <tsimonq2> clivejo: Big Blue Button?
[21:11] <clivejo> what for?
[21:11] <tsimonq2> we needs talk aboot backports
[21:12]  * clivejo covers ears
[21:12] <clivejo> nah nah nah
[21:12] <clivejo> Im not listening
[21:14] <clivejo> what does this mean - http://kci.pangea.pub/job/mgmt_docker/label=master/1038/consoleFull
[21:15] <tsimonq2> clivejo: then bring your pup over here, I want to chat with him
[21:16] <clivejo> hes busy
[21:16] <tsimonq2> dammit, is he chasing that squirrel again?
[21:16] <clivejo> no squirrels here
[21:16] <tsimonq2> oh?
[21:17] <clivejo> he was barking at a cow about 10 mins ago
[21:17] <tsimonq2> XD
[21:18] <acheronuk> valorie: have I missed anything? https://help.ubuntu.com/community/YakketyUpgrades/Kubuntu
[21:19] <clivejo> did you do that acheronuk?
[21:20] <acheronuk> updated it
[21:20] <acheronuk> added the pics and corrected
[21:20] <clivejo> the screenshots?
[21:20] <acheronuk> yes
[21:20] <valorie> acheronuk: the last two images are missing for me
[21:20]  * clivejo pats Rik on the back
[21:20] <valorie> but wow, it looks great
[21:20] <valorie> you rock
[21:20] <clivejo> very nice
[21:21] <acheronuk> I shall add the last few, but I have to let this VM upgrade to get them
[21:22] <acheronuk> also need to add something about switching release update modes from LTS to normal
[21:22] <acheronuk> I'll finish it in a bit
[21:24] <Snowhog> Something I think should be emphasised on that page, is to use a wired connection for the upgrade. A fare number of people get caught with a no-longer working wireless connection when they do these upgraded on a wireless connection. We always recommend to them to do this on a wired ethernet connection.
[21:25] <clivejo> we had issues with Xenial killing wireless
[21:25] <Snowhog> ^^a non-working wireless part way through the process is what I ment to say.
[21:25] <clivejo> but should have that issue with Yakkety Yak dont talk back
[21:25] <clivejo> shouldnt
[21:25] <tsimonq2> Snowhog: *don't
[21:25] <Snowhog> It isn't just Xenial. IF the system being upgraded is using a proprietary wireless driver....
[21:25] <tsimonq2> whoos
[21:25] <tsimonq2> clivejo: *don't
[21:25] <tsimonq2> clivejo: *shouldn't
[21:26] <valorie> I always fish out the wire, yeah
[21:26] <valorie> it's just safer
[21:26] <valorie> same with plugging it into power
[21:26] <valorie> just in case
[21:26] <clivejo> to hbe sure, to be sure
[21:26] <Snowhog> But so many don't, and end up with a non-functioning system and get quiet PO'd. We see a lot of such complaints on our forum.
[21:27] <clivejo> where is this tooling-next from?
[21:27] <tsimonq2> clivejo: s/hbe/be/ :P
[21:27] <Snowhog> Yes. Wired and on AC. It's just a good idea to specify these as "gotcha preventatives".
[21:28] <clivejo> tsimonq2: so when will your pyhon tooling for KCI be ready?
[21:29] <tsimonq2> clivejo: oh, I was given the go-ahead? :D
[21:29] <tsimonq2> s/pyhon/Python/
[21:30] <valorie> perl instead
[21:30] <tsimonq2> NOOOOOOOOOOOO
[21:30] <valorie> php?
[21:30] <valorie> lol
[21:31] <clivejo> java
[21:31] <tsimonq2> no and no
[21:31] <tsimonq2> all three are terrible
[21:31] <clivejo> nice and tidy integration with Jenkin's
[21:31] <tsimonq2> clivejo: with who?
[21:31] <valorie> are you guys actually on BBB?
[21:31]  * valorie would like to listen if so
[21:32] <tsimonq2> yep
[21:32] <tsimonq2> he isn't :P
[21:32] <clivejo> Im in KCI
[21:32] <tsimonq2> s/Im/I'm/
[21:32] <valorie> pfff, still won't work in chromium
[21:32] <clivejo> trying to pull its heart back in
 Kernel 4.9rc1 released :)
 I saw ;)
 I'm subscribed to that ML
[21:34] <clivejo> its in Zazzy?
[21:35] <valorie> oh, I'm the only person in there
[21:36] <valorie> wow, I've never seen this before:
[21:36] <valorie> If you are unable to join using the built-in audio, to join this meeting by phone, dial:
[21:36] <valorie><PHONE_NUMBER>
[21:36] <valorie> Then enter 25318 as the conference pin number.
[21:36] <clivejo> yeah, thats been on there from day one
[21:36] <tsimonq2> ^
[21:36] <clivejo> but Fred said to use it sparingly as it costs them money
[21:37] <valorie> interesting
 Any of you use some ebook reader device?
 And can recommend any good ?
[21:39] <valorie> I have an old kindle
[21:39] <valorie> no touch, no backlight
[21:39] <valorie> no problems!
 ;)
[21:40] <valorie> current favorite seems to be kobo, which is friendly to FOSS
 Any link?
[21:41] <valorie> https://store.kobobooks.com @marcinsagol
[21:41] -kubuntu-ci:#kubuntu-devel- Project mgmt_docker » master build #1039: STILL FAILING in 11 sec: http://kci.pangea.pub/job/mgmt_docker/label=master/1039/
[21:44] <clivejo> she bangs, she bangs
[21:46] <acheronuk> docker still poorly?
[21:47]  * clivejo nods
[21:47] -kubuntu-ci:#kubuntu-devel- Project mgmt_docker » master build #1040: STILL FAILING in 13 sec: http://kci.pangea.pub/job/mgmt_docker/label=master/1040/
[21:48] <clivejo> I dont understand why there are like 3 copies of tooling
[21:49] <valorie> sounds like a question for yofel
[21:55] <clivejo> hummm
[21:55] <clivejo> libkittens.install                                      100%    2     0.0KB/s   00:00
[21:55] <clivejo> kittens.install                                         100%    2     0.0KB/s   00:00
[21:55] <clivejo> libkf5fuckthis5.install
[21:56] <clivejo> really?!?
[21:59] -kubuntu-ci:#kubuntu-devel- Project mgmt_docker » master build #1041: STILL FAILING in 13 sec: http://kci.pangea.pub/job/mgmt_docker/label=master/1041/
[22:00] <valorie> sounds like sitter was killing kittens
[22:01] <valorie> and perhaps a touch of trouble with libkf5 installation?
[22:04] <tsimonq2> yeah :P
[22:07]  * clivejo crosses fingers and toes
[22:07] -kubuntu-ci:#kubuntu-devel- Yippee, build fixed!
[22:07] -kubuntu-ci:#kubuntu-devel- Project mgmt_docker » master build #1042: FIXED in 2 min 59 sec: http://kci.pangea.pub/job/mgmt_docker/label=master/1042/
[22:07] <clivejo> \o/
[22:07] <valorie> woooooooooooooooooo
[22:07] <tsimonq2> WOOOOOOOOOO ð
[22:08] <tsimonq2> that was weird...
 🎉🎉🎉🎉🎉🎉🎉🎉🎉🎉🎉
[22:11] <tsimonq2> ALSO
[22:11]  * clivejo wonders how new packages are deployed
[22:11] <tsimonq2> Frameworks 5.27 was just uploaded to Debian!
[22:11] <clivejo> do I have to do a git pull in master and the slaves?
[22:12] <clivejo> any new ones tsimonq2?
[22:12] <tsimonq2> I don't think so
[22:12] <tsimonq2> I just got spammed with mail
[22:12] <tsimonq2> :P
[22:12] <acheronuk> the release announcement the other say said no new ones.
[22:13] <tsimonq2> clivejo: do we share enough similarities with Debian's packaging to be able to directly merge from their Git?
[22:13] <clivejo> there will be some human effort with merge conflicts
[22:14] <tsimonq2> hm?
[22:14] <clivejo> well the vcs field in the control files will be different
[22:15] <tsimonq2> oh shoot that's right
[22:16] <clivejo> there is probably a way to automate that and always take our version
[22:17] <clivejo> would be nice if KCI could do some of that
[22:18] <tsimonq2> hey so we need gpgme in KCI I think
[22:18] <valorie> oooo, Tomacz from Nootka wrote me back!
[22:18] <tsimonq2> the unstable tip of the git tree
[22:19] <tsimonq2> because according to https://mail.kde.org/pipermail/kde-distro-packagers/2016-October/000227.html it should fix some things
[22:19] <tsimonq2> I'm setting up the jobs now
[22:19] <tsimonq2> (I won't set up a merge_ job, just yakkety/xenial_unstable)
[22:19] <clivejo> tsimonq2: hold on
[22:19] <tsimonq2> ok
[22:19] <clivejo> leave that a second
[22:19] <tsimonq2> didn't do anything yet
[22:19] <tsimonq2> will do
[22:20] <clivejo> I want to add them via the tooling
[22:20] <clivejo> acheronuk: you generated new package requests before
[22:20] <clivejo> care to guide us through it?
[22:21] <acheronuk> nope
[22:21] <clivejo> nope you wont guide us?!?
[22:22] <acheronuk> nope I don't recall doing that before
[22:22] <clivejo> someone submitted a MR
[22:22] <acheronuk> for what?
[22:23] <tsimonq2> clivejo: s/R/P?
[22:23] <tsimonq2> whops *s/R/P/
[22:23] <tsimonq2> argh *whoops
[22:23] <acheronuk> remind me
[22:23] <clivejo> [Merge] ~acheron/kubuntu-ci/+git/pangea-tooling:master into ~kubuntu-ci-admins/kubuntu-ci/+git/pangea-tooling:master
[22:24] <tsimonq2> clivejo: link?
[22:24] <clivejo> for kirigami
[22:24] <tsimonq2> ...link?
[22:24] <acheronuk> that was.... kirigami and kdevplatform
[22:25] <acheronuk> I did that MR, and someone else took care of the rest I think?
[22:25] <tsimonq2> oh, do we make changes to ci-tooling/data/projects/kci.yaml ?
[22:25] <clivejo> https://git.launchpad.net/~kubuntu-ci-admins/kubuntu-ci/+git/pangea-tooling
[22:25] <clivejo> Phil done it, but you submitted a MR
[22:26] <tsimonq2> !grammar
[22:26] <tsimonq2> LOL
[22:26] <acheronuk> gimme 10 mins. just want to finish this wiki
[22:27]  * clivejo ignores the noisey spell/grammar checker
[22:27] <clivejo> ok
[22:28] <tsimonq2> s/noisey/noisy/
[22:28] <clivejo> you do know I do it on purpose now?!?
[22:29] <tsimonq2> clivejo: do I have the right to just take Debian's packaging for https://mail.kde.org/pipermail/kde-distro-packagers/2016-August/000215.html and edit Vcs-* fields, or do I *have* to do it myself?
[22:29] <tsimonq2> clivejo: or Neon's?
[22:29] <clivejo> what do you mean?
[22:30] <clivejo> well to use any of Riddell's IP you have to give him a hug
[22:30] <tsimonq2> git clone debiankde:akonadi-import-wizard && cd akonadi-import-wizard && vim debian/control && git add debian/control && git commit -am "Change th Vcs-* fields" && git push kubuntu:akonadi-import-wizard
[22:31] <tsimonq2> clivejo: I'll have to contact him to get an exception
[22:31] <tsimonq2> clivejo: and have you hugged him?
[22:31] <clivejo> that Im not sure
[22:32] <clivejo> do virtual hugs count?
[22:32] <clivejo> {{{{{{{ tsimonq2 }}}}}}}
[22:32] <tsimonq2> clivejo: just asked Riddell for alternative methods. :P
[22:32] <tsimonq2> have you hugged him yet?
[22:33] <clivejo> kubuntu people hug all the time
[22:33] <clivejo> I never kept track!
[22:33] <clivejo> we are friendly dont you know
[22:33] <tsimonq2> So you don't know if you have ever hugged Riddell?!?
[22:33] <tsimonq2> s/dont/don't/
[22:36] <clivejo> tsimonq2: are you any good at search back logs?
[22:36] <tsimonq2> *searching
[22:36] <tsimonq2> why?
[22:37] <acheronuk> ok. done for now I think https://help.ubuntu.com/community/YakketyUpgrades/Kubuntu
[22:37] <clivejo> when Scarlett was learning about KCI there was a discussion here with Haruld, Phil and Scarlett about how to add jobs etc
[22:39] <acheronuk> valorie: done I hope. please check if you can spare a sec ^^^
[22:39] <clivejo> acheronuk: I wouldnt enjoy a cup of coffee
[22:39] <clivejo> can I have beer instead?
[22:40] <acheronuk> have what you like. it's a wiki :P
[22:40] <tsimonq2> s/wouldnt/wouldn't/
[22:40] <clivejo> I really like it Rik
[22:41] <acheronuk> s/tsimonq2/nitpicker
[22:41] <clivejo> s/tsimonq2/annoying_nitpicker
[22:42] <acheronuk> It's got pretty pics. makes it easy to like
[22:42] <valorie> woooooo
[22:43] <valorie> thank you rik
[22:43] <acheronuk> and just finished what I think Aaron started...
[22:43] <tsimonq2> acheronuk: sed: -e expression #1, char 20: unterminated `s' command
[22:43] <valorie> let me be sure it is properly linked on our announcement
[22:43] <tsimonq2> clivejo: sed: -e expression #1, char 29: unterminated `s' command
[22:43] <valorie> thank you ahoneybun for getting that started
[22:44] <tsimonq2> clivejo, acheronuk: y'all need to learn how to properly sed
[22:44] <tsimonq2> page looks nice :)
[22:45] <clivejo> s/y'all/you all/
[22:45] <acheronuk> lol
[22:46] <tsimonq2> clivejo: it's proper American slang
[22:48] <tsimonq2> right, valorie?
 Y'all is redneck
 Or country slang
[22:49] <clivejo> tsimonq2 is a hill billy?
[22:49] <tsimonq2> But I still put the apostrophe in the right place, unlike clivejo. :P
[22:50] <clivejo> because Im typing to humans who dont need it to understand
[22:50] <tsimonq2> s/Im/I'm/
[22:50] <valorie> rofl
[22:50] <valorie> all y'all should stop arguing
[22:50] <clivejo> sorry granny
[22:50] <tsimonq2> I thought it was "all a y'all"
[22:51]  * clivejo hangs head in shame
[22:51]  * tsimonq2 glowers at clivejo
[22:51] <valorie> haha
[22:52] <valorie> tsimonq2: I'm not from the south, so I might be using it improperly
[22:52] <valorie> all yawlz
[22:52] <tsimonq2> same here
[22:52]  * valorie smacks clivejo for the "granny"
[22:53] <clivejo> you are granny linux!
[22:54] <valorie> for some reason granny sounds much older and scrawnier than I am
[22:54]  * valorie is so not scrawny
[22:55] <acheronuk> clivejo: can't find that discussion get in the IRC logs :/
[22:55] <acheronuk> s/get/yet
[22:56]  * acheronuk looks at clock!
[22:56] <acheronuk> wow. later than I thought
[22:56] <tsimonq2> acheronuk: sed: -e expression #1, char 9: unterminated `s' command
[22:57] <tsimonq2> !sed
[22:59]  * acheronuk steals clivejo's wiki beer
[22:59] <tsimonq2> omg, sgclark is goddess
[22:59] <tsimonq2> s/goddess/godess/
[22:59] <tsimonq2> Kubuntu Developers2014-02-13Memberââ
[22:59] <tsimonq2> she was a developer two MONTHS before becoming a ninja!
[23:00] <valorie> ?
[23:00] <tsimonq2> I couldn't do that if I tried!!!
[23:00] <valorie> she is a goddess, yes, but that seems a bit wrong
[23:01] <acheronuk> something was messed up with her dates. I found that went I went looking for her meeting logs
[23:02] <tsimonq2> sgclark: Can I borrow your time travel device?
[23:02] <tsimonq2> XD
[23:03] <tsimonq2> Tha'ts more realistic than goddess
[23:03] <tsimonq2> *That's
[23:03] <tsimonq2> :P
[23:04] <clivejo> acheronuk: https://irclogs.ubuntu.com/2016/03/02/%23kubuntu-devel.html
[23:12] <acheronuk> that looks fun
[23:14] <Snowhog> Not being pushy (well, yes I am), but is there a reason that you didn't include the *recommendation* to use a wired connection when doing the upgrade on the wiki page?
[23:15] <tsimonq2> clivejo: ping ping ping ping ping ping ping
[23:15]  * clivejo yawns
[23:15] <tsimonq2> clivejo: your fault: http://kci.pangea.pub/job/mgmt_tooling/2/consoleFull
[23:17] <valorie> Snowhog: not sure acheronuk was paying attention when we were talking
[23:17] <valorie> I think he was busy editing
[23:17]  * valorie still can't login to the darn thing
[23:18] <clivejo> how is that my fault?
[23:18] <Snowhog> Did any of you tell acheronuk, that "as the new guy", anthing that goes wrong is his fault?
[23:18] <valorie> lol
[23:18] <valorie> so true!
[23:18] <tsimonq2> no
[23:18] <acheronuk> Snowhog: yes, the reason was that and that I got sidetracked and forgot. sorry.
[23:18] <tsimonq2> *I* always get blamed for things
[23:18] <tsimonq2> :P
[23:19] <Snowhog> acheronuk: Well, that's why "as a concerned user" I'm here to remind you. ;)
[23:21] <clivejo> tsimonq2: you pushed to the tooling
[23:21] <clivejo> https://git.launchpad.net/~kubuntu-ci-admins/kubuntu-ci/+git/pangea-tooling/commit/
[23:21] <clivejo> I blame you!
[23:21] <tsimonq2> clivejo: but it was the first jobs
[23:21] <tsimonq2> clivejo: it lacks permissions
[23:22] <tsimonq2> clivejo: that's where you come in
[23:23] <clivejo> you are soooo annoying!
[23:24] <clivejo> I'm disabling notification on Telegram!
[23:25] <tsimonq2> clivejo: I need to PM you on a serious note
[23:25] <acheronuk> Snowhog: Done :)
[23:26] <mparillo> acheronuk: You are SO fast. I went to update, and you were already in there.
[23:27] <Snowhog> acheronuk: /me smiles On behalf of K users everywhere, I thank you. /me bows
[23:28] <mparillo> But, may I capitalize Internet, and change non-wireless to wired and try to fix the numbering in the box at the right?
[23:28] <acheronuk> feel free
[23:34] <ahoneybun> nice Slack can intergrate Trello!
[23:36] <ahoneybun> soee:  let's use Slack more
 Lot of people against slack


[08:03] <kjackal> Good morning Juju world!
[09:55] <ionutbalutoiu> Hello, guys! Do you know if I'm able to release a charm on charm store without uploading any resources ? My use case is that I have a charm that uses resources, but I don't want to upload them to charm store due to EULA. Still I want users to get the resources and deploy the charm specifying them at deploy.
[09:57] <ionutbalutoiu> Users will get the resources separately as described in the README, thus we don't get into trouble because we redistribute software.
[10:16] <kjackal> ionutbalutoiu: Hi, yes you can do that
[10:17] <kjackal> ionutbalutoiu: this is practicaly how all charms written prior to juju 2.0 work
[10:17] <kjackal> let me grab you an example
[10:17] <ionutbalutoiu> ibalutoiu@samba:~/work/juju/charms/windows/azure-service-fabric$ charm release cs:~cloudbaseit/azure-service-fabric-8
[10:17] <ionutbalutoiu> ERROR cannot release charm or bundle: bad request: charm published with incorrect resources: resources are missing from publish request: asf-zip-package, dotnet-installer
[10:18] <ionutbalutoiu> This is what I get when trying to release a charm that has resources defined but not uploaded. Remember, I mean 'release/publish' not push to the charm store.
[10:19] <kjackal> ionutbalutoiu: Ah I see now what you are saying
[10:19] <kjackal> ionutbalutoiu: you want to use the resources mechanism but not upload a binary
[10:19] <ionutbalutoiu> yep
[10:19] <kjackal> ionutbalutoiu: yes we do have exmple for that too
[10:19] <ionutbalutoiu> as I want users to specify them at deploy.
[10:20] <kjackal> ionutbalutoiu: the idea is that you upload a dummy empty file as a resource
[10:20] <kjackal> ionutbalutoiu: let me grab an example :)
[10:21] <ionutbalutoiu> kjackal, yea. I thought about that too. But hoped that there might be a switch of something which I didn't find in the help to publish without resources.
[10:22] <kjackal> ionutbalutoiu: I am not aware of any such switch
[10:22] <kjackal> unfortunately the example I had in mind is not that helpfull
[10:23] <ionutbalutoiu> kjackal, people will now go the charm page and they can download the resources, a file will pop up for the download, but instead will be a fake file.
[10:24] <ionutbalutoiu> kjackal, that would do the work for now. But still imo it would've been better if resources remained grayed as it is now: https://jujucharms.com/u/cloudbaseit/azure-service-fabric/8 even after the publish.
[10:25] <ionutbalutoiu> Use case it is that sometimes EULA doesn't permit redistributing the software. So people using my resources have to go the original website, accept eula there, and provide the resource for my charm manually at deploy time.
[10:25] <kjackal> I see your point. True, exposing the resources like this some times might be wrong. There might be resources there essoteric to th internal operation of the charm
[10:26] <ionutbalutoiu> Yep
[10:29] <kjackal> Good point, would you want to send an email with your use-case on the list? Best case schenario there might be a way around this already, worst case the teams responsible for this would hear you.
[10:29] <ionutbalutoiu> Yep. Please do send. That would be awesome.
[10:30] <kjackal> What should I tell them? Who are you? What is your affiliation & email?
[10:30] <ionutbalutoiu> I'm Ionut Balutoiu, Cloud Engineer at Cloudbase Solutions. The guys writing Juju charms for Windows. :)
[10:31] <kjackal> Thanks
[10:31] <ionutbalutoiu> np
[10:31] <ionutbalutoiu> kjackal, For now, question is: When I upload an empty file as resource so I can publish the charm, if someone manually specifies the resource at deploy as I want them to, will the resource specified by the user get uploaded to state machine and not the default empty file from charm store, right?
[10:33] <kjackal> Yes. You can even get the size of the resource you got from the store so that you detect that this is not the right file and display the right message
[10:33] <ionutbalutoiu> Cool
[10:34] <ionutbalutoiu> kjackal, and btw<EMAIL_ADDRESS>is my e-mail. You asked for this one also, sorry.
[10:35] <kjackal> thanks I will put you in cc in case you want to add-up anything
[10:41] <ionutbalutoiu> Thank-you
[10:45] <ionutbalutoiu> There's also another topic that I have question for, if you still have some time or anyone else. Context, you have 4 peer units, you remove one unit, only in relation departed you still have access to relation data, I need relation data info, so I want to do my business logic here.
[10:45] <ionutbalutoiu> How do I find out which is the unit leaving and the ones staying ? As far as I noticed, relation departed triggers on all of them like this: once on the units remaining in the peer relation and N number of times on the unit leaving (where N is the number of units remaining).
[10:51] <kjackal> ionutbalutoiu: Email sent
[10:51] <ionutbalutoiu> kjackal, received, thanks.
[10:51] <kjackal> ionutbalutoiu: here is how we query for the nodes in spark: https://github.com/juju-solutions/interface-spark-quorum/blob/master/peers.py
[10:52] <kjackal> we iterate over the conversations
[10:53] <ionutbalutoiu> Yes. I understand, but is there a way to figure out which is the unit leaving?
[10:53] <ionutbalutoiu> That would give you a list of all the peer units, right ? The one leaving and the others. I would like to know which is the one leaving.
[10:54] <stub> ionutbalutoiu: A unit cannot tell if it is the one being torn down, or if it is $REMOTE_UNIT that is being torn down.
[10:54] <stub> I'm sure there is an open bug on this... looking
[10:55] <ionutbalutoiu> stub, I just got into this use base when writing my last charm. Sometimes is if useful to know if you're leaving or not.
[10:55] <ionutbalutoiu> use case*
[10:55] <stub> Yes. I have some data loss issues it causes.
[10:56] <stub> If a Cassandra unit is leaving the cluster, it needs to decomission itself cleanly. If a different unit is leaving the cluster, it doesn't care.
[10:56] <stub> Its tied up in https://bugs.launchpad.net/juju-core/+bug/1417874, but a separate bug report may help
[10:56] <mup> Bug #1417874: [RFE] Impossible to cleanly remove a unit from a relation <canonical-is> <charms> <feature> <hooks> <sts> <sts-rfe> <juju:Triaged> <juju-core:Won't Fix> <https://launchpad.net/bugs/1417874>
[13:50] <stub> ionutbalutoiu, kjackal : I opened up https://github.com/juju/charmstore-client/issues/103 on optional resources. I realized this problem is going to hit all the charms we have in development using snaps.
[13:50] <kjackal> thanks stub
[13:52] <ionutbalutoiu> thank-you stub
[14:02] <skay> hi, I was using 'waiting' for things like waiting for a database relation, but after reading https://jujucharms.com/docs/stable/reference-status I should use 'blocking' for things like that, yes or no?
[14:03] <rick_h> skay: yes, if your application doesn't function without a database then blocked is best
[14:03] <rick_h> skay: it indicates that the user needs to pay attention here
[14:03] <rick_h> skay: waiting is only temp and does not alarm the user
[14:11] <skay_> rick_h: thanks
[14:11] <skay_> (I'm also building up to some questions about reactive states)
[14:16] <skay> ok, reactive states question. the docs don't show @hooks mixed with reactive state decorators. am I allowed to mix them?
[14:17] <skay> if I can't mix them, then I'd just have conditionals inside my hook
[14:28] <stub> Whoops, ranting on bug reports. Must be dinner time.
[14:29] <rick_h> stub: :)
[14:31]  * stub wanders off to find a baby to eat
[15:27] <Spaulding> Hi guys
[16:10] <lazyPower> Heyo Spaulding  (belated)
[16:13] <skay> question, I'm not sure I should keep my install hook. I have a function that does some installation stuff @when_not('snap.installed.yadda')
[16:13] <skay> so, I could just get rid of my install hook and use a reactive function instead. do I understand correctly?
[16:20] <marcoceppi> skay: sounds about right
[16:21] <skay_> cool
[16:22] <marcoceppi> skay: to clarify, you're removing like @hook('install'), yeah?
[16:22] <skay_> marcoceppi: yes. because it doesn't seem necessary anymore
[16:23] <marcoceppi> skay: totally, you almost never need to use @hook
[16:23] <skay_> the relation-joined/changed/departed hooks still get used a lot?
[16:25] <marcoceppi> skay: oh, sure, but in the charm layers (not the interfaces)
[16:30] <skay> marcoceppi: is there a state that gets set when a resource is attached?
[16:30] <skay> marcoceppi: I didn't find it but maybe I overlooked it
[16:30] <marcoceppi> skay: not at the moment, that's triggered in the @hook('upgrade-charm')
[16:31] <marcoceppi> or, if provided during deploy, then it'll just be available
[16:31] <skay> currently I'm just checking resource_get before deciding to install the snap
[16:31] <skay> and in the upgrade-charm hook I check to see if the resource has actually changed
[16:32] <marcoceppi> skay: yeah, resource_get will either get latest, or return current path
[16:32] <skay_> I'm doing that, and then checking any_file_changed([resource_file]) before calling snap.install
[16:33] <skay_> you or someone may have explained that the any_file_changed was good for checking for that
[17:05] <marcoceppi> skay: it wasn't I, but it's actually a pretty good idea. I think we'll work to adding a resource.changed state into the base layer, but it'll need a bit more time to mature to figure out what that would look like form a usability perspective
[17:38] <cholcombe> are we no longer allowed to use the juju-info relation?
[17:38] <cholcombe> i'm seeing: ERROR charm "preserve" using a reserved relation name: "juju-info"
[17:38] <cholcombe> for 2.0.1 juju
[17:39] <cholcombe> oh nvm i had juju-info in the wrong place :)
[17:39] <cholcombe> hah
[17:54] <skay_> when I try to destroy-model it doesn't work because it cannot connect to API
[17:54] <skay_> what do I need to kick?
[18:56] <skay_> help, how did I kill juju this time
[19:04] <rick_h> skay_: ? what's up?
[19:05] <rick_h> skay_: use kill-controller if the controller is down and it should tear everything down bypassing the api server?
[19:05] <skay_> aha, I'll try that
[19:06] <skay_> the api server is not responding
[19:06] <rick_h> yea, it should try, and then fail, and then go straight to the cloud provider to remove the machines using the provider's apis
[20:41] <petevg> bcsaller, cory_fu: hadoop-processing working! (modulo the reset issue, at least) https://github.com/juju-solutions/matrix/pull/34
[21:14] <petevg> bcsaller: any objections to me merging cory_fu's updated color handling? https://github.com/juju-solutions/matrix/pull/32
[21:16] <bcsaller> petevg: sounds good
[21:28] <petevg> bcsaller: merged cory_fu's branch. Rebased and pushed an update for https://github.com/juju-solutions/matrix/pull/34
[21:29] <cory_fu> petevg: Just added a minor comment / question to your PR
[21:30] <petevg> cory_fu: answered your question :-)
[21:31] <petevg> cory_fu: basically, lots of empty parens made me sad, and made me worry about bugs.
[21:32] <cory_fu> Yeah, fair enough.  I think the no-parens vs empty-parens thing with Python decorators is kind of dumb.
[21:33] <cory_fu> petevg: I made @only_once work either way in charms.reactive: https://github.com/juju-solutions/charms.reactive/blob/master/charms/reactive/decorators.py#L217
[21:33] <petevg> cory_fu: yeah. Admittedly, they are two separate beasts. Add the parens, and you either need another level of wrapper function, or another method in the class. The implementation would get really messy if you had to figure which one the user meant ...
[21:33] <cory_fu> But to do that with your decorator would be more of a hassel
[21:33] <cory_fu> *hassle
[21:33] <petevg> cory_fu: fancy :-)  But yeah, too late on a Friday to figure out how to do that with the monster that I've built ...
[21:34] <cory_fu> petevg: Yeah, it's not worth worrying about
[21:34] <petevg> Cool.
[21:39] <cory_fu> petevg: Actually, now that I think about it, I don't really like the potential for errors with tag name typos, either.  What about something like this: http://pastebin.ubuntu.com/23569587/
[21:40] <petevg> cory_fu: if anyone wants to add actions and tags, they'll need to add a bunch of arguments to the tagged_action decorator. The idea with the tags was that outside actions could add to them, without messing with core.
[21:41] <cory_fu> petevg: What would such tags be useful for if they're not understood by the plan generator?
[21:42] <petevg> cory_fu: They might not be. But you're still looking at adding an arg in two places (plan, action) rather than three, plus checking to make sure that nobody has messed things up by making assumptions about positional arguments.
[21:43] <petevg> cory_fu: I guess another approach could be to make a list of constants in tags.py. That saves typos (or at least, surfaces them quickly).
[22:08] <petevg> cory_fu: updated my PR with the constants thing. If you want to argue strongly for just doing args, feel free. I think that the constants will be neater in the long run, though.
[22:08] <petevg> bcsaller ^
[22:09] <petevg> cory_fu, kwmonroe: do we have the sauce for the hadoop-spark bundle checked in anywhere?
[22:10] <kwmonroe> petevg: https://github.com/juju-solutions/bigtop/tree/feature/hadoop-spark-bundle/bigtop-deploy/juju/hadoop-spark
[22:11] <petevg> kwmonroe: got it. Is that close to being checked into master, by any chance?
[22:12] <kwmonroe> no petevg, i haven't created a pr to link to https://issues.apache.org/jira/browse/BIGTOP-2561 yet
[22:12] <kwmonroe> i mean, i could if you need it.  it's not hard.  i just haven't done it yet.
[22:13] <petevg> kwmonroe: I was going to brag about how we were in Apache bigtop in D.C., but then the bundle isn't actually in trunk. I can point the the source on the store, though, and then look at the apache repo once I get to the layer ...
[22:20] <petevg> cory_fu: heh. I had misspelled "subordinate" in my docstring. Thank you for pushing to less typo bugs :-)
[22:27] <lucacome> hello
[22:38] <kwmonroe> petevg: if you're still around, care to gander at this?  https://github.com/apache/bigtop/pull/166
[22:39] <kwmonroe> no worries if you can't get to it tonight petevg.  i can def get it merged before Monday.
[22:39] <petevg> kwmonroe: looking ...
[22:40] <petevg> kwmonroe: +1 thank you :-)
[22:49] <kwmonroe> thar she blows petevg:  https://github.com/apache/bigtop/tree/master/bigtop-deploy/juju  have a good time in DC!
[22:50] <petevg> kwmonroe: yay! You rock. Thank you :-)
[23:05] <lucacome> I'm creating a charm for NGINX, is there someone that can help me/review what I've done so far?
[23:10] <kwmonroe> lucacome: unfortunately, it's already EOD for a lot of people that hang out here (i've got 1 foot out the door myself), but there is an nginx layer that may be helpful to consume/tweak:  https://github.com/battlemidget/juju-layer-nginx
[23:11] <kwmonroe> lucacome: to keep your issues from being lost in irc ether, i'd suggest firing off an email to the list<EMAIL_ADDRESS>if you have specific charming questions or want to have some eyeballs on your work so far.
[23:12] <lucacome> kwmonroe, yes I started from that implementat
[23:12] <lucacome> *implementation


[00:00] <Eickmeyer> Just need to manually add a swap partition or swap file.
[00:00] <Eickmeyer> If you need it.
[01:07] <OvenWerks> Eickmeyer: after a few firefox OOM crashes...
[01:08] <Eickmeyer> Yeah, that's a good reason.
[01:08]  * OvenWerks opens too many tabs at a time
[01:08] <OvenWerks> Eickmeyer: I am guessing that sleep no longer uses swap?
[01:09] <OvenWerks> I had heard at one time it did
[01:09] <Eickmeyer> Sleep doesn't use swap. Hibernate did.
[01:09]  * OvenWerks doesn't know the difference
[01:09] <Eickmeyer> Hibernate saves RAM to disk.
[01:09] <Eickmeyer> Sleep just keeps RAM running.
[01:10] <OvenWerks> untill I got the laptop, I had it set to never sleep or hibernate
[01:10] <OvenWerks> So sleep uses power and hibernate does not.
[01:10] <Eickmeyer> In order to hibernate, you must have exactly as much swap as RAM or more.
[01:10] <Eickmeyer> Correct.
[01:11]  * OvenWerks tries to thin k if that is useful..
[01:11] <Eickmeyer> Just makes it so that you don't have to shut down all of your applications if you have them running, makes boot faster.
[01:12] <Eickmeyer> That said, I think Ubuntu has hibernate disabled and it's a pain to enable even with equivalent swap/RAM.
[01:12] <Eickmeyer> I don't use it, honestly.
[01:13] <OvenWerks> yeah, I started doing a shutdown to save batteries during travel... it took so long to shut down (thankyou snap which for some reason can keep shutdown suspended forever)
[01:14] <Eickmeyer> Hmmm... most recent versions of snapd are supposed to have that fixed.
[01:14] <OvenWerks> I ended up thinking was shutdown, closed the lid which confused it to bits and arived at the other end with a quite warm machiine.
[01:14] <OvenWerks> I had to hold the power button long enough to kill it to get it to do anything
[01:15] <OvenWerks> fixed how long ago?
[01:15] <Eickmeyer> Month or so. You might try running "sudo snap refresh" to see if everything is updated.
[01:16] <OvenWerks> Ug, anothhert pop up that says firefox will update in 13 daysbut no way to update it (with a button click)
[01:17] <Eickmeyer> That's supposed to be fixed with the most recent snapd (fixed this past week)
[01:18] <Eickmeyer> Quit firefox, "sudo snap refresh", open firefox.
[01:18] <OvenWerks> so I guess it will fix itself in 13 days ...
[01:18] <Eickmeyer> Nope. Don't wait that long.
[01:18] <OvenWerks> sudo snap refresh
[01:18] <OvenWerks> [sudo] password for len:
[01:18] <OvenWerks> All snaps up to date.
[01:18] <Eickmeyer> Is firefox really closed?
[01:18] <Eickmeyer> Like, process exited?
[01:19] <OvenWerks> ah, it is doing something this time
[01:20]  * OvenWerks hopes he doesn't loose his settings this time
[01:20] <Eickmeyer> Shouldn't. Settings are in your home directory, the snap is in /var/snaps
[01:21] <OvenWerks> going from 22.10 to 23.04 did
[01:21] <OvenWerks> Anyway. it seems my settings/bookmarks are still there
[01:21] <Eickmeyer> Yeah, I know, but that seems more like a weird glitch than anything.
[01:24] <OvenWerks> so I should try shutting down some time and see if it shuts down quick. The idea that there should be a delayed shutdown doesn't make sense. Generally people do a shutdown cause they need to go... now not sometime soon.
[01:27] <OvenWerks> Anyway. I am thinking to nuc the windows partition because I have to reset the bios just to use it and the only think not working is the camera. It seems the camera used to work when there was a camera on/off switch (same module) but it doesn't any more because the button to turn it on is no longer there
[01:27] <Eickmeyer> Right. I think that's more of a systemd thing than anything where it's trying to stop daemons and it's getting hung confirming something is stopping because it's not coming back stoped.
[01:28] <OvenWerks>  There must be some way of sending the HW a signal to turn on but it is not important enough to me (my wife would like it :) to worry. Apparently windows has a softswitch to turn it on... a privacy thing.
[01:29] <OvenWerks> so I should have room for a swap.
[01:32]  * OvenWerks notes that the module for the camera does load, so it is detected.