[00:01] -kubuntu-ci:#kubuntu-devel- Project merger_kdiamond build #637: FAILURE in 47 sec: http://kci.pangea.pub/job/merger_kdiamond/637/
[00:02] -kubuntu-ci:#kubuntu-devel- Yippee, build fixed!
[00:02] -kubuntu-ci:#kubuntu-devel- Project merger_kcoreaddons build #795: FIXED in 2 min 5 sec: http://kci.pangea.pub/job/merger_kcoreaddons/795/
[00:02] -kubuntu-ci:#kubuntu-devel- Yippee, build fixed!
[00:02] -kubuntu-ci:#kubuntu-devel- Project xenial_unstable_krunner build #220: FIXED in 9 min 46 sec: http://kci.pangea.pub/job/xenial_unstable_krunner/220/
[00:03] -kubuntu-ci:#kubuntu-devel- Yippee, build fixed!
[00:03] -kubuntu-ci:#kubuntu-devel- Project yakkety_unstable_krunner build #136: FIXED in 8 min 49 sec: http://kci.pangea.pub/job/yakkety_unstable_krunner/136/
[00:07] -kubuntu-ci:#kubuntu-devel- Yippee, build fixed!
[00:07] -kubuntu-ci:#kubuntu-devel- Project merger_kdiamond build #638: FIXED in 51 sec: http://kci.pangea.pub/job/merger_kdiamond/638/
[00:07] -kubuntu-ci:#kubuntu-devel- Project mgmt_merger build #715: STILL UNSTABLE in 7 min 5 sec: http://kci.pangea.pub/job/mgmt_merger/715/
[00:07] -kubuntu-ci:#kubuntu-devel- Project mgmt_progenitor build #700: STILL UNSTABLE in 7 min 9 sec: http://kci.pangea.pub/job/mgmt_progenitor/700/
[00:10] -kubuntu-ci:#kubuntu-devel- Yippee, build fixed!
[00:10] -kubuntu-ci:#kubuntu-devel- Project zesty_unstable_krunner build #9: FIXED in 13 min: http://kci.pangea.pub/job/zesty_unstable_krunner/9/
[00:22] -kubuntu-ci:#kubuntu-devel- Project yakkety_unstable_libkipi build #78: STILL UNSTABLE in 14 min: http://kci.pangea.pub/job/yakkety_unstable_libkipi/78/
[00:22] -kubuntu-ci:#kubuntu-devel- Project zesty_unstable_kalzium build #17: STILL FAILING in 10 min: http://kci.pangea.pub/job/zesty_unstable_kalzium/17/
[00:23] -kubuntu-ci:#kubuntu-devel- Project yakkety_unstable_kalzium build #47: STILL FAILING in 11 min: http://kci.pangea.pub/job/yakkety_unstable_kalzium/47/
[00:23] -kubuntu-ci:#kubuntu-devel- Project xenial_unstable_kalzium build #106: STILL FAILING in 11 min: http://kci.pangea.pub/job/xenial_unstable_kalzium/106/
[00:28] -kubuntu-ci:#kubuntu-devel- Project yakkety_unstable_kdesdk-kioslaves build #66: STILL UNSTABLE in 20 min: http://kci.pangea.pub/job/yakkety_unstable_kdesdk-kioslaves/66/
[00:28] -kubuntu-ci:#kubuntu-devel- Project zesty_unstable_kdesdk-kioslaves build #12: FAILURE in 20 min: http://kci.pangea.pub/job/zesty_unstable_kdesdk-kioslaves/12/
[00:29] -kubuntu-ci:#kubuntu-devel- Project xenial_unstable_kdesdk-kioslaves build #105: STILL UNSTABLE in 20 min: http://kci.pangea.pub/job/xenial_unstable_kdesdk-kioslaves/105/
[00:29] -kubuntu-ci:#kubuntu-devel- Project zesty_unstable_kppp build #12: STILL UNSTABLE in 21 min: http://kci.pangea.pub/job/zesty_unstable_kppp/12/
[00:32] -kubuntu-ci:#kubuntu-devel- Project yakkety_unstable_kalzium build #48: STILL FAILING in 3 min 59 sec: http://kci.pangea.pub/job/yakkety_unstable_kalzium/48/
[00:33] -kubuntu-ci:#kubuntu-devel- Project xenial_unstable_kalzium build #107: STILL FAILING in 4 min 58 sec: http://kci.pangea.pub/job/xenial_unstable_kalzium/107/
[00:33] -kubuntu-ci:#kubuntu-devel- Project zesty_unstable_kalzium build #18: STILL FAILING in 6 min 1 sec: http://kci.pangea.pub/job/zesty_unstable_kalzium/18/
[00:37] -kubuntu-ci:#kubuntu-devel- Project xenial_unstable_kde-runtime build #246: STILL FAILING in 26 min: http://kci.pangea.pub/job/xenial_unstable_kde-runtime/246/
[00:37] -kubuntu-ci:#kubuntu-devel- Project zesty_unstable_extra-cmake-modules build #13: STILL UNSTABLE in 27 min: http://kci.pangea.pub/job/zesty_unstable_extra-cmake-modules/13/
[00:42] -kubuntu-ci:#kubuntu-devel- Project zesty_unstable_kmail build #9: STILL FAILING in 4 min 48 sec: http://kci.pangea.pub/job/zesty_unstable_kmail/9/
[00:45] -kubuntu-ci:#kubuntu-devel- Project zesty_unstable_okular build #11: STILL UNSTABLE in 16 min: http://kci.pangea.pub/job/zesty_unstable_okular/11/
[00:45] -kubuntu-ci:#kubuntu-devel- Project yakkety_unstable_kopete build #87: STILL UNSTABLE in 36 min: http://kci.pangea.pub/job/yakkety_unstable_kopete/87/
[00:45] -kubuntu-ci:#kubuntu-devel- Project xenial_unstable_okular build #41: STILL UNSTABLE in 16 min: http://kci.pangea.pub/job/xenial_unstable_okular/41/
[00:45] -kubuntu-ci:#kubuntu-devel- Project xenial_unstable_kopete build #109: STILL UNSTABLE in 36 min: http://kci.pangea.pub/job/xenial_unstable_kopete/109/
[00:45] -kubuntu-ci:#kubuntu-devel- Project zesty_unstable_kde-runtime build #27: STILL FAILING in 34 min: http://kci.pangea.pub/job/zesty_unstable_kde-runtime/27/
[00:45] -kubuntu-ci:#kubuntu-devel- Project yakkety_unstable_kde-runtime build #253: STILL FAILING in 34 min: http://kci.pangea.pub/job/yakkety_unstable_kde-runtime/253/
[00:45] -kubuntu-ci:#kubuntu-devel- Project zesty_unstable_kdesdk-kioslaves build #13: NOW UNSTABLE in 11 min: http://kci.pangea.pub/job/zesty_unstable_kdesdk-kioslaves/13/
[00:46] -kubuntu-ci:#kubuntu-devel- Project zesty_unstable_kopete build #12: STILL UNSTABLE in 37 min: http://kci.pangea.pub/job/zesty_unstable_kopete/12/
[00:51] -kubuntu-ci:#kubuntu-devel- Project zesty_unstable_kmail build #10: STILL FAILING in 3 min 53 sec: http://kci.pangea.pub/job/zesty_unstable_kmail/10/
[00:52] -kubuntu-ci:#kubuntu-devel- Project zesty_unstable_kcoreaddons build #11: STILL UNSTABLE in 14 min: http://kci.pangea.pub/job/zesty_unstable_kcoreaddons/11/
[00:53] -kubuntu-ci:#kubuntu-devel- Project yakkety_unstable_extra-cmake-modules build #144: STILL UNSTABLE in 15 min: http://kci.pangea.pub/job/yakkety_unstable_extra-cmake-modules/144/
[00:54] -kubuntu-ci:#kubuntu-devel- Project zesty_unstable_kitemmodels build #12: STILL UNSTABLE in 16 min: http://kci.pangea.pub/job/zesty_unstable_kitemmodels/12/
[00:59] -kubuntu-ci:#kubuntu-devel- Project xenial_unstable_extra-cmake-modules build #355: STILL UNSTABLE in 13 min: http://kci.pangea.pub/job/xenial_unstable_extra-cmake-modules/355/
[01:00] -kubuntu-ci:#kubuntu-devel- Project yakkety_unstable_okular build #119: STILL UNSTABLE in 21 min: http://kci.pangea.pub/job/yakkety_unstable_okular/119/
[01:08] -kubuntu-ci:#kubuntu-devel- Project xenial_unstable_kde-runtime build #247: STILL FAILING in 25 min: http://kci.pangea.pub/job/xenial_unstable_kde-runtime/247/
[01:12] -kubuntu-ci:#kubuntu-devel- Project yakkety_unstable_kmail build #9: STILL FAILING in 19 min: http://kci.pangea.pub/job/yakkety_unstable_kmail/9/
[01:15] -kubuntu-ci:#kubuntu-devel- Project zesty_unstable_kde-runtime build #28: STILL FAILING in 24 min: http://kci.pangea.pub/job/zesty_unstable_kde-runtime/28/
[01:15] -kubuntu-ci:#kubuntu-devel- Project yakkety_unstable_kde-runtime build #254: STILL FAILING in 24 min: http://kci.pangea.pub/job/yakkety_unstable_kde-runtime/254/
[01:20] -kubuntu-ci:#kubuntu-devel- Project xenial_unstable_kmail build #9: STILL FAILING in 21 min: http://kci.pangea.pub/job/xenial_unstable_kmail/9/
[01:21] -kubuntu-ci:#kubuntu-devel- Project yakkety_unstable_kmail build #10: STILL FAILING in 4 min 7 sec: http://kci.pangea.pub/job/yakkety_unstable_kmail/10/
[01:24] -kubuntu-ci:#kubuntu-devel- Project yakkety_unstable_kcoreaddons build #116: STILL UNSTABLE in 30 min: http://kci.pangea.pub/job/yakkety_unstable_kcoreaddons/116/
[01:29] -kubuntu-ci:#kubuntu-devel- Project xenial_unstable_kmail build #10: STILL FAILING in 3 min 47 sec: http://kci.pangea.pub/job/xenial_unstable_kmail/10/
[01:32] -kubuntu-ci:#kubuntu-devel- Project zesty_unstable_kcrash build #11: STILL UNSTABLE in 38 min: http://kci.pangea.pub/job/zesty_unstable_kcrash/11/
[01:32] -kubuntu-ci:#kubuntu-devel- Project xenial_unstable_kitemmodels build #310: STILL UNSTABLE in 32 min: http://kci.pangea.pub/job/xenial_unstable_kitemmodels/310/
[01:32] -kubuntu-ci:#kubuntu-devel- Project xenial_unstable_kcoreaddons build #286: STILL UNSTABLE in 32 min: http://kci.pangea.pub/job/xenial_unstable_kcoreaddons/286/
[01:33] -kubuntu-ci:#kubuntu-devel- Project yakkety_unstable_kitemmodels build #111: STILL UNSTABLE in 39 min: http://kci.pangea.pub/job/yakkety_unstable_kitemmodels/111/
[01:41] -kubuntu-ci:#kubuntu-devel- Project xenial_unstable_kcrash build #298: STILL UNSTABLE in 9 min 0 sec: http://kci.pangea.pub/job/xenial_unstable_kcrash/298/
[01:49] -kubuntu-ci:#kubuntu-devel- Project yakkety_unstable_kcrash build #171: STILL UNSTABLE in 16 min: http://kci.pangea.pub/job/yakkety_unstable_kcrash/171/
[02:06] -kubuntu-ci:#kubuntu-devel- Project zesty_unstable_kwallet build #8: STILL UNSTABLE in 17 min: http://kci.pangea.pub/job/zesty_unstable_kwallet/8/
[02:38] -kubuntu-ci:#kubuntu-devel- Project xenial_unstable_kwallet build #310: STILL UNSTABLE in 15 min: http://kci.pangea.pub/job/xenial_unstable_kwallet/310/
[02:38] -kubuntu-ci:#kubuntu-devel- Project yakkety_unstable_kwallet build #149: STILL UNSTABLE in 15 min: http://kci.pangea.pub/job/yakkety_unstable_kwallet/149/
[03:18] -kubuntu-ci:#kubuntu-devel- Project zesty_unstable_akonadi-mime build #7: STILL FAILING in 4 min 14 sec: http://kci.pangea.pub/job/zesty_unstable_akonadi-mime/7/
[03:27] -kubuntu-ci:#kubuntu-devel- Project zesty_unstable_akonadi-mime build #8: STILL FAILING in 4 min 29 sec: http://kci.pangea.pub/job/zesty_unstable_akonadi-mime/8/
[03:30] -kubuntu-ci:#kubuntu-devel- Project xenial_unstable_kactivitymanagerd build #125: STILL UNSTABLE in 11 min: http://kci.pangea.pub/job/xenial_unstable_kactivitymanagerd/125/
[03:36] -kubuntu-ci:#kubuntu-devel- Project zesty_unstable_spectacle build #9: STILL UNSTABLE in 13 min: http://kci.pangea.pub/job/zesty_unstable_spectacle/9/
[03:36] -kubuntu-ci:#kubuntu-devel- Project zesty_unstable_libkcompactdisc build #7: STILL UNSTABLE in 11 min: http://kci.pangea.pub/job/zesty_unstable_libkcompactdisc/7/
[03:43] -kubuntu-ci:#kubuntu-devel- Project zesty_unstable_okteta build #7: STILL UNSTABLE in 20 min: http://kci.pangea.pub/job/zesty_unstable_okteta/7/
[03:43] -kubuntu-ci:#kubuntu-devel- Project zesty_unstable_umbrello build #10: STILL UNSTABLE in 13 min: http://kci.pangea.pub/job/zesty_unstable_umbrello/10/
[03:48] -kubuntu-ci:#kubuntu-devel- Project zesty_unstable_cantor build #6: STILL UNSTABLE in 18 min: http://kci.pangea.pub/job/zesty_unstable_cantor/6/
[03:48] -kubuntu-ci:#kubuntu-devel- Project zesty_unstable_kde-baseapps build #11: STILL FAILING in 4 min 53 sec: http://kci.pangea.pub/job/zesty_unstable_kde-baseapps/11/
[03:49] -kubuntu-ci:#kubuntu-devel- Project xenial_unstable_spectacle build #123: STILL UNSTABLE in 9 min 5 sec: http://kci.pangea.pub/job/xenial_unstable_spectacle/123/
[03:52] -kubuntu-ci:#kubuntu-devel- Project zesty_unstable_kgpg build #9: STILL FAILING in 3 min 15 sec: http://kci.pangea.pub/job/zesty_unstable_kgpg/9/
[03:54] -kubuntu-ci:#kubuntu-devel- Project zesty_unstable_kstars build #10: STILL UNSTABLE in 24 min: http://kci.pangea.pub/job/zesty_unstable_kstars/10/
[03:54] -kubuntu-ci:#kubuntu-devel- Project yakkety_unstable_umbrello build #98: STILL UNSTABLE in 18 min: http://kci.pangea.pub/job/yakkety_unstable_umbrello/98/
[03:55] -kubuntu-ci:#kubuntu-devel- Project zesty_unstable_ktp-common-internals build #6: STILL UNSTABLE in 18 min: http://kci.pangea.pub/job/zesty_unstable_ktp-common-internals/6/
[03:57] -kubuntu-ci:#kubuntu-devel- Project zesty_unstable_pim-sieve-editor build #7: STILL FAILING in 1 min 24 sec: http://kci.pangea.pub/job/zesty_unstable_pim-sieve-editor/7/
[03:58] -kubuntu-ci:#kubuntu-devel- Project zesty_unstable_kde-baseapps build #12: STILL FAILING in 4 min 51 sec: http://kci.pangea.pub/job/zesty_unstable_kde-baseapps/12/
[03:59] -kubuntu-ci:#kubuntu-devel- Project xenial_unstable_libkleo build #51: STILL FAILING in 3 min 58 sec: http://kci.pangea.pub/job/xenial_unstable_libkleo/51/
[04:00] -kubuntu-ci:#kubuntu-devel- Project zesty_unstable_pimcommon build #5: STILL FAILING in 4 min 35 sec: http://kci.pangea.pub/job/zesty_unstable_pimcommon/5/
[04:01] -kubuntu-ci:#kubuntu-devel- Project xenial_unstable_kstars build #280: STILL UNSTABLE in 24 min: http://kci.pangea.pub/job/xenial_unstable_kstars/280/
[04:01] -kubuntu-ci:#kubuntu-devel- Project yakkety_unstable_kstars build #149: STILL UNSTABLE in 25 min: http://kci.pangea.pub/job/yakkety_unstable_kstars/149/
[04:01] -kubuntu-ci:#kubuntu-devel- Project zesty_unstable_discover build #17: STILL FAILING in 5 min 23 sec: http://kci.pangea.pub/job/zesty_unstable_discover/17/
[04:01] -kubuntu-ci:#kubuntu-devel- Project zesty_unstable_kgpg build #10: STILL FAILING in 4 min 33 sec: http://kci.pangea.pub/job/zesty_unstable_kgpg/10/
[04:03] -kubuntu-ci:#kubuntu-devel- Project zesty_unstable_pim-sieve-editor build #8: STILL FAILING in 44 sec: http://kci.pangea.pub/job/zesty_unstable_pim-sieve-editor/8/
[04:06] -kubuntu-ci:#kubuntu-devel- Project yakkety_unstable_libkleo build #63: STILL FAILING in 4 min 38 sec: http://kci.pangea.pub/job/yakkety_unstable_libkleo/63/
[04:06] -kubuntu-ci:#kubuntu-devel- Project zesty_unstable_plasma-mediacenter build #4: FAILURE in 10 min: http://kci.pangea.pub/job/zesty_unstable_plasma-mediacenter/4/
[04:08] -kubuntu-ci:#kubuntu-devel- Project zesty_unstable_plasma-pa build #4: STILL FAILING in 12 min: http://kci.pangea.pub/job/zesty_unstable_plasma-pa/4/
[04:08] -kubuntu-ci:#kubuntu-devel- Project zesty_unstable_plasma-integration build #6: STILL UNSTABLE in 12 min: http://kci.pangea.pub/job/zesty_unstable_plasma-integration/6/
[04:08] -kubuntu-ci:#kubuntu-devel- Project zesty_unstable_ktp-auth-handler build #6: STILL UNSTABLE in 13 min: http://kci.pangea.pub/job/zesty_unstable_ktp-auth-handler/6/
[04:09] -kubuntu-ci:#kubuntu-devel- Project xenial_unstable_libkleo build #52: STILL FAILING in 4 min 42 sec: http://kci.pangea.pub/job/xenial_unstable_libkleo/52/
[04:09] -kubuntu-ci:#kubuntu-devel- Project zesty_unstable_pimcommon build #6: STILL FAILING in 3 min 48 sec: http://kci.pangea.pub/job/zesty_unstable_pimcommon/6/
[04:10] -kubuntu-ci:#kubuntu-devel- Project zesty_unstable_discover build #18: STILL FAILING in 4 min 0 sec: http://kci.pangea.pub/job/zesty_unstable_discover/18/
[04:14] -kubuntu-ci:#kubuntu-devel- Project yakkety_unstable_ktp-auth-handler build #151: STILL UNSTABLE in 12 min: http://kci.pangea.pub/job/yakkety_unstable_ktp-auth-handler/151/
[04:14] -kubuntu-ci:#kubuntu-devel- Project xenial_unstable_ktp-auth-handler build #198: STILL UNSTABLE in 12 min: http://kci.pangea.pub/job/xenial_unstable_ktp-auth-handler/198/
[04:18] -kubuntu-ci:#kubuntu-devel- Project zesty_unstable_libgravatar build #5: STILL FAILING in 9 min 20 sec: http://kci.pangea.pub/job/zesty_unstable_libgravatar/5/
[04:19] -kubuntu-ci:#kubuntu-devel- Project zesty_unstable_marble build #5: STILL FAILING in 23 min: http://kci.pangea.pub/job/zesty_unstable_marble/5/
[04:20] -kubuntu-ci:#kubuntu-devel- Project zesty_unstable_libksieve build #7: STILL FAILING in 11 min: http://kci.pangea.pub/job/zesty_unstable_libksieve/7/
[04:20] -kubuntu-ci:#kubuntu-devel- Project yakkety_unstable_libkleo build #64: STILL FAILING in 9 min 41 sec: http://kci.pangea.pub/job/yakkety_unstable_libkleo/64/
[04:21] -kubuntu-ci:#kubuntu-devel- Project yakkety_unstable_plasma-framework build #167: STILL FAILING in 18 min: http://kci.pangea.pub/job/yakkety_unstable_plasma-framework/167/
[04:23] -kubuntu-ci:#kubuntu-devel- Project xenial_unstable_plasma-mediacenter build #202: STILL FAILING in 8 min 13 sec: http://kci.pangea.pub/job/xenial_unstable_plasma-mediacenter/202/
[04:25] -kubuntu-ci:#kubuntu-devel- Project zesty_unstable_plasma-mediacenter build #5: STILL FAILING in 13 min: http://kci.pangea.pub/job/zesty_unstable_plasma-mediacenter/5/
[04:26] -kubuntu-ci:#kubuntu-devel- Project yakkety_unstable_kde-baseapps build #123: STILL FAILING in 4 min 52 sec: http://kci.pangea.pub/job/yakkety_unstable_kde-baseapps/123/
[04:27] -kubuntu-ci:#kubuntu-devel- Project zesty_unstable_libgravatar build #6: STILL FAILING in 3 min 49 sec: http://kci.pangea.pub/job/zesty_unstable_libgravatar/6/
[04:28] -kubuntu-ci:#kubuntu-devel- Project xenial_unstable_plasma-integration build #22: STILL UNSTABLE in 13 min: http://kci.pangea.pub/job/xenial_unstable_plasma-integration/22/
[04:28] -kubuntu-ci:#kubuntu-devel- Project xenial_unstable_peruse build #5: STILL UNSTABLE in 13 min: http://kci.pangea.pub/job/xenial_unstable_peruse/5/
[04:28] -kubuntu-ci:#kubuntu-devel- Project zesty_unstable_plasma-pa build #5: STILL FAILING in 15 min: http://kci.pangea.pub/job/zesty_unstable_plasma-pa/5/
[04:29] -kubuntu-ci:#kubuntu-devel- Project zesty_unstable_libksieve build #8: STILL FAILING in 3 min 50 sec: http://kci.pangea.pub/job/zesty_unstable_libksieve/8/
[04:31] -kubuntu-ci:#kubuntu-devel- Project zesty_unstable_messagelib build #9: STILL FAILING in 4 min 0 sec: http://kci.pangea.pub/job/zesty_unstable_messagelib/9/
[04:32] -kubuntu-ci:#kubuntu-devel- Project xenial_unstable_kde-baseapps build #120: STILL FAILING in 4 min 54 sec: http://kci.pangea.pub/job/xenial_unstable_kde-baseapps/120/
[04:33] -kubuntu-ci:#kubuntu-devel- Project xenial_unstable_discover build #33: STILL FAILING in 5 min 15 sec: http://kci.pangea.pub/job/xenial_unstable_discover/33/
[04:34] -kubuntu-ci:#kubuntu-devel- Project yakkety_unstable_cantor build #103: STILL UNSTABLE in 26 min: http://kci.pangea.pub/job/yakkety_unstable_cantor/103/
[04:34] -kubuntu-ci:#kubuntu-devel- Project xenial_unstable_cantor build #208: STILL UNSTABLE in 25 min: http://kci.pangea.pub/job/xenial_unstable_cantor/208/
[04:34] -kubuntu-ci:#kubuntu-devel- Project xenial_unstable_marble build #17: STILL FAILING in 19 min: http://kci.pangea.pub/job/xenial_unstable_marble/17/
[04:35] -kubuntu-ci:#kubuntu-devel- Project xenial_unstable_plasma-mediacenter build #203: STILL FAILING in 6 min 52 sec: http://kci.pangea.pub/job/xenial_unstable_plasma-mediacenter/203/
[04:36] -kubuntu-ci:#kubuntu-devel- Project yakkety_unstable_kde-baseapps build #124: STILL FAILING in 4 min 50 sec: http://kci.pangea.pub/job/yakkety_unstable_kde-baseapps/124/
[04:37] -kubuntu-ci:#kubuntu-devel- Project yakkety_unstable_kgpg build #107: STILL FAILING in 2 min 50 sec: http://kci.pangea.pub/job/yakkety_unstable_kgpg/107/
[04:40] -kubuntu-ci:#kubuntu-devel- Project zesty_unstable_messagelib build #10: STILL FAILING in 3 min 55 sec: http://kci.pangea.pub/job/zesty_unstable_messagelib/10/
[04:41] -kubuntu-ci:#kubuntu-devel- Project zesty_unstable_kdepim-addons build #5: STILL FAILING in 44 sec: http://kci.pangea.pub/job/zesty_unstable_kdepim-addons/5/
[04:42] -kubuntu-ci:#kubuntu-devel- Project yakkety_unstable_plasma-framework build #168: STILL FAILING in 15 min: http://kci.pangea.pub/job/yakkety_unstable_plasma-framework/168/
[04:42] -kubuntu-ci:#kubuntu-devel- Project xenial_unstable_discover build #34: STILL FAILING in 3 min 53 sec: http://kci.pangea.pub/job/xenial_unstable_discover/34/
[04:42] -kubuntu-ci:#kubuntu-devel- Project xenial_unstable_kde-baseapps build #121: STILL FAILING in 4 min 46 sec: http://kci.pangea.pub/job/xenial_unstable_kde-baseapps/121/
[04:43] -kubuntu-ci:#kubuntu-devel- Project zesty_unstable_marble build #6: STILL FAILING in 18 min: http://kci.pangea.pub/job/zesty_unstable_marble/6/
[04:44] -kubuntu-ci:#kubuntu-devel- Project zesty_unstable_kwin build #7: STILL UNSTABLE in 35 min: http://kci.pangea.pub/job/zesty_unstable_kwin/7/
[04:45] -kubuntu-ci:#kubuntu-devel- Project xenial_unstable_kgpg build #107: STILL FAILING in 3 min 49 sec: http://kci.pangea.pub/job/xenial_unstable_kgpg/107/
[04:46] -kubuntu-ci:#kubuntu-devel- Project yakkety_unstable_kgpg build #108: STILL FAILING in 4 min 2 sec: http://kci.pangea.pub/job/yakkety_unstable_kgpg/108/
[04:47] -kubuntu-ci:#kubuntu-devel- Project zesty_unstable_kdepim-addons build #6: STILL FAILING in 44 sec: http://kci.pangea.pub/job/zesty_unstable_kdepim-addons/6/
[04:48] -kubuntu-ci:#kubuntu-devel- Project yakkety_unstable_plasma-mediacenter build #116: STILL FAILING in 6 min 9 sec: http://kci.pangea.pub/job/yakkety_unstable_plasma-mediacenter/116/
[04:53] -kubuntu-ci:#kubuntu-devel- Project xenial_unstable_kgpg build #108: STILL FAILING in 2 min 45 sec: http://kci.pangea.pub/job/xenial_unstable_kgpg/108/
[04:54] -kubuntu-ci:#kubuntu-devel- Project yakkety_unstable_plasma-pa build #110: STILL FAILING in 12 min: http://kci.pangea.pub/job/yakkety_unstable_plasma-pa/110/
[04:54] -kubuntu-ci:#kubuntu-devel- Project xenial_unstable_akonadi-contacts build #56: STILL UNSTABLE in 12 min: http://kci.pangea.pub/job/xenial_unstable_akonadi-contacts/56/
[04:56] -kubuntu-ci:#kubuntu-devel- Project xenial_unstable_marble build #18: STILL FAILING in 16 min: http://kci.pangea.pub/job/xenial_unstable_marble/18/
[04:57] -kubuntu-ci:#kubuntu-devel- Project yakkety_unstable_discover build #25: STILL FAILING in 3 min 3 sec: http://kci.pangea.pub/job/yakkety_unstable_discover/25/
[04:59] -kubuntu-ci:#kubuntu-devel- Project yakkety_unstable_marble build #17: STILL FAILING in 16 min: http://kci.pangea.pub/job/yakkety_unstable_marble/17/
[04:59] -kubuntu-ci:#kubuntu-devel- Project yakkety_unstable_plasma-mediacenter build #117: STILL FAILING in 5 min 48 sec: http://kci.pangea.pub/job/yakkety_unstable_plasma-mediacenter/117/
[05:01] -kubuntu-ci:#kubuntu-devel- Yippee, build fixed!
[05:01] -kubuntu-ci:#kubuntu-devel- Project yakkety_unstable_breeze build #147: FIXED in 18 min: http://kci.pangea.pub/job/yakkety_unstable_breeze/147/
[05:01] -kubuntu-ci:#kubuntu-devel- Project yakkety_unstable_akonadi-calendar build #19: STILL UNSTABLE in 13 min: http://kci.pangea.pub/job/yakkety_unstable_akonadi-calendar/19/
[05:03] -kubuntu-ci:#kubuntu-devel- Project yakkety_unstable_pim-sieve-editor build #7: STILL FAILING in 1 min 14 sec: http://kci.pangea.pub/job/yakkety_unstable_pim-sieve-editor/7/
[05:04] -kubuntu-ci:#kubuntu-devel- Project xenial_unstable_kwin build #30: STILL UNSTABLE in 35 min: http://kci.pangea.pub/job/xenial_unstable_kwin/30/
[05:05] -kubuntu-ci:#kubuntu-devel- Project yakkety_unstable_discover build #26: STILL FAILING in 2 min 56 sec: http://kci.pangea.pub/job/yakkety_unstable_discover/26/
[05:07] -kubuntu-ci:#kubuntu-devel- Project yakkety_unstable_plasma-pa build #111: STILL FAILING in 7 min 53 sec: http://kci.pangea.pub/job/yakkety_unstable_plasma-pa/111/
[05:07] -kubuntu-ci:#kubuntu-devel- Project xenial_unstable_pimcommon build #7: STILL FAILING in 13 min: http://kci.pangea.pub/job/xenial_unstable_pimcommon/7/
[05:08] -kubuntu-ci:#kubuntu-devel- Project xenial_unstable_pim-sieve-editor build #7: STILL FAILING in 38 sec: http://kci.pangea.pub/job/xenial_unstable_pim-sieve-editor/7/
[05:08] -kubuntu-ci:#kubuntu-devel- Project yakkety_unstable_pim-sieve-editor build #8: STILL FAILING in 39 sec: http://kci.pangea.pub/job/yakkety_unstable_pim-sieve-editor/8/
[05:14] -kubuntu-ci:#kubuntu-devel- Project xenial_unstable_pim-sieve-editor build #8: STILL FAILING in 36 sec: http://kci.pangea.pub/job/xenial_unstable_pim-sieve-editor/8/
[05:15] -kubuntu-ci:#kubuntu-devel- Project yakkety_unstable_plasma-integration build #21: STILL UNSTABLE in 13 min: http://kci.pangea.pub/job/yakkety_unstable_plasma-integration/21/
[05:19] -kubuntu-ci:#kubuntu-devel- Project yakkety_unstable_pimcommon build #7: STILL FAILING in 11 min: http://kci.pangea.pub/job/yakkety_unstable_pimcommon/7/
[05:21] -kubuntu-ci:#kubuntu-devel- Project yakkety_unstable_marble build #18: STILL FAILING in 17 min: http://kci.pangea.pub/job/yakkety_unstable_marble/18/
[05:23] -kubuntu-ci:#kubuntu-devel- Project zesty_unstable_kdeplasma-addons build #3: STILL FAILING in 8 min 58 sec: http://kci.pangea.pub/job/zesty_unstable_kdeplasma-addons/3/
[05:25] -kubuntu-ci:#kubuntu-devel- Project xenial_unstable_pimcommon build #8: STILL FAILING in 12 min: http://kci.pangea.pub/job/xenial_unstable_pimcommon/8/
[05:27] -kubuntu-ci:#kubuntu-devel- Project yakkety_unstable_kwin build #31: STILL UNSTABLE in 25 min: http://kci.pangea.pub/job/yakkety_unstable_kwin/31/
[05:30] -kubuntu-ci:#kubuntu-devel- Project xenial_unstable_kdeplasma-addons build #10: STILL FAILING in 5 min 52 sec: http://kci.pangea.pub/job/xenial_unstable_kdeplasma-addons/10/
[05:35] -kubuntu-ci:#kubuntu-devel- Project zesty_unstable_kdeplasma-addons build #4: STILL FAILING in 6 min 55 sec: http://kci.pangea.pub/job/zesty_unstable_kdeplasma-addons/4/
[05:39] -kubuntu-ci:#kubuntu-devel- Project yakkety_unstable_pimcommon build #8: STILL FAILING in 14 min: http://kci.pangea.pub/job/yakkety_unstable_pimcommon/8/
[05:41] -kubuntu-ci:#kubuntu-devel- Project xenial_unstable_messagelib build #23: STILL FAILING in 5 min 24 sec: http://kci.pangea.pub/job/xenial_unstable_messagelib/23/
[05:41] -kubuntu-ci:#kubuntu-devel- Project xenial_unstable_kdeplasma-addons build #11: STILL FAILING in 5 min 50 sec: http://kci.pangea.pub/job/xenial_unstable_kdeplasma-addons/11/
[05:52] -kubuntu-ci:#kubuntu-devel- Project xenial_unstable_messagelib build #24: STILL FAILING in 6 min 28 sec: http://kci.pangea.pub/job/xenial_unstable_messagelib/24/
[05:53] -kubuntu-ci:#kubuntu-devel- Project xenial_unstable_kdepim-addons build #88: STILL FAILING in 38 sec: http://kci.pangea.pub/job/xenial_unstable_kdepim-addons/88/
[05:58] -kubuntu-ci:#kubuntu-devel- Project xenial_unstable_kdepim-addons build #89: STILL FAILING in 37 sec: http://kci.pangea.pub/job/xenial_unstable_kdepim-addons/89/
[06:02] -kubuntu-ci:#kubuntu-devel- Project yakkety_unstable_messagelib build #25: STILL FAILING in 5 min 32 sec: http://kci.pangea.pub/job/yakkety_unstable_messagelib/25/
[06:03] -kubuntu-ci:#kubuntu-devel- Project yakkety_unstable_kdeplasma-addons build #13: STILL FAILING in 5 min 55 sec: http://kci.pangea.pub/job/yakkety_unstable_kdeplasma-addons/13/
[06:13] -kubuntu-ci:#kubuntu-devel- Project yakkety_unstable_messagelib build #26: STILL FAILING in 5 min 28 sec: http://kci.pangea.pub/job/yakkety_unstable_messagelib/26/
[06:13] -kubuntu-ci:#kubuntu-devel- Project yakkety_unstable_kdepim-addons build #21: STILL FAILING in 41 sec: http://kci.pangea.pub/job/yakkety_unstable_kdepim-addons/21/
[06:14] -kubuntu-ci:#kubuntu-devel- Project yakkety_unstable_kdeplasma-addons build #14: STILL FAILING in 5 min 51 sec: http://kci.pangea.pub/job/yakkety_unstable_kdeplasma-addons/14/
[06:19] -kubuntu-ci:#kubuntu-devel- Project yakkety_unstable_kdepim-addons build #22: STILL FAILING in 1 min 11 sec: http://kci.pangea.pub/job/yakkety_unstable_kdepim-addons/22/
[10:36] <BluesKaj> Hey folks
 Hi there BluesKaj
[10:41] <BluesKaj> HI Sick_Rimmit
[11:40] <clivejo> From #kubuntu - <Sevish> sometimes when I boot, I get the kubuntu logo, then it will disappear and I get a black screen with a underscore in the top corner
[11:41] <clivejo> strangely Ive been getting this in zesty this past few mornings
[11:42] <clivejo> seems to be only a cold boot, rebooting from the black screen allows me to login and use zesty as normal
[11:42] <acheronuk> this zesty just stays on, so only think I've booted it once!
[11:42] <clivejo> I turn off every night
[11:42] <clivejo> and boot in the morning
[11:44] <acheronuk> unless rebooting for a new kernel, suspend to RAM is about the most I do
[11:45] <clivejo> would you try it for a few days?
[11:46] <clivejo> strange why its only started recently
[11:46] <clivejo> and why it would be on 16.04 
[11:46] <clivejo> Im on 17.04 and expect weird stuff!
[11:48] <acheronuk> I can give it a go, but even if I can replicate I'm not sure how relevant that would be.
[11:48] <clivejo> D.... I.... S..... C..... O.....
[11:49] <clivejo> at least Ill know its not something locally 
[11:49] <clivejo> with nvidia drivers and old hardware
[11:53] <clivejo> well its thursday, Ill do my upgrade 
[11:53] <clivejo> 310 packages to upgrade
[11:53] <acheronuk> 143 to upgrade, 5 to newly install, 0 to remove and 3 not to upgrade.
[11:54] <acheronuk> since yesterday!!!
[11:55]  * acheronuk goes to shutdown, then try a boot
[11:55] <clivejo> !info calligraflow-data zesty
[11:56] <clivejo> must be out of proposed
[11:56] <clivejo> oh ubuntu2
[11:57] <clivejo> No change rebuild against boost1.62.
[12:00] <acheronuk> clivejo: full shutdown, wait 10s, then boot = just fine. very rapid login, no hang or black screen, or glitch
 *splits and hisses @acheronuk *
[12:05] <clivejo> Im still downloading
[12:06] <clivejo> how this can be sold as broadband is beyond me
[12:09] <clivejo> acheronuk: would you mind grabbing that fixme file from my Linode container?
[12:10] <BluesKaj_> I have a slow adsl , but it's just fast enough to keep me from using the cable co's ripoff 50Mb for 80bucks /mos  + caps
[12:10] <clivejo> Im on go slow until these updates download
[12:16] <acheronuk> got it
[12:17] <clivejo> can you parse it for missing unstable branches
[12:18] <acheronuk> #<Project::GitNoBranchError: origin/kubuntu_unstable>
[12:18] <acheronuk> new_project({:branch=>"kubuntu_unstable", :name=>"kdelibs4support", :component=>"launchpadgit", :url_base=>"https://git.launchpad.net/~kubuntu-packagers//"})
[12:19] <acheronuk> whoops. not quite
[12:19] <clivejo> looked to be more than one
[12:19] <clivejo> can you pastebin them all
[12:20] <acheronuk> kde4libs, kdenetwork-strigi-analyzers, kdesdk-strigi-analyzers
[12:22] <acheronuk> http://paste.ubuntu.com/23420499/
[12:26] <soee> ahoneybun: https://pbs.twimg.com/media/CwVd9_QW8AIrxLK.jpg
[12:30] <clivejo> acheronuk: can you make an unstable branch here - https://git.launchpad.net/~kubuntu-packagers/kubuntu-packaging/+git/kdenetwork-strigi-analyzers
[12:32] <clivejo> and https://git.launchpad.net/~kubuntu-packagers/kubuntu-packaging/+git/kdesdk-strigi-analyzers
[12:35] <clivejo> the kde4libs I dont know what to do about that!
[12:36] <clivejo> sooner it dies the better :P
 Do we even need it in CI?
[13:01] <acheronuk> clivejo: unstable from zesty archive for example?
[13:02] <acheronuk> clivejo: I would guess we don't need kde4libs
[14:01] -kubuntu-ci:#kubuntu-devel- Project merger_kdesdk-strigi-analyzers build #1: FAILURE in 12 sec: http://kci.pangea.pub/job/merger_kdesdk-strigi-analyzers/1/
[14:01] -kubuntu-ci:#kubuntu-devel- Project merger_kdesdk-strigi-analyzers build #2: STILL FAILING in 10 sec: http://kci.pangea.pub/job/merger_kdesdk-strigi-analyzers/2/
[14:07] -kubuntu-ci:#kubuntu-devel- Project xenial_unstable_krita build #1: FAILURE in 9 min 1 sec: http://kci.pangea.pub/job/xenial_unstable_krita/1/
[14:08] -kubuntu-ci:#kubuntu-devel- Project zesty_unstable_krita build #1: FAILURE in 9 min 32 sec: http://kci.pangea.pub/job/zesty_unstable_krita/1/
[14:08] -kubuntu-ci:#kubuntu-devel- Project yakkety_unstable_krita build #1: FAILURE in 9 min 42 sec: http://kci.pangea.pub/job/yakkety_unstable_krita/1/
[14:09] <clivejo>  sbuild-build-depends-krita-dummy : Depends: libkf5kio-dev (>= 5.7.0) but it is not installable
[14:10] <clivejo> another 3rd party package failing over the naming 
[14:19] -kubuntu-ci:#kubuntu-devel- Project zesty_unstable_krita build #2: STILL FAILING in 5 min 48 sec: http://kci.pangea.pub/job/zesty_unstable_krita/2/
[14:21] -kubuntu-ci:#kubuntu-devel- Project yakkety_unstable_krita build #2: STILL FAILING in 8 min 11 sec: http://kci.pangea.pub/job/yakkety_unstable_krita/2/
[14:24] -kubuntu-ci:#kubuntu-devel- Project xenial_unstable_krita build #2: STILL FAILING in 11 min: http://kci.pangea.pub/job/xenial_unstable_krita/2/
[15:11] -kubuntu-ci:#kubuntu-devel- Project yakkety_unstable_krita build #3: STILL FAILING in 49 min: http://kci.pangea.pub/job/yakkety_unstable_krita/3/
[15:14] -kubuntu-ci:#kubuntu-devel- Project xenial_unstable_krita build #3: STILL FAILING in 49 min: http://kci.pangea.pub/job/xenial_unstable_krita/3/
[15:18] -kubuntu-ci:#kubuntu-devel- Project zesty_unstable_krita build #3: STILL FAILING in 56 min: http://kci.pangea.pub/job/zesty_unstable_krita/3/
 Hai
 What's new?
[15:49] <acheronuk> things that are not old
[16:09] -kubuntu-ci:#kubuntu-devel- Project zesty_unstable_krita build #4: STILL FAILING in 46 min: http://kci.pangea.pub/job/zesty_unstable_krita/4/
[16:10] <clivejo> # already provided by breeze
[16:10] <clivejo> rm -rv debian/tmp/usr/share/color-schemes/Breeze*.colors
[16:10] <clivejo> rm: cannot remove 'debian/tmp/usr/share/color-schemes/Breeze*.colors': No such file or directory
[16:12] -kubuntu-ci:#kubuntu-devel- Project xenial_unstable_krita build #4: STILL FAILING in 53 min: http://kci.pangea.pub/job/xenial_unstable_krita/4/
[16:15] -kubuntu-ci:#kubuntu-devel- Project yakkety_unstable_krita build #4: ABORTED in 59 min: http://kci.pangea.pub/job/yakkety_unstable_krita/4/
[16:18] <apol> hey everyone, I bring you a bug you might want to look into https://bugs.kde.org/show_bug.cgi?id=372011
[16:27] <santa_> [15:09] <clivejo>  sbuild-build-depends-krita-dummy : Depends: libkf5kio-dev (>= 5.7.0) but it is not installable
[16:27] <santa_> [15:10] <clivejo> another 3rd party package failing over the naming 
[16:27] <santa_> did you see trello this morning?
[16:29] <santa_> https://paste.kde.org/pwvn1x0xi
[16:29] <santa_> so they are just 4 packages to merge to solve that
[16:33] <santa_> apol: indeed appstreamcli search vlc doesn't return info about vlc @ yakkety, goind to test on zesty...
[16:34] <santa_> * going
[16:34] <apol> thanks santa_!! :)
[17:01] <clivejo> cant see vlc in discover running on zesty
[17:02] <BluesKaj_>  clivejo it's in the original muon
[17:02] <BluesKaj_> on zesty
[17:02] <clivejo> BluesKaj_: yes, but thats not appstream
[17:04] <BluesKaj_> discover doesn't see a lot of packages in the repos IMEi
[17:04] <clivejo> because the appstream data needs to be provided
[17:09] <clivejo> discover is a cross platform software centre
[17:10] <clivejo> it doesnt know that you are on a debian based system
[17:14] <BluesKaj_> clivejo, why would the devs use a non OS specific package manager?
[17:14] <clivejo> KDE is on many distros
[17:15] <clivejo> to have the same user experience across them all
[17:16] <clivejo> Discover isnt a package manager now
[17:17] <clivejo> it just makes calls to the underlying system to install the packages needed to access a certain application
[17:18] <clivejo> BluesKaj_: do you watch the Podcast?
[17:19] <BluesKaj_> clivejo, well, I'm guilty of missing those 
[17:20] <clivejo> https://www.youtube.com/watch?v=O6iDMqzcSao
[17:24] <clivejo> Ovi needs a mic
[17:24] <clivejo> shoving a phone in peoples faces looks bad!
[17:27] -kubuntu-ci:#kubuntu-devel- Project xenial_unstable_krita build #5: NOW UNSTABLE in 1 hr 7 min: http://kci.pangea.pub/job/xenial_unstable_krita/5/
[17:27] -kubuntu-ci:#kubuntu-devel- Project zesty_unstable_krita build #5: NOW UNSTABLE in 1 hr 7 min: http://kci.pangea.pub/job/zesty_unstable_krita/5/
[17:27] <clivejo> acheronuk: ^^^
[17:29] <acheronuk> on that subject, this came up on mailing lists earlier https://community.kde.org/HowToAppStream
[17:31] <clivejo> should we be injecting missing ones in packaging?
[17:32] -kubuntu-ci:#kubuntu-devel- Project yakkety_unstable_sonnet build #122: FAILURE in 16 min: http://kci.pangea.pub/job/yakkety_unstable_sonnet/122/
[17:32] -kubuntu-ci:#kubuntu-devel- Project zesty_unstable_sonnet build #12: FAILURE in 16 min: http://kci.pangea.pub/job/zesty_unstable_sonnet/12/
[17:33] -kubuntu-ci:#kubuntu-devel- Project xenial_unstable_sonnet build #300: FAILURE in 16 min: http://kci.pangea.pub/job/xenial_unstable_sonnet/300/
[17:34] <acheronuk> not sure. maybe you could make the case for it on apps that don't have it and are important for our users to be able to discover. in general though I'd say it responsibility of upstream
[17:35] <clivejo> must ask Matthias
[17:36] <clivejo> he is usually in here
[17:39] <clivejo> did anyone try the Kubuntu ISO today?
[17:44] -kubuntu-ci:#kubuntu-devel- Project yakkety_unstable_sonnet build #123: STILL FAILING in 11 min: http://kci.pangea.pub/job/yakkety_unstable_sonnet/123/
[17:50] -kubuntu-ci:#kubuntu-devel- Project merger_kio build #841: FAILURE in 15 sec: http://kci.pangea.pub/job/merger_kio/841/
[17:51] -kubuntu-ci:#kubuntu-devel- Project yakkety_unstable_krita build #5: NOW UNSTABLE in 1 hr 31 min: http://kci.pangea.pub/job/yakkety_unstable_krita/5/
[17:52] -kubuntu-ci:#kubuntu-devel- Project xenial_unstable_sonnet build #301: STILL FAILING in 14 min: http://kci.pangea.pub/job/xenial_unstable_sonnet/301/
[17:52] -kubuntu-ci:#kubuntu-devel- Project zesty_unstable_sonnet build #13: STILL FAILING in 14 min: http://kci.pangea.pub/job/zesty_unstable_sonnet/13/
[18:07] -kubuntu-ci:#kubuntu-devel- Project yakkety_unstable_sonnet build #124: STILL FAILING in 18 min: http://kci.pangea.pub/job/yakkety_unstable_sonnet/124/
[18:14] -kubuntu-ci:#kubuntu-devel- Yippee, build fixed!
[18:14] -kubuntu-ci:#kubuntu-devel- Project xenial_unstable_sonnet build #302: FIXED in 15 min: http://kci.pangea.pub/job/xenial_unstable_sonnet/302/
[18:15] -kubuntu-ci:#kubuntu-devel- Yippee, build fixed!
[18:15] -kubuntu-ci:#kubuntu-devel- Project zesty_unstable_sonnet build #14: FIXED in 15 min: http://kci.pangea.pub/job/zesty_unstable_sonnet/14/
[18:22] -kubuntu-ci:#kubuntu-devel- Yippee, build fixed!
[18:22] -kubuntu-ci:#kubuntu-devel- Project yakkety_unstable_sonnet build #125: FIXED in 14 min: http://kci.pangea.pub/job/yakkety_unstable_sonnet/125/
[18:42] -kubuntu-ci:#kubuntu-devel- Project zesty_unstable_plasma-framework build #7: FAILURE in 4 min 17 sec: http://kci.pangea.pub/job/zesty_unstable_plasma-framework/7/
[18:42] -kubuntu-ci:#kubuntu-devel- Project xenial_unstable_plasma-framework build #305: FAILURE in 4 min 35 sec: http://kci.pangea.pub/job/xenial_unstable_plasma-framework/305/
[18:49] -kubuntu-ci:#kubuntu-devel- Project yakkety_unstable_plasma-framework build #169: STILL FAILING in 4 min 39 sec: http://kci.pangea.pub/job/yakkety_unstable_plasma-framework/169/
[18:51] -kubuntu-ci:#kubuntu-devel- Project xenial_unstable_plasma-framework build #306: STILL FAILING in 3 min 6 sec: http://kci.pangea.pub/job/xenial_unstable_plasma-framework/306/
[18:51] -kubuntu-ci:#kubuntu-devel- Project zesty_unstable_plasma-framework build #8: STILL FAILING in 3 min 57 sec: http://kci.pangea.pub/job/zesty_unstable_plasma-framework/8/
[18:54] <santa_> clivejo: ping?
[18:58] -kubuntu-ci:#kubuntu-devel- Project yakkety_unstable_plasma-framework build #170: STILL FAILING in 3 min 57 sec: http://kci.pangea.pub/job/yakkety_unstable_plasma-framework/170/
[19:03] -kubuntu-ci:#kubuntu-devel- Yippee, build fixed!
[19:03] -kubuntu-ci:#kubuntu-devel- Project merger_kio build #842: FIXED in 22 sec: http://kci.pangea.pub/job/merger_kio/842/
[19:14] -kubuntu-ci:#kubuntu-devel- Yippee, build fixed!
[19:14] -kubuntu-ci:#kubuntu-devel- Project merger_kdesdk-strigi-analyzers build #3: FIXED in 18 sec: http://kci.pangea.pub/job/merger_kdesdk-strigi-analyzers/3/
[19:35] -kubuntu-ci:#kubuntu-devel- Project yakkety_unstable_kio build #185: UNSTABLE in 31 min: http://kci.pangea.pub/job/yakkety_unstable_kio/185/
[19:57] -kubuntu-ci:#kubuntu-devel- Project yakkety_unstable_kio build #186: STILL UNSTABLE in 21 min: http://kci.pangea.pub/job/yakkety_unstable_kio/186/
[19:59] -kubuntu-ci:#kubuntu-devel- Yippee, build fixed!
[19:59] -kubuntu-ci:#kubuntu-devel- Project zesty_unstable_plasma-framework build #9: FIXED in 23 min: http://kci.pangea.pub/job/zesty_unstable_plasma-framework/9/
[20:12] -kubuntu-ci:#kubuntu-devel- Project yakkety_unstable_plasma-framework build #171: STILL FAILING in 15 min: http://kci.pangea.pub/job/yakkety_unstable_plasma-framework/171/
[20:19] -kubuntu-ci:#kubuntu-devel- Yippee, build fixed!
[20:19] -kubuntu-ci:#kubuntu-devel- Project xenial_unstable_plasma-framework build #307: FIXED in 15 min: http://kci.pangea.pub/job/xenial_unstable_plasma-framework/307/
[20:38] -kubuntu-ci:#kubuntu-devel- Yippee, build fixed!
[20:38] -kubuntu-ci:#kubuntu-devel- Project yakkety_unstable_kio build #187: FIXED in 21 min: http://kci.pangea.pub/job/yakkety_unstable_kio/187/
[20:52] <clivejo> santa_: pong
[20:53]  * clivejo wonders why video clip thumbs had gone in zesty
[20:53] <santa_> maybe I have the answer to that :P
[20:53] <santa_> but I wanted to talk you about the debian merges
 clivejo: Ping, see Telegram.
[20:53] <santa_> as you could see in trello I made an script to detect package changes
[20:54] <santa_> so I just merged 4 with different dev names
[20:55] <clivejo> yes I can see that from KCI doing stuff on those 
[20:55] -kubuntu-ci:#kubuntu-devel- Project yakkety_unstable_plasma-framework build #172: STILL FAILING in 16 min: http://kci.pangea.pub/job/yakkety_unstable_plasma-framework/172/
[20:55] <santa_> clivejo: so to sum up you won't need to do this https://git.launchpad.net/~kubuntu-packagers/kubuntu-packaging/+git/krita/commit/?id=d97175b535411c71647316dca5e61c09528f8502
[20:58] <clivejo> I know, thats why I wanted to do these debian merges almost two weeks ago now
[20:58] <clivejo> so I wouldnt have to do things like that
[20:59] <santa_> clivejo: also talking about krita I know how to get the openexr problem fixed, do you mind if push my stuf to solve that?
[20:59] <santa_> to the kubuntu_unstable branch I mean
[20:59] <santa_> yes, but keep in mind that this way we have an strategy to get those imporntant merges done first
[21:00] <clivejo> no offence, but if Rik and I had of been let get on with them, 5.27 would have been done and we'd be working on plasma right now
[21:01] <santa_> also note that you would have get dupe breaks with the merges, thing which the merge tooling helpers solve
[21:01] <clivejo> santa_: go ahead with krita
[21:01] <clivejo> I just wanted to get it added to KCI so we could work on it
[21:01] <santa_> clivejo: that would have taken a lot of time, have you done such massive merges before?
[21:01] <clivejo> yes
[21:01] <clivejo> Scarlett and I done applications
[21:02] <clivejo> thats way more than 73 FW
[21:02] <clivejo> plus I wanted to teach Rik how to do it
 Everyone please read Valorie's email.
[21:02] <clivejo> as a learning exercise
 Why not teach me too? :P
[21:04] <clivejo> as I said, Phil and I talked about this ages ago.  I said to him I wanted to keep FW under our control and was prepared to do it manually to learn
[21:04] <clivejo> actually doing something yourself is the best way to learn, IMO
[21:05] <santa_> well you would have spent a lot of time with the merges, now it's a lot less time consuming with the tooling
[21:05] <clivejo> it would have taken about 2 days
[21:05] <santa_> I doubt that very much
[21:05] <clivejo> hi ximion, are your ears burning today?
[21:06] <santa_> but if that's true, we should be able to do it in 2 days from now, right?
[21:06] <clivejo> santa_: I cant right now, I have other things to do
 I can
 I volunteer as tribute. :P
[21:08] <santa_> clivejo: mind if I work with rik and simon on this if they have time? also there will be more releases of frameworks sou you can work on the merges again (this time with a proper tooling)
[21:08] <clivejo> santa_: its not just FW
[21:09] <santa_> tsimonq2: thank you
[21:09] <clivejo> I wanted to have plasma staged by now
[21:10] <santa_> I can do that with simon
[21:10] <genii> Is there a bug number for broken LTS-LTS under Kubuntu right now?
[21:10] <santa_> if you don't have time and you don't mind
[21:11] <clivejo> santa_: if Im expected to upload packages, I need to know what Im uploading
[21:11] <acheronuk> I keep hoping to have the time, but things get sabotaged
[21:11] <clivejo> your comments on uploading 5.27 as they raise huge alarm bells with me
[21:12] <clivejo> and to wait to 5.28
[21:12] <acheronuk> urgh. bad choice or wording ^^^ and that is things happening here to 'sabotage' my free time, not any of you
[21:12] <clivejo> I really do not understand your logic on not allowing us to get on with the Debian merges
[21:13] <clivejo> but I held off because I respect your knowledge and experience
[21:13] <santa_> ok
[21:13] <clivejo> but your warnings of dangerous breaks and so forth, I can see no evidence of
[21:14] <santa_> 1. there was a set of breaks which shouldn't be there (note that philip seemed to agree with it)
[21:14] <santa_> (I can link you to the conversation)
[21:14] <clivejo> I dont think Phillip had the time to actually look at those in depth
[21:14] <santa_> 2. doing the merges would result in getting sometimes dupe breaks without noticing
[21:14] <santa_> you saw that
[21:15] <santa_> so if you would have done the merges probably you would be still fixing the issues today
[21:15] <clivejo> there are other things I would like to see merged with Debian, which include our +git marked symbols
[21:16] <santa_> so now we can do the debian merges faster and better
[21:16] <clivejo> santa_: no offence but your tooling hasnt been tested yet
[21:16] <santa_> yeah, but those merges aren't "mandatory"
[21:17] <clivejo> it might be faster, of it might not work as expected
[21:17] <clivejo> they are in how I learned the workflow
[21:18] <santa_> well, you can do that after uploading given that they are invisible from the user point of view
[21:19] <santa_> regarding the tooling it worked well with todays merges
[21:19] <santa_> and if anything, we can fix it
[21:19] <clivejo> thats 4 out of 72/73
[21:19] <clivejo> Ive yet to see how it handles symbols
[21:19] <santa_> fine, we will see what happens with the others
[21:20] <santa_> it doesn't handle symbols that's like doing a regular merge
[21:21] <santa_> you get the conflicts and you solve them manually
[21:21] <santa_> another possible strategy is just copying the symbols files from debian and start over
[21:21] <santa_> we can do that with a "theirs" merge driver
[21:22] <santa_> clivejo: did you have any strategy to deal with symbols files in the past?
[21:23] <genii> ovidiu-florin: The issue with LTS-LTS upgrade which was mentioned int he latest podcast.. is there a bug number for this? We'd like to make a factoid for this issue which references it if one exists
[21:23] <santa_> clivejo: or it was just solving the conflicts manually?
[21:23] <clivejo> we merged with unstable
[21:24] <clivejo> that only has amd64 symbols and symbols are marked +git ....
[21:24] <clivejo> I wanted to get all the symbols merged and in sync with debian
[21:24] <santa_> debian/master with kubuntu_unstable
[21:25] <clivejo> no
[21:25] <santa_> no what?
[21:26] <clivejo> debian/master with kubuntu_unstable
[21:27] <santa_> so what branches did you merged?
[21:27] <santa_> * merge
[21:28] <clivejo> I wanted to merge FW5.27 with zesty_archive in our staging 
[21:28] <santa_> allright, that's what we are going to do
[21:29] <santa_> I meant in the past debian/master was being merged into kubuntu_unstable sometimes
[21:30] <clivejo> yes, if cherry picking was too much, sometimes it was just merged completely
[21:31] <santa_> meaning completely just getting a verbatim copy of debian's symbols files, right?
[21:32] <clivejo> well the person doing the merge needs to check things first
[21:32] <santa_> such as... ?
[21:32] <clivejo> which version is most sane
[21:33] <clivejo> double check the symbols are the same
[21:34] <santa_> well in that case you can copy the debian symbols files + rebuild the package in the ppa
[21:35] <clivejo> that was the workflow of doing a merge
[21:35] <santa_> and, if anything, fix the debian copy
[21:36] <clivejo> once conflicts fixed, commit to git, run git-buildpackage -s (+1) and upload to staging PPA
[21:37] <santa_> you don't need the +s(+1) anymore :P
[21:37] <santa_> that's done automatically now
[21:37] <santa_> but ok
[21:37] <clivejo> once its building ok and no problems, then you write done on the trello card
[21:39] <santa_> well, I think we can proceed that way for this merge
[21:40] <santa_> (in fact, that was the idea)
[21:40] <clivejo> ??
[21:40] <clivejo> oh man
[21:41] <clivejo> I need to go
 Oh?
[21:41] <santa_> I meant doing what you said with the symbols files
[21:41] <santa_> clivejo: ok, see you later
[21:42] <valorie> <3 to you both
[21:42] <santa_> actually we are 3 :P
[21:43] <acheronuk> 4. I am lurking
 👌👊😺👏
 📨📨📨📨📨📨📨📨
[21:49] <valorie> we should add a warning to "Known Issues" section of the release notes page at https://wiki.ubuntu.com/XenialXerus/ReleaseNotes 
[21:49] <valorie> about attempting to update from Kubuntu 14.04 to 16.04
[21:50] <valorie> but I don't know how to word it
[21:51] <genii> valorie: May I pm?
[21:52] <valorie> sure
[22:08] -kubuntu-ci:#kubuntu-devel- Project yakkety_unstable_kdiagram build #1: FAILURE in 9 min 28 sec: http://kci.pangea.pub/job/yakkety_unstable_kdiagram/1/
[22:09] <santa_> acheronuk: have you seen my reply in trello about the ka-deps package?
[22:10] -kubuntu-ci:#kubuntu-devel- Project xenial_unstable_kdiagram build #1: FAILURE in 10 min: http://kci.pangea.pub/job/xenial_unstable_kdiagram/1/
[22:10] <acheronuk> santa_: yes, got sidetracked with other stuff
[22:10] <santa_> acheronuk: any toughts about it?
[22:12] <acheronuk> santa_: I'm not sure about that dep for the build status pages, and honestly I have never had it installed for any other part of the tools and have not had a problem
[22:13] <acheronuk> so I would say it's a bit much dragging it on, with it's own deps, for a users/deveopers personal KA config on say their machine or a container.
[22:13] <santa_> acheronuk: ok, what about removing it and adding it after if we need it?
[22:14] <santa_> probably in a separate package, such as ka-buildstatus-deps
[22:14] <acheronuk> seems reasonable here. on most of my machine etc, I try to avoid having the JDK/JRE unless unavoidable
[22:14] <santa_> ok, let me reupload to my ppa
[22:14] <santa_> by the way
[22:15] <santa_> who has permissions to create new ppas in kubuntu-ppa?
 Kubuntu Council
[22:16] -kubuntu-ci:#kubuntu-devel- Project zesty_unstable_kdiagram build #1: UNSTABLE in 17 min: http://kci.pangea.pub/job/zesty_unstable_kdiagram/1/
[22:17] <genii> valorie: On the same subject... did you happen to document the steps you took to fix the situation when this happened to you?
[22:17] <genii> ... because those might come in handy
[22:17] <acheronuk> santa_: I would guess actual permission would be any member of the immediate owning team
[22:18] <santa_> ok
[22:18] <acheronuk> santa_: but as tsimonq2 on a real level I would say an 'OK' to do that should actually come from a higher level
[22:18] <acheronuk> as that ppa is the front facing source of updates users may look at
[22:19] <valorie> genii -- I think I wrote to kubuntu-devel about it
[22:19] <acheronuk> so a nod from KC or a -dev probably
[22:19] <santa_> allright
[22:20] <santa_> re-uploaded ka-deps package without jython
[22:20] <genii> valorie: thanks, i'll check the archives
[22:20] <valorie> basically it was a repeat of commands over and over, especially configure and apt install -f until it gave me no output
[22:21] <valorie> and possibly the upgrade command as well
[22:22] -kubuntu-ci:#kubuntu-devel- Project xenial_unstable_kdiagram build #2: STILL FAILING in 6 min 49 sec: http://kci.pangea.pub/job/xenial_unstable_kdiagram/2/
[22:22] <valorie> all a bit cloudy now, and I'm editing the website which will not let me copy/paste, so I'm a bit GRRRRR atm
[22:22] <acheronuk> santa_: thanks
[22:22] <santa_> acheronuk: so if you don't mind, I will update the README.ng installation instructions pointing to my ppa, we can substitute it later with something more 'official'
[22:23] -kubuntu-ci:#kubuntu-devel- Project yakkety_unstable_kdiagram build #2: STILL FAILING in 9 min 20 sec: http://kci.pangea.pub/job/yakkety_unstable_kdiagram/2/
[22:24] <acheronuk> santa_: if it's a kubuntu dev only package, maybe a ninja team ppa may be more appropriate? not sure
[22:24] <santa_> maybe
[22:24] <santa_> the best thing would be keeping it somewhat hidden from regular users
[22:25] <santa_> since that package is only useful for us
[22:25] <santa_> it will get only 4 users, lol
[22:26] <acheronuk> more perhaps if the dojo's start up or more people get into packaging
[22:26] <santa_> of course
[22:29] <genii> valorie: Worst-case, I'll put Trusty on the netbook, do the LTS-LTS , document the steps required ( over the weekend) and have something for Monday
[22:29] <valorie> ok, both the Ubuntu release notes and https://wiki.ubuntu.com/XenialXerus/ReleaseNotes/Kubuntu are updated, along with both old news stories on teh website
[22:30] <valorie> genii: mine was probably more complicated because I had the old project neon in /opt
[22:30] <valorie> so I was taking it on as a challenge, to see if it was possible
[22:30] <valorie> conclusion: possible, not desireable
[22:30] <genii> Good to know
[22:35] <santa_> tsimonq2: since you volunteered for the debian merges, can I use your help?
 OMG I am SO tired.
 Sorry not tonight.
[22:37] <santa_> ok, no problem, you can ping me anytime and if I'm around I can give you things to do
 👍
[22:37] <acheronuk> santa_: I will help tomorrow if can coincide times
[22:38] <acheronuk> I need something to bump me out of the lack of enthusiasm I have felt this week.
[22:38] <santa_> excellent, I might do a few merges more today
[22:38]  * santa_ throws a bucket of enthusiasm to acheronuk
[22:42] <acheronuk> santa_: lol. thanks
[22:50] <valorie> it makes me very happy to see us moving ahead
[22:51] <valorie> I know this point in the release always feels slow and frustrating, as we wait and plan
[22:54] <santa_> plan discussions are though
[22:54] <santa_> when each one has a different idea, but indeed, I think we are slowly moving forward :)
 Bah screw it. Give me something to do!
[22:56] <santa_> tsimonq2: http://kci.pangea.pub/job/yakkety_unstable_plasma-framework/172/parsed_console/
[22:56] <santa_> re-update the symbols files after the debian merge
[22:56] <santa_> (for instance)
 Please teach me.
[22:59] <santa_> hmm, but you updated symbols files before, didn't you?
[22:59] <santa_> I mean even if you are not sure if you did it right or wrong
 Correct.
 Speaking of that, santa_, can you please go through my Akonadi symbols update and fix it?
[23:11] <santa_> hmm ok
[23:11] <santa_> what's the issue with akonadi symbols?
 I've been told I Majorly Fcuked Them Up.
[23:16] <acheronuk> could be none, but it was going to be a learning/checking exercise
[23:16] <santa_> ok
[23:17] <tsimonq2> santa_: Do you have the time to teach me and Rik _right now_ using plasma-framework as an example?
[23:17] <santa_> so the issue is "Simon updated them, but we are not sure if the update is right or not"
[23:17] <tsimonq2> The sonner we learn the more KCI jobs get fixed. :P
[23:17] <tsimonq2> Correct, and I probably did fcuk something up there.
[23:17] <santa_> allright
[23:18] <acheronuk> santa_: pretty much. could be fine, but doubts at the time surfaced if I recall
[23:18] <santa_> you updated them in kubuntu_unstable right?
[23:18] <santa_> the akonadi ones I mean
[23:18] <tsimonq2> Correct.
[23:19] <tsimonq2> Coffee should be kicking in soon here...
[23:22] <santa_> ok
[23:23] <santa_> so indeed the akonadi symbols update is prone to have missing things
[23:25] <santa_> tsimonq2, acheronuk: so let me ask you something before anything. when you update the symbols files and they are symbols gone, are you checking if the ABI is being broken?
[23:25] <tsimonq2> Explain what the ABI is?
[23:25] <tsimonq2> So you can assume no... :P
[23:25] <santa_> ok. so probably you didn't
[23:25] <santa_> it's Application Binary Interface
[23:26] <acheronuk> acheronuk: yes for me, but I am not 100% on my ability to know for sure
[23:26] <santa_> ok
[23:26] <acheronuk> some I look at and can't decide
[23:27] <santa_> so you guys know what's the API (Application Programming Interface) of a library, don't you?
[23:28] <tsimonq2> Of course, I've done SOME programming at one point. :P
[23:29] <santa_> well the ABI is something similar but @ the bin level
[23:29] <tsimonq2> Oh?
[23:30] <santa_> the API of a lib it's the "set of stuff" you can use in your program which uses that library
[23:31] <santa_> the ABI of a lib it's the "set of stuff" you can link (with ld for instance) in your program which uses that library
[23:31] <acheronuk> for ref: https://irclogs.ubuntu.com/2016/10/16/%23kubuntu-devel.html#t18:39
[23:33] <santa_> that being said you know what is an API breakage - for instance removing a public function, right?
[23:34] <tsimonq2> Oh, ok?
[23:34] <santa_> an ABI breakage it's something similar
[23:34] <santa_> it happens allways when you break the API
[23:35] <santa_> and it may happen sometimes even if you don't break the API
[23:35] <santa_> I'll elaborate later
[23:35] <tsimonq2> Awwwww, ok.
[23:35] <santa_> so getting back to the kubuntu/debian/neon worls
[23:35] <santa_> * world
[23:35] <tsimonq2> Ok?
[23:36] <santa_> we have symbols files for our packages
[23:36] <santa_> this symbols files list the symbols exported by the library in question
[23:36] <santa_> toghether with that symbol we have a version listed
[23:37] <santa_> that version is the version where the symbol in question was introduced
[23:37] <santa_> so the purpose of the symbols files is generating dependencies on the library packages
[23:38] <santa_> as you could see all packages arch: any have an ${shlibs:Depends} variable
[23:39] <tsimonq2> Oh, ok?
[23:39] <santa_> that variable is expanded at build time (i.e. replaced with its actual value) by dh_shlibdeps
[23:40] <tsimonq2> I see.
[23:40] <santa_> (which is run when a package is built)
[23:40] <santa_> so dh_shlibdeps can use the symbols files to generate versioned dependencies
[23:41] <acheronuk> santa_: what about symbols versioned x.xx+git+date from KCI build logs etc?
[23:42] <acheronuk> where x.xx may not actually be the real version being built. 
[23:42] <santa_> acheronuk: they are versioned like that because they appeared in git and you updated the symbols files
[23:42] <santa_> ah, ok
[23:42] <santa_> I see what you mean
[23:43] <acheronuk> i.e. building 5.28 built KCI label gives it at say 5.26+git
[23:43] <acheronuk> does it do harm to leave/use those?
[23:43] <santa_> if 5.27 have the symbol in question no
[23:44] <acheronuk> but if they didn't appear really until what upstream lable as 5.28?
[23:44] <santa_> because you would get a dependency on libfoo (>= 5.26+git)
[23:44] <santa_> if we don't have 5.27 in the archive no problem
[23:45] <santa_> if we have and 5.27 doesn't have that symbol we may have a problem
[23:45] <santa_> because 5.27 satisfies the dep libfoo (>= 5.26+git)
[23:46] <santa_> and if 5.27 doesn't have the symbol in question, the dep is wrong
[23:46] <acheronuk> so on a merge where say debian versioned they at the correct release version, we should replace them probably with those?
[23:46] <santa_> yes
[23:46] <acheronuk> ok. thanks
[23:48] <acheronuk> santa_: oh, and I think I've seen debian adding similar form whatever CI they have I assume. do they have a policy do you know?
[23:49] <valorie> their policy is a book!
[23:50] <santa_> acheronuk: there isn't any policy for that, whatever it gets in the symbols file comes from their CI code
[23:50] <santa_> so no policy for  that particular issue, it's just what their CI do
[23:50] <santa_> like ours
[23:50] <santa_> we don't have a "policy" for that, ti's just what the KCI does
[23:51] <acheronuk> I mean policy not to use them in released versions? So make sure they are replaced/updated?
[23:52] <santa_> hmm, I'm not sure about that, but we could find out inspecting what they do in git
[23:52] <santa_> I don't know because back in the days there was no automation nor CI's
[23:53] <santa_> this trend started after the git migration of kde and the following splittery of everything
[23:53] <santa_> I mean the CI's and automation stuff
[23:53] <acheronuk> ok. but I guess a strong preference would be to have proper release versions replacing them if possible.
[23:54] <santa_> yep
[23:54] <santa_> that would be a good thing
[23:55] <tsimonq2> santa_: Ok, so when is it ok to remove symbols?
[23:55] <santa_> ok, so back to what we were talking
[23:55]  * acheronuk shuts up and watches
[23:55] <santa_> it's ok to remove when the missing symbol doesn't mean there's an ABI break
[23:56] <tsimonq2> So what qualifies as an ABI break?
[23:56] <santa_> let me answer: why there's a symbol missing if there isn't an abi break?
[23:56] <santa_> for instance
[23:57] <santa_> a) the symbol is private yet listed in the symbols file
[23:57] <santa_> b) the symbol is public, but it is in a header which is not installed
[23:57] <santa_> c) the symbol is optional
[23:58] <santa_> d) the symbol comes from other library, yet listed in the symbols file
[23:58] <santa_> the d) is a bit wtf'ish but it happens
[23:59] <santa_> with C++ libraries the symbols files tend to have that kind of noise
[23:59] <santa_> with C libs this doesn't happen or so they claim