[00:01] <clivejo> something strange going on
[00:01] <valorie> I can access that URL
[00:01] <wxl> now it's past 00:00 so have fun
[00:01] <valorie> most recent access 2 hours ago by clive
[00:01] <wxl> you can `mtr` the FQDN
[00:05] <wxl> 1604 < foli:#ubuntu-devel> The firewall maintenance is done now, all should be back.
[00:07] -kubuntu-ci:#kubuntu-devel- Yippee, build fixed!
[00:07] -kubuntu-ci:#kubuntu-devel- Project mgmt_merger build #755: FIXED in 7 min 10 sec: http://kci.pangea.pub/job/mgmt_merger/755/
[00:07] -kubuntu-ci:#kubuntu-devel- Yippee, build fixed!
[00:07] -kubuntu-ci:#kubuntu-devel- Project mgmt_progenitor build #739: FIXED in 7 min 13 sec: http://kci.pangea.pub/job/mgmt_progenitor/739/
[00:21] <mamarley> Hah, looks like the build farm is all jammed up again…
[00:24] <clivejo> mamarley: yup :(
[00:24] <clivejo> even uploads
[00:25] <mamarley> Yeah, that was what made me notice.  It took 20 minutes to acknowledge my automatic tvheadend nightly upload.
[00:25] <valorie> good thing they did maintainence!
[00:26] <valorie> wow, I can't spell
[00:41] <clivejo> why does my laptop screen always dim when it locks
[00:42] <valorie> power saving perhaps?
[00:43] <clivejo> Ive told it not to
[00:43] <valorie> gosh, anybody wanna help friti in #kubuntu ?
[00:45]  * mamarley kicks LP
[01:25] <DarinMiller> Hey all   o/
[01:25] <IrcsomeBot> <tsimonq2> Hey o/
[01:27] <IrcsomeBot> <CliffordTheBigRedDoggie> \o
[02:02]  * DarinMiller arrives on-line and everyone goes to sleep (or leaves).
[02:43] <[Relic]> I bet they just go out to the bar
[02:47] <DarinMiller> [Relic]: :)
[03:11] -kubuntu-ci:#kubuntu-devel- Project xenial_unstable_libkcddb build #105: STILL FAILING in 3 hr 2 min: http://kci.pangea.pub/job/xenial_unstable_libkcddb/105/
[03:11] -kubuntu-ci:#kubuntu-devel- Project xenial_unstable_marble build #67: STILL FAILING in 3 hr 3 min: http://kci.pangea.pub/job/xenial_unstable_marble/67/
[03:16] -kubuntu-ci:#kubuntu-devel- Project xenial_unstable_kproperty build #7: STILL UNSTABLE in 3 hr 8 min: http://kci.pangea.pub/job/xenial_unstable_kproperty/7/
[03:16] -kubuntu-ci:#kubuntu-devel- Project xenial_unstable_kdb build #9: STILL UNSTABLE in 3 hr 8 min: http://kci.pangea.pub/job/xenial_unstable_kdb/9/
[03:16] -kubuntu-ci:#kubuntu-devel- Project yakkety_unstable_kproperty build #5: STILL FAILING in 3 hr 8 min: http://kci.pangea.pub/job/yakkety_unstable_kproperty/5/
[03:17] -kubuntu-ci:#kubuntu-devel- Project xenial_unstable_kate build #241: STILL FAILING in 3 hr 9 min: http://kci.pangea.pub/job/xenial_unstable_kate/241/
[03:37] -kubuntu-ci:#kubuntu-devel- Project xenial_unstable_kdiagram build #37: STILL UNSTABLE in 3 hr 29 min: http://kci.pangea.pub/job/xenial_unstable_kdiagram/37/
[03:38] -kubuntu-ci:#kubuntu-devel- Project zesty_unstable_kopete build #36: STILL UNSTABLE in 3 hr 30 min: http://kci.pangea.pub/job/zesty_unstable_kopete/36/
[03:38] -kubuntu-ci:#kubuntu-devel- Project yakkety_unstable_libkipi build #111: STILL UNSTABLE in 3 hr 30 min: http://kci.pangea.pub/job/yakkety_unstable_libkipi/111/
[03:38] -kubuntu-ci:#kubuntu-devel- Project xenial_unstable_trojita build #21: STILL FAILING in 3 hr 30 min: http://kci.pangea.pub/job/xenial_unstable_trojita/21/
[03:38] -kubuntu-ci:#kubuntu-devel- Project zesty_unstable_kproperty build #9: STILL UNSTABLE in 3 hr 30 min: http://kci.pangea.pub/job/zesty_unstable_kproperty/9/
[03:39] -kubuntu-ci:#kubuntu-devel- Project yakkety_unstable_trojita build #16: STILL FAILING in 28 min: http://kci.pangea.pub/job/yakkety_unstable_trojita/16/
[03:41] -kubuntu-ci:#kubuntu-devel- Project yakkety_unstable_libkcddb build #112: STILL FAILING in 25 min: http://kci.pangea.pub/job/yakkety_unstable_libkcddb/112/
[03:54] -kubuntu-ci:#kubuntu-devel- Project yakkety_unstable_oxygen build #48: FAILURE in 16 min: http://kci.pangea.pub/job/yakkety_unstable_oxygen/48/
[03:59] -kubuntu-ci:#kubuntu-devel- Project yakkety_unstable_kfind build #18: STILL UNSTABLE in 42 min: http://kci.pangea.pub/job/yakkety_unstable_kfind/18/
[03:59] -kubuntu-ci:#kubuntu-devel- Project yakkety_unstable_kate build #155: STILL FAILING in 23 min: http://kci.pangea.pub/job/yakkety_unstable_kate/155/
[04:11] -kubuntu-ci:#kubuntu-devel- Project yakkety_unstable_krita build #13: FAILURE in 4 hr 3 min: http://kci.pangea.pub/job/yakkety_unstable_krita/13/
[04:11] -kubuntu-ci:#kubuntu-devel- Project xenial_unstable_krita build #15: FAILURE in 4 hr 3 min: http://kci.pangea.pub/job/xenial_unstable_krita/15/
[04:13] -kubuntu-ci:#kubuntu-devel- Project xenial_unstable_kopete build #135: STILL UNSTABLE in 57 min: http://kci.pangea.pub/job/xenial_unstable_kopete/135/
[04:14] -kubuntu-ci:#kubuntu-devel- Project yakkety_unstable_cantor build #137: STILL UNSTABLE in 36 min: http://kci.pangea.pub/job/yakkety_unstable_cantor/137/
[04:21] -kubuntu-ci:#kubuntu-devel- Project zesty_unstable_ktp-auth-handler build #38: STILL UNSTABLE in 21 min: http://kci.pangea.pub/job/zesty_unstable_ktp-auth-handler/38/
[04:21] -kubuntu-ci:#kubuntu-devel- Project yakkety_unstable_kstars build #184: STILL UNSTABLE in 44 min: http://kci.pangea.pub/job/yakkety_unstable_kstars/184/
[04:30] -kubuntu-ci:#kubuntu-devel- Project xenial_unstable_kirigami build #77: STILL FAILING in 16 min: http://kci.pangea.pub/job/xenial_unstable_kirigami/77/
[04:33] -kubuntu-ci:#kubuntu-devel- Project xenial_unstable_oxygen build #43: FAILURE in 19 min: http://kci.pangea.pub/job/xenial_unstable_oxygen/43/
[04:34] -kubuntu-ci:#kubuntu-devel- Project zesty_unstable_kirigami build #26: STILL FAILING in 15 min: http://kci.pangea.pub/job/zesty_unstable_kirigami/26/
[04:39] -kubuntu-ci:#kubuntu-devel- Project zesty_unstable_marble build #52: STILL FAILING in 25 min: http://kci.pangea.pub/job/zesty_unstable_marble/52/
[04:41] -kubuntu-ci:#kubuntu-devel- Project xenial_unstable_print-manager build #217: STILL UNSTABLE in 27 min: http://kci.pangea.pub/job/xenial_unstable_print-manager/217/
[04:41] -kubuntu-ci:#kubuntu-devel- Project zesty_unstable_oxygen build #40: FAILURE in 24 min: http://kci.pangea.pub/job/zesty_unstable_oxygen/40/
[04:42] -kubuntu-ci:#kubuntu-devel- Project xenial_unstable_libkcddb build #106: STILL FAILING in 19 min: http://kci.pangea.pub/job/xenial_unstable_libkcddb/106/
[04:43] -kubuntu-ci:#kubuntu-devel- Project zesty_unstable_kate build #38: FAILURE in 24 min: http://kci.pangea.pub/job/zesty_unstable_kate/38/
[04:44] -kubuntu-ci:#kubuntu-devel- Project xenial_unstable_marble build #68: STILL FAILING in 22 min: http://kci.pangea.pub/job/xenial_unstable_marble/68/
[04:44] -kubuntu-ci:#kubuntu-devel- Project yakkety_unstable_marble build #75: STILL FAILING in 22 min: http://kci.pangea.pub/job/yakkety_unstable_marble/75/
[04:45] -kubuntu-ci:#kubuntu-devel- Project yakkety_unstable_kirigami build #84: STILL FAILING in 23 min: http://kci.pangea.pub/job/yakkety_unstable_kirigami/84/
[04:46] -kubuntu-ci:#kubuntu-devel- Project zesty_unstable_konqueror build #33: STILL UNSTABLE in 32 min: http://kci.pangea.pub/job/zesty_unstable_konqueror/33/
[04:46] -kubuntu-ci:#kubuntu-devel- Project zesty_unstable_trojita build #20: STILL UNSTABLE in 32 min: http://kci.pangea.pub/job/zesty_unstable_trojita/20/
[04:50] -kubuntu-ci:#kubuntu-devel- Project xenial_unstable_kate build #242: STILL FAILING in 26 min: http://kci.pangea.pub/job/xenial_unstable_kate/242/
[04:53] -kubuntu-ci:#kubuntu-devel- Project xenial_unstable_kreport build #9: STILL UNSTABLE in 31 min: http://kci.pangea.pub/job/xenial_unstable_kreport/9/
[04:53] -kubuntu-ci:#kubuntu-devel- Project yakkety_unstable_kproperty build #6: STILL FAILING in 30 min: http://kci.pangea.pub/job/yakkety_unstable_kproperty/6/
[04:53] -kubuntu-ci:#kubuntu-devel- Project xenial_unstable_kfind build #6: STILL UNSTABLE in 14 min: http://kci.pangea.pub/job/xenial_unstable_kfind/6/
[04:53] -kubuntu-ci:#kubuntu-devel- Project zesty_unstable_kalzium build #38: STILL UNSTABLE in 31 min: http://kci.pangea.pub/job/zesty_unstable_kalzium/38/
[04:53] -kubuntu-ci:#kubuntu-devel- Project xenial_unstable_umbrello build #157: STILL UNSTABLE in 39 min: http://kci.pangea.pub/job/xenial_unstable_umbrello/157/
[04:55] -kubuntu-ci:#kubuntu-devel- Project yakkety_unstable_trojita build #17: STILL FAILING in 12 min: http://kci.pangea.pub/job/yakkety_unstable_trojita/17/
[05:00] -kubuntu-ci:#kubuntu-devel- Project zesty_unstable_cantor build #41: STILL UNSTABLE in 45 min: http://kci.pangea.pub/job/zesty_unstable_cantor/41/
[05:00] -kubuntu-ci:#kubuntu-devel- Project yakkety_unstable_oxygen build #49: STILL FAILING in 14 min: http://kci.pangea.pub/job/yakkety_unstable_oxygen/49/
[05:00] -kubuntu-ci:#kubuntu-devel- Project yakkety_unstable_kalzium build #75: STILL UNSTABLE in 21 min: http://kci.pangea.pub/job/yakkety_unstable_kalzium/75/
[05:00] -kubuntu-ci:#kubuntu-devel- Project zesty_unstable_kfind build #24: STILL UNSTABLE in 26 min: http://kci.pangea.pub/job/zesty_unstable_kfind/24/
[05:01] -kubuntu-ci:#kubuntu-devel- Project yakkety_unstable_libkcddb build #113: STILL FAILING in 16 min: http://kci.pangea.pub/job/yakkety_unstable_libkcddb/113/
[05:04] -kubuntu-ci:#kubuntu-devel- Project yakkety_unstable_kate build #156: STILL FAILING in 18 min: http://kci.pangea.pub/job/yakkety_unstable_kate/156/
[05:07] -kubuntu-ci:#kubuntu-devel- Project zesty_unstable_marble build #53: STILL FAILING in 13 min: http://kci.pangea.pub/job/zesty_unstable_marble/53/
[05:07] -kubuntu-ci:#kubuntu-devel- Project xenial_unstable_oxygen build #44: STILL FAILING in 14 min: http://kci.pangea.pub/job/xenial_unstable_oxygen/44/
[05:08] -kubuntu-ci:#kubuntu-devel- Project xenial_unstable_kirigami build #78: STILL FAILING in 14 min: http://kci.pangea.pub/job/xenial_unstable_kirigami/78/
[05:08] -kubuntu-ci:#kubuntu-devel- Project yakkety_unstable_kirigami build #85: STILL FAILING in 8 min 20 sec: http://kci.pangea.pub/job/yakkety_unstable_kirigami/85/
[05:08] -kubuntu-ci:#kubuntu-devel- Project zesty_unstable_oxygen build #41: STILL FAILING in 14 min: http://kci.pangea.pub/job/zesty_unstable_oxygen/41/
[05:09] -kubuntu-ci:#kubuntu-devel- Project xenial_unstable_kstars build #317: STILL UNSTABLE in 55 min: http://kci.pangea.pub/job/xenial_unstable_kstars/317/
[05:09] -kubuntu-ci:#kubuntu-devel- Project yakkety_unstable_ktp-auth-handler build #184: STILL UNSTABLE in 22 min: http://kci.pangea.pub/job/yakkety_unstable_ktp-auth-handler/184/
[05:09] -kubuntu-ci:#kubuntu-devel- Project yakkety_unstable_konqueror build #23: STILL UNSTABLE in 30 min: http://kci.pangea.pub/job/yakkety_unstable_konqueror/23/
[05:09] -kubuntu-ci:#kubuntu-devel- Project xenial_unstable_cantor build #243: STILL UNSTABLE in 27 min: http://kci.pangea.pub/job/xenial_unstable_cantor/243/
[05:09] -kubuntu-ci:#kubuntu-devel- Project zesty_unstable_kirigami build #27: STILL FAILING in 15 min: http://kci.pangea.pub/job/zesty_unstable_kirigami/27/
[05:09] -kubuntu-ci:#kubuntu-devel- Project xenial_unstable_kalzium build #132: STILL UNSTABLE in 30 min: http://kci.pangea.pub/job/xenial_unstable_kalzium/132/
[05:12] -kubuntu-ci:#kubuntu-devel- Project zesty_unstable_kdeplasma-addons build #52: STILL FAILING in 11 min: http://kci.pangea.pub/job/zesty_unstable_kdeplasma-addons/52/
[05:14] -kubuntu-ci:#kubuntu-devel- Project zesty_unstable_kate build #39: STILL FAILING in 18 min: http://kci.pangea.pub/job/zesty_unstable_kate/39/
[05:14] -kubuntu-ci:#kubuntu-devel- Project yakkety_unstable_discover build #71: FAILURE in 6 min 1 sec: http://kci.pangea.pub/job/yakkety_unstable_discover/71/
[05:15] -kubuntu-ci:#kubuntu-devel- Project yakkety_unstable_marble build #76: STILL FAILING in 14 min: http://kci.pangea.pub/job/yakkety_unstable_marble/76/
[05:15] -kubuntu-ci:#kubuntu-devel- Project xenial_unstable_discover build #87: FAILURE in 6 min 59 sec: http://kci.pangea.pub/job/xenial_unstable_discover/87/
[05:17] -kubuntu-ci:#kubuntu-devel- Project xenial_unstable_ktp-auth-handler build #232: STILL UNSTABLE in 23 min: http://kci.pangea.pub/job/xenial_unstable_ktp-auth-handler/232/
[05:17] -kubuntu-ci:#kubuntu-devel- Project xenial_unstable_konqueror build #33: STILL UNSTABLE in 38 min: http://kci.pangea.pub/job/xenial_unstable_konqueror/33/
[05:17] -kubuntu-ci:#kubuntu-devel- Project zesty_unstable_discover build #69: FAILURE in 8 min 13 sec: http://kci.pangea.pub/job/zesty_unstable_discover/69/
[05:18] -kubuntu-ci:#kubuntu-devel- Project zesty_unstable_kstars build #45: STILL UNSTABLE in 1 hr 4 min: http://kci.pangea.pub/job/zesty_unstable_kstars/45/
[05:28] -kubuntu-ci:#kubuntu-devel- Project xenial_unstable_kexi build #17: STILL UNSTABLE in 28 min: http://kci.pangea.pub/job/xenial_unstable_kexi/17/
[05:28] -kubuntu-ci:#kubuntu-devel- Project xenial_unstable_trojita build #22: STILL FAILING in 46 min: http://kci.pangea.pub/job/xenial_unstable_trojita/22/
[05:31] -kubuntu-ci:#kubuntu-devel- Project zesty_unstable_kdeplasma-addons build #53: STILL FAILING in 13 min: http://kci.pangea.pub/job/zesty_unstable_kdeplasma-addons/53/
[05:39] -kubuntu-ci:#kubuntu-devel- Project xenial_unstable_discover build #88: STILL FAILING in 18 min: http://kci.pangea.pub/job/xenial_unstable_discover/88/
[05:40] -kubuntu-ci:#kubuntu-devel- Project yakkety_unstable_kexi build #18: STILL UNSTABLE in 25 min: http://kci.pangea.pub/job/yakkety_unstable_kexi/18/
[05:40] -kubuntu-ci:#kubuntu-devel- Project yakkety_unstable_discover build #72: STILL FAILING in 20 min: http://kci.pangea.pub/job/yakkety_unstable_discover/72/
[05:41] -kubuntu-ci:#kubuntu-devel- Project zesty_unstable_discover build #70: STILL FAILING in 19 min: http://kci.pangea.pub/job/zesty_unstable_discover/70/
[05:51] -kubuntu-ci:#kubuntu-devel- Project zesty_unstable_ktp-common-internals build #37: STILL UNSTABLE in 33 min: http://kci.pangea.pub/job/zesty_unstable_ktp-common-internals/37/
[05:54] -kubuntu-ci:#kubuntu-devel- Project yakkety_unstable_kwin build #86: STILL FAILING in 53 min: http://kci.pangea.pub/job/yakkety_unstable_kwin/86/
[06:02] -kubuntu-ci:#kubuntu-devel- Project xenial_unstable_ktp-common-internals build #245: STILL UNSTABLE in 33 min: http://kci.pangea.pub/job/xenial_unstable_ktp-common-internals/245/
[06:05] -kubuntu-ci:#kubuntu-devel- Project yakkety_unstable_kdepim-addons build #62: STILL FAILING in 4 min 12 sec: http://kci.pangea.pub/job/yakkety_unstable_kdepim-addons/62/
[06:06] -kubuntu-ci:#kubuntu-devel- Project yakkety_unstable_pim-sieve-editor build #28: STILL FAILING in 5 min 11 sec: http://kci.pangea.pub/job/yakkety_unstable_pim-sieve-editor/28/
[06:11] -kubuntu-ci:#kubuntu-devel- Project yakkety_unstable_krita build #14: NOW UNSTABLE in 1 hr 18 min: http://kci.pangea.pub/job/yakkety_unstable_krita/14/
[06:13] -kubuntu-ci:#kubuntu-devel- Project xenial_unstable_kdepim-addons build #132: STILL FAILING in 2 min 41 sec: http://kci.pangea.pub/job/xenial_unstable_kdepim-addons/132/
[06:15] -kubuntu-ci:#kubuntu-devel- Project yakkety_unstable_kdepim-addons build #63: STILL FAILING in 4 min 11 sec: http://kci.pangea.pub/job/yakkety_unstable_kdepim-addons/63/
[06:16] -kubuntu-ci:#kubuntu-devel- Project yakkety_unstable_pim-sieve-editor build #29: STILL FAILING in 4 min 41 sec: http://kci.pangea.pub/job/yakkety_unstable_pim-sieve-editor/29/
[06:22] -kubuntu-ci:#kubuntu-devel- Project xenial_unstable_kdepim-addons build #133: STILL FAILING in 3 min 34 sec: http://kci.pangea.pub/job/xenial_unstable_kdepim-addons/133/
[06:27] -kubuntu-ci:#kubuntu-devel- Project zesty_unstable_kdepim-addons build #51: STILL FAILING in 3 min 54 sec: http://kci.pangea.pub/job/zesty_unstable_kdepim-addons/51/
[06:35] -kubuntu-ci:#kubuntu-devel- Project xenial_unstable_krita build #16: NOW UNSTABLE in 1 hr 41 min: http://kci.pangea.pub/job/xenial_unstable_krita/16/
[06:35] -kubuntu-ci:#kubuntu-devel- Project zesty_unstable_kdepim-addons build #52: STILL FAILING in 2 min 42 sec: http://kci.pangea.pub/job/zesty_unstable_kdepim-addons/52/
[06:35] -kubuntu-ci:#kubuntu-devel- Project xenial_unstable_kdeplasma-addons build #55: STILL FAILING in 12 min: http://kci.pangea.pub/job/xenial_unstable_kdeplasma-addons/55/
[06:42] -kubuntu-ci:#kubuntu-devel- Project zesty_unstable_korganizer build #37: STILL UNSTABLE in 19 min: http://kci.pangea.pub/job/zesty_unstable_korganizer/37/
[06:45] -kubuntu-ci:#kubuntu-devel- Project yakkety_unstable_kwin build #87: STILL FAILING in 45 min: http://kci.pangea.pub/job/yakkety_unstable_kwin/87/
[06:48] -kubuntu-ci:#kubuntu-devel- Project xenial_unstable_kdeplasma-addons build #56: STILL FAILING in 8 min 10 sec: http://kci.pangea.pub/job/xenial_unstable_kdeplasma-addons/56/
[06:50] -kubuntu-ci:#kubuntu-devel- Project yakkety_unstable_kdeplasma-addons build #62: STILL FAILING in 5 min 44 sec: http://kci.pangea.pub/job/yakkety_unstable_kdeplasma-addons/62/
[06:56] -kubuntu-ci:#kubuntu-devel- Project xenial_unstable_pim-sieve-editor build #35: STILL FAILING in 5 min 40 sec: http://kci.pangea.pub/job/xenial_unstable_pim-sieve-editor/35/
[07:03] -kubuntu-ci:#kubuntu-devel- Project yakkety_unstable_kdeplasma-addons build #63: STILL FAILING in 7 min 43 sec: http://kci.pangea.pub/job/yakkety_unstable_kdeplasma-addons/63/
[07:06] -kubuntu-ci:#kubuntu-devel- Project xenial_unstable_pim-sieve-editor build #36: STILL FAILING in 4 min 39 sec: http://kci.pangea.pub/job/xenial_unstable_pim-sieve-editor/36/
[07:15] -kubuntu-ci:#kubuntu-devel- Project yakkety_unstable_messagelib build #91: STILL FAILING in 33 min: http://kci.pangea.pub/job/yakkety_unstable_messagelib/91/
[07:15] -kubuntu-ci:#kubuntu-devel- Project zesty_unstable_calligra build #33: STILL FAILING in 1 hr 34 min: http://kci.pangea.pub/job/zesty_unstable_calligra/33/
[07:21] -kubuntu-ci:#kubuntu-devel- Project yakkety_unstable_calligra build #35: STILL FAILING in 1 hr 20 min: http://kci.pangea.pub/job/yakkety_unstable_calligra/35/
[07:48] -kubuntu-ci:#kubuntu-devel- Project yakkety_unstable_messagelib build #92: STILL FAILING in 28 min: http://kci.pangea.pub/job/yakkety_unstable_messagelib/92/
[07:48] -kubuntu-ci:#kubuntu-devel- Project xenial_unstable_calligra build #33: STILL FAILING in 1 hr 25 min: http://kci.pangea.pub/job/xenial_unstable_calligra/33/
[07:49] -kubuntu-ci:#kubuntu-devel- Starting build #6 for job iso_xenial_unstable_amd64 (previous build: STILL FAILING)
[07:50] -kubuntu-ci:#kubuntu-devel- Project iso_xenial_unstable_amd64 build #6: STILL FAILING in 1 min 51 sec: http://kci.pangea.pub/job/iso_xenial_unstable_amd64/6/
[07:52] -kubuntu-ci:#kubuntu-devel- Starting build #7 for job iso_xenial_unstable_amd64 (previous build: STILL FAILING)
[07:53] -kubuntu-ci:#kubuntu-devel- Project iso_xenial_unstable_amd64 build #7: STILL FAILING in 1 min 46 sec: http://kci.pangea.pub/job/iso_xenial_unstable_amd64/7/
[08:27] -kubuntu-ci:#kubuntu-devel- Project zesty_unstable_calligra build #34: STILL FAILING in 1 hr 7 min: http://kci.pangea.pub/job/zesty_unstable_calligra/34/
[08:32] -kubuntu-ci:#kubuntu-devel- Starting build #8 for job iso_xenial_unstable_amd64 (previous build: STILL FAILING)
[08:42] -kubuntu-ci:#kubuntu-devel- Project zesty_unstable_kitemmodels build #52: STILL UNSTABLE in 14 min: http://kci.pangea.pub/job/zesty_unstable_kitemmodels/52/
[08:44] -kubuntu-ci:#kubuntu-devel- Project iso_xenial_unstable_amd64 build #8: STILL FAILING in 12 min: http://kci.pangea.pub/job/iso_xenial_unstable_amd64/8/
[08:50] -kubuntu-ci:#kubuntu-devel- Project yakkety_unstable_calligra build #36: STILL FAILING in 1 hr 23 min: http://kci.pangea.pub/job/yakkety_unstable_calligra/36/
[08:51] -kubuntu-ci:#kubuntu-devel- Yippee, build fixed!
[08:51] -kubuntu-ci:#kubuntu-devel- Project xenial_unstable_kate build #243: FIXED in 12 min: http://kci.pangea.pub/job/xenial_unstable_kate/243/
[08:53] -kubuntu-ci:#kubuntu-devel- Yippee, build fixed!
[08:53] -kubuntu-ci:#kubuntu-devel- Project xenial_unstable_discover build #89: FIXED in 11 min: http://kci.pangea.pub/job/xenial_unstable_discover/89/
[08:54] -kubuntu-ci:#kubuntu-devel- Yippee, build fixed!
[08:54] -kubuntu-ci:#kubuntu-devel- Project yakkety_unstable_discover build #73: FIXED in 12 min: http://kci.pangea.pub/job/yakkety_unstable_discover/73/
[08:58] -kubuntu-ci:#kubuntu-devel- Yippee, build fixed!
[08:58] -kubuntu-ci:#kubuntu-devel- Project yakkety_unstable_oxygen build #50: FIXED in 11 min: http://kci.pangea.pub/job/yakkety_unstable_oxygen/50/
[08:58] -kubuntu-ci:#kubuntu-devel- Yippee, build fixed!
[08:58] -kubuntu-ci:#kubuntu-devel- Project yakkety_unstable_kate build #157: FIXED in 19 min: http://kci.pangea.pub/job/yakkety_unstable_kate/157/
[09:05] -kubuntu-ci:#kubuntu-devel- Yippee, build fixed!
[09:05] -kubuntu-ci:#kubuntu-devel- Project xenial_unstable_oxygen build #45: FIXED in 17 min: http://kci.pangea.pub/job/xenial_unstable_oxygen/45/
[09:05] -kubuntu-ci:#kubuntu-devel- Project xenial_unstable_calligra build #34: STILL FAILING in 1 hr 11 min: http://kci.pangea.pub/job/xenial_unstable_calligra/34/
[09:06] -kubuntu-ci:#kubuntu-devel- Starting build #9 for job iso_xenial_unstable_amd64 (previous build: STILL FAILING)
[09:19] -kubuntu-ci:#kubuntu-devel- Project iso_xenial_unstable_amd64 build #9: STILL FAILING in 13 min: http://kci.pangea.pub/job/iso_xenial_unstable_amd64/9/
[09:20] <yofel> ...
[09:28] -kubuntu-ci:#kubuntu-devel- Starting build #10 for job iso_xenial_unstable_amd64 (previous build: STILL FAILING)
[09:42] <yofel> oh, it got to the squashfs part, progress :D
[09:47] -kubuntu-ci:#kubuntu-devel- Project iso_xenial_unstable_amd64 build #10: STILL FAILING in 18 min: http://kci.pangea.pub/job/iso_xenial_unstable_amd64/10/
[09:47] <yofel> that's SUCCESS really. It only failed at trying to put the finished file in /var/www/ 
[09:48] <acheronuk> \o/
[09:53] <kfunk> I'm not sure why, but I got subscribed to kdevelop-related build notifications on launchpad. e.g. I just got: https://launchpadlibrarian.net/298407446/buildlog_ubuntu-yakkety-i386.kdevelop-python_5.0.3-0ubuntu1~ubuntu16.10~ppa1_BUILDING.txt.gz
[09:53] <kfunk> dh_install: Cannot find (any matches for) "usr/lib/*/qt5/plugins/kdevplatform/26/kdevpdb.so" (tried in "." and "debian/tmp")
[09:53] <kfunk> dh_install: kdevelop-python missing files: usr/lib/*/qt5/plugins/kdevplatform/26/kdevpdb.so
[09:53] <yofel> acheronuk: not that we really need that? http://kci.pangea.pub/job/iso_xenial_unstable_amd64/ws/result/
[09:53] <kfunk> while CMake installed the following:
[09:53] <kfunk> -- Installing: /<<PKGBUILDDIR>>/debian/tmp/usr/lib/i386-linux-gnu/qt5/plugins/kdevplatform/25/kdevpdb.so
[09:53] <kfunk> -- Set runtime path of "/<<PKGBUILDDIR>>/debian/tmp/usr/lib/i386-linux-gnu/qt5/plugins/kdevplatform/25/kdevpdb.so" to ""
[09:53] <yofel> so I'll just remove that part for now
[09:53] <kfunk> I suggest replacing the 25|26 with a wildmask
[09:53] <kfunk> that number can change any time
[09:53] <yofel> hm, that would break the workspace cleanup though :/
[09:54] <yofel> and we can't really keep image workspaces around
[09:56] <kfunk> yofel: talking to me?
[09:56] <yofel> no, rik
[09:57] <kfunk> ok :)
[09:58] <yofel> what you're saying makes sense. clivejo ^
[09:58] <yofel> and you're getting the notifications because they're from the kdevelop team ppa
[09:59] <yofel> if anything, clivejo: please testbuild stuff before uploading it to a "release" ppa
[10:00] <acheronuk> yofel: suppose it depends who we are doing these images for? just us to grab the latest and test? or to me made available a bit more generally to testers who would expect things not to vanish? 
[10:00] <yofel> hm. good question.
[10:01] <yofel> The default CI behavior is to keep the workspace for failed builds, but delete it for successful ones, which is a bit inconvenient here
[10:01] <acheronuk> oh.
[10:01] <yofel> We could change for for iso_* I guess as long as we only want to keep the latest
[10:02] <yofel> *change that
[10:03] <yofel> but having maybe the latest... 10 would be nice for debugging purposes
[10:03] <yofel> the current build job expects to be run on master, and the storage to be on master as well though
[10:04] <yofel> we have plenty of disk space on master for the storage, would just need a vHost directory (which might already be there actually)
[10:05] <yofel> but unless we setup the build infra on master as well, we'll need to change the imager job to scp/rsync the result folder to master
[10:05] <acheronuk> will the rysnc link let us update daily images locally, or does the file name change with the buildstamp foil that?
[10:07] <yofel> the job puts the timestamp into the file right now, but I would prefer a timestamp subfolder and a current symlink the way cdimage.u.c is set up
[10:07] <yofel> then we can also make that accessible to rsync
[10:07] <acheronuk> yep, sounds a better way
[10:11] <alleehol> with backports-landing:  purging the now transisional pkg kdeconnect-plasma wants to remove kamoso here too.    Removing them nevertheless, schedules kdeconnect for autoremoval.    kubuntu-{desktop,full} and libpurpose(?) should depend now on kdeconnect not the 'old' kdeconnect-plasma'  (apt-cache rdepends kdeconnect{,-plasma})
[10:20] -kubuntu-ci:#kubuntu-devel- Starting build #11 for job iso_xenial_unstable_amd64 (previous build: STILL FAILING)
[10:40] -kubuntu-ci:#kubuntu-devel- Yippee, build fixed!
[10:40] -kubuntu-ci:#kubuntu-devel- Project iso_xenial_unstable_amd64 build #11: FIXED in 20 min: http://kci.pangea.pub/job/iso_xenial_unstable_amd64/11/
[10:55] <yofel> hm, I tried to disable ws-cleanup, but that thing doesn't match the documentation :/
[10:56] <yofel> oh no, it worked
[10:56] <yofel> I was looking at the wrong place >.<
[10:56] <yofel> now we just need to figure out how to work around gpg2 for the newer releases
[11:31] -kubuntu-ci:#kubuntu-devel- Yippee, build fixed!
[11:31] -kubuntu-ci:#kubuntu-devel- Project zesty_unstable_kate build #40: FIXED in 15 min: http://kci.pangea.pub/job/zesty_unstable_kate/40/
[11:36] -kubuntu-ci:#kubuntu-devel- Yippee, build fixed!
[11:36] -kubuntu-ci:#kubuntu-devel- Project zesty_unstable_oxygen build #42: FIXED in 20 min: http://kci.pangea.pub/job/zesty_unstable_oxygen/42/
[11:42] -kubuntu-ci:#kubuntu-devel- Project zesty_unstable_kdevelop build #33: STILL FAILING in 12 min: http://kci.pangea.pub/job/zesty_unstable_kdevelop/33/
[11:44] <yofel> shadeslayer: is the gpg2 failure in http://kci.pangea.pub/job/iso_yakkety_unstable_amd64/3/console familiar to you by chance? Sounds like something that should be happening in stretch as well
[11:45] <yofel> and I'm not really convinced that *I* am supposed to install and run dirmngr here
[11:45] <shadeslayer> Nope haven't seen that
[11:46] <yofel> hm, thanks
[11:47] -kubuntu-ci:#kubuntu-devel- Yippee, build fixed!
[11:47] -kubuntu-ci:#kubuntu-devel- Project zesty_unstable_discover build #71: FIXED in 16 min: http://kci.pangea.pub/job/zesty_unstable_discover/71/
[11:58] -kubuntu-ci:#kubuntu-devel- Project zesty_unstable_kdevelop build #34: STILL FAILING in 11 min: http://kci.pangea.pub/job/zesty_unstable_kdevelop/34/
[12:03] <yofel> oh, that code path is only triggered when you set extra ppa's, so maybe we're just the first ones to hit this *-.-
[12:06] <yofel> root@packaging:/usr/lib/live/build# apt-cache depends gnupg
[12:06] <yofel> gnupg
[12:06] <yofel>   Recommends: dirmngr
[12:06] <yofel> who packaged this >.<
[12:13] <clivejo> kfunk: yes sorry, Launchpad was in a bit of a mess last night and I was trying to dput to my own testing PPA which wouldnt work, do I tried to upload to the release PPA as a test.  I thought it had failed too, but apparently not!  
[12:15] -kubuntu-ci:#kubuntu-devel- Starting build #4 for job iso_yakkety_unstable_amd64 (previous build: STILL FAILING)
[12:16] -kubuntu-ci:#kubuntu-devel- Project iso_yakkety_unstable_amd64 build #4: STILL FAILING in 1 min 16 sec: http://kci.pangea.pub/job/iso_yakkety_unstable_amd64/4/
[12:16] <clivejo> yofel: are we still paying for the S3 bucket?
[12:16]  * clivejo notices a payment to Amazon on the accounts
[12:16] <yofel> dunno
[12:17] <yofel> hm, that didn't work
[12:25] -kubuntu-ci:#kubuntu-devel- Starting build #5 for job iso_yakkety_unstable_amd64 (previous build: STILL FAILING)
[12:26] <clivejo> yofel: where is the vhost pointing?
[12:26] <yofel> which one?
[12:26] <clivejo> for the finished iso?
[12:26] <yofel> dunno, would have to read the config
[12:27] <yofel> uhuh... running dirmngr by hand fixed the problem. this is retarded
[12:28] -kubuntu-ci:#kubuntu-devel- Project iso_yakkety_unstable_amd64 build #5: STILL FAILING in 3 min 17 sec: http://kci.pangea.pub/job/iso_yakkety_unstable_amd64/5/
[12:28] -kubuntu-ci:#kubuntu-devel- Project yakkety_unstable_kdev-python build #41: FAILURE in 6 min 25 sec: http://kci.pangea.pub/job/yakkety_unstable_kdev-python/41/
[12:29] <clivejo> is binary.hybrid.iso the actual built iso?
[12:30] <yofel> yes, though you should really be looking in result/ not build/
[12:31] <yofel> latter is just the workdir from lb
[12:31] -kubuntu-ci:#kubuntu-devel- Starting build #6 for job iso_yakkety_unstable_amd64 (previous build: STILL FAILING)
[12:32] -kubuntu-ci:#kubuntu-devel- Project iso_yakkety_unstable_amd64 build #6: STILL FAILING in 48 sec: http://kci.pangea.pub/job/iso_yakkety_unstable_amd64/6/
[12:34] -kubuntu-ci:#kubuntu-devel- Starting build #7 for job iso_yakkety_unstable_amd64 (previous build: STILL FAILING)
[12:37] -kubuntu-ci:#kubuntu-devel- Project iso_yakkety_unstable_amd64 build #7: STILL FAILING in 3 min 9 sec: http://kci.pangea.pub/job/iso_yakkety_unstable_amd64/7/
[12:37] <yofel> ?!?
[12:38] <yofel> can we go back to gpg1 please? gpg2 is just plain broken
[12:38] -kubuntu-ci:#kubuntu-devel- Project zesty_unstable_breeze-icons build #49: STILL FAILING in 5 min 40 sec: http://kci.pangea.pub/job/zesty_unstable_breeze-icons/49/
[12:39] -kubuntu-ci:#kubuntu-devel- Project yakkety_unstable_kdev-python build #42: STILL FAILING in 5 min 59 sec: http://kci.pangea.pub/job/yakkety_unstable_kdev-python/42/
[12:42] <yofel> I give up, back to work
[12:48] -kubuntu-ci:#kubuntu-devel- Project zesty_unstable_breeze-icons build #50: STILL FAILING in 4 min 39 sec: http://kci.pangea.pub/job/zesty_unstable_breeze-icons/50/
[12:53] -kubuntu-ci:#kubuntu-devel- Project zesty_unstable_kdev-python build #31: FAILURE in 6 min 24 sec: http://kci.pangea.pub/job/zesty_unstable_kdev-python/31/
[13:04] -kubuntu-ci:#kubuntu-devel- Project zesty_unstable_kdev-python build #32: STILL FAILING in 5 min 59 sec: http://kci.pangea.pub/job/zesty_unstable_kdev-python/32/
[13:14] <clivejo> when will a decision on backports be made?
[13:15] -kubuntu-ci:#kubuntu-devel- Project xenial_unstable_kdev-python build #36: FAILURE in 5 min 49 sec: http://kci.pangea.pub/job/xenial_unstable_kdev-python/36/
[13:17] <clivejo> kfunk: are you using those packages in kdevelop team?
[13:21] <soee> clivejo: wasn't it more or less made ? 
[13:22] <clivejo> I dunno
[13:25] <IrcsomeBot> <ahoneybun> Rik put out a vote I believe
[13:26] <IrcsomeBot> <ahoneybun> Val and I said yed
[13:26] <acheronuk> I put out a 'proposal'
[13:26] <IrcsomeBot> <ahoneybun> Yes
[13:26] -kubuntu-ci:#kubuntu-devel- Project xenial_unstable_kdev-python build #37: STILL FAILING in 5 min 44 sec: http://kci.pangea.pub/job/xenial_unstable_kdev-python/37/
[13:26] <acheronuk> so far yofel ack'd it and gave a +1
[13:27] <acheronuk> same with ahoneybun and valorie 
[13:28] <clivejo> is wxl not acting RM?
[13:29] <acheronuk> faff about too much and we will never get anything done, so it was put in the terms of "I would like to do this tomorrow. if you think it shouldn't please raise objections"
[13:30] <clivejo> ok
[13:30] <clivejo> make it so, Number One!
[13:30] <kfunk> clivejo: what do you mean? if the kdevelop team installs ubuntu packages?
[13:30] <clivejo> do you use them?
[13:30] <kfunk> we use our self-compiled versions of course :)
[13:31] <kfunk> so, no, not really
[13:31] <clivejo> I see
[13:32] <kfunk> why? any problems?
[13:32] <acheronuk> clivejo: well wxl probably isn't sufficiently bedded in on the technical side yet, so what would in theory be a RM decision is I think a bit more of "are we ready yet, any objections?" to current -devs etc
[13:32] <acheronuk> if anyone objects, tell me!
[13:33] <yofel> backports has typically not been a concern to the RM anyway, as that position mostly just covers the primary archive tasks. Whoever did most of the work on the backports decided what gets done with it
[13:33] <clivejo> kfunk: no no, I dont use them myself.  Ovi setup a team on LP to provide released versions, while we sorted out the backporting issues with Frameworks and Plasma 
[13:33] <acheronuk> yofel: ah. ok. that I didn't know. ty
[13:34] <kfunk> okok
[13:34] <clivejo> kfunk: the xenial build it failing as the arhive doesnt have the required Frameworks for it
[13:36] <kfunk> /<<BUILDDIR>>/kdevelop-python-5.0.3+p16.04+git20161216.1310/docfilekcm/kcm_docfiles.cpp:42:12: error: ‘DocumentationConfigPage’ is not a member of ‘KDevelop::ConfigPage’
[13:36] <kfunk>      return KDevelop::ConfigPage::DocumentationConfigPage;
[13:36] <kfunk>             ^
[13:36] <kfunk> hmm
[13:36] <clivejo> acheronuk: so your decision :)
[13:38] <acheronuk> clivejo: as it might come to that, is why I sent the email asking for opinions
[13:38] <kfunk> ah, that's actually kdevelop-python master branch. /me just got confused about "kdevelop-python-5.0.3" in there
[13:38] <kfunk> ok, that just needs a newer kdevplatform master, yep
[14:35] <alleehol> acheronuk: FWIW  +1 from me.    No problems found after 1/2 day of usage
[14:48] <BluesKaj> Howdy all
[14:51] <yofel> o/
[15:14] -kubuntu-ci:#kubuntu-devel- Starting build #8 for job iso_yakkety_unstable_amd64 (previous build: STILL FAILING)
[15:19] -kubuntu-ci:#kubuntu-devel- Project iso_yakkety_unstable_amd64 build #8: ABORTED in 4 min 39 sec: http://kci.pangea.pub/job/iso_yakkety_unstable_amd64/8/
[15:20] -kubuntu-ci:#kubuntu-devel- Starting build #9 for job iso_yakkety_unstable_amd64 (previous build: ABORTED)
[15:30] <IrcsomeBot> <tsimonq2> acheronuk: You do it yet?
[15:31] <acheronuk> alleehol: great. thanks for the feedback
[15:32] <acheronuk> tsimonq2: nope. had said late afternoon. so taking a fairly arbitrary meaning for that, I was waiting until 4pm UTC
[15:37] -kubuntu-ci:#kubuntu-devel- Project iso_yakkety_unstable_amd64 build #9: STILL FAILING in 16 min: http://kci.pangea.pub/job/iso_yakkety_unstable_amd64/9/
[15:40] <alleehol> acheronuk: about the kdeconnect fixes for (reverse)dependencies.  If it helps: I've seen it's fixed in kde neon.
[15:48] <yofel> kubuntu-meta will need an update. I think -backports already has a patched one
[15:48] <yofel> for earlier changes
[15:49] -kubuntu-ci:#kubuntu-devel- Starting build #10 for job iso_yakkety_unstable_amd64 (previous build: STILL FAILING)
[15:50] <wxl> clivejo: yeah, i don't think me being RM has been made official. also, i've yet to hear anything constructive from Riddell, so if i (or i guess any of us) proceed as RM, we're kind of on our own to figure it out
[15:51] <Riddell> kubuntu's never had an official release manager, feel free to make one but the important bit is being on the ubuntu release team
[15:52] <wxl> Riddell: and by that you mean having access to mark images as ready on the qa tracker?
[15:52] <Riddell> right
[15:52] <wxl> right right
[15:53] <Riddell> the ubuntu release team should be there to help anyone figure it out, feel free to ask me if there's specific questions too but for the most part it's making sure everything is in place
[15:53] <wxl> within lubuntu that access is granted in other forms other than being on the release team itself
[15:54] <wxl> afaik you're the only release team member that's not a core ubuntu person
[15:54] <yofel> I think I'm still set as the manager for the kubuntu images, so worst case ask me
[15:56] <acheronuk> I'm reasonably sure in a few cases, after having some testing logged, the release team have just gone ahead and marked our images as ready themselves
[15:56] <yofel> they did. The only criteria is that the test are done anyway
[15:57] <wxl> they rarely do that, though
[15:57] -kubuntu-ci:#kubuntu-devel- Project xenial_unstable_marble build #69: NOW UNSTABLE in 36 min: http://kci.pangea.pub/job/xenial_unstable_marble/69/
[15:57] <wxl> at least not without bugging SOMEONE on irc before
[15:57] <yofel> well yes, *with* bugging someone on irc
[15:57] <wxl> i know at least during some cycle i wandered in here to get an idea of what's going on to pass off to them
[15:57] -kubuntu-ci:#kubuntu-devel- Project yakkety_unstable_marble build #77: STILL FAILING in 37 min: http://kci.pangea.pub/job/yakkety_unstable_marble/77/
[15:57] <acheronuk> wxl: if I recall, they 'bugged' us on IRC at the time :P
[15:57] <wxl> :)
[15:58] <yofel> 1.0.5-1build1~2 - what the hell is that version supposed to mean... yay for copying stuff from ppas I guess
[15:59] <acheronuk> ok. if no objections, I am about to hit 'kopy' on the backports
[16:00] <wxl> yofel: do you know what membership gives you that ability? (you could try a fresh SSO login to the QA tracker)
[16:00]  * clem_l holds his breath
[16:00] <yofel> wxl: I would have to check again, but I'm failry certain that when I checked last time my actual account ID was set there
[16:00] <wxl> yofel: that's… weird.
[16:01] <acheronuk> kopy running :P
[16:01] <yofel> wxl: so, it's asking me for "ubuntu-testcase, kubuntu-council'
[16:02] <wxl> ah it's probably set so that all kouncil (name change suggested) members can mark images
[16:02] <wxl> which i think is totally sensible
[16:02] <wxl> but obviously not for me XD
[16:02] <yofel> maybe. Now I wondere where I saw my ID....
[16:04] -kubuntu-ci:#kubuntu-devel- Project iso_yakkety_unstable_amd64 build #10: STILL FAILING in 14 min: http://kci.pangea.pub/job/iso_yakkety_unstable_amd64/10/
[16:04] <acheronuk> kopy for xenial requested :)
[16:05] <acheronuk> wonder if I should give the LP publisher time to recover from a mild nervous breakdown before I do yaketty?
[16:05] <yofel> check the PPA page for errors please if you didn't use --sync
[16:06] <wxl> Lubuntu has a "product-manager" team
[16:06] <wxl> i think k could use something similar
[16:08] <clem_l> acheronuk: the issue where kalarm can't start is the same as the one for kmail right?
[16:08] <clem_l> it's the /var/lib/mysql-files dir missing?
[16:09] <yofel> uh, that would be akonadi being broken
[16:09] <yofel> did someone backport the broken version from yakkety?
[16:09] <yofel> actually, did we ever fix that in >=yakkety?
[16:10] <blaze> mysql is not meant for desktop apps :\
[16:11] <yofel> I think most of us got that by now, we just can't get rid of it -.-
[16:12] <yofel> bug 1633855
[16:12] <ubottu> bug 1633855 in akonadi (Ubuntu Zesty) "akonadi fails to start after upgrade to yakkety" [High,Triaged] https://launchpad.net/bugs/1633855
[16:12] <yofel> we did not -.-
[16:12] <wxl> blaze: tell that to the kde developers :)
[16:12] <yofel> someone please keep pinging me over the weekend until I'm annoyed enough to fix that
[16:13] <acheronuk> I didn't think that was fixable with the mysql in Xenial?
[16:13] <acheronuk> but I may be wrong there
[16:13] <clem_l> yofel: ping
[16:13] <clem_l> yofel: ping
[16:13] <clem_l> yofel: ping
[16:13] <clem_l> oh wait.. is it the weekend yet?
[16:13] <acheronuk> lol
[16:13] <wxl> hah
[16:13]  * wxl hands yofel a trout
[16:14] <yofel> good start, but you'll have to do better :D
[16:14]  * yofel binds the trout to an auto-slapper that responds to pings
[16:14]  * wxl sets the auto-slapper to kill
[16:14] <yofel> acheronuk: that was never broken in xenail
[16:14] <yofel> *xenial
[16:16] <acheronuk> I meant in xenial when you are running the backports akonadi 
[16:17] <yofel> if that has the patches disabled that will probably break
[16:17] <yofel> as we esp. wrote those a couple days before the xenial release to get it running with 5.7
[16:22] <acheronuk> umm. I was only paying attention part of the time back then
[16:22] <yofel> well, me too ^^
[16:22] <yofel> oh, not then, but now
[16:23] <yofel> #postgresql-data-checksums.patch
[16:23] <yofel> #postgresql9.5.patch
[16:23] <yofel> #kubuntu_disable_secure_file_priv_check.diff
[16:23] <yofel> #kubuntu_fix_mysql_db_creation_57.diff
[16:23] <yofel> yep, we have a problem
[16:24] <yofel> typical release days :D
[16:26] <acheronuk> yeah. I find out that something I thought was not fixable, or very difficult to fix, actually has disabled patches 2 mins after hitting the 'release' button!
[16:26] <acheronuk> such is life XD
[16:29] <clem_l> that's all I've got
[16:30] <clem_l> other than that, the theming on the session screen
[16:30] <clem_l> I'm going to fix that right now
[16:30] <clem_l> I can squeeze an mkdir -p /var/lib/mysql-files in a postinst too if it helps
[16:31] <yofel> FWIW, that's done in the postinst of 'mysql-server', what you want is enable kubuntu_disable_secure_file_priv_check.diff in akonadi
[16:32] <yofel> and kubuntu_fix_mysql_db_creation_57.diff for initial DB creation using 5.7
[16:32] <clem_l> are you enabling these in an update in the backports PPA?
[16:32] <yofel> yes
[16:32] <clem_l> ok
[16:32] <yofel> acheronuk: are you? otherwise I'll have time to do that later
[16:34] <acheronuk> yofel: I'm not really sure what I'm doing with akonadi, so if you would be kind enough to do the honours as you know what is needed, that would be appreciated
[16:34] <yofel> ack
[16:35] <clem_l> I was looking at the task switcher there in Plasma, it's impressive the amount of configuration...
[16:36] <clem_l> not only you can choose among a wide variety of what is essentially a core component, but you can fine tune the selected switcher in detail
[16:36] <clem_l> and then not only that but you can go ahead and pull 3rd party ones
[16:37] <clem_l> I'm not sure whether that's completely mad or absolutely awesome, but it's impressive
[16:37] <acheronuk> that is one thing we tend love about KDE. configurability and being able to extend it
[17:04] -kubuntu-ci:#kubuntu-devel- Project xenial_unstable_pim-sieve-editor build #37: STILL FAILING in 7 min 2 sec: http://kci.pangea.pub/job/xenial_unstable_pim-sieve-editor/37/
[17:07] <yofel> the publisher really went on vacation it seems
[17:15] -kubuntu-ci:#kubuntu-devel- Project xenial_unstable_pim-sieve-editor build #38: STILL FAILING in 5 min 38 sec: http://kci.pangea.pub/job/xenial_unstable_pim-sieve-editor/38/
[17:19] <acheronuk> hmmm. did I kill it?
[17:21] <acheronuk> if clem_l is still holding his breath, I think he'll have turned blue by now :P
[17:21] <yofel> more likely the archive rebuilds :D
[17:29] <clem_l> :)
[17:55] -kubuntu-ci:#kubuntu-devel- Project zesty_unstable_marble build #54: NOW UNSTABLE in 2 hr 34 min: http://kci.pangea.pub/job/zesty_unstable_marble/54/
[18:00] <acheronuk> looks like Xenial has published
[18:05] <clivejo> oh its Friday today!
[18:05]  * clivejo looks at yofel
[18:05] <clivejo> and December too
[18:06] <yofel> hm? :D
[18:06] <clivejo> just reminding you :P
[18:06] <yofel> what, what could possibly go wrong on a december friday ^^
[18:06] <yofel> evening
[18:09] <clivejo> backports mayhem!  
[18:12] <acheronuk> clivejo: right. I'm off. I'll be back on Monday :P
[18:12] <yofel> hey! XD
[18:13] <clivejo> me too
[18:13] <clivejo> probably wont be around until noon on Monday
[18:13] <acheronuk> tsimonq2: you'll be here, right :P
[18:13] <clivejo> let the dust settle
[18:13]  * mamarley turns on the HEPA filter.
[18:15] <clivejo> course tsimonq2 will be here, he volunteers to rebuild the entire stack on new Qt didn't he?
[18:16] <wxl> did he do his homework?
[18:16] <clivejo> no!
[18:16] <wxl> well—
[18:17] <yofel> well then, I'm out for about an hour. Try to not blow everything up in the meantime
[18:17] <clivejo> awwww yofel
[18:18] <clivejo> you're no fun!
[18:18] <yofel> hey, I'm still sitting in the office ^^
[18:18] <clivejo> why?!?
[18:18] <yofel> overtime work
[18:18] <clivejo> :(
[18:18] <clivejo> but its.... christmas
[18:18] <yofel> ... in a week
[18:18] <yofel> anyway, bbl
[18:19] <clivejo> did you do something naughty at your Christmas party?!?
[18:22]  * acheronuk tries updating VMs
[18:41] -kubuntu-ci:#kubuntu-devel- Project zesty_unstable_kdevelop build #35: ABORTED in 17 sec: http://kci.pangea.pub/job/zesty_unstable_kdevelop/35/
[18:42] -kubuntu-ci:#kubuntu-devel- Starting build #12 for job iso_zesty_unstable_amd64 (previous build: STILL FAILING)
[18:58] -kubuntu-ci:#kubuntu-devel- Project iso_zesty_unstable_amd64 build #12: STILL FAILING in 15 min: http://kci.pangea.pub/job/iso_zesty_unstable_amd64/12/
[18:59] <clivejo> 18:58:17 The following packages have unmet dependencies:
[18:59] <clivejo> 18:58:17  fcitx-frontend-qt5 : Depends: qtbase-abi-5-6-1
[18:59] <clivejo> 18:58:17 E: Unable to correct problems, you have held broken packages.
[19:18] <acheronuk> clivejo: where is that from?
[19:18] <clivejo> the ISO build job
[19:18] <acheronuk> right. just double checking 
[19:19] <clivejo> some KDE4 stuffs being pulled in too
[19:34] -kubuntu-ci:#kubuntu-devel- Yippee, build fixed!
[19:34] -kubuntu-ci:#kubuntu-devel- Project xenial_unstable_kleopatra build #102: FIXED in 2 hr 36 min: http://kci.pangea.pub/job/xenial_unstable_kleopatra/102/
[19:34] -kubuntu-ci:#kubuntu-devel- Project yakkety_unstable_marble build #78: STILL FAILING in 3 hr 31 min: http://kci.pangea.pub/job/yakkety_unstable_marble/78/
[19:41] <yofel> clivejo: I uploaded rebuilds for that, they were just stuck on the publisher
[19:41]  * clivejo kicks publisher
[19:42] <yofel> lets try this agian
[19:42] -kubuntu-ci:#kubuntu-devel- Starting build #11 for job iso_yakkety_unstable_amd64 (previous build: STILL FAILING)
[19:42] -kubuntu-ci:#kubuntu-devel- Starting build #12 for job iso_xenial_unstable_amd64 (previous build: FIXED)
[19:42] -kubuntu-ci:#kubuntu-devel- Starting build #13 for job iso_zesty_unstable_amd64 (previous build: STILL FAILING)
[19:42] <clivejo> has it published?
[19:43] <yofel> yes
[19:43] <yofel> after like 3h..
[19:44] -kubuntu-ci:#kubuntu-devel- Project iso_yakkety_unstable_amd64 build #11: STILL FAILING in 1 min 38 sec: http://kci.pangea.pub/job/iso_yakkety_unstable_amd64/11/
[19:44] <clivejo> ah only a slight delay then
[19:44] -kubuntu-ci:#kubuntu-devel- Project iso_zesty_unstable_amd64 build #13: STILL FAILING in 1 min 40 sec: http://kci.pangea.pub/job/iso_zesty_unstable_amd64/13/
[19:44] <yofel> wtf
[19:44] <yofel> 19:44:01 gpg: keyserver receive failed: No data
[19:44] <yofel> the server is broken >.<
[19:44] <clivejo> LP keyserver?
[19:44] <yofel> ubuntu keyserver
[19:44] -kubuntu-ci:#kubuntu-devel- Starting build #12 for job iso_yakkety_unstable_amd64 (previous build: STILL FAILING)
[19:45] -kubuntu-ci:#kubuntu-devel- Starting build #14 for job iso_zesty_unstable_amd64 (previous build: STILL FAILING)
[19:45] <yofel> OTOH, we need job group throttling. 3 iso jobs at the same time is doable, but not a particulary good idea
[19:46] <yofel> (this is stress testing now)
[19:46] <tsimonq2> MEOW
[19:46] <yofel> HISS
[19:48] <yofel> now to fix akonadi for backports
[19:50] <mamarley> WOOF
[20:00] <yofel> clivejo: if you refresh patches, please also update the "Updated" field in the patch notes
[20:01] <clivejo> can you give me an example?
[20:01] <yofel> your patch updates in akonadi
[20:08] -kubuntu-ci:#kubuntu-devel- Yippee, build fixed!
[20:08] -kubuntu-ci:#kubuntu-devel- Project zesty_unstable_kdevelop build #36: FIXED in 1 hr 26 min: http://kci.pangea.pub/job/zesty_unstable_kdevelop/36/
[20:08] -kubuntu-ci:#kubuntu-devel- Project iso_xenial_unstable_amd64 build #12: SUCCESS in 26 min: http://kci.pangea.pub/job/iso_xenial_unstable_amd64/12/
[20:08]  * clivejo high fives yofel
[20:09] <yofel> that one worked in the morning already ^^
[20:09] <yofel> at least I didn't break it
[20:09] <yofel> but the other too are looking good as well
[20:09] <yofel> *two
[20:10] <yofel> urgh, good that I did that on linode. Scaleway would've run out of disk space by now
[20:11] -kubuntu-ci:#kubuntu-devel- Project iso_zesty_unstable_amd64 build #14: STILL FAILING in 26 min: http://kci.pangea.pub/job/iso_zesty_unstable_amd64/14/
[20:11] -kubuntu-ci:#kubuntu-devel- Project iso_yakkety_unstable_amd64 build #12: STILL FAILING in 26 min: http://kci.pangea.pub/job/iso_yakkety_unstable_amd64/12/
[20:12] <clivejo> awwwww
[20:12] <yofel> 20:11:47 E: /usr/share/syslinux/themes/ubuntu-yakkety - no such directory.
[20:12] <yofel> hmmmmmm
[20:17] <tsimonq2> yofel: OOOOOOOOOH where is the code to do that???
[20:18] <yofel> tsimonq2: hm?
[20:18] <clivejo> pangea-tooling does it?!
[20:19] <yofel> pangea-tooling/kci/imager.rb and imager/* if you want to look at it
[20:19] <tsimonq2> :D :D :D :D :D
[20:24] <yofel> hm, looks like we're still using the xenial theme, now where the hell do I tell live build that
[20:25] <yofel> found it
[20:27] <IrcsomeBot> <tsimonq2> Hey yofel, questions
[20:27] -kubuntu-ci:#kubuntu-devel- Starting build #13 for job iso_yakkety_unstable_amd64 (previous build: STILL FAILING)
[20:27] <yofel> hm?
[20:27] -kubuntu-ci:#kubuntu-devel- Starting build #15 for job iso_zesty_unstable_amd64 (previous build: STILL FAILING)
[20:28] <IrcsomeBot> <tsimonq2> Let's say we ship Kubuntu G with Plasma 1.1.1. Kubuntu G gets released. Can 1.1.2 be SRUed into G?
[20:28] <yofel> yes, 1.2 no
[20:28] <yofel> well
[20:28] <yofel> yes, under the condition that it contains no features
[20:29] <yofel> so the question is are we talking about semantic versioning here? ^^
[20:29] <IrcsomeBot> <tsimonq2> I mean if we ship Zesty with 5.9.4 for example, can we SRU in 5.9.5?
[20:29] <yofel> yes we can
[20:29] <IrcsomeBot> <tsimonq2> Ooh yay ok
[20:29] <yofel> I believe the MRE for plasma is still valid
[20:30] <wxl> http://i.imgur.com/aAbDQy9.gif
[20:30] <IrcsomeBot> <tsimonq2> 'cause we might end up needing to do that
[20:30] <yofel> XD
[20:31] <IrcsomeBot> <tsimonq2> (Photo, 720x1280) https://irc-attachments.kde.org/oGslA00o/file_1399.jpg
[20:31] <IrcsomeBot> <tsimonq2> Hmm
[20:31] <wxl> aw
[20:32] <wxl> works for me
[20:32] <IrcsomeBot> <tsimonq2> Oh I see it
[20:32] <IrcsomeBot> <tsimonq2> Lol
[20:34] <yofel> hm, now I completely broke the workspace cleanup for the image builds it seems -.-
[20:37] <yofel> oh, ws-cleanup renamed the folders instead of wiping them o.O
[20:43] <yofel> which is *supposedly* fixed in 0.32 - which we have...
[20:47] <yofel> oh hm, rm: cannot remove 'imager-amd64_ws-cleanup_1481883609881/build/chroot/lib/modules/4.4.0-53-generic/kernel/drivers/usb/gadget/legacy/tcm_usb_gadget.ko': Permission denied
[20:48] <yofel> might be a problem
[20:51] <yofel> a hm, yeah. The user/group names aren't consistent in the CI
[20:54] -kubuntu-ci:#kubuntu-devel- Yippee, build fixed!
[20:54] -kubuntu-ci:#kubuntu-devel- Project iso_yakkety_unstable_amd64 build #13: FIXED in 27 min: http://kci.pangea.pub/job/iso_yakkety_unstable_amd64/13/
[20:54] -kubuntu-ci:#kubuntu-devel- Yippee, build fixed!
[20:54] -kubuntu-ci:#kubuntu-devel- Project iso_zesty_unstable_amd64 build #15: FIXED in 26 min: http://kci.pangea.pub/job/iso_zesty_unstable_amd64/15/
[20:55] -kubuntu-ci:#kubuntu-devel- Project yakkety_unstable_libkcompactdisc build #58: STILL FAILING in 17 min: http://kci.pangea.pub/job/yakkety_unstable_libkcompactdisc/58/
[20:55] -kubuntu-ci:#kubuntu-devel- Project zesty_unstable_libkcompactdisc build #41: NOW UNSTABLE in 17 min: http://kci.pangea.pub/job/zesty_unstable_libkcompactdisc/41/
[20:55] -kubuntu-ci:#kubuntu-devel- Project xenial_unstable_libkcompactdisc build #78: NOW UNSTABLE in 17 min: http://kci.pangea.pub/job/xenial_unstable_libkcompactdisc/78/
[20:55] -kubuntu-ci:#kubuntu-devel- Project yakkety_unstable_akonadi build #229: STILL FAILING in 49 min: http://kci.pangea.pub/job/yakkety_unstable_akonadi/229/
[20:55] <yofel> please don't touch the image jobs for now, linode will run ENOSPC after a few
[20:59] <yofel> great, how the hell do I figure out what UID I need to chown this to...
[21:05] <yofel> great, how the hell do I figure out what UID I need to chown this to...
[21:05] <yofel> and why do I have connection issues again
[21:11] -kubuntu-ci:#kubuntu-devel- Starting build #16 for job iso_zesty_unstable_amd64 (previous build: FIXED)
[21:11] -kubuntu-ci:#kubuntu-devel- Project iso_zesty_unstable_amd64 build #16: FAILURE in 1.9 sec: http://kci.pangea.pub/job/iso_zesty_unstable_amd64/16/
[21:14] <yofel> o.O
[21:17] -kubuntu-ci:#kubuntu-devel- Starting build #17 for job iso_zesty_unstable_amd64 (previous build: FAILURE -- last SUCCESS #15 50 min ago)
[21:17] -kubuntu-ci:#kubuntu-devel- Project iso_zesty_unstable_amd64 build #17: STILL FAILING in 1.9 sec: http://kci.pangea.pub/job/iso_zesty_unstable_amd64/17/
[21:17] -kubuntu-ci:#kubuntu-devel- Project yakkety_unstable_libkcompactdisc build #59: STILL FAILING in 17 min: http://kci.pangea.pub/job/yakkety_unstable_libkcompactdisc/59/
[21:17] -kubuntu-ci:#kubuntu-devel- Yippee, build fixed!
[21:17] -kubuntu-ci:#kubuntu-devel- Project xenial_unstable_libkcompactdisc build #79: FIXED in 18 min: http://kci.pangea.pub/job/xenial_unstable_libkcompactdisc/79/
[21:18] -kubuntu-ci:#kubuntu-devel- Yippee, build fixed!
[21:18] -kubuntu-ci:#kubuntu-devel- Project zesty_unstable_libkcompactdisc build #42: FIXED in 18 min: http://kci.pangea.pub/job/zesty_unstable_libkcompactdisc/42/
[21:19] -kubuntu-ci:#kubuntu-devel- Starting build #18 for job iso_zesty_unstable_amd64 (previous build: STILL FAILING -- last SUCCESS #15 52 min ago)
[21:19] <yofel> ruby is wieird
[21:30]  * clivejo nods
[21:32] -kubuntu-ci:#kubuntu-devel- Project yakkety_unstable_akonadi build #230: STILL FAILING in 32 min: http://kci.pangea.pub/job/yakkety_unstable_akonadi/230/
[21:41] -kubuntu-ci:#kubuntu-devel- Yippee, build fixed!
[21:41] -kubuntu-ci:#kubuntu-devel- Project iso_zesty_unstable_amd64 build #18: FIXED in 21 min: http://kci.pangea.pub/job/iso_zesty_unstable_amd64/18/
[21:46] -kubuntu-ci:#kubuntu-devel- Starting build #19 for job iso_zesty_unstable_amd64 (previous build: FIXED)
[21:47] -kubuntu-ci:#kubuntu-devel- Project yakkety_unstable_libkcddb build #114: STILL FAILING in 16 min: http://kci.pangea.pub/job/yakkety_unstable_libkcddb/114/
[21:47] <yofel> that didn't work :(
[21:47] -kubuntu-ci:#kubuntu-devel- Project xenial_unstable_libkcddb build #107: STILL FAILING in 17 min: http://kci.pangea.pub/job/xenial_unstable_libkcddb/107/
[21:47] -kubuntu-ci:#kubuntu-devel- Project zesty_unstable_libkcddb build #40: STILL FAILING in 17 min: http://kci.pangea.pub/job/zesty_unstable_libkcddb/40/
[21:48] <yofel> because I'm running chown in the wrong folder -.-
[21:52] <valorie> everybody be sure to run updates or at least check your version of apport: https://bugs.launchpad.net/apport/+bug/1648806
[21:52] <ubottu> Launchpad bug 1648806 in apport (Ubuntu Zesty) "Arbitrary code execution through crafted CrashDB or Package/Source fields in .crash files" [Undecided,Fix released]
[21:52] <valorie> undecided?
[21:53] <valorie> weird, but fixed
[21:56] <valorie> http://www.theregister.co.uk/2016/12/15/researcher_details_justpatched_pwnage_flaws_in_ubuntu/ -- wow: "while working on his Apport research, he was offered $10,000 for his exploits by an unnamed third party."
[21:56] -kubuntu-ci:#kubuntu-devel- Yippee, build fixed!
[21:56] -kubuntu-ci:#kubuntu-devel- Project zesty_unstable_kdev-python build #33: FIXED in 12 min: http://kci.pangea.pub/job/zesty_unstable_kdev-python/33/
[22:04] -kubuntu-ci:#kubuntu-devel- Yippee, build fixed!
[22:04] -kubuntu-ci:#kubuntu-devel- Project yakkety_unstable_libkcddb build #115: FIXED in 12 min: http://kci.pangea.pub/job/yakkety_unstable_libkcddb/115/
[22:04] -kubuntu-ci:#kubuntu-devel- Yippee, build fixed!
[22:04] -kubuntu-ci:#kubuntu-devel- Project xenial_unstable_libkcddb build #108: FIXED in 12 min: http://kci.pangea.pub/job/xenial_unstable_libkcddb/108/
[22:04] -kubuntu-ci:#kubuntu-devel- Yippee, build fixed!
[22:04] -kubuntu-ci:#kubuntu-devel- Project zesty_unstable_libkcddb build #41: FIXED in 12 min: http://kci.pangea.pub/job/zesty_unstable_libkcddb/41/
[22:08] -kubuntu-ci:#kubuntu-devel- Project iso_zesty_unstable_amd64 build #19: SUCCESS in 21 min: http://kci.pangea.pub/job/iso_zesty_unstable_amd64/19/
[22:10] -kubuntu-ci:#kubuntu-devel- Starting build #20 for job iso_zesty_unstable_amd64 (previous build: SUCCESS)
[22:17] -kubuntu-ci:#kubuntu-devel- Project xenial_unstable_audiocd-kio build #85: NOW UNSTABLE in 13 min: http://kci.pangea.pub/job/xenial_unstable_audiocd-kio/85/
[22:17] -kubuntu-ci:#kubuntu-devel- Project yakkety_unstable_audiocd-kio build #82: NOW UNSTABLE in 13 min: http://kci.pangea.pub/job/yakkety_unstable_audiocd-kio/82/
[22:17] -kubuntu-ci:#kubuntu-devel- Project zesty_unstable_audiocd-kio build #28: NOW UNSTABLE in 13 min: http://kci.pangea.pub/job/zesty_unstable_audiocd-kio/28/
[22:29] -kubuntu-ci:#kubuntu-devel- Project iso_zesty_unstable_amd64 build #20: SUCCESS in 19 min: http://kci.pangea.pub/job/iso_zesty_unstable_amd64/20/
[22:35] -kubuntu-ci:#kubuntu-devel- Starting build #21 for job iso_zesty_unstable_amd64 (previous build: SUCCESS)
[22:35] <yofel> ok, I think I got it now
[22:35] <clivejo> yipppeeee
[22:42] <valorie> nice to see the green
[22:45] <clivejo> were is the gree?
[22:51] -kubuntu-ci:#kubuntu-devel- Yippee, build fixed!
[22:51] -kubuntu-ci:#kubuntu-devel- Project yakkety_unstable_audiocd-kio build #83: FIXED in 16 min: http://kci.pangea.pub/job/yakkety_unstable_audiocd-kio/83/
[22:51] -kubuntu-ci:#kubuntu-devel- Yippee, build fixed!
[22:51] -kubuntu-ci:#kubuntu-devel- Project xenial_unstable_audiocd-kio build #86: FIXED in 17 min: http://kci.pangea.pub/job/xenial_unstable_audiocd-kio/86/
[22:52] -kubuntu-ci:#kubuntu-devel- Yippee, build fixed!
[22:52] -kubuntu-ci:#kubuntu-devel- Project zesty_unstable_audiocd-kio build #29: FIXED in 17 min: http://kci.pangea.pub/job/zesty_unstable_audiocd-kio/29/
[22:53] -kubuntu-ci:#kubuntu-devel- Project iso_zesty_unstable_amd64 build #21: SUCCESS in 18 min: http://kci.pangea.pub/job/iso_zesty_unstable_amd64/21/
[22:59] -kubuntu-ci:#kubuntu-devel- Starting build #13 for job iso_xenial_unstable_amd64 (previous build: SUCCESS)
[22:59] -kubuntu-ci:#kubuntu-devel- Starting build #14 for job iso_yakkety_unstable_amd64 (previous build: FIXED)
[23:00] -kubuntu-ci:#kubuntu-devel- Starting build #22 for job iso_zesty_unstable_amd64 (previous build: SUCCESS)
[23:23] -kubuntu-ci:#kubuntu-devel- Project iso_xenial_unstable_amd64 build #13: SUCCESS in 23 min: http://kci.pangea.pub/job/iso_xenial_unstable_amd64/13/
[23:26] -kubuntu-ci:#kubuntu-devel- Project iso_yakkety_unstable_amd64 build #14: SUCCESS in 26 min: http://kci.pangea.pub/job/iso_yakkety_unstable_amd64/14/
[23:26] -kubuntu-ci:#kubuntu-devel- Project iso_zesty_unstable_amd64 build #22: SUCCESS in 25 min: http://kci.pangea.pub/job/iso_zesty_unstable_amd64/22/
[23:54] -kubuntu-ci:#kubuntu-devel- Yippee, build fixed!
[23:54] -kubuntu-ci:#kubuntu-devel- Project zesty_unstable_libkgeomap build #20: FIXED in 13 min: http://kci.pangea.pub/job/zesty_unstable_libkgeomap/20/