[00:00]  * DarinMiller wonders how Rik can old conversations so fast !!!
[00:01] <DarinMiller> ^can find....
[00:01] <valorie> good searching skillz!
[00:01] <acheronuk> magic
[00:01] <acheronuk> lol
[00:02] <mparillo> valorie: Well in that case, I can see (after we get the tooling in shape and mint new developers (and maybe a MOTU)), three kinds of users. First, those like me. Ideally I would always stay on the development version (ZZ), and it would feel like a rolling distro. This would keep us at top of mind with the Distrowatchs etc.. Second, I believe most of our users want an LTS to be as current as reasonably possible (I understand 
[00:02] <mparillo> that this time the Qt dependency added to our burdens). I think updates to the current supported version are a distant third priority, but if necessary as a step to upgrading backports for LTS, I understand it.
[00:04] <valorie> mparillo: probably true
[00:05] <valorie> in this case though, I'd like to see plasma updated for YY
[00:05] <valorie> because we're not sure we can do it for LTS
[00:05] <valorie> because of Qt
[00:06] <tsimonq2> In my opinion, we should keep Xenial Backports up to date until 18.04 gets released.
[00:06] <tsimonq2> We do testing to make sure a user can easily enable backports, and we're good to go.
[00:06] <valorie> well, as we can
[00:06] <valorie> keeping it working for people is the most important part
[00:07] <tsimonq2> Yes, for sure.;
[00:07] <valorie> the reason people choose LTS is stability
[00:07] <valorie> not "the latest"
[00:07] <tsimonq2> Since our plan was to at the very minimum keep Xenial Backports up-to-date until Plasma 5.8.9, we should figure out what to do then.
[00:07] <acheronuk> which is part of the reason it's not in backports, even though it's 90% done. 5.7.5 at least
[00:08] <tsimonq2> acheronuk: Let's discuss that quick. What's stopping things from getting into Xenial Backports at the moment?
[00:08] <tsimonq2> valorie: But if the latest is tested and works fine, why shouldn't we?
[00:09] <acheronuk> same things that were the case the last time you asked only a few days ago
[00:09] <tsimonq2> But as far as I remember, I didn't get an answer.
[00:09] <acheronuk> you did
[00:09] <valorie> we'll get there
[00:09] <valorie> one thing at a time
[00:09] <mparillo> Oh oh, here comes a link to the logs.
[00:10] <tsimonq2> Apologies for repeating questions that might have been answered a few days ago, this last week with the lack of sleep was a blur...
[00:10] <acheronuk> or I though you did, anyway
[00:11] <tsimonq2> acheronuk: Mind searching the logs? :)
[00:11] <acheronuk> (1) needs merging into XX_backports branch (2) need to review what from the Qt overlay PPA we need, or to rebuild to mitigate Qt ABI issues, (3) then need to test that properly for a bit
[00:12] <tsimonq2> Ok, what *exactly* needs merging?
[00:12] <tsimonq2> Because if that's our first step, let's do it.
[00:13]  * clivejo quickly closes the IRC window and goes to bed
[00:13] <tsimonq2> Bai clivejo. Sleep good. :)
[00:15] <tsimonq2> !info kde-full unstable
[00:16] <tsimonq2> acheronuk: So what needs merging into kubuntu_xenial_backports?
[00:16] <acheronuk> eeek! 1:15am
[00:16] <tsimonq2> acheronuk: So let's pick this up tomorrow then? :P
[00:17] <acheronuk> yep. that would be best, as I would like to go through this just once with clive and santa as well is poss
[00:17] <tsimonq2> acheronuk: Ok, please keep me in the loop.
[00:17] <acheronuk> *if possible
[00:17] <tsimonq2> Nighty night. :)
[00:18] <acheronuk> Night :)
[01:39] -kubuntu-ci:#kubuntu-devel- Yippee, build fixed!
[01:39] -kubuntu-ci:#kubuntu-devel- Project yakkety_unstable_kcontacts build #135: FIXED in 13 min: http://kci.pangea.pub/job/yakkety_unstable_kcontacts/135/
[01:54] -kubuntu-ci:#kubuntu-devel- Project yakkety_unstable_kdeplasma-addons build #3: STILL FAILING in 14 min: http://kci.pangea.pub/job/yakkety_unstable_kdeplasma-addons/3/
[02:14] -kubuntu-ci:#kubuntu-devel- Project yakkety_unstable_kdeplasma-addons build #4: STILL FAILING in 15 min: http://kci.pangea.pub/job/yakkety_unstable_kdeplasma-addons/4/
[02:24] -kubuntu-ci:#kubuntu-devel- Yippee, build fixed!
[02:24] -kubuntu-ci:#kubuntu-devel- Project yakkety_unstable_libkscreen build #123: FIXED in 9 min 53 sec: http://kci.pangea.pub/job/yakkety_unstable_libkscreen/123/
[02:31] <tsimonq2> I just documented the FTBFS for all of yakkety_unstable KCI: https://docs.google.com/spreadsheets/d/1sDfr6pwLRtaJXkgKJ6WXDLklq6FF47cqtGcTdEUo0S0/edit?usp=sharing
[02:32] <tsimonq2> I'll do the same for xenial_unstable tomorrow
[02:32] <tsimonq2> yofel, clivejo, acheronuk, santa_, valorie ^^
[02:34] <valorie> nice
[02:35] <tsimonq2> I postponed the KCI nightly for three hours so I can work on this.
[02:46] -kubuntu-ci:#kubuntu-devel- Yippee, build fixed!
[02:46] -kubuntu-ci:#kubuntu-devel- Project yakkety_unstable_kidletime build #82: FIXED in 7 min 53 sec: http://kci.pangea.pub/job/yakkety_unstable_kidletime/82/
[02:46] -kubuntu-ci:#kubuntu-devel- Yippee, build fixed!
[02:46] -kubuntu-ci:#kubuntu-devel- Project xenial_unstable_kidletime build #275: FIXED in 8 min 20 sec: http://kci.pangea.pub/job/xenial_unstable_kidletime/275/
[02:49] -kubuntu-ci:#kubuntu-devel- Project xenial_unstable_libkleo build #47: STILL FAILING in 3 min 44 sec: http://kci.pangea.pub/job/xenial_unstable_libkleo/47/
[02:49] -kubuntu-ci:#kubuntu-devel- Project yakkety_unstable_libkleo build #60: STILL FAILING in 3 min 50 sec: http://kci.pangea.pub/job/yakkety_unstable_libkleo/60/
[02:56] -kubuntu-ci:#kubuntu-devel- Yippee, build fixed!
[02:56] -kubuntu-ci:#kubuntu-devel- Project yakkety_unstable_libkdepim build #3: FIXED in 9 min 52 sec: http://kci.pangea.pub/job/yakkety_unstable_libkdepim/3/
[02:56] -kubuntu-ci:#kubuntu-devel- Yippee, build fixed!
[02:56] -kubuntu-ci:#kubuntu-devel- Project xenial_unstable_libkdepim build #3: FIXED in 9 min 46 sec: http://kci.pangea.pub/job/xenial_unstable_libkdepim/3/
[02:58] -kubuntu-ci:#kubuntu-devel- Project yakkety_unstable_libkleo build #61: STILL FAILING in 3 min 49 sec: http://kci.pangea.pub/job/yakkety_unstable_libkleo/61/
[02:58] -kubuntu-ci:#kubuntu-devel- Project xenial_unstable_libkleo build #48: STILL FAILING in 4 min 9 sec: http://kci.pangea.pub/job/xenial_unstable_libkleo/48/
[03:01] -kubuntu-ci:#kubuntu-devel- Project mgmt_progenitor build #678: ABORTED in 27 sec: http://kci.pangea.pub/job/mgmt_progenitor/678/
[03:01] <tsimonq2> that's me
[03:02] -kubuntu-ci:#kubuntu-devel- Project merger_kdeconnect-kde build #93: FAILURE in 55 sec: http://kci.pangea.pub/job/merger_kdeconnect-kde/93/
[03:02] -kubuntu-ci:#kubuntu-devel- Project merger_kcoreaddons build #771: FAILURE in 1 min 0 sec: http://kci.pangea.pub/job/merger_kcoreaddons/771/
[03:02] -kubuntu-ci:#kubuntu-devel- Project merger_kdesdk-thumbnailers build #98: STILL FAILING in 1 min 10 sec: http://kci.pangea.pub/job/merger_kdesdk-thumbnailers/98/
[03:06] -kubuntu-ci:#kubuntu-devel- Project mgmt_merger build #692: STILL UNSTABLE in 5 min 37 sec: http://kci.pangea.pub/job/mgmt_merger/692/
[03:07] -kubuntu-ci:#kubuntu-devel- Yippee, build fixed!
[03:07] -kubuntu-ci:#kubuntu-devel- Project yakkety_unstable_libgravatar build #3: FIXED in 11 min: http://kci.pangea.pub/job/yakkety_unstable_libgravatar/3/
[03:07] -kubuntu-ci:#kubuntu-devel- Yippee, build fixed!
[03:07] -kubuntu-ci:#kubuntu-devel- Project yakkety_unstable_mailimporter build #3: FIXED in 11 min: http://kci.pangea.pub/job/yakkety_unstable_mailimporter/3/
[03:07] -kubuntu-ci:#kubuntu-devel- Yippee, build fixed!
[03:07] -kubuntu-ci:#kubuntu-devel- Project xenial_unstable_mailimporter build #3: FIXED in 10 min: http://kci.pangea.pub/job/xenial_unstable_mailimporter/3/
[03:07] -kubuntu-ci:#kubuntu-devel- Yippee, build fixed!
[03:07] -kubuntu-ci:#kubuntu-devel- Project xenial_unstable_libgravatar build #3: FIXED in 10 min: http://kci.pangea.pub/job/xenial_unstable_libgravatar/3/
[03:13] -kubuntu-ci:#kubuntu-devel- Yippee, build fixed!
[03:13] -kubuntu-ci:#kubuntu-devel- Project yakkety_unstable_libksieve build #3: FIXED in 17 min: http://kci.pangea.pub/job/yakkety_unstable_libksieve/3/
[03:13] -kubuntu-ci:#kubuntu-devel- Yippee, build fixed!
[03:13] -kubuntu-ci:#kubuntu-devel- Project xenial_unstable_libksieve build #3: FIXED in 17 min: http://kci.pangea.pub/job/xenial_unstable_libksieve/3/
[03:15] <tsimonq2> Ok, I'll start the nightly now. I just wanted to work on this, but building marble is taking longer than expected, so I'll just finish tomorrow.
[03:15] <tsimonq2> Good night everyone! o/
[03:17] -kubuntu-ci:#kubuntu-devel- Yippee, build fixed!
[03:17] -kubuntu-ci:#kubuntu-devel- Project merger_kcoreaddons build #772: FIXED in 1 min 13 sec: http://kci.pangea.pub/job/merger_kcoreaddons/772/
[03:18] -kubuntu-ci:#kubuntu-devel- Project merger_kdiamond build #609: FAILURE in 1 min 9 sec: http://kci.pangea.pub/job/merger_kdiamond/609/
[03:18] -kubuntu-ci:#kubuntu-devel- Yippee, build fixed!
[03:18] -kubuntu-ci:#kubuntu-devel- Project merger_kdeconnect-kde build #94: FIXED in 2 min 4 sec: http://kci.pangea.pub/job/merger_kdeconnect-kde/94/
[03:19] -kubuntu-ci:#kubuntu-devel- Project merger_kdesdk-thumbnailers build #99: STILL FAILING in 2 min 21 sec: http://kci.pangea.pub/job/merger_kdesdk-thumbnailers/99/
[03:21] <valorie> niters tsimonq2
[03:22] -kubuntu-ci:#kubuntu-devel- Project mgmt_merger build #693: STILL UNSTABLE in 5 min 26 sec: http://kci.pangea.pub/job/mgmt_merger/693/
[03:22] -kubuntu-ci:#kubuntu-devel- Project mgmt_progenitor build #679: STILL UNSTABLE in 5 min 29 sec: http://kci.pangea.pub/job/mgmt_progenitor/679/
[03:38] -kubuntu-ci:#kubuntu-devel- Project xenial_unstable_kajongg build #71: FAILURE in 15 min: http://kci.pangea.pub/job/xenial_unstable_kajongg/71/
[03:38] -kubuntu-ci:#kubuntu-devel- Project xenial_unstable_kppp build #8: STILL UNSTABLE in 16 min: http://kci.pangea.pub/job/xenial_unstable_kppp/8/
[03:39] -kubuntu-ci:#kubuntu-devel- Project yakkety_unstable_kdesdk-kioslaves build #43: STILL UNSTABLE in 16 min: http://kci.pangea.pub/job/yakkety_unstable_kdesdk-kioslaves/43/
[03:44] -kubuntu-ci:#kubuntu-devel- Project xenial_unstable_kde-runtime build #197: STILL FAILING in 22 min: http://kci.pangea.pub/job/xenial_unstable_kde-runtime/197/
[03:45] -kubuntu-ci:#kubuntu-devel- Project yakkety_unstable_kde-runtime build #203: STILL FAILING in 21 min: http://kci.pangea.pub/job/yakkety_unstable_kde-runtime/203/
[03:46] -kubuntu-ci:#kubuntu-devel- Project yakkety_unstable_kajongg build #66: FAILURE in 23 min: http://kci.pangea.pub/job/yakkety_unstable_kajongg/66/
[03:49] -kubuntu-ci:#kubuntu-devel- Project xenial_unstable_kajongg build #72: STILL FAILING in 6 min 49 sec: http://kci.pangea.pub/job/xenial_unstable_kajongg/72/
[03:50] -kubuntu-ci:#kubuntu-devel- Project xenial_unstable_kcoreaddons build #264: STILL UNSTABLE in 17 min: http://kci.pangea.pub/job/xenial_unstable_kcoreaddons/264/
[03:50] -kubuntu-ci:#kubuntu-devel- Project yakkety_unstable_kppp build #85: STILL UNSTABLE in 27 min: http://kci.pangea.pub/job/yakkety_unstable_kppp/85/
[03:51] -kubuntu-ci:#kubuntu-devel- Project yakkety_unstable_kopete build #62: STILL UNSTABLE in 28 min: http://kci.pangea.pub/job/yakkety_unstable_kopete/62/
[03:51] -kubuntu-ci:#kubuntu-devel- Project xenial_unstable_okular build #18: STILL UNSTABLE in 12 min: http://kci.pangea.pub/job/xenial_unstable_okular/18/
[03:51] -kubuntu-ci:#kubuntu-devel- Project xenial_unstable_kdesdk-kioslaves build #82: STILL UNSTABLE in 28 min: http://kci.pangea.pub/job/xenial_unstable_kdesdk-kioslaves/82/
[04:01] -kubuntu-ci:#kubuntu-devel- Project yakkety_unstable_kajongg build #67: STILL FAILING in 9 min 47 sec: http://kci.pangea.pub/job/yakkety_unstable_kajongg/67/
[04:02] -kubuntu-ci:#kubuntu-devel- Project xenial_unstable_kopete build #85: STILL UNSTABLE in 39 min: http://kci.pangea.pub/job/xenial_unstable_kopete/85/
[04:02] -kubuntu-ci:#kubuntu-devel- Project xenial_unstable_kcrash build #275: STILL UNSTABLE in 12 min: http://kci.pangea.pub/job/xenial_unstable_kcrash/275/
[04:02] -kubuntu-ci:#kubuntu-devel- Project xenial_unstable_kauth build #282: STILL UNSTABLE in 12 min: http://kci.pangea.pub/job/xenial_unstable_kauth/282/
[04:02] -kubuntu-ci:#kubuntu-devel- Project yakkety_unstable_okular build #96: STILL UNSTABLE in 12 min: http://kci.pangea.pub/job/yakkety_unstable_okular/96/
[04:08] -kubuntu-ci:#kubuntu-devel- Project yakkety_unstable_kauth build #154: STILL UNSTABLE in 17 min: http://kci.pangea.pub/job/yakkety_unstable_kauth/154/
[04:08] -kubuntu-ci:#kubuntu-devel- Project xenial_unstable_kde-runtime build #198: STILL FAILING in 18 min: http://kci.pangea.pub/job/xenial_unstable_kde-runtime/198/
[04:08] -kubuntu-ci:#kubuntu-devel- Project yakkety_unstable_kdevelop-pg-qt build #19: STILL UNSTABLE in 17 min: http://kci.pangea.pub/job/yakkety_unstable_kdevelop-pg-qt/19/
[04:08] -kubuntu-ci:#kubuntu-devel- Project yakkety_unstable_kde-runtime build #204: STILL FAILING in 18 min: http://kci.pangea.pub/job/yakkety_unstable_kde-runtime/204/
[04:17] -kubuntu-ci:#kubuntu-devel- Project yakkety_unstable_kcrash build #151: STILL UNSTABLE in 9 min 17 sec: http://kci.pangea.pub/job/yakkety_unstable_kcrash/151/
[04:40] -kubuntu-ci:#kubuntu-devel- Project xenial_unstable_kwallet build #289: STILL UNSTABLE in 11 min: http://kci.pangea.pub/job/xenial_unstable_kwallet/289/
[05:01] -kubuntu-ci:#kubuntu-devel- Project yakkety_unstable_kwallet build #128: STILL UNSTABLE in 21 min: http://kci.pangea.pub/job/yakkety_unstable_kwallet/128/
[05:39] -kubuntu-ci:#kubuntu-devel- Project xenial_unstable_minuet build #21: STILL FAILING in 7 min 41 sec: http://kci.pangea.pub/job/xenial_unstable_minuet/21/
[05:53] -kubuntu-ci:#kubuntu-devel- Project xenial_unstable_minuet build #22: STILL FAILING in 8 min 56 sec: http://kci.pangea.pub/job/xenial_unstable_minuet/22/
[06:00] -kubuntu-ci:#kubuntu-devel- Project xenial_unstable_spectacle build #106: STILL UNSTABLE in 13 min: http://kci.pangea.pub/job/xenial_unstable_spectacle/106/
[06:13] -kubuntu-ci:#kubuntu-devel- Project xenial_unstable_kdenlive build #286: STILL FAILING in 30 min: http://kci.pangea.pub/job/xenial_unstable_kdenlive/286/
[06:19] -kubuntu-ci:#kubuntu-devel- Project xenial_unstable_plasma-framework build #278: STILL FAILING in 5 min 55 sec: http://kci.pangea.pub/job/xenial_unstable_plasma-framework/278/
[06:21] -kubuntu-ci:#kubuntu-devel- Project yakkety_unstable_kdenlive build #135: STILL FAILING in 21 min: http://kci.pangea.pub/job/yakkety_unstable_kdenlive/135/
[06:22] -kubuntu-ci:#kubuntu-devel- Project xenial_unstable_umbrello build #92: STILL UNSTABLE in 15 min: http://kci.pangea.pub/job/xenial_unstable_umbrello/92/
[06:22] -kubuntu-ci:#kubuntu-devel- Project yakkety_unstable_spectacle build #85: STILL UNSTABLE in 13 min: http://kci.pangea.pub/job/yakkety_unstable_spectacle/85/
[06:29] -kubuntu-ci:#kubuntu-devel- Project xenial_unstable_plasma-framework build #279: STILL FAILING in 5 min 0 sec: http://kci.pangea.pub/job/xenial_unstable_plasma-framework/279/
[06:29] -kubuntu-ci:#kubuntu-devel- Project xenial_unstable_kstars build #257: STILL UNSTABLE in 22 min: http://kci.pangea.pub/job/xenial_unstable_kstars/257/
[06:29] -kubuntu-ci:#kubuntu-devel- Project xenial_unstable_ktp-common-internals build #208: STILL UNSTABLE in 17 min: http://kci.pangea.pub/job/xenial_unstable_ktp-common-internals/208/
[06:29] -kubuntu-ci:#kubuntu-devel- Project xenial_unstable_okteta build #114: STILL UNSTABLE in 29 min: http://kci.pangea.pub/job/xenial_unstable_okteta/114/
[06:37] -kubuntu-ci:#kubuntu-devel- Project xenial_unstable_kdenlive build #287: STILL FAILING in 19 min: http://kci.pangea.pub/job/xenial_unstable_kdenlive/287/
[06:39] -kubuntu-ci:#kubuntu-devel- Project yakkety_unstable_kdenlive build #136: STILL FAILING in 13 min: http://kci.pangea.pub/job/yakkety_unstable_kdenlive/136/
[06:41] -kubuntu-ci:#kubuntu-devel- Project yakkety_unstable_kstars build #125: STILL UNSTABLE in 18 min: http://kci.pangea.pub/job/yakkety_unstable_kstars/125/
[06:41] -kubuntu-ci:#kubuntu-devel- Project xenial_unstable_kirigami build #34: STILL UNSTABLE in 12 min: http://kci.pangea.pub/job/xenial_unstable_kirigami/34/
[06:42] -kubuntu-ci:#kubuntu-devel- Project xenial_unstable_libkcompactdisc build #48: STILL UNSTABLE in 12 min: http://kci.pangea.pub/job/xenial_unstable_libkcompactdisc/48/
[06:44] -kubuntu-ci:#kubuntu-devel- Project yakkety_unstable_audiocd-kio build #52: STILL FAILING in 14 min: http://kci.pangea.pub/job/yakkety_unstable_audiocd-kio/52/
[06:46] -kubuntu-ci:#kubuntu-devel- Project yakkety_unstable_plasma-framework build #142: STILL FAILING in 11 min: http://kci.pangea.pub/job/yakkety_unstable_plasma-framework/142/
[06:48] -kubuntu-ci:#kubuntu-devel- Project xenial_unstable_ktp-auth-handler build #182: STILL UNSTABLE in 18 min: http://kci.pangea.pub/job/xenial_unstable_ktp-auth-handler/182/
[06:48] -kubuntu-ci:#kubuntu-devel- Project yakkety_unstable_umbrello build #77: STILL UNSTABLE in 26 min: http://kci.pangea.pub/job/yakkety_unstable_umbrello/77/
[06:52] -kubuntu-ci:#kubuntu-devel- Project xenial_unstable_audiocd-kio build #50: STILL FAILING in 9 min 58 sec: http://kci.pangea.pub/job/xenial_unstable_audiocd-kio/50/
[06:57] -kubuntu-ci:#kubuntu-devel- Project yakkety_unstable_ktp-common-internals build #134: STILL UNSTABLE in 22 min: http://kci.pangea.pub/job/yakkety_unstable_ktp-common-internals/134/
[06:58] -kubuntu-ci:#kubuntu-devel- Project yakkety_unstable_audiocd-kio build #53: STILL FAILING in 8 min 51 sec: http://kci.pangea.pub/job/yakkety_unstable_audiocd-kio/53/
[06:59] -kubuntu-ci:#kubuntu-devel- Project xenial_unstable_plasma-sdk build #227: STILL UNSTABLE in 17 min: http://kci.pangea.pub/job/xenial_unstable_plasma-sdk/227/
[07:02] -kubuntu-ci:#kubuntu-devel- Project xenial_unstable_audiocd-kio build #51: STILL FAILING in 4 min 56 sec: http://kci.pangea.pub/job/xenial_unstable_audiocd-kio/51/
[07:02] -kubuntu-ci:#kubuntu-devel- Project yakkety_unstable_plasma-framework build #143: STILL FAILING in 10 min: http://kci.pangea.pub/job/yakkety_unstable_plasma-framework/143/
[07:05] -kubuntu-ci:#kubuntu-devel- Project xenial_unstable_marble build #3: STILL FAILING in 24 min: http://kci.pangea.pub/job/xenial_unstable_marble/3/
[07:12] -kubuntu-ci:#kubuntu-devel- Project xenial_unstable_plasma-integration build #3: UNSTABLE in 14 min: http://kci.pangea.pub/job/xenial_unstable_plasma-integration/3/
[07:12] -kubuntu-ci:#kubuntu-devel- Project yakkety_unstable_ktp-auth-handler build #135: STILL UNSTABLE in 14 min: http://kci.pangea.pub/job/yakkety_unstable_ktp-auth-handler/135/
[07:13] -kubuntu-ci:#kubuntu-devel- Project xenial_unstable_plasma-workspace build #5: STILL FAILING in 52 sec: http://kci.pangea.pub/job/xenial_unstable_plasma-workspace/5/
[07:19] -kubuntu-ci:#kubuntu-devel- Project xenial_unstable_plasma-workspace build #6: STILL FAILING in 49 sec: http://kci.pangea.pub/job/xenial_unstable_plasma-workspace/6/
[07:20] -kubuntu-ci:#kubuntu-devel- Project yakkety_unstable_kirigami build #38: STILL UNSTABLE in 17 min: http://kci.pangea.pub/job/yakkety_unstable_kirigami/38/
[07:20] -kubuntu-ci:#kubuntu-devel- Project xenial_unstable_akonadi-contacts build #39: STILL UNSTABLE in 22 min: http://kci.pangea.pub/job/xenial_unstable_akonadi-contacts/39/
[07:22] -kubuntu-ci:#kubuntu-devel- Project xenial_unstable_marble build #4: STILL FAILING in 11 min: http://kci.pangea.pub/job/xenial_unstable_marble/4/
[07:28] -kubuntu-ci:#kubuntu-devel- Project xenial_unstable_kdepim-runtime build #3: STILL FAILING in 42 sec: http://kci.pangea.pub/job/xenial_unstable_kdepim-runtime/3/
[07:34] -kubuntu-ci:#kubuntu-devel- Project xenial_unstable_kdepim-runtime build #4: STILL FAILING in 41 sec: http://kci.pangea.pub/job/xenial_unstable_kdepim-runtime/4/
[07:35] -kubuntu-ci:#kubuntu-devel- Project yakkety_unstable_plasma-sdk build #121: STILL UNSTABLE in 15 min: http://kci.pangea.pub/job/yakkety_unstable_plasma-sdk/121/
[07:41] -kubuntu-ci:#kubuntu-devel- Project yakkety_unstable_marble build #3: STILL FAILING in 20 min: http://kci.pangea.pub/job/yakkety_unstable_marble/3/
[07:41] -kubuntu-ci:#kubuntu-devel- Project yakkety_unstable_plasma-integration build #3: UNSTABLE in 14 min: http://kci.pangea.pub/job/yakkety_unstable_plasma-integration/3/
[07:42] -kubuntu-ci:#kubuntu-devel- Project yakkety_unstable_akonadi-calendar build #3: STILL UNSTABLE in 13 min: http://kci.pangea.pub/job/yakkety_unstable_akonadi-calendar/3/
[07:42] -kubuntu-ci:#kubuntu-devel- Project yakkety_unstable_plasma-workspace build #5: STILL FAILING in 54 sec: http://kci.pangea.pub/job/yakkety_unstable_plasma-workspace/5/
[07:43] -kubuntu-ci:#kubuntu-devel- Project yakkety_unstable_kdepim-runtime build #3: STILL FAILING in 47 sec: http://kci.pangea.pub/job/yakkety_unstable_kdepim-runtime/3/
[07:48] -kubuntu-ci:#kubuntu-devel- Project yakkety_unstable_discover build #3: STILL UNSTABLE in 13 min: http://kci.pangea.pub/job/yakkety_unstable_discover/3/
[07:48] -kubuntu-ci:#kubuntu-devel- Project yakkety_unstable_plasma-workspace build #6: STILL FAILING in 55 sec: http://kci.pangea.pub/job/yakkety_unstable_plasma-workspace/6/
[07:49] -kubuntu-ci:#kubuntu-devel- Project yakkety_unstable_kdepim-runtime build #4: STILL FAILING in 48 sec: http://kci.pangea.pub/job/yakkety_unstable_kdepim-runtime/4/
[07:53] -kubuntu-ci:#kubuntu-devel- Project xenial_unstable_messagelib build #3: STILL FAILING in 5 min 9 sec: http://kci.pangea.pub/job/xenial_unstable_messagelib/3/
[08:02] -kubuntu-ci:#kubuntu-devel- Project xenial_unstable_messagelib build #4: STILL FAILING in 3 min 52 sec: http://kci.pangea.pub/job/xenial_unstable_messagelib/4/
[08:06] -kubuntu-ci:#kubuntu-devel- Project yakkety_unstable_marble build #4: STILL FAILING in 19 min: http://kci.pangea.pub/job/yakkety_unstable_marble/4/
[08:06] -kubuntu-ci:#kubuntu-devel- Project yakkety_unstable_messagelib build #3: STILL FAILING in 5 min 1 sec: http://kci.pangea.pub/job/yakkety_unstable_messagelib/3/
[08:13] -kubuntu-ci:#kubuntu-devel- Yippee, build fixed!
[08:13] -kubuntu-ci:#kubuntu-devel- Project yakkety_unstable_plasma-desktop build #3: FIXED in 24 min: http://kci.pangea.pub/job/yakkety_unstable_plasma-desktop/3/
[08:16] -kubuntu-ci:#kubuntu-devel- Project yakkety_unstable_messagelib build #4: STILL FAILING in 5 min 28 sec: http://kci.pangea.pub/job/yakkety_unstable_messagelib/4/
[09:17] <yofel> tsimonq2, clivejo: The reason the staging script only works with "dev", is that "forward-merging" is not supported anywhere in the workflow
[09:18] <yofel> IMO - but not really having thought about the work it'll take - we should go and start using 'master' for it's intended purpose again
[09:20] <yofel> i.e. _archive gets repurposed to actually match the archive - would make tag-patching-and-merging for archive fixes unnecessary - and master tracks what's in the PPA for dev
[09:20] <yofel> then you can stage against UNRELEASED no matter what the current release state is
[09:22] <yofel> offhand I can say that the merge targets in the automation tooling would need fixing and the merge cascade in the CI has to be redone
[09:23] <yofel> and one has to figure out how to actually put the code in master, as I'm not sure if force-pushing _archive into master would break anything
[10:40] <soee> ‎[12:40] ‎<‎Riddell‎>‎ ** Plasma 5.9 Kickoff meeting in 20 minutes in #plasma
[10:40] <Riddell> that too
[10:40] <soee> :D
[10:46]  * mamarley just wants to start running 5.8.
[10:50] <soee> :D
 o/
 Ooh I'll hop in there
 Thanks yofel
[11:06] <clivejo> yofel: you still about?
[11:11] <yofel> clivejo: now againi
[11:11] <yofel> -i
[11:12] <clivejo> could you give me a quick riun through how to add jobs to KCI?
[11:12] <clivejo> I dont understand why there are 3 toolings
[11:12] <yofel> let me answer the toolings first
[11:13] <yofel> "tooling" is AFAIK historc, and only exists because the PGP keys are in that folder, everything else can probably be removed
[11:13] <yofel> tooling3 is what the CI expects as the current tooling folder. E.g. git-monitor is used from there
[11:15] <yofel> tooling-pending is what gets deployed into docker by mgmt_docker. That's currently an exact copy of tooling3 because there's no deployment job for the slaves. When the CI was only running on master, mgmt_tooling would take tooling3, run the tests on it, cache the required ruby gems, then put the result into tooling-pending
[11:15] <clivejo> ok, that explains why front end always mentions tooling3
[11:15] <yofel> the mobile CI has a kind of deploy setup that I never looked at yet
[11:16] <yofel> but for now you need to do the git pull and copy by hand on linode and scaleway for tooling changes
[11:16] <clivejo> git pull in tooling3
[11:16] <yofel> that's why they also have a pangea-tooling folder where I did by hand git pulls if I needed to cherry pick something
[11:16] <clivejo> then cp tooling3 => tooling pending?
[11:17] <yofel> yes, that should do the job
[11:17] <yofel> then spawn mgmt_docker
[11:17] <clivejo> do I not have to run a script?
[11:18] <yofel> well, you can run the docker deploy, but mgmt_docker is supposed to do that
[11:18] <yofel> *that* automated part still works
[11:18]  * clivejo remembers Scarlett talking about a script that takes ages
[11:18] <yofel> right, that comes now ;)
[11:18] <yofel> which is how to update the jobs
[11:19] <yofel> tl;dr is: edit the job list in kci.yaml, then run update-projects.rb
[11:19]  * acheronuk is taking notes 
[11:20] <yofel> now to actually run that you need some setup that's explained in the README
[11:21] <yofel> where the user is the important part, as you need a real admin user
[11:21] <clivejo> and everytime I edit kci.yaml I need to do a git pull and copy and do it for the two slaves as well?
[11:22] <yofel> no, kci.yaml is only read by update-projects.rb, you only need to run that. The pull on the slaves is only required for changes to the docker relevant parts of the tooling
[11:31] <BluesKaj_> Hiyas all
[11:39] -kubuntu-ci:#kubuntu-devel- Project xenial_unstable_plasma-framework build #280: STILL FAILING in 2 min 54 sec: http://kci.pangea.pub/job/xenial_unstable_plasma-framework/280/
[11:40] -kubuntu-ci:#kubuntu-devel- Project yakkety_unstable_plasma-framework build #144: STILL FAILING in 4 min 36 sec: http://kci.pangea.pub/job/yakkety_unstable_plasma-framework/144/
[11:43] <clivejo> cp: cannot create regular file 'tooling-pending/tooling3/.git/objects/93/378bb81066312f37ae9b4d70721fc366c7e2b2': Permission denied
[11:43] <clivejo> yofel: but I dont need the git stuff?
[11:43] <clivejo> just a copy
[11:44] <yofel> you don't, I might've copied it anyway. And tooling-pending/tooling3/ sounds wrong
[11:58] -kubuntu-ci:#kubuntu-devel- Project xenial_unstable_plasma-framework build #281: STILL FAILING in 14 min: http://kci.pangea.pub/job/xenial_unstable_plasma-framework/281/
[11:58] -kubuntu-ci:#kubuntu-devel- Project yakkety_unstable_plasma-framework build #145: STILL FAILING in 13 min: http://kci.pangea.pub/job/yakkety_unstable_plasma-framework/145/
[12:18] -kubuntu-ci:#kubuntu-devel- Project yakkety_unstable_plasma-framework build #146: STILL FAILING in 19 min: http://kci.pangea.pub/job/yakkety_unstable_plasma-framework/146/
[12:29] -kubuntu-ci:#kubuntu-devel- Yippee, build fixed!
[12:29] -kubuntu-ci:#kubuntu-devel- Project xenial_unstable_plasma-framework build #282: FIXED in 30 min: http://kci.pangea.pub/job/xenial_unstable_plasma-framework/282/
[12:38] -kubuntu-ci:#kubuntu-devel- Project yakkety_unstable_plasma-framework build #147: STILL FAILING in 14 min: http://kci.pangea.pub/job/yakkety_unstable_plasma-framework/147/
[13:00] <soee> do we still need backports for precise and trusty ?
[13:01] <soee> or leave only Xenial and add Yakkety ?
[13:01] <soee> launchpad.net/~kubuntu-ppa/+archive/ubuntu/backports
[13:29] <soee> BOOM
[13:29] <soee> Mark Shuttleworth announced this morning via his blog that Ubuntu 17.04 is codenamed Zesty Zapus
[13:42] <acheronuk> not sure why, but that seems a slightly disappointing end to the alphabet :/
[13:43] <soee> true -:)
[13:54]  * acheronuk was hoping for 'zombies'
[14:13] <yofel> who cares, it's cute :P
[14:16] <acheronuk> yes, and it's already growing on me :)
[14:18] <clivejo> Zesty like a Lemon?
 WOOOOOOOOOOOOOOOOO
 ZESTY ZAPUS
[14:21] <acheronuk> https://featuredcreature.com/wp-content/uploads/2013/01/Capture20-750x380.jpg
[14:22] <clivejo> thats a zapus?
[14:23] <clivejo> eakkk
[14:23] <clivejo> I swear its whiskers just twitched
[14:24] <acheronuk> need a pic of one sitting on a lemon ;)
[14:26] <clivejo> ask CRogers
 I met up with CRogers for beer last week, he's a bloody nice chap
[14:28] <clivejo> Sick_Rimmit: any word from DO?
[14:36] <clivejo> yofel: what machine is arcona?
[14:36] <yofel> swy-01 on ci
[14:40] <clivejo> why am I seeing an output log
[14:48] <jimarvan> hey peeps
[14:48] <jimarvan> how is everyone?
[14:48] <jimarvan> ZESTY ZAPUS?
[14:48] <jimarvan> what the...
 Hey jimarvan all good here,
[14:49] <yofel> clivejo: what log and where?
[14:50] <yofel> clivejo: and I just set the executor count to 48 on arcona. You'll get oom-kills >50
[14:50] <jimarvan> i would prefer a zero zapper :P
[14:50] <jimarvan> Hey rick :)
[14:50] <clivejo> oh
[14:51] <clivejo> any idea why linode executors are dying?
[14:51] <yofel> no..
[14:52] <acheronuk> 'cannot create a build with number 3 since that (or higher) is already in use among [51]'
[14:52] <acheronuk> ????
[14:52] <clivejo> probably need to clear out the workspace
[14:52] <yofel> wtf indeed o.O
[14:56] <clivejo> see 113 on linode is dead
[14:57] <acheronuk> https://issues.jenkins-ci.org/browse/JENKINS-29049
[14:57] <clivejo> where do I run update-projects.rb
[14:58] <yofel> yeah, with the exception that rik posted, but I know too little about java threads to make sense of the error
[14:58] <acheronuk> a few like that on Google. not sure if that is helpful, or just further confusion
[14:59] <acheronuk> "there is something wrong with the 'nextBuildNumber' file for the job. It needs to be larger than the largest build number."
[14:59] <yofel> I run update-projects.rb on my notebook, all you need it the config file from the README
[14:59] <jimarvan> :/
[14:59] <acheronuk> so there is a borked job somewhere causing that to fail when it tries to run it?
[15:00] <clivejo> are there instructions anywhere, this is confusing
[15:00] <acheronuk> I was able to rectify the problem (i think) by increasing the Next Build Number file, the current build number is 1720 and yet it is trying to build using 256.
[15:00] <acheronuk> For anyone also facing this problem, also restart Jenkins for the change to take effect. If you do not restart the issue will not go away.
[15:01] <acheronuk> since I have no access to KCI in any way, I can only guess at what you do there ^^^
[15:02] <yofel> clivejo: if you're looking for the credentials: go to your user in jenkins > configure > "Show API token"
[15:02] <clivejo> yeah, just clicked
[15:02] <clivejo> this uses the API
[15:03] <clivejo> so Im connecting via the API when I run that script
[15:03] <clivejo> for some reason I thought it was done from within
[15:03] <clivejo> on master
[15:05] <clivejo> eak
[15:05] <clivejo> I already have a pangea-jenkins.json file
[15:06] <yofel> the token is probably invalid though, I also just updated mine
[15:09] -kubuntu-ci:#kubuntu-devel- Project yakkety_unstable_kwin build #3: STILL FAILING in 1 min 22 sec: http://kci.pangea.pub/job/yakkety_unstable_kwin/3/
[15:14] <clivejo> hi blaze
[15:14] <blaze> hi clivejo 
[15:15] -kubuntu-ci:#kubuntu-devel- Project yakkety_unstable_kwin build #4: STILL FAILING in 1 min 17 sec: http://kci.pangea.pub/job/yakkety_unstable_kwin/4/
[15:16] <clivejo> ok in pangea-tooling do you append bunble exec ./update-projects.rb ?
[15:16] <blaze> just found some packaging issue
[15:17] <blaze> here http://packages.ubuntu.com/xenial/plasma-framework-dev
[15:17] <clivejo> grrr
[15:17] <clivejo> my head is fried
[15:17] <blaze> should depend on plasma-framework binary package
[15:17] <blaze> just as in yakkety http://packages.ubuntu.com/yakkety/plasma-framework-dev
[15:21] <yofel> clivejo: append?
[15:21] <yofel> just run it
[15:21] <yofel> with bundle
[15:21] <clivejo> https://git.launchpad.net/~kubuntu-ci-admins/kubuntu-ci/+git/pangea-tooling/tree/README
[15:22] <clivejo> bundler install --path vendor/bundle 
[15:22] <clivejo> fails
[15:22] <yofel> you're running that in pangea-tooling?
[15:22] <clivejo> yes, where should I be running it?
[15:22] <yofel> there... what's the error?
[15:23] <clivejo> /usr/local/bin/bundler:23:in `load': cannot load such file -- /usr/share/rubygems-integration/all/gems/bundler-1.12.5/exe/bundler (LoadError)
[15:23] <clivejo>         from /usr/local/bin/bundler:23:in `<main>'
[15:23] <yofel> o.O
[15:23] <yofel> dunno
[15:24] <yofel> I just used bundler from apt
[15:28] <clivejo> you on xenial?
[15:29] <yofel> yes
[15:30] <clivejo> !info rubygems
[15:30] <clivejo> !info ruby
[15:30] <clivejo> !info ruby xenial
[15:31] <yofel> !info bundler
[15:31] <clivejo> !info bundler xenial
[15:35] <clivejo> I hate ruby
[15:35] <clivejo> burn it!
[15:39] <yofel> sounds like you'll have fun once you get to the rvm part :P
[15:39] <yofel> unless you already did
[15:40] <clivejo> bundler install --path vendor/bundle
[15:40] <clivejo> bash: /usr/local/bin/bundler: /usr/bin/ruby2.2: bad interpreter: No such file or directory
[15:41] <clivejo> yet the system said it installed ruby2.3
[15:41] <clivejo> stupid thing!
[15:41] <yofel> you are still calling bundler from local
[15:41] <yofel> try /usr/bin/bundler explicitly
[15:42] <clivejo> bingo
[15:44] <clivejo> doing something!
[15:45] <acheronuk> can we document this?
[15:46] <yofel> well, I did start a README, feel free to extend it ;)
[15:47] <acheronuk> clivejo: ^^^
[15:48] <acheronuk> as only about 50% of what you have been saying actually makes sense to me at the moment
[15:48] <clivejo> yofel: how much authorisation do I need to give it?
[15:48] <clivejo> to LP
[15:49] <yofel> no idea, public read only should do though
[15:50] <clivejo> done
[15:51] <clivejo> ok that was too fast
[15:51] <clivejo> what did it even do
[15:52] <yofel> it should be cloning all packaging repositories from kci.yaml, check whether they have an unstable branch, then generate jobs for all the valid ones
[15:52] <clivejo> does that generate output?
[15:53] <yofel> yes, a bunch
[15:53] <clivejo> nothing here
[15:54] <clivejo> /usr/bin/bundle exec ./update-projects.rb
[15:54] <yofel> hm, you should see stuff like
[15:54] <yofel> new_project({:branch=>"kubuntu_unstable", :name=>"akonadi", :component=>"launchpadgit", :url_base=>"https://git.launchpad.net/~kubuntu-packagers//"})
[15:54] <yofel> build.rb does not use the branch attr of SCM and has a problem there
[15:54] <yofel> Updating yakkety_unstable_calendarsupport
[15:55] <yofel> etc.
[15:55] <yofel> hm, maybe the LP access isn't enough after all
[15:58] <clivejo> where does the tool store my LP details
[15:58] <clivejo> I revoked it in LP
[15:58] <clivejo> but its not asking me again when I run the script
[16:00] <clivejo> ~/.config/lp-tokens.json?
[16:01] <yofel> grepping through the code that sounds about right
[16:01] <clivejo> yup
[16:01] <clivejo> redone it
[16:02] <clivejo> but it still doesnt actually do anything!
[16:02] <clivejo> this is mental
[16:08]  * soee happy panda :)
[16:08] <soee> "WIP: Restore global menu support"
[16:08] <soee> Kai started working on it for Plasma 5.9 it seems :)
[16:17] <jimarvan> :D
[16:17] <jimarvan> see ya peeps! :)
 Is someone interested with packaging Qupzilla 2.x?
 In some personal report so the users of different distros could use it?
 *personal repo
[16:24] <acheronuk> blaze was trying
[16:25] <blaze> not really :)
[16:25] <acheronuk> I tried locally, and it was flicker city
[16:26] <acheronuk> not usable
[16:26] <blaze> I just added some feature to Qupzilla
[16:27] <blaze> since Qt 5.6.2 released it is usable
[16:27] <blaze> just needs fresh QtWebEngine
[17:31] <tsimonq2> WOOOOOOOAH santa_ santa_ santa_ 
[17:32] <tsimonq2> santa_: I'm gonna push a commit to Marble but the symbols need some SERIOUS work...
[17:33] <tsimonq2> There, pushed
[17:34] <acheronuk> ???? -usr/lib/*/libmarblewidget-qt5.so.25
 I'm sure it's replaced with something, I just know it. But symbols are so bad at the moment that that's the priority.
[17:35] <acheronuk> it needs a soname bump, that is likely why
 That's why I'm pinging Santa, he knows how. :P
[17:43] <acheronuk> ok. It's not that complicated, but good that you are double checking if you are not sure. :)
[17:43]  * clivejo pats Simon on the back
[17:43] <tsimonq2> :)
[17:44] <clivejo> an even number of times
[17:44] <tsimonq2> I'm SO glad they didn't decide to release Plasma in April or October
[17:44] <clivejo> why?
[17:44] <tsimonq2> it sucks shipping outdated Plasma... :/
[17:44] <tsimonq2> If it's close to release, the scramble to get it in isn't worth it sometimes...
[17:45] <acheronuk> oh. 5.9. yes
[17:45] <clivejo> ooo Kdevelop 5.0.2 is out
[17:45] <tsimonq2> :D
[17:45] <acheronuk> yep. just got 5.0.2+git via blazes ppa
[17:46] <clivejo> surprised Ovi One Kinobee hasnt been looking for it
[17:47] <clivejo> blaze do you use our packaging?
[17:47] <tsimonq2> LOL
[17:48] <tsimonq2> Yeah, blaze for Kubuntu Ninja! :P
[17:48] <clivejo> well makes sense to at least submit packaging MR's
[17:49] <acheronuk> Zesty :) https://launchpad.net/ubuntu/+series
[17:49] <tsimonq2> :D :D :D :D :D :D :D 
[17:49]  * tsimonq2 scolds clivejo 
[17:49] <tsimonq2> Don't combine PR and MP!
[17:49] <clivejo> they are merge requests
[17:49] <clivejo> MR
[17:50] <tsimonq2> Nope, Mere
[17:50] <tsimonq2> *Merge Proposals
[17:50] <clivejo> waits for the archive is now open email!
[17:50] <tsimonq2> ^^^^^^^^^
[17:51] <tsimonq2> Then we get All The Things(tm) synced from Sid!
[17:51] <acheronuk> nowt created yet http://archive.ubuntu.com/ubuntu/dists/
[17:51] <clivejo> tsimonq2: whats the ETA on your new KCI tooling based on Python?
[17:51] <tsimonq2> Ok, I'm off early today. Telegram if you want
[17:51] <tsimonq2> o/
[17:52] <acheronuk> ok. I can now to a MR to XX, YY and ZZ. :P
[17:52] <acheronuk> *do
[17:53] -kubuntu-ci:#kubuntu-devel- Project xenial_unstable_marble build #5: STILL FAILING in 19 min: http://kci.pangea.pub/job/xenial_unstable_marble/5/
[17:53] <clivejo> so what Phil was talking about earlier, we should use master for UNRELEASED stuff
[17:53] <clivejo> how would that affect our tooling
[17:55] <blaze> and what's the right branch to commit unreleased changes now?
[17:55] <clivejo> depends for what
[17:55] <blaze> mm, okay
[17:56] <clivejo> we have been staging to deve_archive_branch
[17:57] <clivejo> but for packaging to kdevelop for example if you commited to kubuntu_stable for releases and kubuntu_unstable for KDE git
[17:58] -kubuntu-ci:#kubuntu-devel- Project yakkety_unstable_marble build #5: STILL FAILING in 24 min: http://kci.pangea.pub/job/yakkety_unstable_marble/5/
[17:59] <clivejo> is there a way to force everything in one branch into another?
 git checkout initial
 git checkout -b next
[18:00] <acheronuk> ha! just a tad in need of a soname bump! https://launchpadlibrarian.net/289849099/buildlog_ubuntu-yakkety-amd64.marble_4%3A16.04.3+p16.10+git20161017.1734-0_BUILDING.txt.gz
[18:00] <clivejo> ie make master the same as yakkety_archive
 If initial changes, git merge initial when in next
[18:02] <acheronuk> [10:23] <yofel> and one has to figure out how to actually put the code in master, as I'm not sure if force-pushing _archive into master would break anything
 You guys check out my spreadsheet?
[18:10] <acheronuk> no idea what you mean
 Read logs
 Was early morning for you
[18:14] -kubuntu-ci:#kubuntu-devel- Project xenial_unstable_marble build #6: STILL FAILING in 16 min: http://kci.pangea.pub/job/xenial_unstable_marble/6/
[18:20] -kubuntu-ci:#kubuntu-devel- Project yakkety_unstable_marble build #6: STILL FAILING in 17 min: http://kci.pangea.pub/job/yakkety_unstable_marble/6/
[19:08] <clivejo> cant figure out why this script wont work
[19:09] <clivejo> Haruld sitter??
[19:13] <acheronuk> clivejo: SRU? --> https://bugs.launchpad.net/ubuntu/+source/plasma-discover/+bug/1633692
[19:16] <clivejo> I thought it didnt affect Yakkety
[19:19] <acheronuk> sorry, update for xenial I mean
[19:20] <acheronuk> however you want to term that
[19:23] <clivejo> oh its not in yakkety either
[19:23] <clivejo> https://git.launchpad.net/~kubuntu-packagers/kubuntu-packaging/+git/discover/tree/debian/control?h=kubuntu_yakkety_archive
[19:24] <acheronuk> clivejo: rdepends on yakkety shows that ubuntu-release-upgrader-qt and update-manager-kde depend on nothing but each other, so problem is likely to be there as well
[19:25] <acheronuk> and that control form YY confirms that
[19:27] <clivejo> so what package is plasma-discover supposed to pull in?
[19:29] <acheronuk> as the bugs says, previously muon updated was pulling in ubuntu-release-upgrader-qt. 
[19:29] <acheronuk> have now had 2 or 3 people who have found the GUI upgrade broken, and installing just that package fixes it
[19:32] <clivejo> Rik can you help fill out that SRU templete Ive pasted in the Bug report
[19:33] <acheronuk> ok
[19:33] <clivejo> thanks
[19:47] <clivejo> acheronuk: you got a xenial machine?
[19:48] <acheronuk> a VM
[19:52] <clivejo> uploaded the patched package to my XX PPA - https://launchpad.net/~clivejo/+archive/ubuntu/xenial/+packages
[19:52] <clivejo> and attached a debdiff to the bug report
[19:52] <clivejo> would you try installing it when it builds and publishes
[19:55] <acheronuk> yep, I can roll back my VM to a fairly pristine xenial
[19:55] <clivejo> thanks, if you can add that as a test case
[19:59] <acheronuk> published already!
[20:01] <clivejo> that was quick
[20:02] <acheronuk> LP is playing nice
[20:03] <acheronuk> wish this VM would update as quickly
[20:06] <acheronuk> clivejo: I guess current package in backports ppa needs an update as well, assuming that replaces the xenial archive one
 Hai y'all
 Went to McDonald's during lunch and slammed a few sodas, so I'm not crashing like usual
 So happy happy stuff :D
 I actually have energy to do stuff
[20:11] <clivejo> Im downgraded yakkety to Low and upgraded xenial to critical
 For?
 Oic
[20:12] <clivejo> LP 1633692
 Hai Clive :D
 Cool
[20:14] <acheronuk> you mean to say you have extra energy from caffinated or sugar loaded fizzy drinks?
 YES :D :D :D
 I slammed two large Dr. Peppers
[20:15] <valorie> yikes
 Yeah I was full after that
 But I also had a double cheeseburger and an ice cream cone
[20:16] <acheronuk> clivejo: that package appears to have done the trick
[20:16] <acheronuk> god help us!
[20:16] <clivejo> can you add that as a test case please
[20:16] <clivejo> ??
 XD
[20:16] <clivejo> oh Simon high as a kite
[20:16] <acheronuk> yes ^^
 I'm home within 10 minutes, I'm go on hyperdrive mode :D
 *I'll
[20:20] <acheronuk> clivejo: Ok. done.
[20:45] <clivejo> acheronuk: uploaded a fixed package to landing PPA
[20:45] <clivejo> can you test that too and if its ok, move it into backports
[20:51] <acheronuk> ok. in a bit hopefully
[21:02] <acheronuk> clivejo: ummmm.... updates landing won't work
[21:04] <clivejo> eak
[21:04] <clivejo> what happened there!
[21:05] <clivejo> build deps
[21:05]  * clivejo wonders could he just upload it directly to backports
[21:06] <tsimonq2> mmmHM
[21:06] <tsimonq2> yes siree you can
[21:07] <clivejo> I know I can, but its not how we are supposed to do it!
[21:07] <acheronuk> you could find an empty ppa, add backports as a ppa dependancy on that, and upload there
 I like the name
 I would have liked something with Zombies but still decent
[21:12] <clivejo> Zesty Zombies
[21:12] <acheronuk> Zany Zombie
 Zombies with hats lol
[21:13] <acheronuk> Zoophagous Zombie
[21:14] <tsimonq2> ZEALOUS ZEBU :D :D :D
[21:14] <acheronuk> but we have a jumping mouse
[21:16] <clivejo> LOL
[21:17] <Snowhog> Well, zombies are 'real' animals, so that left them out of the naming pool. To bad. I would have liked something with zombie in the name too.
[21:17] <Snowhog> ^^aren't 'real'
 Neither are unicorns or werewolfs
 ;)
[21:22] <acheronuk> ^^^ :D
[21:34] <valorie> I think zombie would be fun, but unfortunate naming for any software-connected stuff
[21:35] <valorie> we can still call it zombie around halloween
[21:35] <valorie> zz zombie
[21:35] <ahoneybun> well it is halloween time now
[21:36] <valorie> getting there for sure
[21:36] <valorie> leaves on the lawn
[21:36] <valorie> I'm not raking until it stops raining though
[21:40] <clivejo> did I mention I hate ruby?
 Valorie what green flower can you recommend for a low sunlight room to put it on floor and it should be ~ 1.5m height
[21:42] <clivejo> simon who do we have to sub on that bug report to get the fix into xenial?
[21:43] <tsimonq2> clivejo: When you want to get my attention, PING. :P
[21:43] <tsimonq2> clivejo: Link?
[21:43] <clivejo> LP 1633692
[21:46] <tsimonq2> clivejo: Upload it to xenial-proposed.
[21:46] <tsimonq2> clivejo: Or just dput it.
[21:46] <tsimonq2> clivejo: You have access: http://people.canonical.com/~ubuntu-archive/packagesets/xenial/kubuntu
[21:47] <tsimonq2> clivejo: Unless it isn't in the Kubuntu packageset?
[21:47] <tsimonq2> !info plasma-discover
[21:48] <tsimonq2> clivejo: Yep, you can upload to xenial-proposed.
[21:49] <clivejo> dont I have to get approval from someone first?
[21:49] <tsimonq2> Nope.
[21:49] <tsimonq2> According to https://wiki.ubuntu.com/StableReleaseUpdates#Procedure , when you upload it, mark it as In Progress.
[21:49] <tsimonq2> When it gets accepted into proposed, mark it as Fix Committed.
[21:50] <tsimonq2> clivejo: Then, unless you need it in NOW, it goes through a one week aging period,
[21:50] <clivejo> dont I have to get approval from someone first??
[21:50] <tsimonq2> You do not.
[21:50] <acheronuk> "Ask the Ubuntu bug control team to nominate the bug for the appropriate Ubuntu release(s)/series (e. g. the current LTS and latest stable release). You can ask on IRC (Freenode) in #ubuntu-bugs, or by emailing them at the address found on the linked page. "
[21:50] <tsimonq2> According to that page.
[21:50] <clivejo> it needs to go in ASAP
[21:50] <tsimonq2> acheronuk: "Upload the fixed package to release-proposed with the patch in the bug report, a detailed and user-readable changelog, and no other unrelated changes. If you can't upload to the archive yourself, get a sponsor, attach a debdiff to the bug and subscribe ubuntu-sponsors, as usual. There is no need to wait before uploading. After upload, the bug status should be changed to In Progress, onc
[21:50] <tsimonq2> e accepted into release-proposed, the status will be automatically changed to Fix Committed."
[21:51] <clivejo> is preventing people from upgrading to Yakkety Yak
[21:51] <tsimonq2> clivejo: Then upload it, pop into #ubuntu-release, and ask for it to be sped along, is my understading.
[21:51] <tsimonq2> *understanding
[21:52] <tsimonq2> clivejo: Don't worry. As long as the diff follows the proper format, the archive admins have guards in place to make sure you are safe. :)
[21:52] <acheronuk> what I quoted is 4. which comes before your 5.
[21:52] <tsimonq2> (which it does)
[21:56] <clivejo> I posted that to the wrong channel!
[21:56]  * tsimonq2 nods
[21:56] <tsimonq2> :)
[21:56] <tsimonq2> clivejo: Dude, just upload it.
[21:56] <tsimonq2> clivejo: RTFM. ;)
[22:02] <tsimonq2> clivejo: https://lists.ubuntu.com/archives/ubuntu-devel/2010-July/030999.html
[22:03] <clivejo> tsimonq2: can you tell me why most if not all archs are enabled on backports?
[22:04] <tsimonq2> clivejo: I thought we discussed?
[22:05] <clivejo> I brief remember you talking about it
[22:05] <tsimonq2> clivejo: Is that bad?
[22:05] <clivejo> briefly, but I didnt know you had gone ahead and enabled them all!
[22:06] <acheronuk> staging ppas for stuff to do in the archive, maybe. though debatable.
[22:06] <acheronuk> the actual backport ppa? no
[22:06] <tsimonq2> Ay jeez
[22:06] <clivejo> https://launchpad.net/~kubuntu-ppa/+archive/ubuntu/backports/+packages?field.name_filter=discover&field.status_filter=published&field.series_filter=
[22:07] <clivejo> its failing on 3 archs
[22:07] <tsimonq2> clivejo: But it still published
[22:07] <tsimonq2> for i386 and amd64
[22:07] <acheronuk> not as bad as it looks, as the amd64 and i386 will publish and no one will know about the ones that dep waited
[22:07] <tsimonq2> which counts
[22:07] <tsimonq2> yeah
[22:07] <tsimonq2> Should someone disable that then? lol
[22:08] <acheronuk> but it's still not needed in there.
[22:08] <tsimonq2> Ok, disabling.
[22:08]  * tsimonq2 made clivejo jump... :P
[22:08] <acheronuk> stuff in there gets copied over 99% of the time anyway.
[22:09] <tsimonq2> acheronuk: Think about it, if we solved all the dep waits, we could publish backports in all arches. :P
[22:10] <tsimonq2> SPEAKING OF BACKPORTS
[22:10] <tsimonq2> acheronuk: Up to chat about that?
[22:10] <acheronuk> sayign what I think of that idea would be against the CoC
[22:10] <tsimonq2> Oh?
[22:10] <tsimonq2> How so?
[22:12] <ahoneybun> XD
[22:12] <clivejo> if I uploaded a ppa3 that would rebuild with only the two archs?
[22:12] <tsimonq2> clivejo: Correct, but it's not needed, since amd64 and i386 published anyways.
[22:13] <clivejo> yes, but what resources does that waste on LP?
[22:14] <clivejo> if we had hundreds of packages waiting on deps that would never land
[22:14] <tsimonq2> Those are disabled now.
[22:17] <acheronuk> ppa3 would make the ppa look tidy ;)
[22:17] <tsimonq2> acheronuk: What are we doing to upload to backports?
[22:17] <acheronuk> though backport users may think it odd to get another update so soon
[22:18] <tsimonq2> acheronuk: Can we get things in backports-landing now?
[22:19] <tsimonq2> acheronuk: What else do we have to do for that?
[22:20]  * clivejo wishes there was a feature to set reminders on LP
[22:21] <valorie> sheesh KDE stickers are expensive compared to Kubuntu stickers
[22:21] <acheronuk> clivejo: like a calendar?
[22:21] <tsimonq2> clivejo: How about you? What do you have to say for yourself? :P
[22:21] <tsimonq2> clivejo: Backports Landing?
[22:22] <clivejo> acheronuk: like a todo type thing
[22:22] <valorie> evidently unixstickers are in europe, and that's where they sent from, even though they had stickermule make 'em!
[22:22] <clivejo> if you didnt check it off in a certain time it would remind you
[22:22] <acheronuk> would be handy
[22:22] <clivejo> LP does seem faster recently
[22:22]  * acheronuk wants sticker
[22:23]  * tsimonq2 wonders if I'm being ignored
[22:23] <acheronuk> *stickers
[22:23]  * clivejo wants sticker too
[22:23]  * clivejo wants a personalised kubuntu t-shirt
[22:23] <valorie> I wonder if there are any left
[22:23] <valorie> of the tshirts
[22:24] <valorie> I can send you some stickers tsimonq2
[22:24] <ahoneybun> I need a Kubuntu shirt lol
[22:24] <valorie> I can send to clivejo if you'll be in charge of sending them elsewhere in europe
[22:24] <tsimonq2> valorie: Yes, send it with that promised SSD. ;)
[22:24] <valorie> we should make more
[22:24] <valorie> righto, I've not had a chance to take that sucker apart
[22:25] <clivejo> maybe could get a batch for this side of the atlantic
[22:25] <tsimonq2> Does nobody want anything in Backports?
[22:25] <valorie> my shipping is probably cheaper than stickermule
[22:26] <valorie> tsimonq2: I very much want everything that will run in backports
[22:26] <ahoneybun> what I want is someone to stop asking every few hours
[22:26] <ahoneybun> valorie: how fast was the shipping from hellotux?
[22:26] <ahoneybun> thinking of ordering a kubuntu jacket from them
[22:26] <valorie> tsimonq2: I'm pretty sure everyone else wants the same thing
[22:26] <tsimonq2> valorie: FINALLY! Someone that will acknowledge me about getting things in Backports Landing!
[22:26] <tsimonq2> :P
[22:26] <valorie> I've said it quite a few times
[22:26] <acheronuk> valorie: those stickers you had looked great
[22:27] <valorie> but badgering doesn't help
[22:27] <valorie> they are great indeed
[22:27] <valorie> I'll go a photo of the KDE stickers when I get over being grumpy at how expensive they are
[22:27] <clivejo> tsimonq2: find a way of copying yakkety_archive to master, without breaking it
[22:28] <valorie> over 50 cents each with shipping
[22:28] <clivejo> and DO NOT practive on the LP git repos!
[22:29]  * tsimonq2 clones akonadi and does it
[22:29] <tsimonq2> :P
[22:29] <clivejo> yeah, dont pick an easy package or anything!
[22:30] <tsimonq2> clivejo: EASY! http://paste.ubuntu.com/23341141/
[22:31] <clivejo> o_O
[22:31] <tsimonq2> Hah
[22:32] <tsimonq2> clivejo: I'll use kubuntu-automation to clone everything and see if I can do it for all the repos.
[22:32] <clivejo> look at debian/control
[22:32] <clivejo> have we still got LP as VCS?
[22:33] <clivejo> dont push anything to the LP repos until we have a chance to look at it
[22:33] <tsimonq2> Vcs-Browser: https://code.launchpad.net/~kubuntu-packagers/kubuntu-packaging/+git/akonadi
[22:33] <tsimonq2> Vcs-Git: git://git.launchpad.net/~kubuntu-packagers/kubuntu-packaging/+git/akonadi
[22:33] <tsimonq2> Yes siree!
[22:33] <clivejo> just dont think its gonna be that easy!
[22:34] <acheronuk> well, master on that is basically the state of debian master back in Feb 2016
[22:35] <acheronuk> so considering there was a debian merge after that in yakkety_achive, and then just out packaging changes on top, that would be a fairly clean merge back into master I think? 
[22:36] <tsimonq2> mmmHM
[22:38] <acheronuk> might not be quite that simple on others. maybe
[22:38] <tsimonq2> I'll try it. ;)
[22:39] <ahoneybun> soee: Rocket League is $9 on cdkeys.com
 :0
[22:39] <ahoneybun> not sure how much that is in your currency
[22:39] <ahoneybun> I got it and the key worked fine for me
 @marcinsagol http://www.cdkeys.com/pc/games/rocket-league-pc-cd-key?mw_aref=slickdeals&data1=e5df8c3c94b811e6ad5b4627076903cf0INT
[22:40] <acheronuk> The way the £ is sinking, I'm not sure either
 1$=~4zl
 so 36 or so?
 Yes 36zl
 nice still I think
 Not that much ;)
 I'm still waiting for Mad Max
[22:42] <valorie> @marcinsagol do you really want flowers? or just a green plant
 well that's money for you lol
 I have just stalled Warhammer 2 but wasn't impressed
 @Valoriez well some flower
[22:44] <valorie> http://www.bhg.com/gardening/houseplants/projects/indoor-plants-for-low-light/
[22:44] <valorie> I've grown many of those
[22:45] <valorie> oops, sorry about off-topic in here
[22:55] <clivejo> acheronuk: can you test that ppa3 in backports please
[22:56] <tsimonq2> You uploaded a no-change rebuild?!? :| :?
[22:56] <tsimonq2> *:/
[22:56] <clivejo> yes
[22:56] <tsimonq2> Why?!?
[22:56] <tsimonq2> And you still haven't uploaded to xenial! :/
[22:56] <acheronuk> ok
[22:57] <clivejo> I want to know how and where to upload to
[22:58] <tsimonq2> debuild -S
[22:58] <tsimonq2> cd ..
[22:58] <tsimonq2> dput PACKAGE_source.changes
[22:58] <tsimonq2> done
[22:58] <clivejo> dput where?
[22:58] <tsimonq2> clivejo: As long as the release is specified as xenial, then it should be fine.
[22:59] <tsimonq2> You don't need any arguments when running dput if you are uploading to the main archive.
[22:59] <tsimonq2> Just like in this case, no arguments needed.
[22:59] <clivejo> so its dput ubuntu?
[22:59] <tsimonq2> Yes.
[23:01] <acheronuk> clivejo: confirmed fixed with that in backports :)
[23:01] <clivejo> good stuff
[23:02] <clivejo> is that version number right for an SRU?
[23:02] <clivejo> 1.1?
[23:02] <clivejo> my problem is what is devel at the moment
[23:02] <acheronuk> AFAIK
[23:03] <clivejo> zesty archive isnt open, so cant put it there
[23:03] <clivejo> so just assume yakkety id devel and backport to xenial :/
[23:03] <clivejo> Im confused
[23:04] <acheronuk> we are in limbo
[23:05] <clivejo> and my brain is in limbo
[23:05] <clivejo> that ruby tooling make it go to mush
[23:06] <acheronuk> I would imagine YY gets a 2.1 and ZZ gets a ubuntu3 when it opens
[23:06] <clivejo> but they different versions?
[23:07] <clivejo> !info plasma-discover
[23:07] <clivejo> !info plasma-discover xenial
[23:07] <clivejo> and one in backports was 5.6.5
[23:08] <acheronuk> and yakkety = 5.7.5-0ubuntu2
[23:08] <clivejo> so is yakkety 2.1?
[23:08] <clivejo> or 3?
[23:08] <clivejo> grrr I dunno
[23:09] <acheronuk> if technically a SRU, 2.1 I would say
[23:09] <clivejo> open the blooming archive!
[23:09] <valorie> last I heard, they were doing the setup
[23:10] <acheronuk> they've got to twiddle the knobs, open the valves and flick all sorts of switches first....
[23:10] <acheronuk> setup ^^^ yes
[23:10] <clivejo> lies!
[23:10] <clivejo> its a big red button in Marks office
[23:10] <clivejo> and he wont push it!
[23:11] <Snowhog> You 'guys' (deference to Valorie) are hilarious!
[23:11] <valorie> Snowhog: "y'all" works
[23:11] <Snowhog> It's so Southern though.
[23:11] <clivejo> Snowhog: if we didnt have a sense of humour, we ya'll would crack up!
[23:12] <Snowhog> That I understand completely!
[23:12] <valorie> "we y'all" lol
[23:13]  * valorie thinks clivejo is already cracking up!
[23:13] <clivejo> wee y'all
[23:13] <acheronuk> I reckon it's this http://lostpedia.wikia.com/wiki/Pushing_the_button
[23:13] <Snowhog> Should be "all y'all"
[23:13] <valorie> wee'uns
[23:13] <clivejo> aye thats what I meant!
[23:13] <ahoneybun> I think they are all cracked up
[23:13] <clivejo> I blame valorie
[23:13] <clivejo> I was prefectly sane til I met her
[23:14] <valorie> oh so true
[23:14] <valorie> and I take full responsibility
[23:14]  * valorie shares the Jamesons around the channel
[23:14] <valorie> I have to have only clear liquids tomorrow
[23:14] <ahoneybun> better share some of that in Nov lol
[23:14] <valorie> that's clear and liquid, right?
[23:15] <clivejo> I still have Romanian  mineral water left
[23:15] <valorie> and that has nothing to do with cracking up, I presume
[23:15] <Snowhog> Given the dialog I've seen here so far, a CD should be put together that has a "How Kubuntu is maintained and packaged -- The side of things the world doesn't know about"
[23:15] <ahoneybun> you mean paint thiner?
[23:15] <clivejo> no the label says water
[23:16] <ahoneybun> it's redneck water lol
[23:16] <clivejo> its good stuff!!
[23:16] <ahoneybun> it's so bad lol
[23:16] <ahoneybun> I have to be drunk first to drink tha
[23:16] <ahoneybun> *that
[23:16] <clivejo> gut rot at its finest
[23:16] <clivejo> I have brandy balls poteen somewhere
[23:17] <clivejo> or is it the cherry one
[23:17] <clivejo> cant remember
[23:20] <clivejo> anyways night night
[23:21] <clivejo> acheronuk: can you remind me tomorrow to update git with the changes we are making to plasma-discover
[23:22] <acheronuk> clivejo: I'll try to remember
[23:22]  * clivejo LMAO
[23:22] <clivejo> I crack myself up!
[23:23] <clivejo> Simon says!
[23:23] <tsimonq2>  I SAY YOU FIX KCI :P
[23:23] <valorie> sweet dreams, clivejo
[23:23] <tsimonq2> o/ clivejo 
[23:24]  * clivejo says Simon dont break our git repos!
[23:24]  * simon-says breaks git repos
[23:25] <simon-says> :P
[23:25]  * ahoneybun plays GOW4
[23:25] <clivejo> couple of merge fixes on KCI BTW
[23:26] <clivejo> did you see I got counts of the packages in the tabs?!?
[23:26] <clivejo> y'all see that?!?
[23:26] <tsimonq2> clivejo: yes :)
[23:27] <clivejo> tsimonq2: ping
[23:27] <clivejo> did you see?
[23:27] <tsimonq2> yep
[23:27] <tsimonq2> yep
[23:27] <tsimonq2> yep
[23:27] <tsimonq2> yep
[23:27] <tsimonq2> yep
[23:27] <clivejo> ok zzzzz time
[23:27] <clivejo> o/
[23:27] <valorie> niters
[23:48] <tsimonq2> OOH fayncy
[23:48] <tsimonq2> https://calendar.google.com/calendar/embed?src=031gkgqg1hjf8lcmj0em1d2sj8@group.calendar.google.com&ctz=Europe/London&pli=1
[23:50] <acheronuk> plasma 5.9 31st January
[23:51] <valorie> cool
[23:51] <ahoneybun> a point release every week!
[23:52] <acheronuk> hope they have landed Qt 5.7 in the archive by then!
[23:54] <valorie> if so, there would be time to get it into zz zazzle
[23:54]  * valorie goes to chop onions
[23:56] <acheronuk> mirv said Jan-feb for Qt 5.7 I think?
[23:58] <acheronuk> so hope there is not another late or lengthy transition