[00:01] -kubuntu-ci:#kubuntu-devel- Project merger_kcoreaddons build #805: FAILURE in 1 min 2 sec: http://kci.pangea.pub/job/merger_kcoreaddons/805/
[00:02] -kubuntu-ci:#kubuntu-devel- Yippee, build fixed!
[00:02] -kubuntu-ci:#kubuntu-devel- Project merger_kdiamond build #646: FIXED in 2 min 40 sec: http://kci.pangea.pub/job/merger_kdiamond/646/
[00:04] -kubuntu-ci:#kubuntu-devel- Project merger_print-manager build #739: FAILURE in 1 min 32 sec: http://kci.pangea.pub/job/merger_print-manager/739/
[00:05] -kubuntu-ci:#kubuntu-devel- Project merger_kwayland build #832: STILL FAILING in 3 min 40 sec: http://kci.pangea.pub/job/merger_kwayland/832/
[00:06] -kubuntu-ci:#kubuntu-devel- Project mgmt_merger build #722: STILL UNSTABLE in 6 min 41 sec: http://kci.pangea.pub/job/mgmt_merger/722/
[00:06] -kubuntu-ci:#kubuntu-devel- Project mgmt_progenitor build #707: STILL UNSTABLE in 6 min 43 sec: http://kci.pangea.pub/job/mgmt_progenitor/707/
[00:14] -kubuntu-ci:#kubuntu-devel- Project xenial_unstable_okular build #50: STILL FAILING in 1 min 39 sec: http://kci.pangea.pub/job/xenial_unstable_okular/50/
[00:14] -kubuntu-ci:#kubuntu-devel- Project zesty_unstable_okular build #22: STILL FAILING in 2 min 23 sec: http://kci.pangea.pub/job/zesty_unstable_okular/22/
[00:14] -kubuntu-ci:#kubuntu-devel- Project yakkety_unstable_okular build #128: STILL FAILING in 3 min 0 sec: http://kci.pangea.pub/job/yakkety_unstable_okular/128/
[00:20] -kubuntu-ci:#kubuntu-devel- Project zesty_unstable_okular build #23: STILL FAILING in 49 sec: http://kci.pangea.pub/job/zesty_unstable_okular/23/
[00:20] -kubuntu-ci:#kubuntu-devel- Project xenial_unstable_okular build #51: STILL FAILING in 1 min 14 sec: http://kci.pangea.pub/job/xenial_unstable_okular/51/
[00:20] -kubuntu-ci:#kubuntu-devel- Project yakkety_unstable_okular build #129: STILL FAILING in 1 min 18 sec: http://kci.pangea.pub/job/yakkety_unstable_okular/129/
[00:25] -kubuntu-ci:#kubuntu-devel- Project xenial_unstable_peruse build #11: STILL UNSTABLE in 17 min: http://kci.pangea.pub/job/xenial_unstable_peruse/11/
[00:33] -kubuntu-ci:#kubuntu-devel- Project yakkety_unstable_libkipi build #85: STILL UNSTABLE in 25 min: http://kci.pangea.pub/job/yakkety_unstable_libkipi/85/
[00:33] -kubuntu-ci:#kubuntu-devel- Project zesty_unstable_kdesdk-kioslaves build #21: STILL UNSTABLE in 25 min: http://kci.pangea.pub/job/zesty_unstable_kdesdk-kioslaves/21/
[00:33] -kubuntu-ci:#kubuntu-devel- Project yakkety_unstable_kde-runtime build #267: STILL FAILING in 21 min: http://kci.pangea.pub/job/yakkety_unstable_kde-runtime/267/
[00:43] -kubuntu-ci:#kubuntu-devel- Project xenial_unstable_kde-runtime build #260: STILL FAILING in 30 min: http://kci.pangea.pub/job/xenial_unstable_kde-runtime/260/
[00:43] -kubuntu-ci:#kubuntu-devel- Project yakkety_unstable_cantor build #109: STILL UNSTABLE in 36 min: http://kci.pangea.pub/job/yakkety_unstable_cantor/109/
[00:43] -kubuntu-ci:#kubuntu-devel- Project zesty_unstable_kde-runtime build #44: STILL FAILING in 30 min: http://kci.pangea.pub/job/zesty_unstable_kde-runtime/44/
[00:57] -kubuntu-ci:#kubuntu-devel- Yippee, build fixed!
[00:57] -kubuntu-ci:#kubuntu-devel- Project xenial_unstable_extra-cmake-modules build #365: FIXED in 13 min: http://kci.pangea.pub/job/xenial_unstable_extra-cmake-modules/365/
[00:57] -kubuntu-ci:#kubuntu-devel- Yippee, build fixed!
[00:57] -kubuntu-ci:#kubuntu-devel- Yippee, build fixed!
[00:57] -kubuntu-ci:#kubuntu-devel- Project zesty_unstable_extra-cmake-modules build #26: FIXED in 13 min: http://kci.pangea.pub/job/zesty_unstable_extra-cmake-modules/26/
[00:57] -kubuntu-ci:#kubuntu-devel- Project yakkety_unstable_extra-cmake-modules build #153: FIXED in 13 min: http://kci.pangea.pub/job/yakkety_unstable_extra-cmake-modules/153/
[00:57] -kubuntu-ci:#kubuntu-devel- Project yakkety_unstable_kde-runtime build #268: STILL FAILING in 19 min: http://kci.pangea.pub/job/yakkety_unstable_kde-runtime/268/
[01:00] -kubuntu-ci:#kubuntu-devel- Project xenial_unstable_kmail build #17: STILL FAILING in 3 min 15 sec: http://kci.pangea.pub/job/xenial_unstable_kmail/17/
[01:02] -kubuntu-ci:#kubuntu-devel- Project yakkety_unstable_kmail build #17: STILL FAILING in 4 min 22 sec: http://kci.pangea.pub/job/yakkety_unstable_kmail/17/
[01:04] -kubuntu-ci:#kubuntu-devel- Project zesty_unstable_kde-runtime build #45: STILL FAILING in 15 min: http://kci.pangea.pub/job/zesty_unstable_kde-runtime/45/
[01:06] -kubuntu-ci:#kubuntu-devel- Project zesty_unstable_kmail build #17: STILL FAILING in 8 min 41 sec: http://kci.pangea.pub/job/zesty_unstable_kmail/17/
[01:10] -kubuntu-ci:#kubuntu-devel- Project xenial_unstable_kmail build #18: STILL FAILING in 4 min 50 sec: http://kci.pangea.pub/job/xenial_unstable_kmail/18/
[01:11] -kubuntu-ci:#kubuntu-devel- Project yakkety_unstable_kmail build #18: STILL FAILING in 3 min 52 sec: http://kci.pangea.pub/job/yakkety_unstable_kmail/18/
[01:11] -kubuntu-ci:#kubuntu-devel- Project xenial_unstable_kde-runtime build #261: STILL FAILING in 23 min: http://kci.pangea.pub/job/xenial_unstable_kde-runtime/261/
[01:16] -kubuntu-ci:#kubuntu-devel- Project zesty_unstable_kmail build #18: STILL FAILING in 4 min 27 sec: http://kci.pangea.pub/job/zesty_unstable_kmail/18/
[01:19] -kubuntu-ci:#kubuntu-devel- Project xenial_unstable_kcoreaddons build #299: STILL UNSTABLE in 22 min: http://kci.pangea.pub/job/xenial_unstable_kcoreaddons/299/
[01:20] -kubuntu-ci:#kubuntu-devel- Project yakkety_unstable_kitemmodels build #120: STILL UNSTABLE in 22 min: http://kci.pangea.pub/job/yakkety_unstable_kitemmodels/120/
[01:20] -kubuntu-ci:#kubuntu-devel- Project xenial_unstable_kitemmodels build #319: STILL UNSTABLE in 22 min: http://kci.pangea.pub/job/xenial_unstable_kitemmodels/319/
[01:20] -kubuntu-ci:#kubuntu-devel- Project zesty_unstable_kitemmodels build #23: STILL UNSTABLE in 22 min: http://kci.pangea.pub/job/zesty_unstable_kitemmodels/23/
[01:21] -kubuntu-ci:#kubuntu-devel- Project zesty_unstable_kcrash build #20: STILL UNSTABLE in 23 min: http://kci.pangea.pub/job/zesty_unstable_kcrash/20/
[01:21] <tsimonq2> Hai hai hai!
[01:26] -kubuntu-ci:#kubuntu-devel- Project xenial_unstable_kcrash build #308: STILL UNSTABLE in 6 min 28 sec: http://kci.pangea.pub/job/xenial_unstable_kcrash/308/
[01:48] -kubuntu-ci:#kubuntu-devel- Project yakkety_unstable_kpackage build #157: STILL UNSTABLE in 16 min: http://kci.pangea.pub/job/yakkety_unstable_kpackage/157/
[02:08] <valorie> read up when you can, tsimonq2
[02:08] <valorie> you were asked for
[02:08] <tsimonq2> Rik filled me in
[02:11] <valorie> cool
[02:14] -kubuntu-ci:#kubuntu-devel- Project xenial_unstable_kwallet build #317: STILL UNSTABLE in 12 min: http://kci.pangea.pub/job/xenial_unstable_kwallet/317/
[02:14] -kubuntu-ci:#kubuntu-devel- Project yakkety_unstable_kwallet build #156: STILL UNSTABLE in 12 min: http://kci.pangea.pub/job/yakkety_unstable_kwallet/156/
[02:14] -kubuntu-ci:#kubuntu-devel- Project zesty_unstable_kwallet build #16: STILL UNSTABLE in 12 min: http://kci.pangea.pub/job/zesty_unstable_kwallet/16/
[02:46] -kubuntu-ci:#kubuntu-devel- Project zesty_unstable_minuet build #5: STILL FAILING in 7 min 27 sec: http://kci.pangea.pub/job/zesty_unstable_minuet/5/
[02:51] -kubuntu-ci:#kubuntu-devel- Yippee, build fixed!
[02:51] -kubuntu-ci:#kubuntu-devel- Project zesty_unstable_kinit build #14: FIXED in 12 min: http://kci.pangea.pub/job/zesty_unstable_kinit/14/
[02:53] -kubuntu-ci:#kubuntu-devel- Yippee, build fixed!
[02:53] -kubuntu-ci:#kubuntu-devel- Project zesty_unstable_kalgebra build #15: FIXED in 14 min: http://kci.pangea.pub/job/zesty_unstable_kalgebra/15/
[02:57] -kubuntu-ci:#kubuntu-devel- Project zesty_unstable_minuet build #6: STILL FAILING in 5 min 36 sec: http://kci.pangea.pub/job/zesty_unstable_minuet/6/
[03:04] -kubuntu-ci:#kubuntu-devel- Project zesty_unstable_marble build #9: STILL FAILING in 11 min: http://kci.pangea.pub/job/zesty_unstable_marble/9/
[03:05] -kubuntu-ci:#kubuntu-devel- Project zesty_unstable_spectacle build #16: STILL UNSTABLE in 11 min: http://kci.pangea.pub/job/zesty_unstable_spectacle/16/
[03:09] -kubuntu-ci:#kubuntu-devel- Project xenial_unstable_minuet build #27: STILL FAILING in 11 min: http://kci.pangea.pub/job/xenial_unstable_minuet/27/
[03:10] -kubuntu-ci:#kubuntu-devel- Project yakkety_unstable_minuet build #29: STILL FAILING in 12 min: http://kci.pangea.pub/job/yakkety_unstable_minuet/29/
[03:12] -kubuntu-ci:#kubuntu-devel- Project xenial_unstable_kactivitymanagerd build #132: STILL UNSTABLE in 14 min: http://kci.pangea.pub/job/xenial_unstable_kactivitymanagerd/132/
[03:12] -kubuntu-ci:#kubuntu-devel- Yippee, build fixed!
[03:12] -kubuntu-ci:#kubuntu-devel- Project xenial_unstable_kinit build #275: FIXED in 14 min: http://kci.pangea.pub/job/xenial_unstable_kinit/275/
[03:19] -kubuntu-ci:#kubuntu-devel- Yippee, build fixed!
[03:19] -kubuntu-ci:#kubuntu-devel- Project yakkety_unstable_kinit build #100: FIXED in 21 min: http://kci.pangea.pub/job/yakkety_unstable_kinit/100/
[03:20] -kubuntu-ci:#kubuntu-devel- Project xenial_unstable_minuet build #28: STILL FAILING in 5 min 53 sec: http://kci.pangea.pub/job/xenial_unstable_minuet/28/
[03:20] -kubuntu-ci:#kubuntu-devel- Project yakkety_unstable_minuet build #30: STILL FAILING in 5 min 29 sec: http://kci.pangea.pub/job/yakkety_unstable_minuet/30/
[03:23] -kubuntu-ci:#kubuntu-devel- Project zesty_unstable_marble build #10: STILL FAILING in 14 min: http://kci.pangea.pub/job/zesty_unstable_marble/10/
[03:26] -kubuntu-ci:#kubuntu-devel- Project zesty_unstable_kpimtextedit build #11: FAILURE in 5 min 58 sec: http://kci.pangea.pub/job/zesty_unstable_kpimtextedit/11/
[03:26] -kubuntu-ci:#kubuntu-devel- Project zesty_unstable_okteta build #13: STILL UNSTABLE in 21 min: http://kci.pangea.pub/job/zesty_unstable_okteta/13/
[03:33] -kubuntu-ci:#kubuntu-devel- Project zesty_unstable_umbrello build #16: STILL UNSTABLE in 20 min: http://kci.pangea.pub/job/zesty_unstable_umbrello/16/
[03:33] -kubuntu-ci:#kubuntu-devel- Project zesty_unstable_kstars build #16: STILL UNSTABLE in 20 min: http://kci.pangea.pub/job/zesty_unstable_kstars/16/
[03:34] -kubuntu-ci:#kubuntu-devel- Project xenial_unstable_marble build #23: STILL FAILING in 21 min: http://kci.pangea.pub/job/xenial_unstable_marble/23/
[03:34] -kubuntu-ci:#kubuntu-devel- Project xenial_unstable_umbrello build #121: STILL UNSTABLE in 21 min: http://kci.pangea.pub/job/xenial_unstable_umbrello/121/
[03:34] -kubuntu-ci:#kubuntu-devel- Project zesty_unstable_libkcompactdisc build #14: STILL UNSTABLE in 14 min: http://kci.pangea.pub/job/zesty_unstable_libkcompactdisc/14/
[03:34] -kubuntu-ci:#kubuntu-devel- Project zesty_unstable_kpimtextedit build #12: STILL FAILING in 3 min 47 sec: http://kci.pangea.pub/job/zesty_unstable_kpimtextedit/12/
[03:40] -kubuntu-ci:#kubuntu-devel- Project yakkety_unstable_umbrello build #104: NOW UNSTABLE in 20 min: http://kci.pangea.pub/job/yakkety_unstable_umbrello/104/
[03:40] -kubuntu-ci:#kubuntu-devel- Project yakkety_unstable_ktp-auth-handler build #158: STILL UNSTABLE in 14 min: http://kci.pangea.pub/job/yakkety_unstable_ktp-auth-handler/158/
[03:40] -kubuntu-ci:#kubuntu-devel- Project zesty_unstable_ktp-common-internals build #12: STILL UNSTABLE in 20 min: http://kci.pangea.pub/job/zesty_unstable_ktp-common-internals/12/
[03:40] -kubuntu-ci:#kubuntu-devel- Project zesty_unstable_kio-extras build #12: UNSTABLE in 19 min: http://kci.pangea.pub/job/zesty_unstable_kio-extras/12/
[03:40] -kubuntu-ci:#kubuntu-devel- Project yakkety_unstable_marble build #23: STILL FAILING in 20 min: http://kci.pangea.pub/job/yakkety_unstable_marble/23/
[03:40] -kubuntu-ci:#kubuntu-devel- Project xenial_unstable_kstars build #288: STILL UNSTABLE in 27 min: http://kci.pangea.pub/job/xenial_unstable_kstars/288/
[03:40] -kubuntu-ci:#kubuntu-devel- Project xenial_unstable_spectacle build #130: STILL UNSTABLE in 17 min: http://kci.pangea.pub/job/xenial_unstable_spectacle/130/
[03:40] -kubuntu-ci:#kubuntu-devel- Yippee, build fixed!
[03:40] -kubuntu-ci:#kubuntu-devel- Project yakkety_unstable_kdesignerplugin build #92: FIXED in 14 min: http://kci.pangea.pub/job/yakkety_unstable_kdesignerplugin/92/
[03:40] -kubuntu-ci:#kubuntu-devel- Project yakkety_unstable_plasma-framework build #177: STILL FAILING in 12 min: http://kci.pangea.pub/job/yakkety_unstable_plasma-framework/177/
[03:44] -kubuntu-ci:#kubuntu-devel- Project xenial_unstable_ktp-desktop-applets build #145: STILL FAILING in 2 min 7 sec: http://kci.pangea.pub/job/xenial_unstable_ktp-desktop-applets/145/
[03:44] -kubuntu-ci:#kubuntu-devel- Project zesty_unstable_ktp-desktop-applets build #7: STILL FAILING in 2 min 26 sec: http://kci.pangea.pub/job/zesty_unstable_ktp-desktop-applets/7/
[03:44] -kubuntu-ci:#kubuntu-devel- Project xenial_unstable_kpimtextedit build #190: FAILURE in 4 min 14 sec: http://kci.pangea.pub/job/xenial_unstable_kpimtextedit/190/
[03:46] -kubuntu-ci:#kubuntu-devel- Project yakkety_unstable_kstars build #156: STILL UNSTABLE in 25 min: http://kci.pangea.pub/job/yakkety_unstable_kstars/156/
[03:46] -kubuntu-ci:#kubuntu-devel- Project xenial_unstable_ktp-auth-handler build #205: STILL UNSTABLE in 12 min: http://kci.pangea.pub/job/xenial_unstable_ktp-auth-handler/205/
[03:50] -kubuntu-ci:#kubuntu-devel- Project zesty_unstable_kmailtransport build #9: STILL FAILING in 3 min 46 sec: http://kci.pangea.pub/job/zesty_unstable_kmailtransport/9/
[03:50] -kubuntu-ci:#kubuntu-devel- Project zesty_unstable_ktp-desktop-applets build #8: STILL FAILING in 42 sec: http://kci.pangea.pub/job/zesty_unstable_ktp-desktop-applets/8/
[03:50] -kubuntu-ci:#kubuntu-devel- Project xenial_unstable_ktp-desktop-applets build #146: STILL FAILING in 1 min 7 sec: http://kci.pangea.pub/job/xenial_unstable_ktp-desktop-applets/146/
[03:53] -kubuntu-ci:#kubuntu-devel- Project xenial_unstable_kpimtextedit build #191: STILL FAILING in 3 min 42 sec: http://kci.pangea.pub/job/xenial_unstable_kpimtextedit/191/
[03:56] -kubuntu-ci:#kubuntu-devel- Project xenial_unstable_marble build #24: STILL FAILING in 17 min: http://kci.pangea.pub/job/xenial_unstable_marble/24/
[03:58] -kubuntu-ci:#kubuntu-devel- Project zesty_unstable_kmailtransport build #10: STILL FAILING in 2 min 50 sec: http://kci.pangea.pub/job/zesty_unstable_kmailtransport/10/
[03:58] -kubuntu-ci:#kubuntu-devel- Project zesty_unstable_grantlee-editor build #7: STILL FAILING in 44 sec: http://kci.pangea.pub/job/zesty_unstable_grantlee-editor/7/
[03:59] -kubuntu-ci:#kubuntu-devel- Project zesty_unstable_ktp-auth-handler build #12: STILL UNSTABLE in 18 min: http://kci.pangea.pub/job/zesty_unstable_ktp-auth-handler/12/
[03:59] -kubuntu-ci:#kubuntu-devel- Yippee, build fixed!
[03:59] -kubuntu-ci:#kubuntu-devel- Project yakkety_unstable_kdenlive build #157: FIXED in 39 min: http://kci.pangea.pub/job/yakkety_unstable_kdenlive/157/
[03:59] -kubuntu-ci:#kubuntu-devel- Project xenial_unstable_print-manager build #192: STILL UNSTABLE in 17 min: http://kci.pangea.pub/job/xenial_unstable_print-manager/192/
[03:59] -kubuntu-ci:#kubuntu-devel- Project zesty_unstable_print-manager build #7: STILL UNSTABLE in 17 min: http://kci.pangea.pub/job/zesty_unstable_print-manager/7/
[04:01] -kubuntu-ci:#kubuntu-devel- Project zesty_unstable_messagelib build #17: STILL FAILING in 3 min 57 sec: http://kci.pangea.pub/job/zesty_unstable_messagelib/17/
[04:02] -kubuntu-ci:#kubuntu-devel- Project yakkety_unstable_marble build #24: STILL FAILING in 16 min: http://kci.pangea.pub/job/yakkety_unstable_marble/24/
[04:03] -kubuntu-ci:#kubuntu-devel- Project yakkety_unstable_plasma-framework build #178: STILL FAILING in 17 min: http://kci.pangea.pub/job/yakkety_unstable_plasma-framework/178/
[04:04] -kubuntu-ci:#kubuntu-devel- Project zesty_unstable_grantlee-editor build #8: STILL FAILING in 47 sec: http://kci.pangea.pub/job/zesty_unstable_grantlee-editor/8/
[04:04] -kubuntu-ci:#kubuntu-devel- Project yakkety_unstable_ktp-desktop-applets build #85: STILL FAILING in 45 sec: http://kci.pangea.pub/job/yakkety_unstable_ktp-desktop-applets/85/
[04:10] -kubuntu-ci:#kubuntu-devel- Project yakkety_unstable_ktp-desktop-applets build #86: STILL FAILING in 41 sec: http://kci.pangea.pub/job/yakkety_unstable_ktp-desktop-applets/86/
[04:11] -kubuntu-ci:#kubuntu-devel- Project zesty_unstable_messagelib build #18: STILL FAILING in 4 min 19 sec: http://kci.pangea.pub/job/zesty_unstable_messagelib/18/
[04:12] -kubuntu-ci:#kubuntu-devel- Project zesty_unstable_kdepim-addons build #11: STILL FAILING in 44 sec: http://kci.pangea.pub/job/zesty_unstable_kdepim-addons/11/
[04:17] -kubuntu-ci:#kubuntu-devel- Project zesty_unstable_kdepim-addons build #12: STILL FAILING in 45 sec: http://kci.pangea.pub/job/zesty_unstable_kdepim-addons/12/
[04:18] -kubuntu-ci:#kubuntu-devel- Project yakkety_unstable_kio-extras build #92: UNSTABLE in 19 min: http://kci.pangea.pub/job/yakkety_unstable_kio-extras/92/
[04:18] -kubuntu-ci:#kubuntu-devel- Project xenial_unstable_kio-extras build #231: NOW UNSTABLE in 19 min: http://kci.pangea.pub/job/xenial_unstable_kio-extras/231/
[04:19] -kubuntu-ci:#kubuntu-devel- Project xenial_unstable_cantor build #214: STILL UNSTABLE in 19 min: http://kci.pangea.pub/job/xenial_unstable_cantor/214/
[04:19] -kubuntu-ci:#kubuntu-devel- Project xenial_unstable_plasma-integration build #28: STILL UNSTABLE in 19 min: http://kci.pangea.pub/job/xenial_unstable_plasma-integration/28/
[04:19] -kubuntu-ci:#kubuntu-devel- Project zesty_unstable_plasma-integration build #13: STILL UNSTABLE in 19 min: http://kci.pangea.pub/job/zesty_unstable_plasma-integration/13/
[04:39] -kubuntu-ci:#kubuntu-devel- Project xenial_unstable_kwin build #37: STILL UNSTABLE in 39 min: http://kci.pangea.pub/job/xenial_unstable_kwin/37/
[05:05] -kubuntu-ci:#kubuntu-devel- Project xenial_unstable_kmailtransport build #113: STILL FAILING in 45 min: http://kci.pangea.pub/job/xenial_unstable_kmailtransport/113/
[05:05] -kubuntu-ci:#kubuntu-devel- Project xenial_unstable_mailimporter build #26: FAILURE in 45 min: http://kci.pangea.pub/job/xenial_unstable_mailimporter/26/
[05:05] -kubuntu-ci:#kubuntu-devel- Project yakkety_unstable_plasma-integration build #26: FAILURE in 45 min: http://kci.pangea.pub/job/yakkety_unstable_plasma-integration/26/
[05:05] -kubuntu-ci:#kubuntu-devel- Project yakkety_unstable_kmailtransport build #98: STILL FAILING in 45 min: http://kci.pangea.pub/job/yakkety_unstable_kmailtransport/98/
[05:05] -kubuntu-ci:#kubuntu-devel- Project yakkety_unstable_kwin build #36: FAILURE in 46 min: http://kci.pangea.pub/job/yakkety_unstable_kwin/36/
[05:05] -kubuntu-ci:#kubuntu-devel- Project yakkety_unstable_libkdepim build #26: FAILURE in 46 min: http://kci.pangea.pub/job/yakkety_unstable_libkdepim/26/
[05:05] -kubuntu-ci:#kubuntu-devel- Project zesty_unstable_plasma-workspace build #12: FAILURE in 46 min: http://kci.pangea.pub/job/zesty_unstable_plasma-workspace/12/
[05:10] -kubuntu-ci:#kubuntu-devel- Project xenial_unstable_kdev-python build #11: FAILURE in 46 min: http://kci.pangea.pub/job/xenial_unstable_kdev-python/11/
[05:25] -kubuntu-ci:#kubuntu-devel- Project xenial_unstable_oxygen build #20: FAILURE in 46 min: http://kci.pangea.pub/job/xenial_unstable_oxygen/20/
[05:25] -kubuntu-ci:#kubuntu-devel- Project xenial_unstable_plasma-workspace build #33: FAILURE in 46 min: http://kci.pangea.pub/job/xenial_unstable_plasma-workspace/33/
[05:56] -kubuntu-ci:#kubuntu-devel- Project xenial_unstable_mailimporter build #27: STILL FAILING in 45 min: http://kci.pangea.pub/job/xenial_unstable_mailimporter/27/
[05:56] -kubuntu-ci:#kubuntu-devel- Project yakkety_unstable_plasma-integration build #27: STILL FAILING in 45 min: http://kci.pangea.pub/job/yakkety_unstable_plasma-integration/27/
[05:56] -kubuntu-ci:#kubuntu-devel- Project yakkety_unstable_kmailtransport build #99: STILL FAILING in 45 min: http://kci.pangea.pub/job/yakkety_unstable_kmailtransport/99/
[05:56] -kubuntu-ci:#kubuntu-devel- Project xenial_unstable_kmailtransport build #114: STILL FAILING in 46 min: http://kci.pangea.pub/job/xenial_unstable_kmailtransport/114/
[05:56] -kubuntu-ci:#kubuntu-devel- Project yakkety_unstable_kwin build #37: STILL FAILING in 46 min: http://kci.pangea.pub/job/yakkety_unstable_kwin/37/
[05:56] -kubuntu-ci:#kubuntu-devel- Project yakkety_unstable_libkdepim build #27: STILL FAILING in 45 min: http://kci.pangea.pub/job/yakkety_unstable_libkdepim/27/
[05:57] -kubuntu-ci:#kubuntu-devel- Project zesty_unstable_plasma-workspace build #13: STILL FAILING in 46 min: http://kci.pangea.pub/job/zesty_unstable_plasma-workspace/13/
[05:57] -kubuntu-ci:#kubuntu-devel- Project xenial_unstable_grantlee-editor build #9: STILL FAILING in 38 sec: http://kci.pangea.pub/job/xenial_unstable_grantlee-editor/9/
[06:01] -kubuntu-ci:#kubuntu-devel- Project xenial_unstable_kdev-python build #12: STILL FAILING in 45 min: http://kci.pangea.pub/job/xenial_unstable_kdev-python/12/
[06:03] -kubuntu-ci:#kubuntu-devel- Project xenial_unstable_grantlee-editor build #10: STILL FAILING in 37 sec: http://kci.pangea.pub/job/xenial_unstable_grantlee-editor/10/
[06:16] -kubuntu-ci:#kubuntu-devel- Project xenial_unstable_plasma-workspace build #34: STILL FAILING in 45 min: http://kci.pangea.pub/job/xenial_unstable_plasma-workspace/34/
[06:16] -kubuntu-ci:#kubuntu-devel- Project xenial_unstable_oxygen build #21: STILL FAILING in 46 min: http://kci.pangea.pub/job/xenial_unstable_oxygen/21/
[06:42] -kubuntu-ci:#kubuntu-devel- Project yakkety_unstable_akonadi-calendar build #25: FAILURE in 46 min: http://kci.pangea.pub/job/yakkety_unstable_akonadi-calendar/25/
[06:42] -kubuntu-ci:#kubuntu-devel- Project xenial_unstable_libksieve build #25: FAILURE in 46 min: http://kci.pangea.pub/job/xenial_unstable_libksieve/25/
[06:42] -kubuntu-ci:#kubuntu-devel- Project xenial_unstable_messagelib build #31: STILL FAILING in 46 min: http://kci.pangea.pub/job/xenial_unstable_messagelib/31/
[06:43] -kubuntu-ci:#kubuntu-devel- Project yakkety_unstable_libksieve build #25: FAILURE in 46 min: http://kci.pangea.pub/job/yakkety_unstable_libksieve/25/
[06:43] -kubuntu-ci:#kubuntu-devel- Project yakkety_unstable_libgravatar build #25: FAILURE in 46 min: http://kci.pangea.pub/job/yakkety_unstable_libgravatar/25/
[06:43] -kubuntu-ci:#kubuntu-devel- Project xenial_unstable_calendarsupport build #25: FAILURE in 46 min: http://kci.pangea.pub/job/xenial_unstable_calendarsupport/25/
[06:43] -kubuntu-ci:#kubuntu-devel- Project yakkety_unstable_mailimporter build #25: FAILURE in 46 min: http://kci.pangea.pub/job/yakkety_unstable_mailimporter/25/
[06:43] -kubuntu-ci:#kubuntu-devel- Project yakkety_unstable_oxygen build #24: FAILURE in 46 min: http://kci.pangea.pub/job/yakkety_unstable_oxygen/24/
[06:43] -kubuntu-ci:#kubuntu-devel- Project zesty_unstable_khotkeys build #12: FAILURE in 46 min: http://kci.pangea.pub/job/zesty_unstable_khotkeys/12/
[06:43] -kubuntu-ci:#kubuntu-devel- Project yakkety_unstable_plasma-workspace build #33: FAILURE in 46 min: http://kci.pangea.pub/job/yakkety_unstable_plasma-workspace/33/
[06:43] -kubuntu-ci:#kubuntu-devel- Project zesty_unstable_plasma-desktop build #13: FAILURE in 46 min: http://kci.pangea.pub/job/zesty_unstable_plasma-desktop/13/
[06:52] -kubuntu-ci:#kubuntu-devel- Yippee, build fixed!
[06:52] -kubuntu-ci:#kubuntu-devel- Project merger_print-manager build #740: FIXED in 19 sec: http://kci.pangea.pub/job/merger_print-manager/740/
[06:55] -kubuntu-ci:#kubuntu-devel- Yippee, build fixed!
[06:55] -kubuntu-ci:#kubuntu-devel- Project merger_kcoreaddons build #806: FIXED in 19 sec: http://kci.pangea.pub/job/merger_kcoreaddons/806/
[07:02] -kubuntu-ci:#kubuntu-devel- Project xenial_unstable_powerdevil build #24: FAILURE in 45 min: http://kci.pangea.pub/job/xenial_unstable_powerdevil/24/
[07:02] -kubuntu-ci:#kubuntu-devel- Project xenial_unstable_khotkeys build #24: FAILURE in 46 min: http://kci.pangea.pub/job/xenial_unstable_khotkeys/24/
[07:34] -kubuntu-ci:#kubuntu-devel- Project xenial_unstable_libksieve build #26: STILL FAILING in 46 min: http://kci.pangea.pub/job/xenial_unstable_libksieve/26/
[07:34] -kubuntu-ci:#kubuntu-devel- Project yakkety_unstable_akonadi-calendar build #26: STILL FAILING in 46 min: http://kci.pangea.pub/job/yakkety_unstable_akonadi-calendar/26/
[07:34] -kubuntu-ci:#kubuntu-devel- Project yakkety_unstable_libksieve build #26: STILL FAILING in 46 min: http://kci.pangea.pub/job/yakkety_unstable_libksieve/26/
[07:34] -kubuntu-ci:#kubuntu-devel- Project yakkety_unstable_libgravatar build #26: STILL FAILING in 46 min: http://kci.pangea.pub/job/yakkety_unstable_libgravatar/26/
[07:34] -kubuntu-ci:#kubuntu-devel- Project xenial_unstable_messagelib build #32: STILL FAILING in 46 min: http://kci.pangea.pub/job/xenial_unstable_messagelib/32/
[07:34] -kubuntu-ci:#kubuntu-devel- Project xenial_unstable_calendarsupport build #26: STILL FAILING in 46 min: http://kci.pangea.pub/job/xenial_unstable_calendarsupport/26/
[07:34] -kubuntu-ci:#kubuntu-devel- Project yakkety_unstable_mailimporter build #26: STILL FAILING in 46 min: http://kci.pangea.pub/job/yakkety_unstable_mailimporter/26/
[07:34] -kubuntu-ci:#kubuntu-devel- Project zesty_unstable_khotkeys build #13: STILL FAILING in 46 min: http://kci.pangea.pub/job/zesty_unstable_khotkeys/13/
[07:34] -kubuntu-ci:#kubuntu-devel- Project yakkety_unstable_oxygen build #25: STILL FAILING in 46 min: http://kci.pangea.pub/job/yakkety_unstable_oxygen/25/
[07:34] -kubuntu-ci:#kubuntu-devel- Project zesty_unstable_plasma-desktop build #14: STILL FAILING in 46 min: http://kci.pangea.pub/job/zesty_unstable_plasma-desktop/14/
[07:34] -kubuntu-ci:#kubuntu-devel- Project xenial_unstable_kdepim-addons build #94: STILL FAILING in 37 sec: http://kci.pangea.pub/job/xenial_unstable_kdepim-addons/94/
[07:35] -kubuntu-ci:#kubuntu-devel- Project yakkety_unstable_plasma-workspace build #34: STILL FAILING in 47 min: http://kci.pangea.pub/job/yakkety_unstable_plasma-workspace/34/
[07:40] -kubuntu-ci:#kubuntu-devel- Project xenial_unstable_kdepim-addons build #95: STILL FAILING in 39 sec: http://kci.pangea.pub/job/xenial_unstable_kdepim-addons/95/
[07:47] -kubuntu-ci:#kubuntu-devel- Project zesty_unstable_plasma-desktop build #15: ABORTED in 8 min 8 sec: http://kci.pangea.pub/job/zesty_unstable_plasma-desktop/15/
[07:53] -kubuntu-ci:#kubuntu-devel- Project xenial_unstable_powerdevil build #25: STILL FAILING in 45 min: http://kci.pangea.pub/job/xenial_unstable_powerdevil/25/
[07:53] -kubuntu-ci:#kubuntu-devel- Project xenial_unstable_khotkeys build #25: STILL FAILING in 45 min: http://kci.pangea.pub/job/xenial_unstable_khotkeys/25/
[08:01] <acheronuk> damn. KCI ppa is now over it's size limit
[08:02] <valorie> I think the LP admins can raise the limit
[08:05] <acheronuk> valorie: they just *doubled* it. wow
[08:05] <valorie> NICE!
[08:05] <valorie> so there will be room for stable too
[08:06] <acheronuk> that will be in a separate ppa
[08:07] <acheronuk> https://launchpad.net/~kubuntu-ci/+archive/ubuntu/stable
[08:08] -kubuntu-ci:#kubuntu-devel- Project zesty_unstable_kmenuedit build #12: ABORTED in 34 min: http://kci.pangea.pub/job/zesty_unstable_kmenuedit/12/
[08:12] <valorie> that's good news! heading to bed
[08:12] <acheronuk> night valorie. sleep well
[08:20] -kubuntu-ci:#kubuntu-devel- Project yakkety_unstable_eventviews build #25: FAILURE in 45 min: http://kci.pangea.pub/job/yakkety_unstable_eventviews/25/
[08:20] -kubuntu-ci:#kubuntu-devel- Project yakkety_unstable_messagelib build #33: STILL FAILING in 46 min: http://kci.pangea.pub/job/yakkety_unstable_messagelib/33/
[08:21] -kubuntu-ci:#kubuntu-devel- Project yakkety_unstable_khotkeys build #24: FAILURE in 46 min: http://kci.pangea.pub/job/yakkety_unstable_khotkeys/24/
[08:21] -kubuntu-ci:#kubuntu-devel- Project yakkety_unstable_plasma-desktop build #24: FAILURE in 46 min: http://kci.pangea.pub/job/yakkety_unstable_plasma-desktop/24/
[08:23] -kubuntu-ci:#kubuntu-devel- Project yakkety_unstable_powerdevil build #24: FAILURE in 47 min: http://kci.pangea.pub/job/yakkety_unstable_powerdevil/24/
[08:30] -kubuntu-ci:#kubuntu-devel- Project yakkety_unstable_messagelib build #34: STILL FAILING in 4 min 59 sec: http://kci.pangea.pub/job/yakkety_unstable_messagelib/34/
[08:40] -kubuntu-ci:#kubuntu-devel- Project xenial_unstable_kmenuedit build #22: FAILURE in 47 min: http://kci.pangea.pub/job/xenial_unstable_kmenuedit/22/
[08:40] -kubuntu-ci:#kubuntu-devel- Yippee, build fixed!
[08:40] -kubuntu-ci:#kubuntu-devel- Project zesty_unstable_plasma-workspace build #14: FIXED in 32 min: http://kci.pangea.pub/job/zesty_unstable_plasma-workspace/14/
[08:41] -kubuntu-ci:#kubuntu-devel- Yippee, build fixed!
[08:41] -kubuntu-ci:#kubuntu-devel- Project yakkety_unstable_powerdevil build #25: FIXED in 12 min: http://kci.pangea.pub/job/yakkety_unstable_powerdevil/25/
[08:41] -kubuntu-ci:#kubuntu-devel- Yippee, build fixed!
[08:41] -kubuntu-ci:#kubuntu-devel- Project yakkety_unstable_khotkeys build #25: FIXED in 14 min: http://kci.pangea.pub/job/yakkety_unstable_khotkeys/25/
[08:41] -kubuntu-ci:#kubuntu-devel- Yippee, build fixed!
[08:41] -kubuntu-ci:#kubuntu-devel- Project yakkety_unstable_eventviews build #26: FIXED in 16 min: http://kci.pangea.pub/job/yakkety_unstable_eventviews/26/
[08:42] -kubuntu-ci:#kubuntu-devel- Project yakkety_unstable_kdepim-addons build #27: STILL FAILING in 42 sec: http://kci.pangea.pub/job/yakkety_unstable_kdepim-addons/27/
[08:48] -kubuntu-ci:#kubuntu-devel- Project yakkety_unstable_kdepim-addons build #28: STILL FAILING in 42 sec: http://kci.pangea.pub/job/yakkety_unstable_kdepim-addons/28/
[08:51] -kubuntu-ci:#kubuntu-devel- Yippee, build fixed!
[08:51] -kubuntu-ci:#kubuntu-devel- Project zesty_unstable_khotkeys build #14: FIXED in 10 min: http://kci.pangea.pub/job/zesty_unstable_khotkeys/14/
[08:52] -kubuntu-ci:#kubuntu-devel- Yippee, build fixed!
[08:52] -kubuntu-ci:#kubuntu-devel- Project yakkety_unstable_plasma-desktop build #25: FIXED in 26 min: http://kci.pangea.pub/job/yakkety_unstable_plasma-desktop/25/
[09:00] -kubuntu-ci:#kubuntu-devel- Yippee, build fixed!
[09:00] -kubuntu-ci:#kubuntu-devel- Project xenial_unstable_kmenuedit build #23: FIXED in 14 min: http://kci.pangea.pub/job/xenial_unstable_kmenuedit/23/
[09:07] -kubuntu-ci:#kubuntu-devel- Yippee, build fixed!
[09:07] -kubuntu-ci:#kubuntu-devel- Project zesty_unstable_plasma-desktop build #16: FIXED in 26 min: http://kci.pangea.pub/job/zesty_unstable_plasma-desktop/16/
[09:10] -kubuntu-ci:#kubuntu-devel- Project yakkety_unstable_okular build #130: STILL FAILING in 45 sec: http://kci.pangea.pub/job/yakkety_unstable_okular/130/
[09:10] -kubuntu-ci:#kubuntu-devel- Project zesty_unstable_okular build #24: STILL FAILING in 48 sec: http://kci.pangea.pub/job/zesty_unstable_okular/24/
[09:11] -kubuntu-ci:#kubuntu-devel- Project xenial_unstable_okular build #52: STILL FAILING in 1 min 10 sec: http://kci.pangea.pub/job/xenial_unstable_okular/52/
[09:16] -kubuntu-ci:#kubuntu-devel- Project yakkety_unstable_okular build #131: STILL FAILING in 44 sec: http://kci.pangea.pub/job/yakkety_unstable_okular/131/
[09:17] -kubuntu-ci:#kubuntu-devel- Project xenial_unstable_okular build #53: STILL FAILING in 42 sec: http://kci.pangea.pub/job/xenial_unstable_okular/53/
[09:17] -kubuntu-ci:#kubuntu-devel- Project zesty_unstable_okular build #25: STILL FAILING in 1 min 19 sec: http://kci.pangea.pub/job/zesty_unstable_okular/25/
[09:25] -kubuntu-ci:#kubuntu-devel- Project xenial_unstable_okular build #54: STILL FAILING in 4 min 52 sec: http://kci.pangea.pub/job/xenial_unstable_okular/54/
[09:25] -kubuntu-ci:#kubuntu-devel- Project zesty_unstable_okular build #26: STILL FAILING in 5 min 1 sec: http://kci.pangea.pub/job/zesty_unstable_okular/26/
[09:27] -kubuntu-ci:#kubuntu-devel- Project yakkety_unstable_okular build #132: STILL FAILING in 6 min 27 sec: http://kci.pangea.pub/job/yakkety_unstable_okular/132/
[09:27] <acheronuk> clivejo and ninjas: looks like okular have finally switched their master to Qt5, so that is a nice little porting job if anyone in particular wants it
[09:34] -kubuntu-ci:#kubuntu-devel- Project xenial_unstable_okular build #55: STILL FAILING in 3 min 53 sec: http://kci.pangea.pub/job/xenial_unstable_okular/55/
[09:35] -kubuntu-ci:#kubuntu-devel- Project zesty_unstable_okular build #27: STILL FAILING in 4 min 30 sec: http://kci.pangea.pub/job/zesty_unstable_okular/27/
[09:37] -kubuntu-ci:#kubuntu-devel- Project yakkety_unstable_okular build #133: STILL FAILING in 4 min 58 sec: http://kci.pangea.pub/job/yakkety_unstable_okular/133/
[09:39] <jimarvan> good morning peeps
[09:39] <jimarvan> acheronuk: okular huh? :)
[11:41] -kubuntu-ci:#kubuntu-devel- Project zesty_unstable_kleopatra build #5: STILL FAILING in 40 min: http://kci.pangea.pub/job/zesty_unstable_kleopatra/5/
[11:49] -kubuntu-ci:#kubuntu-devel- Yippee, build fixed!
[11:49] -kubuntu-ci:#kubuntu-devel- Project zesty_unstable_kmahjongg build #7: FIXED in 48 min: http://kci.pangea.pub/job/zesty_unstable_kmahjongg/7/
[11:51] -kubuntu-ci:#kubuntu-devel- Project zesty_unstable_kleopatra build #6: STILL FAILING in 5 min 8 sec: http://kci.pangea.pub/job/zesty_unstable_kleopatra/6/
[12:21] -kubuntu-ci:#kubuntu-devel- Project zesty_unstable_kstars build #17: STILL UNSTABLE in 21 min: http://kci.pangea.pub/job/zesty_unstable_kstars/17/
[12:26] -kubuntu-ci:#kubuntu-devel- Yippee, build fixed!
[12:26] -kubuntu-ci:#kubuntu-devel- Project zesty_unstable_palapeli build #19: FIXED in 9 min 34 sec: http://kci.pangea.pub/job/zesty_unstable_palapeli/19/
[12:26] -kubuntu-ci:#kubuntu-devel- Yippee, build fixed!
[12:26] -kubuntu-ci:#kubuntu-devel- Project zesty_unstable_lskat build #19: FIXED in 10 min: http://kci.pangea.pub/job/zesty_unstable_lskat/19/
[12:34] -kubuntu-ci:#kubuntu-devel- Project yakkety_unstable_plasma-pa build #116: STILL FAILING in 8 min 53 sec: http://kci.pangea.pub/job/yakkety_unstable_plasma-pa/116/
[12:34] -kubuntu-ci:#kubuntu-devel- Project zesty_unstable_plasma-pa build #10: STILL FAILING in 8 min 56 sec: http://kci.pangea.pub/job/zesty_unstable_plasma-pa/10/
[12:42] <BluesKaj> Howdy all
[12:47] -kubuntu-ci:#kubuntu-devel- Project yakkety_unstable_plasma-pa build #117: STILL FAILING in 7 min 52 sec: http://kci.pangea.pub/job/yakkety_unstable_plasma-pa/117/
[12:52] -kubuntu-ci:#kubuntu-devel- Project zesty_unstable_plasma-pa build #11: STILL FAILING in 13 min: http://kci.pangea.pub/job/zesty_unstable_plasma-pa/11/
 :D
[13:15] <jimarvan> :)
[13:15] <jimarvan> BluesKaj: hey :)
[13:16] <BluesKaj> hi jimarvan :-)
[13:32] <BluesKaj> any word when X11/Kwin gets replaced by Wayland and Weston on Zesty, if at all ?
[13:33] <mgraesslin> no
[13:33] <mgraesslin> nobody plans to replace anything by Weston
[13:34] <BluesKaj> could be optional eventually
[13:34] <mgraesslin> nobody wants to replace anything by Weston
[13:34] <BluesKaj> nobody?
[13:34] <mgraesslin> no
[13:34] <BluesKaj> sez you
[13:34] <mgraesslin> yes, I say that nobody wants to use Weston
[13:35] <mamarley> kwin will implement its own Wayland compositor, right?
[13:35] <BluesKaj> i see , so you speak for everyone
[13:35]  * mgraesslin is using KWin as a Wayland compositor right now
[13:35] <mgraesslin> but I'm not using Weston
[13:36] <BluesKaj> yean , but you're not eveyone
[13:36]  * mgraesslin is head of KDE Wayland porting
[13:36] <BluesKaj> everyone even
[13:36] <mgraesslin> so I can talk with quite authority on that matter
[13:37] <BluesKaj> I don't care, pulling rank doesn't mean it's not going to happen
[13:37] <mgraesslin> ok, let's summarize: you don't know the difference between Wayland and Weston, and I pointed that out
[13:38] <mamarley> BluesKaj: I think the point is that kwin will never be replaced by Weston on Kubuntu, since Kubuntu will just start using Kwin as a Wayland compositor when we switch to Wayland.
[13:38] <mgraesslin> as I say: nobody is going to replace anyting by Weston
[13:39] <BluesKaj> weston is the compositor afaik. but making sweeping statements about futeure deveopments is risky to say the least
[13:40] <mgraesslin> Weston is the reference compositor and as max a toy
[13:40] <mgraesslin> it canot support Plasma
[13:40] <mgraesslin> I know that because I did most of the Plasma porting
[13:45]  * BluesKaj shrugs
[13:48] <mamarley> Kubuntu may very well switch to Wayland at some point (I haven't heard about any plans though), but it just won't be using Weston as the compositor, it will be using Kwin.  Weston is just a reference compositor, an example, not designed to replace all other existing compositors.
[13:50] <BluesKaj> mamarley, thanks for the logical explanation, that makes sense now
[15:03] <blaze> I miss sgclark being hyperactive and doing everything superultrafast
[15:05] <acheronuk> +1 although I only saw that for a shorter time
[15:06] <sgclark> sorry, had to get a job. pesky bills and life costs money
[15:10] <BluesKaj> don't be sorry sgclark, we all have to make a living ;-)
[15:12]  * ahoneybun misses hanging out with sgclark
[15:34] <clivejo> mgraesslin: do you have many testers running totally wayland sessions?
[15:34] <mgraesslin> I have some testers
[15:34] <clivejo> is it useable?
[15:35] <mgraesslin> yes
[15:35] <mgraesslin> but not in Kubuntu - too old
[15:35]  * clivejo it hoping to try wayland in 5.8.3 if we even get it out the door
[15:35] <clivejo> s/even/ever
[15:37] <clivejo> what are min requirements for kwayland session?
[15:50] <blaze> can this session be started via display manager?
[16:13] <acheronuk> wayland still won't work with Nvidia I think?
[16:14]  * acheronuk swears at Avogadro
[16:15] <mamarley> I saw a thread on Reddit the other day where someone was using Wayland with the NVIDIA blob.  They weren't using KDE though.
[16:19] <acheronuk> https://blog.martin-graesslin.com/blog/2016/09/to-eglstream-or-not/
[16:19] <acheronuk> "The announcement of KDE Neon dev/unstable switching to Wayland by default raised quite a few worried comments as NVIDIA’s proprietary driver is not supported. "
[16:20] <acheronuk> not seen anything to suggest that has suddenly changed
[16:20] <blaze> poor nvidia users :\
[16:27]  * ahoneybun is one
[16:46] <BluesKaj> as am I ..it's too bad because my experience has been quite good with nvidia gpus so far on Kubuntu
 With 16.10 and the nvidia drivers ppa, same
[16:48] <blaze> X is still there and will be for foreseeable future, because of BSD systems
[17:05] <clivejo> hummm my kmail has died
[17:05] <clivejo> all acounts have gone :/
[17:12] <BluesKaj> too bad about kmail going enterprise data-based ..it was a great app on kde3
[17:14] <blaze> the last non-Akonadi version was 4.4 for KDE4
 @acheronuk, +1
 Well we could offer an alternative session like Ubuntu and Unity 8
 Probably wouldn't be too hard.
[17:25] <acheronuk> akonadi is evil
[17:31] <BluesKaj> akonadi is useless to most home users
[17:36] <blaze> well, it's possible to package kdepim 4.4 and to use it
[17:36] <blaze> opensuse does so
[17:38]  * clivejo turned it off and on again
[17:38] <clivejo> emails are back
[17:38] <acheronuk> LOL
[17:38]  * clivejo dances
[17:39] <clivejo> I need to find employment on an IT helpdesk
[17:39] <clivejo> Id be great!
[17:39] <acheronuk> that would drive me mad
[17:39] <acheronuk> *madder
[17:40] <clivejo> calm down mister Rik
[17:40] <clivejo> now please follow my instructions very carefully
[17:41] <clivejo> now sir, if you are going to shout and be very rude, I will terminate this call
[17:43] <acheronuk> are you from Microsoft telling me I 'have a virus' or 'errors'?
[17:45] <BluesKaj> I got one of those calls ...asked the guy,  oh microsoft Mumbai ?  :-)
[17:49] <BluesKaj> wife's windows pc was turned off at the time. told him he had the wrong number because there'no windows pcs running here atm. then I asked where I was located.
[17:50] <BluesKaj> he hung up after insulting me when i laughed at him
[17:50] <mamarley> I keep meaning to set up a VM with some zip bombs and stuff I can use in case I get one of those calls.
[17:54] <BluesKaj> one of my friends got conned by thses guys and ended paying them 100bucks/yr to keep him safe from other viruses.  It was basically a protection racket
[17:55] <BluesKaj> unfortunately my friend was a afraid of linux
[18:12] <blaze> what's so scary?
[18:28] <BluesKaj> I guess when just running Windows is a challenge anything less familiar can be daunting
 <IP_ADDRESS>
 np
 Hello all, the Meeting is about to start. Detail here: https://lists.ubuntu.com/archives/kubuntu-devel/2016-November/010861.html
[20:41] <valorie> mumble is very easy to set up
[20:43] <valorie> join us now and test your connection
[20:44] <acheronuk> WTF?
 what?
[20:48] <acheronuk> something like running water in valorie's background
[20:50] <valorie> ah, that could be the fishtank behind me
[20:50] <valorie> I could turn off the pump if it's distracting?
 clivejo ping
[20:51] <claydoh> I can't make it home in time so I can't join in, it looks sorry. No earphones, too noisy here and holding the phone to my ear is not all that convenient
 :(
[20:54] <valorie> :(
[20:54] <valorie> please add to the document then, if nothing else
[20:54] <valorie> https://docs.google.com/document/d/10M-hYkzHBLnPihbgk6J-u9QcYVW2y8U-jhnjo3rhq_Y/edit
 santa_ santa ping
[20:57] <valorie> santa_: ping
[20:57] <valorie> lol
[21:01] <acheronuk> your names are flashing but I no longer hear anything?
 we just heard a hello
 Bah
 acheronuk, if you have issues try to use push to speak
 Simon, yeeeey
 Grumble grumble
 can you join?
 On the bus so I'll have to see if I can get headphones
 when will you get home?
 Maybe I have some in my backpack...
 Sure.
[21:03] <acheronuk> not heard anything for the last few mins, but see your names flash
 we hear you acheronuk
 loud and clear
[21:04] <acheronuk> hmmm.......
 we're making test noises for you
 actually it's just me
 talking to myself
 because the rest won't talk
 yeeey meee
[21:04] <acheronuk> silence
 try restarting Mumble
 yea... we can hear you
[21:05] <acheronuk> ok
 this is not skype :D
 (Photo, 720x1280) https://irc-attachments.kde.org/HiUWr8Wo/file_1085.jpg
 ?
[21:07] <acheronuk> reconnected and I can see ovidio is maybe saying something but can't hear
 remove the http simon
[21:07] <acheronuk> drat
 just bare IP
[21:08]  * acheronuk reboots
 acheronuk Valorie sais to redo the audio setup
 there's a button for that
[21:09] <santa_> pong
 hey santa_
 can you join us on Mumble?
[21:09] <ahoneybun> santa_: we are in mumble server atm
 for the Vision meeting?
[21:09] <valorie> apt install mumble
[21:10] <ahoneybun> <IP_ADDRESS>
 santa_ still here?
 Ok, meeting will start
[21:20] <acheronuk> Ok.
[21:21] <valorie> please everyone contribute to the doc especially if you don't speak
[21:21] <valorie> https://docs.google.com/document/d/10M-hYkzHBLnPihbgk6J-u9QcYVW2y8U-jhnjo3rhq_Y/edit
[21:21] <acheronuk> will do :)
[21:53] <ahoneybun> clivejo: having internet issues?
[21:54] <clivejo> it is living up to its name
[21:55] <clivejo> all I can hear is mumbles
 Lol
[21:55] <ahoneybun> XD opps
[21:59] <valorie> clivejo: :(
[21:59] <valorie> missing your voice
[22:52] <santa_> !ninjas
[22:52] <tsimonq2> Hai
[22:52] <santa_> so can we continue the discussion about KA branches here?
[22:53] <tsimonq2> Sure.
[22:53]  * acheronuk goes to find aspirin
[22:53] <clivejo> Id rather not, had a long day and still in a good mood, so you guys go ahead
[22:54] <santa_> ok, so my point is: KA has 4 users if we have branches which aren't actually used by you we aren't going to do any progress
[22:54] <tsimonq2> Well I'm going to eat anyways.
[22:54] <tsimonq2> NINJAS: Please please please please PLEASE respond to my email!
[22:54] <tsimonq2> clivejo, acheronuk, santa_ ^^^^^^^^^^^^^^
[22:54]  * tsimonq2 goes to find food
[22:54] <santa_> so it's better to keep the master banch as it is and have another one in case of emergency
[22:57] <santa_> the other way around is going to hinder the development of KA. there are so much things to do and I can't afford to ask for permission each time I need to fix something, that would get us back to the days when I didn't have git permissions, and we already know the results of that
[22:59] <acheronuk> I guess the pace of the changes you make will slow down a bit as the new tooling matures?
 ^
[23:00] <santa_> yes, maybe in the future we could do it as you propose
[23:00] <santa_> but right now, given the fact that we are 4 users, supose we have 2 branches
[23:01] <acheronuk> I think one thing is that we haven't really been able to do things the same way twice in a row much, which means at the moment it constant adaptation
[23:01] <santa_> yep
[23:01] <acheronuk> and if you miss a session of staging etc, people quickly feel out of the loop
[23:02] <acheronuk> and notes/readme, no matter how good, are no real substitute to doing
[23:02] <acheronuk> and if you mis the doing, you feel a bit lost
[23:02] <santa_> anyway we did some progress on that
 I am completely lost in regards to tooling.
 So when you say things have been decided on, they haven't by everyone...
 Is it me, acheronuk?
[23:04] <santa_> tsimonq2: that's why we wanted you to stage plasma 5.8.3 so you get familiar with the tooling
 Was it? Have I been missing out on this?
[23:05] <acheronuk> somewhat I think?
[23:06] <santa_> that's what we mentioned yesterday
[23:06] <acheronuk> I think I've maybe done the most with santa_ on it, and I'm struggling sometimes to keep up with the changes
[23:08] <santa_> acheronuk: such as?
[23:09] <acheronuk> nothing specific, but I find myself wondering each time if things will work the same as they did last time
[23:10] <acheronuk> and I don't always understand the code well enough for the logs to tell me
 One thing. Please implement unit testing.
 We all make mistakes.
 Python has some awesome libraries for that.
[23:11] <acheronuk> not a HUGE moan on my part.
[23:11] <santa_> acheronuk: the user interface of gbp-* didn't change
 Well unit testing is practically docs. :P
 Shows usability.
 I can help if you want. :)
[23:11] <santa_> but we have the new tooling for merges and several bug fixes
 Exactly. Implement unit testing. :)
[23:12] <santa_> I don't think unit testing would be very hepful for this
 It would be for sure!
 Documentation *and* making sure we have very little bugs.
[23:13] <santa_> fine, go ahead and do it
 I'm saying for it to be a team effort. Sure I can show y'all how it's done, but eventually we should write unit tests alongside code.
 It's just good practice.
 Unless someone objects?
 I'm open to suggestions. :)
 Thoughts?
 @CliffordTheBigRedDoggie? @acheronuk?
 not much clue on that, hence my silence
[23:30] <santa_> acheronuk, tsimonq2: I think we should focus on staging plasma 5.8.3, can we meet tomorow to do it. so Simon would learn to use what we have so far
[23:30] <santa_> and then we can see how to handle KA in the future
 siomon has to work late (late our time( I think?
 which is why we said tonight
 but that plan got messed up with that meeting
[23:32] <santa_> yep
[23:33] <santa_> acheronuk: also I would like to get clivejo around whenever we do that
[23:33] <santa_> tsimonq2: any time preference?
[23:38] <genii> ovidiu-florin: Anywhere i can see how the meeting went?
 How about you guys look at my proposal first. :(
 I did look at your essay, it was very well written, precise and I thought that you put your opinions over very well.  I award you an A*  Thankyou please
[23:50] <santa_> tsimonq2: you mean the mail @ kubuntu-devel? seems mostly sane for me, but I think we can't anticipate the dates
[23:50] <valorie> I'm grateful for the meeting, even though I couldn't stay to the end
 at least i know to avoid mumble from now on :P
 on this laptop, anyway....
 Could you please all respond giving a +1 please?
 Please?


[01:07] <mup> PR snapcraft#2967 opened: requirements: uprev click to 7.1.1 <Created by cjp256> <https://github.com/snapcore/snapcraft/pull/2967>
[06:11] <mborzecki> morning
[07:02] <mborzecki> re
[07:04] <zyga> Good morning
[07:04] <mborzecki> zyga: hey
[07:04] <zyga> I fixed the exec env bug but it will take me some more time to adjust tests in two packages
[07:04] <zyga> I made it impossible to easily cause bugs like that again
[08:02] <pstolowski> mornings
[08:05] <mborzecki> pstolowski: mvo: morning
[08:07] <mvo> mborzecki: good morning
[08:07] <mvo> and good morning to pstolowski
[08:08] <pstolowski> o/
[08:10] <zyga> hey pawel
[08:10] <zyga> mvo: I'm considering taking today off
[08:10] <zyga> I feel super tired somehow
[08:10] <zyga> I will work some more on wrapping up two things from yesterday
[08:10] <zyga> and EOD around noon
[08:23] <mup> PR snapd#8225 closed: snapcraft.yaml: use sudo -E and remove workaround <Created by mvo5> <Merged by mvo5> <https://github.com/snapcore/snapd/pull/8225>
[08:23] <mvo> zyga: sure, get well
[08:23] <zyga> mvo: I hope I'm not sick, I just feel tired
[08:23] <zyga> anyway, I'll finish what I have to first :)
[08:25] <mup> PR snapd#8233 closed: snap-confine: unconditionally add /dev/net/tun to the device cgroup <Created by jdstrand> <Merged by mvo5> <https://github.com/snapcore/snapd/pull/8233>
[08:40] <mup> PR snapd#8214 closed: tests: test that after "remove-user" the system is unmanaged <Simple 😃> <Created by mvo5> <Merged by mvo5> <https://github.com/snapcore/snapd/pull/8214>
[08:41] <mup> PR snapd#8211 closed: tests: run ipv6 network-retry test too <Created by mvo5> <Merged by mvo5> <https://github.com/snapcore/snapd/pull/8211>
[08:44] <mup> PR snapd#7999 closed: devicestate: allow encryption regardless of grade <UC20> <Created by cmatsuoka> <Merged by mvo5> <https://github.com/snapcore/snapd/pull/7999>
[09:19] <mup> PR snapd#7673 closed: interfaces/desktop: allow access to system prompter interface <Created by alexmurray> <Merged by mvo5> <https://github.com/snapcore/snapd/pull/7673>
[09:48] <amurray> mvo: thanks for merging my PR :)
[09:48] <mvo> amurray: thanks for making it in the first place :)
[09:59] <pedronis> pstolowski: hi, what's the status of #8201 ?
[09:59] <mup> PR #8201: tests: mock prune ticker in overlord tests to reduce wait times <Created by stolowski> <https://github.com/snapcore/snapd/pull/8201>
[10:00] <pstolowski> pedronis: hi; it's ready but i'm pondering if it makes sense to pass N to tick
[10:02] <pedronis> pstolowski: should we close #8198 ? afaiu mvo skipped some tests in 2.44 instead
[10:03] <mup> PR #8198: o/tests: bump TestEnsureLoopPruneAbortsOld sleep time <⛔ Blocked> <Created by stolowski> <https://github.com/snapcore/snapd/pull/8198>
[10:04] <pstolowski> done
[10:04] <mup> PR snapd#8198 closed: o/tests: bump TestEnsureLoopPruneAbortsOld sleep time <⛔ Blocked> <Created by stolowski> <Closed by stolowski> <https://github.com/snapcore/snapd/pull/8198>
[10:08] <mborzecki> we don't have a page that lists know model names do we?
[10:15] <pedronis> mborzecki: known in which sense?
[10:22] <mborzecki> pedronis: say, i forgot the actual model name for rpi3 on core18, not sure there's an easy way to find a list of model names of supported devices
[10:32] <pedronis> mborzecki: ah, no we don't have a list but should have one I suppose in the new UC docs (cc degville)
[10:33] <mborzecki> pedronis: our use case may be a bit weird, a i know where to find the models repo ;) others may not
[10:34] <mup> PR snapd#8234 opened: devicestate: support dropping "cloud.cfg" user-data cloud-init <Created by mvo5> <https://github.com/snapcore/snapd/pull/8234>
[10:48] <degville> pedronis / mborzecki: thanks for bringing this up. So, I guess I can get the model names from the model assertions (http://cdimage.ubuntu.com/ubuntu-core/18/stable/current/). If so, I'll add them to the supported platforms page I've already created.
[10:51] <mborzecki> degville: sounds good, there's also a repository with model assertions right here https://github.com/snapcore/models in case it's useful
[10:51] <degville> mborzecki: brilliant, thanks!
[10:51] <mborzecki> degville: some of those are for core20 though
[10:52] <degville> mborzecki: ok, thanks.
[11:14] <pedronis> mborzecki: seems #8185 needs a master merge?  snapd-failover failed there (cc mvo)
[11:14] <mup> PR #8185: tests: add uc20 kernel snap upgrade managers test, fix bootloadertest bugs <Test Robustness> <UC20> <Created by anonymouse64> <https://github.com/snapcore/snapd/pull/8185>
[11:16] <mborzecki> pedronis: i'll merge master and push there, hopefully it's not another unexpected failure more in snapd-failover
[11:17] <mvo> thanks mborzecki
[11:31]  * zyga has completed fixing snap environment
[11:31] <zyga> this was nice
[11:51] <mup> PR snapd#7731 closed: usersession/userd: add "apt" to the white list of URL schemes handled by xdg-open <⛔ Blocked> <Created by oSoMoN> <Merged by mvo5> <https://github.com/snapcore/snapd/pull/7731>
[11:51] <mup> PR snapd#8235 opened: cmd/snap-preseed: handle --reset flag <Preseeding 🍞> <Created by stolowski> <https://github.com/snapcore/snapd/pull/8235>
[11:58] <mup> PR snapd#7588 closed: cmd/snap: add a "snap routine portal-info" command <Created by jhenstridge> <Merged by mvo5> <https://github.com/snapcore/snapd/pull/7588>
[12:05] <mup> PR snapd#8232 closed: interfaces: miscellaneous policy updates <Created by jdstrand> <Merged by bboozzoo> <https://github.com/snapcore/snapd/pull/8232>
[12:11]  * zyga lunch
[12:12]  * zyga notices open season for PRs :)
[12:14] <mvo> zyga: haha - not quite, I think it's just the result of a week of staleness
[12:14] <jdstrand> mvo: hi! do you want a separate 2.44-specific PR for PR 8232?
[12:14] <mup> PR #8232: interfaces: miscellaneous policy updates <Created by jdstrand> <Merged by bboozzoo> <https://github.com/snapcore/snapd/pull/8232>
[12:15] <ackk> hi, I'm seeing these errors when I "snap try" over the current running snap: https://paste.ubuntu.com/p/zQq2cFPCbM/ could it be related to the content interface?
[12:15] <jdstrand> mvo: also, is ijohnson off? if so, someone else can review PR 8231
[12:15] <mup> PR #8231: interfaces/{docker,kubernetes}-support: updates for lastest k8s <Created by jdstrand> <https://github.com/snapcore/snapd/pull/8231>
[12:15] <zyga> mvo: can we merge https://github.com/snapcore/snapd/pull/8230 once green, I have a fix piled up on top and would love to reuse the branch
[12:15] <mup> PR #8230: cmd/snap-exec: add test case for LP:#1860369 <Created by zyga> <https://github.com/snapcore/snapd/pull/8230>
[12:16] <zyga> after lunch I'll address the uio issue raised by a customer
[12:16]  * zyga thanks jdstrand once again for insight on that topic
[12:16] <jdstrand> np :)
[12:22] <mvo> jdstrand: 8232> if it's not a burden to you, then yes
[12:22] <jdstrand> mvo: not at all! coming up :)
[12:23] <mvo> jdstrand: 8321> I think someone from the team can review it
[12:23] <mvo> zyga: 8230> we can merge once it has two reviews :)
[12:23] <zyga> it's just a test showing we have a bug, I guess we can get those quickly
[12:24] <ackk> with a simplified testcase I get: - Setup snap "maas" (unset) security profiles (cannot update mount namespace of snap "maas": cannot update preserved namespace of snap "maas": cannot update snap namespace: read-only file system)
[12:24] <mvo> zyga: uio> did you figure out more about this?
[12:24] <zyga> mborzecki: could you look at 8230 please, super easy
[12:24] <mvo> zyga: yeah
[12:24] <zyga> mvo: yes, mostly jdstrand did
[12:24] <jdstrand> mvo: thanks! I will continue to work on figuring out what to do with a weird k8s access with highest priority. I'd like to say it would be ready today, but I'm not sure yet
[12:24] <zyga> mvo: I can give you the details now or in the standup, as you wish
[12:24] <mvo> jdstrand: ok
[12:25] <mvo> jdstrand: I want to release 2.44-final this week but we are still early
[12:25] <mvo> zyga: either way is fine, maybe a tl;dr summary here?
[12:26] <zyga> mvo: tl;dr; is apparor-parser requires hand-holding without the optimizations that we disable; we disable them because they are very slow on smaller systems. The fix involves fine tuning the profile so that we don't hit this pathological case
[12:27] <jdstrand> mvo: ack. I'm trying not to cause you any delays! :)
[12:28] <mvo> jdstrand: :)
[12:28] <mvo> zyga: nice, thank you
[12:28] <zyga>  brb
[12:36] <mup> PR snapd#8236 opened: interfaces: miscellaneous policy updates - 2.44 <Created by jdstrand> <https://github.com/snapcore/snapd/pull/8236>
[12:36] <jdstrand> mvo: there you go ^
[12:36] <mvo> jdstrand: \o/
[12:37] <jdstrand> I'll do a similar on for PR 8231
[12:37] <mup> PR #8231: interfaces/{docker,kubernetes}-support: updates for lastest k8s <Created by jdstrand> <https://github.com/snapcore/snapd/pull/8231>
[12:37] <mvo> jdstrand: +1
[12:40] <mup> PR snapd#8237 opened: interfaces/{docker,kubernetes}-support: updates for lastest k8s - 2.44 <Created by jdstrand> <https://github.com/snapcore/snapd/pull/8237>
[12:55] <pedronis> mborzecki: there's a arch failure in 8185 now: https://api.travis-ci.org/v3/job/660576207/log.txt
[13:02] <pedronis> pstolowski: did a pass on #8201, bunch of questions
[13:02] <mup> PR #8201: tests: mock prune ticker in overlord tests to reduce wait times <Created by stolowski> <https://github.com/snapcore/snapd/pull/8201>
[13:03] <pstolowski> pedronis: thanks
[13:11] <mborzecki> pedronis: hmm interesting, we had a workaround for a similar problem with snap services in one of the failover tests, restarted the travis job for now, but we'll probably need to add a litte fix tehre to make the test more robust
[13:11] <zyga> snapd/boot/export_test.go:38:14 uses type aliases
[13:14] <mup> PR snapd#8238 opened: many: fix a pari of ineffectual assignments <Created by zyga> <https://github.com/snapcore/snapd/pull/8238>
[13:16] <zyga> https://www.irccloud.com/pastebin/M7lC1BK4/
[13:16] <mup> PR snapd#8179 closed: interfaces: power control interface <Needs Samuele review> <⛔ Blocked> <Created by EthanHsieh> <Merged by pedronis> <https://github.com/snapcore/snapd/pull/8179>
[13:17] <zyga> pstolowski: is this still expected? overlordSuite.TestEnsureLoopPruneAbortsOld
[13:17] <zyga> pstolowski: IIRC you fixed it last week
[13:17] <pstolowski> zyga: yes, but not landed. the PR is being reviewed
[13:17] <zyga> ah
[13:17] <zyga> ok
[13:20]  * zyga switches to uio
[13:21] <mup> PR snapcraft#2967 closed: requirements: uprev click to 7.1.1 <Created by cjp256> <Merged by sergiusens> <https://github.com/snapcore/snapcraft/pull/2967>
[13:28] <mup> PR snapd#8239 opened: interfaces/audio_playback: Fix pulseaudio config access [2.44] <Created by Erick555> <https://github.com/snapcore/snapd/pull/8239>
[13:29] <cmatsuoka> cachio: I retrieved the image and I'm booting it locally, it's failing in install mode but it's different from what we saw in Frankfurt
[13:32] <cmatsuoka> hmm, slightly different, but the cause seems to be the same
[13:42] <mup> PR snapd#8215 closed: interfaces: make the network-status interface implicit on classic <Created by jhenstridge> <Merged by pedronis> <https://github.com/snapcore/snapd/pull/8215>
[13:58] <mup> PR snapd#8239 closed: interfaces/audio_playback: Fix pulseaudio config access [2.44] <Created by Erick555> <Merged by mvo5> <https://github.com/snapcore/snapd/pull/8239>
[13:59] <mup> PR snapd#8236 closed: interfaces: miscellaneous policy updates - 2.44 <Created by jdstrand> <Merged by mvo5> <https://github.com/snapcore/snapd/pull/8236>
[14:00] <zyga> 2fa
[14:00] <zyga> logged out again?
[14:13] <mup> PR snapd#8240 opened: tests: just remove user when the system is not managed on create-user-2 test (2.44) <Created by mvo5> <https://github.com/snapcore/snapd/pull/8240>
[14:13] <mup> PR snapd#8241 opened: interfaces: work around apparmor_parser slowness affecting uio <Created by zyga> <https://github.com/snapcore/snapd/pull/8241>
[14:15] <mup> PR snapd#8230 closed: cmd/snap-exec: add test case for LP:#1860369 <Created by zyga> <Merged by zyga> <https://github.com/snapcore/snapd/pull/8230>
[14:34] <mup> PR snapd#8242 opened: many: improve environment handling, fixing duplicate entries <Created by zyga> <https://github.com/snapcore/snapd/pull/8242>
[14:35] <zyga> ^ that's a longer PR sorry
[14:38] <zyga> mvo: about https://github.com/snapcore/snapd/pull/8242 -- let me know if you want a fix that's hacky but small and "maybe ok" for 2.44
[14:38] <zyga> mvo: otherwise I don't consider it a thing to rush
[14:38] <mup> PR #8242: many: improve environment handling, fixing duplicate entries <Created by zyga> <https://github.com/snapcore/snapd/pull/8242>
[14:39] <zyga> but please check as the bug affects microk8s
[14:39] <zyga> so perhaps we may have to
[14:39] <pstolowski> mvo: should the --reset be tagged for 2.44.x?
[14:39] <zyga> I did some impact analysis in the bug report, in comment 13
[14:39] <zyga> https://bugs.launchpad.net/snapd/+bug/1860369/comments/13
[14:39] <mup> Bug #1860369: Python apps broken in MicroStack (a classic snap) after Jan 14 snapcraft update <core20> <snapd:In Progress by zyga> <https://launchpad.net/bugs/1860369>
[14:41] <pedronis> mborzecki: now it (8185) failed again on arch and also fedora :/
[15:03]  * cachio lunch
[15:04] <mvo> pstolowski: +1
[15:04] <pstolowski> k
[15:23] <pstolowski> mvo: i remember you mentioned 'Core snap is installed when reverting a core18 based snap' ~last week; was the problem understood?
[15:30] <mvo> pstolowski: no :(
[15:30] <mvo> pstolowski: I think there is a bugreport and a testcase
[15:30] <mvo> pstolowski: but iirc noone looked at it
[15:30] <pstolowski> mvo: ack, ty
[15:35] <mvo> pstolowski: https://bugs.launchpad.net/snapd/+bug/1864944
[15:35] <mup> Bug #1864944: Core snap is installed when reverting a core18 based snap <original-1853411> <snapd:New> <https://launchpad.net/bugs/1864944>
[15:36] <mvo> pstolowski: it even has a test case that looks super easy to convert into ta spread test
[15:36] <pstolowski> mvo: yeah, i saw it, just wasn't sure if it was missing an update. i'm trying the steps right now
[15:37] <mvo> pstolowski: \o/
[15:55] <pstolowski> mvo: reproduced
[15:58] <mvo> pstolowski: nice!
[15:59] <zyga> back from break
[16:03] <pstolowski> mvo, pedronis: Revert() does not set base in snapsup, so it gets "core" by default
[16:04] <pedronis> pstolowski: ah
[16:04] <pedronis> good catch
[16:04] <mvo> pstolowski: \o/ nice find
[16:04]  * mvo hugs pstolowski
[16:07] <zyga> pedronis: thank you for the review on environment PR
[16:07] <zyga> pedronis: I think we could chat about it tomorrow (or when you have time) to figure out what we want to do
[16:07] <zyga> pedronis: I'll spend the rest of today on fixing the uio performance bug to the point where the draft can be opened and we can try to cherry-pick that to 2.44
[16:08] <zyga> pedronis: but as I said to mvo earlier, I don't know the priority of the environment bug as it seems to affect microk8s
[16:08] <zyga> pedronis: could be low (workaround in snapcraft, perhaps) or higher (blocked on us)
[16:11] <pedronis> zyga: what's the bug number?
[16:11] <pedronis> anyway if this is the fix, we cannot rush it, it's kind of large
[16:12] <zyga> pedronis: I agree
[16:12] <zyga> pedronis: it's referred from the 2nd commit, let me find it
[16:12] <zyga> https://bugs.launchpad.net/snapd/+bug/1860369
[16:12] <mup> Bug #1860369: Python apps broken in MicroStack (a classic snap) after Jan 14 snapcraft update <core20> <snapd:In Progress by zyga> <https://launchpad.net/bugs/1860369>
[16:26] <pedronis> zyga: it seems the branch adds feature that were not there, like ignoring order of hook envs etc
[16:27] <zyga> ignoring order of hook envs?
[16:27] <pedronis> zyga: ApplyDelta seems much more powerful than SubstituteEnv
[16:28] <pedronis> (because of the changed check), I'm not sure fixing a bug and expanding feature should happen together unless they relate to each other
[16:29] <pedronis> zyga: SubsituteEnv says very precisely: "and substitutes them top-down from the given environment"
[16:32] <zyga> pedronis: while that is true I think we need to sit down and evaluate what is the semantics we want; We should check what is documented on snapcraft docs and if that makes sense. We should also check how adapters impact anything. I suspect that previous behavior was buggy in more than one way. At the same time I agree that ApplyDelta is more "able" than previous code and can result in what people meant more than what
[16:32] <zyga> people got
[16:33] <pedronis> zyga: I can only repeat my point, if we want this in quickly expanding feature is a problem
[16:34] <zyga> pedronis: I don't know if this is needed urgently, I hope it's not but in such case I also offered a small targeted branch that fixes PATH issue in a more hacky but controlled way
[16:35] <zyga> pedronis: I think we should discuss and figure out how to evolve the bigger branch to the point where we are happy with it as my main goal was to fix the type system of the problem. We can discuss and change specific bits of implementation if what I did would affect existing snaps in a way we didn't intend
[16:35] <pedronis> zyga: have you tried what happens with the new code and a circular reference ?
[16:35] <zyga> I don't believe I have, unless one of the existing tests has effective circular refs
[16:35]  * zyga looks
[16:37] <zyga> pedronis: both get expanded to empty
[16:38] <zyga> pedronis: there's an existing test for that
[16:38] <zyga> pedronis: in env_test.go:265
[16:39] <zyga> (it behaved this way before as well)
[16:39] <pedronis> yes, but for different reasons
[16:47] <mup> PR snapd#8243 opened: o/snapstate: set base in SnapSetup on snap revert <Bug> <Created by stolowski> <https://github.com/snapcore/snapd/pull/8243>
[16:47] <pstolowski> mvo: ^
[16:50] <zyga> pedronis: I think this is interesting https://github.com/snapcore/snapd/pull/8242#discussion_r390461058
[16:50] <mup> PR #8242: many: improve environment handling, fixing duplicate entries <Bug> <Needs Samuele review> <Created by zyga> <https://github.com/snapcore/snapd/pull/8242>
[16:51] <zyga> pedronis: I want to EOD soon as I want to sleep a little longer today, would you mind if we parked this until tomorrow?
[16:51] <zyga> pedronis: I want to spend some more time on the uio code
[16:51] <pedronis> zyga: that's fine, my general input that we should try to be more convervative with the change
[16:52] <zyga> I agree
[16:52] <mvo> pstolowski: nice, thank you
[16:52] <zyga> I wonder what people would expect in the example I gave, I think it's a good chance we will get 50-50 responses
[16:52] <pstolowski> eod, need to run an errand
[16:52] <zyga> pedronis: note that current code (in master) just inserts both PATH values, because of the bug
[16:53] <zyga> so you kind of get a superposition :)
[16:53] <zyga> but that's for sure not what we want
[16:53] <pedronis> unless we promised that we merge values
[16:53] <pedronis> the one in the app should win
[16:53] <cjp256> zyga/pedronis: the priority for build env is high for core20, as it won't generate command wrappers.  snapcraft currently forces the wrappers for when adapter != none, and it became a problem when we stopped generating unnecessary wrappers
[16:54] <cjp256> but core20 still isn't for some time, so it's not a rush imo :)
[16:55] <zyga> pedronis: I wonder if the fact that this was shoved through shell wrappers meant that we got the expanding semantics at any time in the past
[16:55] <zyga> pedronis: tomorrow I'll write a regression test for this
[16:55] <zyga> pedronis: as in end-to-end spread test
[16:55] <zyga> pedronis: at least then it's measured
[17:03] <mvo> cachio: if you could double check and approve 8240 that would be great
[17:09] <mvo> zyga: are you around? I wonder how 1866424 should be attacked, it seems a missing gpio should not cause snapd to stop refreshing forever
[17:09] <zyga> around
[17:09] <mvo> zyga: I wonder if we could make missing gpios a warning?
[17:09] <zyga> mvo: "ish", the problem is what you want to happen then
[17:09] <mvo> zyga: but it's a bit tricky as it's a real error
[17:09] <zyga> but yeagh
[17:09] <mvo> zyga: yeah, the gpio will be missing from the profile
[17:09] <zyga> it's not really missing, the user was holding it wrong (unexporting behind snapd's back)
[17:10] <mvo> zyga: so subsequent stuff may misbehave
[17:10] <zyga> but I agree it's a very bad property
[17:10] <zyga> mvo: consider this idea:
[17:10] <zyga> mvo: when an interface instance (plug or slot)'s corresponding method fails, we could mark it as bad and skip it in the profile generation
[17:10] <zyga> mvo: we could warn (finally a use case for warnings)
[17:11] <zyga> mvo: it would require some changes around but not too hard
[17:11] <zyga> mvo: I would rather do it at interface level
[17:11] <zyga> mvo: rather than at the level of a specific method
[17:11] <zyga> mvo: because it's more proper, in my eyes, to say "this plug or slot is entirely absent"
[17:11] <mvo> zyga: yeah, the downside of that is that it requires more discussion/work so it will take longer but I agree
[17:12] <zyga> mvo: rather than to say "a specific part of the implementation failed so we skipped it"
[17:12] <zyga> mvo: since those can have security implications
[17:12] <zyga> mvo: .e.g. apparmor gave you access to /dev but udev tagging failed so you have open access
[17:13] <mvo> zyga: aha, indeed, I was thinking we would only narrow access down
[17:13] <zyga> unfortunately that is not the case
[17:13] <zyga> mvo: I could look at that after UIO tomorrow
[17:13] <mvo> zyga: yeah, makes sense. i pasted what you wrote into the bug
[17:14] <zyga> mvo: if you have an agreement on the design
[17:14] <mvo> zyga: that would be nice indeed
[17:14] <zyga> perfect, thank you
[17:14] <mvo> zyga: it sounds like we can have a quick chat during standup/after stnadup
[17:14] <zyga> that sounds good
[17:14] <zyga> what I said has a scary component
[17:14] <mvo> zyga: we certainly need samuele to think about it/agree :)
[17:14] <zyga> because what it means if an implicit slot misbehaves?
[17:14] <zyga> mvo: does it mean it is disconnected
[17:14] <zyga> is it broken?
[17:15] <zyga> some things to ponder over
[17:15] <mvo> zyga: we could error in those cases maybe?
[17:15] <zyga> yes but the devil is in the details, a single interface (plug or slot) interacts with loads of parts
[17:15] <zyga> in my eyes it would be neutered _for the purpose of a given connection_
[17:15] <zyga> so not globally
[17:16] <zyga> so less chance to break the world
[17:16]  * mvo nods
[17:22]  * zyga EODs without finishing UIO
[17:23] <zyga> I'm sorry, need to rest
[17:26] <mvo> zyga: no worries, get some good rest!
[18:49] <mup> PR snapcraft#2965 closed: rosdep: include EOL ROS distros <Created by kyrofa> <Merged by sergiusens> <https://github.com/snapcore/snapcraft/pull/2965>
[19:04] <mup> PR snapcraft#2964 closed: build providers: remove LXD specific env setup <Created by sergiusens> <Merged by sergiusens> <https://github.com/snapcore/snapcraft/pull/2964>
[19:24] <ogra> $ grep ubuntu /etc/group
[19:24] <ogra> sudo:x:27:ubuntu
[19:24] <ogra> docker:x:113:ubuntu
[19:25] <ogra> hmm, so why are there entries for a non-existing ubuntu user in my readonly /etc/group file in core16
[21:53] <mup> PR snapcraft#2962 closed: Go: unable to build snap when using `go mod` and main package is not in the root <Created by pavel-d> <Merged by sergiusens> <https://github.com/snapcore/snapcraft/pull/2962>


[08:00] <dholbach> good morning
[12:36] <bluesabre> Greetings MOTU!
[12:37] <bluesabre> I know it's short notice, but I was hoping that we might be able to get light-locker-settings uploaded to trusty before FF
[12:37] <bluesabre> https://bugs.launchpad.net/light-locker-settings/+bug/1281536
[12:37] <ochosi> +1
[12:37] <ochosi> we need it quite direly for xubuntu, which is going to use light-locker by default
[12:38] <bluesabre> light-locker-settings is a simple configuration utility for light-locker
[12:38] <bluesabre> it helps to fill the gap between light-locker and xscreensaver
[12:40] <ochosi> (sidenote: upstream we haven't provided a settings-utility for light-locker yet, but we might do that for a later release, says /me with the light-locker-dev hat on)
[12:41] <ochosi> if you have questions/doubts, feel free to ping us
[12:53] <ochosi> and just to mention that, the xubuntu community would be very greatful! show your <3 for xubuntu :)
[12:55] <Laney> bluesabre: you should subscribe ubuntu-sponsors to sponsorship requests
[12:56] <ochosi> Laney: thanks, i've done it now (bluesabre is already @work)
[12:56] <bluesabre> ok, thanks Laney. I didn't know if the process was different for packages not yet in the archive
[12:57] <ochosi> oh, and there he is! :)
[12:57] <bluesabre> and here I go, bbl
[12:58] <Laney> thanks, no it's not
[12:58] <bluesabre> was following https://wiki.ubuntu.com/UbuntuDevelopment/NewPackages
[12:58] <Laney> it makes the request appear on the list that people look at
[12:58] <bluesabre> but thanks
[12:58] <Laney> feel free to edit that to add this step
[13:09] <ochosi> Laney: ok, added it to the newpackages page
[20:36] <Logan_> infinity: This is so odd. Some packages to which I previously added dh-autoreconf and previously built properly on ppc64el are failing.
[20:37] <Logan_> cc doko
[20:37] <Logan_> Was there a regression in libtool?
[20:49] <Ampelbein> Logan_: Which package for example?
[23:02] <infinity> Logan_: It won't be a libtool/autoconf regression, it'll be something else (like the toolchain now defaulting to -O3, or possibly just a rebuild dep ordering thing in some cases)
[23:02] <infinity> Logan_: Do you have examples?
[23:51] <Logan_> infinity: https://launchpad.net/ubuntu/+source/ulogd2/2.0.3-1ubuntu1


[00:04] <axisys> http://wiki.debian.org/QemuUserEmulation <-- it points to http://www.emdebian.org/debian/pool/cross-unstable/g/glibc/libc6-dev-arm-cross_2.3.6.ds1-6_all.deb
[00:05] <axisys> but that does not exist
[00:16] <GrueMaster> axisys: That seems like a question for the debian channels.
[00:17] <axisys> GrueMaster: was replying to twb's comment from yesterday.. i guess he left
[00:17] <axisys> GrueMaster: trying to find out how to cross compile a kernel module for armv7l.. host is ubuntu on x86
[00:18] <GrueMaster> Oh, I'm actually doing the same.  Here is the instructions:  https://wiki.ubuntu.com/Kernel/BuildYourOwnKernel
[00:18] <axisys> GrueMaster: :-)
[00:19] <axisys> how do I know if it is armel or armhf ? dont know the difference
[00:20] <Neko> axisys, http://www.emdebian.org/debian/pool/main/g/glibc/
[00:20] <Neko> they moved it. the debian wiki is out of date, feel free to update.
[00:20] <axisys> Neko: i dont use debian
[00:21] <Neko> you're on ubuntu?
[00:21] <axisys> Neko: my laptop is ubuntu 11.10 x86 64bit
[00:21] <axisys> twb suggested to read that.. hence my query
[00:21] <GrueMaster> axisys: What are you trying to build?
[00:21] <Neko> oh.. ARCH=arm CROSS_COMPILE=arm-linux-gnueabi-
[00:21] <Neko> to make. it'll work.
[00:21] <Neko> you really don't need much else than those two
[00:22] <axisys> i want to build a rtl8150.ko for android tablet
[00:22] <axisys> usb ethernet driver
[00:22] <Neko> just the driver on it's own?
[00:22] <axisys> Neko: i need to get the cross compiler
[00:22] <Neko> it's part of the kernel since forever so you're better off building the whole kernel from scratch
[00:22] <axisys> Neko: kernel module .. yes
[00:22] <axisys> Neko: right
[00:23] <axisys> Neko: but never done it
[00:23] <axisys> Neko: cyanogenmod's wiki is not working for me
[00:23] <Neko> never compiled a kernel or never cross compiled a kernel?
[00:23] <axisys> neither
[00:23] <axisys> well did a little bit today with a cross compiler from codesourcery.com ?
[00:23] <axisys> i think that is the url.. forgot
[00:24] <axisys> in the past did build an alpha kernel.. but still very limited experience..
[00:24] <Neko> them's the guys, but you should be able to use the arm cross compilers in the standard ubuntu repos
[00:24] <axisys> have been using unix for 10+ yrs.. but now like to dive into lower layer
[00:24] <Neko> just apt-get install gcc-arm-linux-gnueabi binutils-multiarch
[00:25] <Neko> don't kick me if that doesn't install anything, I'm remembering those from last time I had to install them :D
[00:25] <Neko> you'll probably also need u-boot-tools or u-boot-mkimage or whatever they call it now
[00:25] <axisys> Neko: was looking at GrueMaster's url
[00:25] <Neko> you're not building an ubuntu kernel though
[00:25] <axisys> Neko: no
[00:26] <Neko> so half of that doesn't make any sense for you
[00:26] <axisys> i think i need a good cross compiler.. i got all the CM kernel
[00:26] <axisys> but now need to build the kernel and then push the driver over
[00:27] <axisys> here is my android
[00:27] <axisys> Linux localhost <IP_ADDRESS>-00020-g3d351b6 #1 SMP PREEMPT Wed Oct 19 10:52:26 JST 2011 armv7l GNU/Linux
[00:28] <Neko> okay you probably best to get the config from the kernel on the android device, I dunno how you're going to get that off though, find the exact source used to build it, and then just cp myandroidconfig /my/linux/source/.config and then "make ARCH=arm CROSS_COMPILE=arm-none-linux-gnueabi- menuconfig"
[00:28] <Neko> hit / and then type rtl8150 and find the menu it's in, go there, enable it as a module, et voila
[00:28] <axisys> i got the kernel
[00:28] <Neko> make ARCH=arm CROSS_COMPILE=arm-none-linux-gnueabi- uImage
[00:28] <GrueMaster> You should be able to make the module out of tree.  Just add "export CROSS_COMPILE=arm-linux-gnueabi-" to the process of making an out-of-tree module.
[00:28] <Neko> that's assuming it boots off a uImage
[00:29] <axisys> ok so first thing first.. what do I run to get the arm cross compiler?
[00:29] <Neko> you said you already have it
[00:29] <axisys> i have the kernel
[00:29] <Neko> I'm gonna leave you to it, I have a ton of work to do
[00:29] <Neko> you said you got a compiler from codesourcery.com
[00:30] <Neko> so you're set up and ready to go
[00:30] <axisys> the cross compiler i used was from there ^ .. but did not build any module
[00:30] <Neko> .. did you make modules?
[00:30] <Neko> and use the original config and update it?
[00:30] <Neko> no wait I said I was gonna leave you to it. sorry, bye :D
[00:31] <axisys> http://paste.ubuntu.com/865728/ <- this is what I ran so far
[00:34] <GrueMaster> axisys: I personally don't want to sound like an ass, but I really don't know how to help on this.  This is more of an android question than an ubuntu-arm question.
[00:35] <axisys> well.. do I need to run make modules after make ?
[00:35] <GrueMaster> There is a way to just make the one module you need.  let me look.
[00:36] <GrueMaster> http://hex.ro/wp/blog/compile-an-android-kernel-module-outside-the-kernel-source-tree/ will give you some ideas.  But you should be able to build that module by itsself.
[00:37] <axisys> GrueMaster: thanks
[00:38] <GrueMaster> Here's a google search that helps.  "kernel module build android".
[00:38] <GrueMaster> Tons of returns.
[00:38] <axisys> :-) .. wow you did not give me the lmgtfy .. lol
[00:39] <axisys> GrueMaster: thank you for your help
[00:39] <GrueMaster> This one in particular might be more helpful.  http://omappedia.org/wiki/Building_Android_Kernel
[00:39] <GrueMaster> Thant's not how I roll.  :P
[00:40] <axisys> GrueMaster: i was using the first link from that search.. let me bug those guys more
[00:40] <axisys> i think i am very close
[00:40] <GrueMaster> Let me know if it works for you.
[00:40] <axisys> GrueMaster: sure
[03:07] <GrueMaster> HA!  Fixed my audio (bug 925094) and my network (bug 838200) on my beaglexm.  Now to get the kernel team to accept them.
[03:07] <ubot2`> Launchpad bug 925094 in linux "No audio on omap (beagleXM) system" [Medium,Confirmed] https://launchpad.net/bugs/925094
[03:07] <ubot2`> Launchpad bug 838200 in u-boot-linaro "No network support on Beagle XM" [High,Confirmed] https://launchpad.net/bugs/838200
[10:24] <James_KL> hello , installing ubuntu on arm , gives that error x86_64 : http://bitsy.me/img4dy - WTF?
[19:21] <juno> hello
[19:22] <juno> I have been an ubuntu user for ages and now have some spare time and would like to contribute, specially interested in ARM issues
[19:25] <juno> have been cherry picking ftbfs bugs on armhf, any ideas about how to contribute best to the upcoming release?
[22:26] <steev_> juno: silly question, but how do you go about finding the ftbfs bugs on armhf?  i suck at launchpad
[22:36] <infinity> steev_: http://people.ubuntuwire.org/~wgrant/rebuild-ftbfs-test/test-rebuild-20120201-precise.html
[22:36] <infinity> steev_: http://qa.ubuntuwire.org/ftbfs/
[22:36] <steev_> oh spiffy, i like wgrant, he's good people
[22:36] <infinity> steev_: Between those two pages, there should be enough FTBFS and bug references to keep anyone busy.
[22:36] <infinity> steev_: The first is a summary of the last rebuild test, the second is the state of the current archive.
[22:38] <steev_> yeah i've been playing with precise armhf on my efika for a while now, it's decent enough (there are some minor issues with opengl es that i haven't tracked down)
[22:51] <juno> steev_: I have been using this page, which is a subset of the page mentioned by infinity, only showing armel and armhf FTBFS: http://qa.ubuntuwire.org/ftbfs/primary-precise-armhf.html
[23:12] <wgrant> juno: Hm, I actually meant to delete that one when I added armhf to the main one. But if it's still useful, I'll keep it :)
[23:13] <steev_> wgrant: i like it, i can focus on the arch i care about ;)
[23:22] <juno> wgrant: agree with steev_, it allows to focus on the arch
[23:27] <juno> by the way, I read a lot in this channel about setting up a pandaboard with usb disk, but not so much about NFS
[23:28] <juno> is there any reason why I should not use a root-NFS mount setup? I love the control this gives me to try different rootfs easily
[23:35] <mythos> i use it all the time
[23:35] <mythos> so... no, there is not really a reason not to do it
[23:36] <mythos> in fact, i love it to restore the root with a simple tar xzf -C


[14:53] -queuebot:#ubuntu-ci-eng- tdaitx, https://bileto.ubuntu.com/#/ticket/3953 Pending binary packages
[15:14] -queuebot:#ubuntu-ci-eng- tdaitx, https://bileto.ubuntu.com/#/ticket/3953 Successfully built
[17:20] -queuebot:#ubuntu-ci-eng- xnox, https://bileto.ubuntu.com/#/ticket/3967 Preparing packages
[22:38] -queuebot:#ubuntu-ci-eng- Laney, https://bileto.ubuntu.com/#/ticket/3937 Dependency wait (focal/gjs). Diff missing (focal/adwaita-icon-theme, focal/mozjs68). Needs rebuild due to burned version number (focal/gnome-shell-extensions). Needs rebuild due to higher version at destination (focal/budgie-desktop, focal/gnome-shell, focal/gnome-shell-extension-appindicator, focal/gnome-shell-extension-desktop-icons, focal/gnome-shell-extension-ubuntu-dock, focal/mutter, focal/y