[00:02] -kubuntu-ci:#kubuntu-devel- Yippee, build fixed!
[00:02] -kubuntu-ci:#kubuntu-devel- Project merger_kdesdk-thumbnailers build #103: FIXED in 1 min 37 sec: http://kci.pangea.pub/job/merger_kdesdk-thumbnailers/103/
[00:04] -kubuntu-ci:#kubuntu-devel- Project merger_kdiamond build #613: FAILURE in 3 min 29 sec: http://kci.pangea.pub/job/merger_kdiamond/613/
[00:07] -kubuntu-ci:#kubuntu-devel- Project mgmt_merger build #697: STILL UNSTABLE in 6 min 13 sec: http://kci.pangea.pub/job/mgmt_merger/697/
[00:07] -kubuntu-ci:#kubuntu-devel- Project mgmt_progenitor build #683: STILL UNSTABLE in 6 min 15 sec: http://kci.pangea.pub/job/mgmt_progenitor/683/
[00:12] -kubuntu-ci:#kubuntu-devel- Project yakkety_unstable_kgpg build #97: STILL FAILING in 4 min 1 sec: http://kci.pangea.pub/job/yakkety_unstable_kgpg/97/
[00:13] -kubuntu-ci:#kubuntu-devel- Project xenial_unstable_kgpg build #97: STILL FAILING in 4 min 16 sec: http://kci.pangea.pub/job/xenial_unstable_kgpg/97/
[00:22] -kubuntu-ci:#kubuntu-devel- Project xenial_unstable_kgpg build #98: STILL FAILING in 3 min 45 sec: http://kci.pangea.pub/job/xenial_unstable_kgpg/98/
[00:25] -kubuntu-ci:#kubuntu-devel- Project yakkety_unstable_kgpg build #98: STILL FAILING in 8 min 30 sec: http://kci.pangea.pub/job/yakkety_unstable_kgpg/98/
[00:27] -kubuntu-ci:#kubuntu-devel- Project yakkety_unstable_kppp build #89: STILL UNSTABLE in 19 min: http://kci.pangea.pub/job/yakkety_unstable_kppp/89/
[00:27] -kubuntu-ci:#kubuntu-devel- Project yakkety_unstable_kdesdk-kioslaves build #47: STILL UNSTABLE in 19 min: http://kci.pangea.pub/job/yakkety_unstable_kdesdk-kioslaves/47/
[00:28] -kubuntu-ci:#kubuntu-devel- Project xenial_unstable_kdesdk-kioslaves build #86: STILL UNSTABLE in 20 min: http://kci.pangea.pub/job/xenial_unstable_kdesdk-kioslaves/86/
[00:43] -kubuntu-ci:#kubuntu-devel- Project xenial_unstable_kde-runtime build #206: STILL FAILING in 34 min: http://kci.pangea.pub/job/xenial_unstable_kde-runtime/206/
[00:43] -kubuntu-ci:#kubuntu-devel- Project xenial_unstable_kppp build #12: STILL UNSTABLE in 35 min: http://kci.pangea.pub/job/xenial_unstable_kppp/12/
[00:59] -kubuntu-ci:#kubuntu-devel- Project xenial_unstable_kcoreaddons build #268: STILL UNSTABLE in 32 min: http://kci.pangea.pub/job/xenial_unstable_kcoreaddons/268/
[00:59] -kubuntu-ci:#kubuntu-devel- Yippee, build fixed!
[00:59] -kubuntu-ci:#kubuntu-devel- Project xenial_unstable_breeze-icons build #292: FIXED in 32 min: http://kci.pangea.pub/job/xenial_unstable_breeze-icons/292/
[00:59] -kubuntu-ci:#kubuntu-devel- Project xenial_unstable_kopete build #89: STILL UNSTABLE in 51 min: http://kci.pangea.pub/job/xenial_unstable_kopete/89/
[01:00] -kubuntu-ci:#kubuntu-devel- Project yakkety_unstable_kde-runtime build #212: STILL FAILING in 51 min: http://kci.pangea.pub/job/yakkety_unstable_kde-runtime/212/
[01:12] -kubuntu-ci:#kubuntu-devel- Project xenial_unstable_kde-runtime build #207: STILL FAILING in 23 min: http://kci.pangea.pub/job/xenial_unstable_kde-runtime/207/
[01:12] -kubuntu-ci:#kubuntu-devel- Project yakkety_unstable_kopete build #66: STILL UNSTABLE in 1 hr 4 min: http://kci.pangea.pub/job/yakkety_unstable_kopete/66/
[01:12] -kubuntu-ci:#kubuntu-devel- Project yakkety_unstable_kauth build #158: STILL UNSTABLE in 28 min: http://kci.pangea.pub/job/yakkety_unstable_kauth/158/
[01:12] -kubuntu-ci:#kubuntu-devel- Project yakkety_unstable_okular build #100: STILL UNSTABLE in 27 min: http://kci.pangea.pub/job/yakkety_unstable_okular/100/
[01:12] -kubuntu-ci:#kubuntu-devel- Project xenial_unstable_okular build #22: STILL UNSTABLE in 29 min: http://kci.pangea.pub/job/xenial_unstable_okular/22/
[01:12] -kubuntu-ci:#kubuntu-devel- Yippee, build fixed!
[01:12] -kubuntu-ci:#kubuntu-devel- Project yakkety_unstable_breeze-icons build #176: FIXED in 28 min: http://kci.pangea.pub/job/yakkety_unstable_breeze-icons/176/
[01:12] -kubuntu-ci:#kubuntu-devel- Project yakkety_unstable_kdevelop-pg-qt build #23: STILL UNSTABLE in 28 min: http://kci.pangea.pub/job/yakkety_unstable_kdevelop-pg-qt/23/
[01:13] -kubuntu-ci:#kubuntu-devel- Project xenial_unstable_kcrash build #279: STILL UNSTABLE in 13 min: http://kci.pangea.pub/job/xenial_unstable_kcrash/279/
[01:23] -kubuntu-ci:#kubuntu-devel- Project xenial_unstable_kauth build #286: STILL UNSTABLE in 23 min: http://kci.pangea.pub/job/xenial_unstable_kauth/286/
[01:30] -kubuntu-ci:#kubuntu-devel- Project yakkety_unstable_kde-runtime build #213: STILL FAILING in 24 min: http://kci.pangea.pub/job/yakkety_unstable_kde-runtime/213/
[01:30] -kubuntu-ci:#kubuntu-devel- Project yakkety_unstable_kcrash build #155: STILL UNSTABLE in 18 min: http://kci.pangea.pub/job/yakkety_unstable_kcrash/155/
[02:15] -kubuntu-ci:#kubuntu-devel- Project xenial_unstable_kwallet build #293: STILL UNSTABLE in 16 min: http://kci.pangea.pub/job/xenial_unstable_kwallet/293/
[02:24] -kubuntu-ci:#kubuntu-devel- Project yakkety_unstable_kwallet build #132: STILL UNSTABLE in 16 min: http://kci.pangea.pub/job/yakkety_unstable_kwallet/132/
[03:02] <ahoneybun> darn OBS has not updated the PPA for yakkety
[03:03] <DarinMiller> OBS?
[03:11] <ahoneybun> https://obsproject.com/
[03:37] <tsimonq2> Night o/
[03:39] <DarinMiller> night simon o/
[03:47] -kubuntu-ci:#kubuntu-devel- Project xenial_unstable_spectacle build #109: STILL UNSTABLE in 13 min: http://kci.pangea.pub/job/xenial_unstable_spectacle/109/
[03:47] -kubuntu-ci:#kubuntu-devel- Project yakkety_unstable_spectacle build #88: STILL UNSTABLE in 13 min: http://kci.pangea.pub/job/yakkety_unstable_spectacle/88/
[03:55] -kubuntu-ci:#kubuntu-devel- Project xenial_unstable_kdenlive build #288: STILL FAILING in 24 min: http://kci.pangea.pub/job/xenial_unstable_kdenlive/288/
[03:55] -kubuntu-ci:#kubuntu-devel- Project yakkety_unstable_kdenlive build #137: STILL FAILING in 24 min: http://kci.pangea.pub/job/yakkety_unstable_kdenlive/137/
[04:08] -kubuntu-ci:#kubuntu-devel- Project xenial_unstable_okteta build #117: STILL UNSTABLE in 21 min: http://kci.pangea.pub/job/xenial_unstable_okteta/117/
[04:08] -kubuntu-ci:#kubuntu-devel- Project xenial_unstable_umbrello build #95: STILL UNSTABLE in 21 min: http://kci.pangea.pub/job/xenial_unstable_umbrello/95/
[04:15] -kubuntu-ci:#kubuntu-devel- Project xenial_unstable_kstars build #260: STILL UNSTABLE in 28 min: http://kci.pangea.pub/job/xenial_unstable_kstars/260/
[04:19] -kubuntu-ci:#kubuntu-devel- Project xenial_unstable_kdenlive build #289: STILL FAILING in 19 min: http://kci.pangea.pub/job/xenial_unstable_kdenlive/289/
[04:19] -kubuntu-ci:#kubuntu-devel- Project yakkety_unstable_kdenlive build #138: STILL FAILING in 19 min: http://kci.pangea.pub/job/yakkety_unstable_kdenlive/138/
[04:22] -kubuntu-ci:#kubuntu-devel- Project yakkety_unstable_kstars build #128: STILL UNSTABLE in 26 min: http://kci.pangea.pub/job/yakkety_unstable_kstars/128/
[04:22] -kubuntu-ci:#kubuntu-devel- Project yakkety_unstable_ktp-common-internals build #137: STILL UNSTABLE in 20 min: http://kci.pangea.pub/job/yakkety_unstable_ktp-common-internals/137/
[04:22] -kubuntu-ci:#kubuntu-devel- Project xenial_unstable_ktp-common-internals build #211: STILL UNSTABLE in 21 min: http://kci.pangea.pub/job/xenial_unstable_ktp-common-internals/211/
[04:23] -kubuntu-ci:#kubuntu-devel- Project yakkety_unstable_umbrello build #80: STILL UNSTABLE in 26 min: http://kci.pangea.pub/job/yakkety_unstable_umbrello/80/
[04:23] -kubuntu-ci:#kubuntu-devel- Project yakkety_unstable_plasma-framework build #152: STILL FAILING in 19 min: http://kci.pangea.pub/job/yakkety_unstable_plasma-framework/152/
[04:25] -kubuntu-ci:#kubuntu-devel- Project yakkety_unstable_kde-baseapps build #102: STILL FAILING in 10 min: http://kci.pangea.pub/job/yakkety_unstable_kde-baseapps/102/
[04:30] -kubuntu-ci:#kubuntu-devel- Project xenial_unstable_libkcompactdisc build #51: STILL UNSTABLE in 16 min: http://kci.pangea.pub/job/xenial_unstable_libkcompactdisc/51/
[04:36] -kubuntu-ci:#kubuntu-devel- Project xenial_unstable_kde-baseapps build #97: STILL FAILING in 4 min 55 sec: http://kci.pangea.pub/job/xenial_unstable_kde-baseapps/97/
[04:36] -kubuntu-ci:#kubuntu-devel- Project yakkety_unstable_kde-baseapps build #103: STILL FAILING in 5 min 56 sec: http://kci.pangea.pub/job/yakkety_unstable_kde-baseapps/103/
[04:44] -kubuntu-ci:#kubuntu-devel- Project xenial_unstable_kirigami build #37: STILL UNSTABLE in 20 min: http://kci.pangea.pub/job/xenial_unstable_kirigami/37/
[04:44] -kubuntu-ci:#kubuntu-devel- Project xenial_unstable_ktp-auth-handler build #185: STILL UNSTABLE in 21 min: http://kci.pangea.pub/job/xenial_unstable_ktp-auth-handler/185/
[04:44] -kubuntu-ci:#kubuntu-devel- Project yakkety_unstable_ktp-auth-handler build #138: STILL UNSTABLE in 21 min: http://kci.pangea.pub/job/yakkety_unstable_ktp-auth-handler/138/
[04:44] -kubuntu-ci:#kubuntu-devel- Project xenial_unstable_plasma-mediacenter build #188: STILL UNSTABLE in 21 min: http://kci.pangea.pub/job/xenial_unstable_plasma-mediacenter/188/
[04:45] -kubuntu-ci:#kubuntu-devel- Project xenial_unstable_kde-baseapps build #98: STILL FAILING in 3 min 46 sec: http://kci.pangea.pub/job/xenial_unstable_kde-baseapps/98/
[04:45] -kubuntu-ci:#kubuntu-devel- Project xenial_unstable_kwin build #7: STILL FAILING in 50 sec: http://kci.pangea.pub/job/xenial_unstable_kwin/7/
[04:51] -kubuntu-ci:#kubuntu-devel- Project xenial_unstable_kwin build #8: STILL FAILING in 43 sec: http://kci.pangea.pub/job/xenial_unstable_kwin/8/
[04:55] -kubuntu-ci:#kubuntu-devel- Project yakkety_unstable_plasma-framework build #153: STILL FAILING in 26 min: http://kci.pangea.pub/job/yakkety_unstable_plasma-framework/153/
[05:02] -kubuntu-ci:#kubuntu-devel- Project xenial_unstable_plasma-integration build #6: STILL UNSTABLE in 16 min: http://kci.pangea.pub/job/xenial_unstable_plasma-integration/6/
[05:02] -kubuntu-ci:#kubuntu-devel- Project xenial_unstable_marble build #7: STILL FAILING in 17 min: http://kci.pangea.pub/job/xenial_unstable_marble/7/
[05:03] -kubuntu-ci:#kubuntu-devel- Project xenial_unstable_plasma-sdk build #230: STILL UNSTABLE in 18 min: http://kci.pangea.pub/job/xenial_unstable_plasma-sdk/230/
 anybody awake here?
 how do I add Yakety to this bug report? https://bugs.launchpad.net/network-manager-vpnc/+bug/1297849
[05:09] -kubuntu-ci:#kubuntu-devel- Project xenial_unstable_discover build #5: STILL FAILING in 7 min 0 sec: http://kci.pangea.pub/job/xenial_unstable_discover/5/
[05:11] -kubuntu-ci:#kubuntu-devel- Project yakkety_unstable_akonadi-calendar build #6: STILL UNSTABLE in 16 min: http://kci.pangea.pub/job/yakkety_unstable_akonadi-calendar/6/
[05:12] -kubuntu-ci:#kubuntu-devel- Project xenial_unstable_akonadi-contacts build #42: STILL UNSTABLE in 17 min: http://kci.pangea.pub/job/xenial_unstable_akonadi-contacts/42/
[05:12] -kubuntu-ci:#kubuntu-devel- Project yakkety_unstable_kirigami build #41: STILL UNSTABLE in 16 min: http://kci.pangea.pub/job/yakkety_unstable_kirigami/41/
[05:12] -kubuntu-ci:#kubuntu-devel- Project yakkety_unstable_plasma-mediacenter build #105: STILL UNSTABLE in 16 min: http://kci.pangea.pub/job/yakkety_unstable_plasma-mediacenter/105/
[05:13] -kubuntu-ci:#kubuntu-devel- Project yakkety_unstable_kwin build #7: STILL FAILING in 1 min 7 sec: http://kci.pangea.pub/job/yakkety_unstable_kwin/7/
[05:19] -kubuntu-ci:#kubuntu-devel- Project yakkety_unstable_kwin build #8: STILL FAILING in 50 sec: http://kci.pangea.pub/job/yakkety_unstable_kwin/8/
[05:19] -kubuntu-ci:#kubuntu-devel- Project xenial_unstable_discover build #6: STILL FAILING in 4 min 54 sec: http://kci.pangea.pub/job/xenial_unstable_discover/6/
[05:24] -kubuntu-ci:#kubuntu-devel- Project xenial_unstable_marble build #8: STILL FAILING in 17 min: http://kci.pangea.pub/job/xenial_unstable_marble/8/
[05:27] -kubuntu-ci:#kubuntu-devel- Project yakkety_unstable_plasma-integration build #6: STILL UNSTABLE in 15 min: http://kci.pangea.pub/job/yakkety_unstable_plasma-integration/6/
[05:28] -kubuntu-ci:#kubuntu-devel- Project yakkety_unstable_plasma-sdk build #124: STILL UNSTABLE in 15 min: http://kci.pangea.pub/job/yakkety_unstable_plasma-sdk/124/
[05:29] -kubuntu-ci:#kubuntu-devel- Project yakkety_unstable_marble build #7: STILL FAILING in 17 min: http://kci.pangea.pub/job/yakkety_unstable_marble/7/
[05:40] -kubuntu-ci:#kubuntu-devel- Project yakkety_unstable_discover build #6: STILL UNSTABLE in 12 min: http://kci.pangea.pub/job/yakkety_unstable_discover/6/
[05:40] -kubuntu-ci:#kubuntu-devel- Project xenial_unstable_kdeplasma-addons build #3: STILL FAILING in 13 min: http://kci.pangea.pub/job/xenial_unstable_kdeplasma-addons/3/
[05:51] -kubuntu-ci:#kubuntu-devel- Project xenial_unstable_kdepim-addons build #74: STILL FAILING in 39 sec: http://kci.pangea.pub/job/xenial_unstable_kdepim-addons/74/
[05:51] -kubuntu-ci:#kubuntu-devel- Project yakkety_unstable_kdepim-addons build #7: STILL FAILING in 43 sec: http://kci.pangea.pub/job/yakkety_unstable_kdepim-addons/7/
[05:57] -kubuntu-ci:#kubuntu-devel- Project xenial_unstable_kdepim-addons build #75: STILL FAILING in 37 sec: http://kci.pangea.pub/job/xenial_unstable_kdepim-addons/75/
[05:57] -kubuntu-ci:#kubuntu-devel- Project yakkety_unstable_marble build #8: STILL FAILING in 22 min: http://kci.pangea.pub/job/yakkety_unstable_marble/8/
[05:57] -kubuntu-ci:#kubuntu-devel- Project yakkety_unstable_kdepim-addons build #8: STILL FAILING in 41 sec: http://kci.pangea.pub/job/yakkety_unstable_kdepim-addons/8/
[05:57] -kubuntu-ci:#kubuntu-devel- Project xenial_unstable_kdeplasma-addons build #4: STILL FAILING in 11 min: http://kci.pangea.pub/job/xenial_unstable_kdeplasma-addons/4/
[06:03] -kubuntu-ci:#kubuntu-devel- Project yakkety_unstable_kdeplasma-addons build #5: STILL FAILING in 12 min: http://kci.pangea.pub/job/yakkety_unstable_kdeplasma-addons/5/
[06:21] -kubuntu-ci:#kubuntu-devel- Project yakkety_unstable_kdeplasma-addons build #6: STILL FAILING in 13 min: http://kci.pangea.pub/job/yakkety_unstable_kdeplasma-addons/6/
[06:23] <yofel> tsimonq2: dunno, as I said, I don't have time for afternoon meetings before friday
[06:37] <yofel> ovidiuflorin: if you open the URL for the package task, i.e. https://bugs.launchpad.net/ubuntu/+source/network-manager-vpnc/+bug/1297849 then there's a "Nominate for series" link. There select yakkety for the task
[06:37] <yofel> do that for every package you think is relevant, then ask a dev to accept them
[06:38] <acheronuk> yofel: not here? do you need to be a member of one of the bug teams? either direct or through kubuntu-dev?
[06:39] <yofel> well, I can accept them, but I'm not really sure if that's because I'm in ubuntu-dev or ubuntu-bug-control. It's one of those IIRC
[06:39] <yofel> although ubuntu-dev also implies ubuntu-bug-control
[06:39] <yofel> which is why I said dev
[06:40] <acheronuk> "Only the bug supervisor for a project can nominate a bug or blueprint as affecting a particular series with the Nominate for release link. "
[06:41] <yofel> oh, when did they do that
[06:41] <acheronuk> https://help.launchpad.net/Projects/SeriesMilestonesReleases
[06:41] <yofel> ovidiuflorin: ok, so just tell me what you think is affected
[06:41] <acheronuk> dunno, but I looked the other day for the SRU upgrade bug and found I could not do it
[06:42] <yofel> probably from back when they decided to lock down some bug stats etc.
 yofel, I'm not sure what's affected
 I just get the same-ish log messages
 basically the effect is: I connect to the VPN but there is no DNS resolving
[07:53] <yofel> well, I know even less about the issue, but if you could comment that you're able to reproduce the issue in yakkety for e.g. vpnc, then I'm willing to add a yakkety bug task for vpnc
[07:53] <yofel> but adding random bug tasks without actually verifying that the bug actually happens
 resolv.conf gets updated then reverted....
[07:53] <yofel> ... is a no-go in general
 I've added the comment
 but not much detail in it
 I'm not sure what is relevan
 I'll looke more into this tomorrow
 if I work remotely
[07:56] <yofel> do you remember the connection type? vpnc/openconnect/..
 openvpn
[07:57] <yofel> ok, then I'll add a task for that at least
 what does a task mean?
[07:58] <yofel> oh great, that added them for all packages *-.-
 ... :(
[07:59] <KurousagiMK2> The workaround https://ubuntuforums.org/showthread.php?t=2340042&p=13558035#post13558035 
[07:59]  * yofel removes the ones for the fixed packages
[07:59] <yofel> "task" is how we refer to... one line in the bug status block at the top
 KurousagiMK2 that's for vpnc
[09:25] -kubuntu-ci:#kubuntu-devel- Project yakkety_unstable_kwin build #9: STILL FAILING in 13 min: http://kci.pangea.pub/job/yakkety_unstable_kwin/9/
[09:26] -kubuntu-ci:#kubuntu-devel- Project xenial_unstable_kwin build #9: STILL FAILING in 15 min: http://kci.pangea.pub/job/xenial_unstable_kwin/9/
[09:44] -kubuntu-ci:#kubuntu-devel- Project yakkety_unstable_kwin build #10: STILL FAILING in 14 min: http://kci.pangea.pub/job/yakkety_unstable_kwin/10/
[09:46] -kubuntu-ci:#kubuntu-devel- Project xenial_unstable_kwin build #10: STILL FAILING in 15 min: http://kci.pangea.pub/job/xenial_unstable_kwin/10/
[10:57] <acheronuk> clivejo @Santa et al : do you think this fix from plasma 5.8.1 is potentially backportable to plasma 5.7.5?
[10:59] <acheronuk> this I mean https://phabricator.kde.org/D3006
[11:32] <santa_> good morning everyone
[11:32] <acheronuk> hi santa_ :)
[11:33] <santa_> acheronuk: I was thinking in rebuilding everything for xenial, move it to the ppa and work on framewworks and new plasma for zesty
[11:34] <santa_> s/in/about/
[11:35] <santa_> * move it to the ppa ~ move it to the backports ppa
[11:35] <santa_> (like simon asked us a few days ago)
[11:36] <acheronuk> yeah, or backports-landing anyway.
[11:40] <santa_> acheronuk: ok, so do you mind if I start with frameworks? my idea is merging kubuntu_yakkety_archive into kubuntu_xenial_backports and rebuild everything in the fw staging ppa
[11:40] <santa_> any objections?
[11:41] <acheronuk> clive said yesterday I think that he wanted to start staging stuff. not sure what though
[11:41] <santa_> clivejo: ↑
 +1
 No objections from me
[11:42] <acheronuk> not from me. I think that needs to be done. I think Simon enabled all the architectures on the staging ppa, which may be a unnecessary while staging xenial backports?
[11:43] <yofel> someone might want to look at lp 1634125
 I can handle that later if nobody else does.
[11:46] <santa_> yofel: oh, now that you mention it we also have a pending bug fix for a frameworks package
[11:47] <santa_> ktexteditor/kubuntu_yakkety_archive branch
[11:47] <santa_> so if someone can upload that one it would be nice
[11:48] <yofel> I don't see anything
[11:57] <jimarvan> hey peeps :)
[11:57] <santa_> hi jimarvan
[11:58] <santa_> yofel: sorry, just pushed the commit in question now. I tought I alredy did that
[11:59] <jimarvan> hey santa_ :)
[12:00] -kubuntu-ci:#kubuntu-devel- Project yakkety_unstable_ktexteditor build #95: FAILURE in 1 min 27 sec: http://kci.pangea.pub/job/yakkety_unstable_ktexteditor/95/
[12:00] -kubuntu-ci:#kubuntu-devel- Project xenial_unstable_ktexteditor build #233: FAILURE in 1 min 37 sec: http://kci.pangea.pub/job/xenial_unstable_ktexteditor/233/
[12:01] <yofel> I updated the bug, but upload will have to wait until evening, if clive isn't faster
[12:04] <santa_> np
[12:06] -kubuntu-ci:#kubuntu-devel- Project xenial_unstable_ktexteditor build #234: STILL FAILING in 1 min 3 sec: http://kci.pangea.pub/job/xenial_unstable_ktexteditor/234/
[12:06] -kubuntu-ci:#kubuntu-devel- Project yakkety_unstable_ktexteditor build #96: STILL FAILING in 1 min 31 sec: http://kci.pangea.pub/job/yakkety_unstable_ktexteditor/96/
[12:51] <soee> ahoneybun: http://www.feralinteractive.com/en/games/madmax/?page=setting
[12:51] <soee> out now on mac and linux :)
[12:53] <BluesKaj> Hey folks
[12:54] <soee> hiho BluesKaj
[12:54] <BluesKaj> Hi soee
[13:18] -kubuntu-ci:#kubuntu-devel- Project yakkety_unstable_kwin build #11: STILL FAILING in 4 min 59 sec: http://kci.pangea.pub/job/yakkety_unstable_kwin/11/
[13:19] -kubuntu-ci:#kubuntu-devel- Project xenial_unstable_kwin build #11: ABORTED in 5 min 39 sec: http://kci.pangea.pub/job/xenial_unstable_kwin/11/
[13:29] <clivejo> LP 1632848
[13:36] -kubuntu-ci:#kubuntu-devel- Project yakkety_unstable_kwin build #12: STILL FAILING in 18 min: http://kci.pangea.pub/job/yakkety_unstable_kwin/12/
[13:38] -kubuntu-ci:#kubuntu-devel- Project xenial_unstable_kwin build #12: STILL FAILING in 18 min: http://kci.pangea.pub/job/xenial_unstable_kwin/12/
[13:40]  * mamarley upgraded to Zesty. O.o
[13:46]  * acheronuk makes the mouse jump
[13:50] <clivejo> !testers | Please test the patched package for LP 1632848
[13:50] <clivejo> grrr that needs changed!
[13:51] <clivejo> could do with a package testers and +1 testers
[14:00] -kubuntu-ci:#kubuntu-devel- Project yakkety_unstable_kwin build #13: STILL FAILING in 18 min: http://kci.pangea.pub/job/yakkety_unstable_kwin/13/
[14:01] <clivejo> tsdgeos: ping
[14:01] <tsdgeos> clivejo: hi
[14:02] <clivejo> howdy, regarding LP 1632848, would you mind testing that package in my PPA?
[14:02] <clivejo> I know the version number is wrong, but the patch should work
[14:03] <clivejo> for SRU needs to be ktexteditor (5.26.0-0ubuntu1.1
[14:03] <acheronuk> lol. I was just about to point that out.
[14:04] <clivejo> :P
[14:04] <tsdgeos> clivejo: link to the deb file?
[14:05] <clivejo> do you know which binary package it changes?
[14:05] <clivejo> I just added my PPA
[14:05] <clivejo> and done an upgrade
[14:06] <clivejo> it pulled in ktexteditor-data ktexteditor-katepart libkf5texteditor5 libkf5texteditor5-libjs-underscore
[14:06] <acheronuk> the debs? https://launchpad.net/~clivejo/+archive/ubuntu/yakkety/+build/11047602
[14:06] <tsdgeos> ok
[14:07] <clivejo> remember to remove and ppa purge my PPA after the test
[14:07] <clivejo> I upload a lot of testing stuff there
[14:07] <clivejo> and you dont want it!
[14:09] <tsdgeos> i like how stupid dpkg has a force-all switch
[14:09] <tsdgeos> that doesn't forces shit
[14:10] <tsdgeos> clivejo: yes, fixes it
[14:10] <clivejo> acheronuk: did you test it?
[14:10] <Quintasan> shadeslayer: Happy birthday!
[14:10] <shadeslayer> thank you :)
[14:11] -kubuntu-ci:#kubuntu-devel- Project xenial_unstable_kwin build #13: STILL FAILING in 28 min: http://kci.pangea.pub/job/xenial_unstable_kwin/13/
[14:11] <clivejo> tsdgeos: can you add a comment as the orginal bug reporter that this package fixes it please?
[14:16] -kubuntu-ci:#kubuntu-devel- Project xenial_unstable_ktexteditor build #235: STILL FAILING in 48 sec: http://kci.pangea.pub/job/xenial_unstable_ktexteditor/235/
[14:16] -kubuntu-ci:#kubuntu-devel- Project yakkety_unstable_ktexteditor build #97: STILL FAILING in 51 sec: http://kci.pangea.pub/job/yakkety_unstable_ktexteditor/97/
[14:16] <tsdgeos> clivejo: done, when do we get those packages in yakkety updates?
[14:16] <clivejo> Im trying to get them uploaded
 Happy birthday shadeslayer
[14:17] <clivejo> Im not very comfortable with doing SRU at the moment and it takes me a long time
[14:18] <clivejo> the problem is that the update needs to go to zesty first we havent proprly got our infrastructure configured just yet
[14:19] -kubuntu-ci:#kubuntu-devel- Project yakkety_unstable_kwin build #14: STILL FAILING in 16 min: http://kci.pangea.pub/job/yakkety_unstable_kwin/14/
[14:19] <BluesKaj> BBL
[14:21] -kubuntu-ci:#kubuntu-devel- Project xenial_unstable_ktexteditor build #236: STILL FAILING in 45 sec: http://kci.pangea.pub/job/xenial_unstable_ktexteditor/236/
[14:21] -kubuntu-ci:#kubuntu-devel- Project yakkety_unstable_ktexteditor build #98: STILL FAILING in 48 sec: http://kci.pangea.pub/job/yakkety_unstable_ktexteditor/98/
[14:31] -kubuntu-ci:#kubuntu-devel- Project xenial_unstable_kwin build #14: STILL FAILING in 20 min: http://kci.pangea.pub/job/xenial_unstable_kwin/14/
 the problem is that the update needs to go to zesty first we havent proprly got our infrastructure configured just yet
[14:40] <santa_> I don't think so
[14:40] -kubuntu-ci:#kubuntu-devel- Project yakkety_unstable_kwin build #15: STILL FAILING in 21 min: http://kci.pangea.pub/job/yakkety_unstable_kwin/15/
[14:40] <santa_> clivejo: what is the problem exactly?
[14:41] <clivejo> not a problem, just not great situation to be in when Im learning the ropes
[14:41] <clivejo> yakkety is an SRU so the version should be 1.1?
[14:42] <acheronuk> yes
[14:42] <clivejo> and I would like to have zesty_archive branches
[14:46] -kubuntu-ci:#kubuntu-devel- Project merger_ktexteditor build #763: FAILURE in 11 sec: http://kci.pangea.pub/job/merger_ktexteditor/763/
[14:51]  * acheronuk yawns
[14:51] <santa_> clivejo: if the version should be 1.1 would you mind to wait a bit so I can provide you a gbp-sru ?
[14:52] <santa_> nvm
[14:52] <santa_> I think the current gbp-archive should be enough
[14:52] <santa_> with "-d yakkety"
[14:54] <acheronuk> clivejo have you been using gpg-archive? or some other?
[14:54] -kubuntu-ci:#kubuntu-devel- Project xenial_unstable_kwin build #15: STILL FAILING in 17 min: http://kci.pangea.pub/job/xenial_unstable_kwin/15/
[14:54] <santa_> gbp
[14:54] <acheronuk> lol. yes
[14:56] <acheronuk> someone on kubuntu forums spent pages trying to work out why kpgp wouldn't install saying the package didn't exist. when it should be kgpg!
[14:57] <acheronuk> so easy to mistype with similar acronyms
[15:09] -kubuntu-ci:#kubuntu-devel- Project yakkety_unstable_kwin build #16: STILL FAILING in 23 min: http://kci.pangea.pub/job/yakkety_unstable_kwin/16/
[15:30] <santa_> clivejo, acheronuk: just fyi I pushed some stuff to KA this week; a few changes to prepare for zesty and I also added a feature to gbp-ppa so you don't have to type "-s <number>", the number is calculated from launchpad, yet you can override the number providing "-s <number>" (that's useful if, for instance, you are not uploadng to your own ppas, not our staging ones)
[15:31] <acheronuk> santa_: I was just looking at those changes a few mins ago :)
[15:32] <santa_> ok. let me know if I broke something so we can fix it
[15:36] <jimarvan> :D
[16:48] <clivejo> tsimonq2: can you SHOW us how to get a full list of packages from LP git repo
[16:51] -kubuntu-ci:#kubuntu-devel- Project xenial_unstable_kwin build #16: NOW UNSTABLE in 27 min: http://kci.pangea.pub/job/xenial_unstable_kwin/16/
[17:00] -kubuntu-ci:#kubuntu-devel- Project yakkety_unstable_kwin build #17: NOW UNSTABLE in 36 min: http://kci.pangea.pub/job/yakkety_unstable_kwin/17/
[17:02] <acheronuk> clivejo: wget -q -O - https://code.launchpad.net/~kubuntu-packagers/+git | grep kubuntu-packaging | awk -v FS="(+git/|</a>)" '{print $3}'
[17:02] <acheronuk> and repeat for each page on the repo?
[17:18] <clivejo> cool
[17:18] <clivejo> so can you find out of that entire list, how many of those packages have yakkety_archive branches?
[17:24] <santa_> why do you want to do that?
[17:25] <clivejo> because I think there are some that dont, and want to look at them
 Hai
 I see Rik answered?
[17:26] <clivejo> tsimonq2: is that how you did it?
[17:26] -kubuntu-ci:#kubuntu-devel- Project xenial_unstable_kwin build #17: STILL UNSTABLE in 34 min: http://kci.pangea.pub/job/xenial_unstable_kwin/17/
 Nope
[17:27] <santa_> clivejo: from which package set? frameworks, plasma, applications or others?
 ./gitcloneall
 (with some arguments l
[17:27] <clivejo> others
[17:27] <santa_> ah, ok
[17:27] <clivejo> git clone all is only fw, plasma and apps
[17:27] <clivejo> I want all of them
[17:27] <santa_> yes
[17:28] <clivejo> gimme all your packages!
 sudo apt install santa
 XD
[17:28] <santa_> but what's the problem you want to solve exactly?
[17:29] <clivejo> just asking questions!
[17:30] <santa_> at some point we could extend git-clone-all so we could make git-clone-all -r other
[17:30] <clivejo> dunno if that would help, its only for rare occasions like we have now
[17:30] <santa_> however automatin the extra packages is a tough thing to do since it's a very heterogenours world
[17:31] <santa_> so, again, what are you trying to do? (if you are tryng to do something)
 So for sure we'll get QtWebEngine stuffs in the archive sometime around December and January. It'll be included with the 5.7.1 upload apparently.
[17:32] <clivejo> I want to create zesty_archive branches
[17:33] <clivejo> but I want to also see out of our entire package set, which ones are missing a yakkety one
[17:33] <clivejo> if any
[17:33] <clivejo> as the zesty branches will be from yakkety_archive
[17:34] <santa_> well, I would handle plasma frameworks and apps with git-clone-all/do-all
[17:34] <santa_> and the rest manually
 What's do-all?
[17:34] <santa_> because the work done in the other packages is manual anyway
 Example syntax?
[17:36] -kubuntu-ci:#kubuntu-devel- Project yakkety_unstable_kwin build #18: STILL UNSTABLE in 35 min: http://kci.pangea.pub/job/yakkety_unstable_kwin/18/
[17:38] <acheronuk> clivejo: git ls-remote -h kubuntu:kwin
[17:38] <clivejo> why is kwin going round in circles?
[17:38] <acheronuk> huh?
[17:39] <clivejo> KCI seems to be building kwin a lot
[17:40] <acheronuk> clivejo: doing soname bump on that in stages. so several commits and wait for result
[17:40] <clivejo> ah
 Oh you are?
 Cool!
 I want to see how you did it when you're done. :l
 *:)
[17:41] <acheronuk> and correcting some stupid typo where I forgot to put NOCI
 :P
[17:42] <acheronuk> then KCI does retries as well...
 This weekend I think I might get a local KCI setup good to go
 So I can rewrite in Python ;)
 But doing that might also require me to set up a mock Launchpad install
 But either way, whatever I do to get it building, I hope to do a lot of work
 Including *possibly* getting Stable builds working again
[17:54] <yofel> I seriously doubt you'll need a launchpad install? you might need a mock lplib though, just for the few calls that are being done
[17:54] <clivejo> you'll have that all ready for Monday morning I trust?
[17:55] <yofel> acheronuk: btw. manage-repo-webhooks has code that loops through *all* repositories, so you could just hack that with a print to get all relevant repo names
[17:55] <yofel> that script is in kubuntu-dev-tools
[17:56] <acheronuk> ^^ aha. thought there was bound to be a cleverer way :)
[17:57] <clivejo> I though that was Simon was told to use last time he batch edited the VCS?
[17:58] <yofel> althoug the changes itself I would do with do-all
 yofel: Yeah, that was my concern, although my thought is that I can mess with getting my own archive set up and tweaking everything for that. Or creating a PPA and asking for space to be allocated then tweaking the API calls.
 clivejo: Hopefully. ;)
[18:02] <yofel> well, for dev purposes a normal PPA will probably suffice, I wouldn't develop on production scale ^^
[18:03] <yofel> or you want to *also* look into our own build system setup? ^^
[18:04] <clivejo> yofel: how much rubish do you think is in unstable PPA?
[18:04] <yofel> not much I think, maybe some qt packages you don't need and a couple things that aren't CId anymore
[18:05] <yofel> you can definitely remove anything that LP marks as having a higher version
 yofel: I want to fully replicate our existing CI with the exception of different builders and different PPAs.
 That's it.
 I want all the same jobs and everything.
 I even want to try to run a nightly. 😂
[18:07] <yofel> uhm, I'm not quite sure why you would want to do that, but feel free to. We can give you a backup of the CI folder on master - except for the keys
[18:07] <yofel> which reminds me of backups...
 OK fair enough
 YES PLEASE 😜
[18:08] <yofel> maybe a combination of rsync to linode & rdiff-backup
 Yeah the nightly is painful enough, have it run at the same time as that. :P
 OK I'm off o/
 are we having an informal planning meeting tommorow evening or over the weekend?
[19:36] <valorie> acheronuk: I saw this yesterday in #ubuntu-release and wondered what it means - [22:21] <slangasek> acheronuk: there are now a number of Kubuntu packages listed on https://merges.ubuntu.com/universe.html that I'm TIL on; is there a better plan for getting these up-to-date wrt Debian unstable than for me to merge them via MoM?
[19:37] <mparillo> And on the topic of other channels, in Neon,  <tittiatcoke> Calibre comes from Ubuntu 16.04 and it was compiled against a lower Qt5 version. 
[19:37] <mparillo> If calibre is important software, then I hope we have somebody who knows how to test it if we upgrade Qt for 16.04 via Kubuntu-Backports.
[19:38] <valorie> we don't package calibre, but that's a good point
[19:38] <valorie> I usually get that from the calibre website, sadly
[19:39] <valorie> someone who wants to become a MotU could package it though......
[19:42] <clivejo> good luck someone
[19:42] <clivejo> you'll need it
[20:12] <clivejo> what are the resource available on KCI master?
[20:14] <yofel> as in?
[20:15] <clivejo> RAM, Disk, CPU
[20:15] <yofel> run top? ^^
[20:15] <clivejo> sorry resources
[20:15] <yofel> or look at zabbix
[20:15] <clivejo> do you know off hand?
[20:16] <yofel> just checked, 4G RAM, 10G SWAP, 2 CPU, 493GB 87% used
[20:17] <yofel> where the hell is that disk usage from o.O
[20:17] <clivejo> indeed, I just gulped
[20:18] <yofel> well, 66G free, so not too worrying, still weird
[20:19] <yofel> looking at zabbix, the restore on the 6th/7th caused most of that
[20:19] <yofel> before that the usage was more like 45%
[20:19] <clivejo> can I have a link?
[20:20] <valorie> archive is about to be unfrozen btw
[20:20] <clivejo> that box is a VM isnt it?
[20:21] <yofel> I think it's an EC2 instance
[20:21] <yofel> hm, or no, the IP looks proxied, so something else
[20:24] <clivejo> acheronuk: can you test the version in proposed please and comment - LP 1632848
[20:24] <yofel> clivejo: PM for link
[20:24] <clivejo> I dont see Albert in the channel list
[20:25] <yofel> he's not always on, and if then as tsdgeos or so
[20:25] <valorie> tsgeos usually quits when he goes to bed
[20:27] <valorie> tsdgeos I mean
[20:29] <santa_> FYI I have just fixed a bug with the KA automatic calculation of ~ppaX numbers feature I have just implemented today
[21:12] <clivejo> valorie: was tsdgeos at QtCon?
[21:14] <valorie> yes, I'm sure you met Albert?
[21:15] <valorie> I think he left Wed. from Akademy, but yes, he is the e.V. board member whose term just ended
[21:21] <clivejo> I did?
[21:24] <valorie> well, I did 
[21:24] <valorie> unsure if I introduced you
[21:24] <clivejo> probably not, you so rude!
[22:11] <valorie> gosh someone upgraded from 16.04 to 16.10 and now has a non-working lightdm
[22:12] <valorie> he wrote to me personally, kub-devel and kub-users
[22:12] <valorie> someone who knows more than me should give him some advice!
 well SDDM is what he/she should be using
 sudo dpkg-reconfigure sddm
 I believe
[22:25] <valorie> oh gosh, what is the best way to get the correct nvidia driver?
[22:25] <valorie> sudo driver manager something....
 well the driver manager app does not work without another command
[22:28] <valorie> hmmm, there is nvidia-settings - Tool for configuring the NVIDIA graphics driver
[22:29] <valorie> I'll leave that for others I guess
[22:29] <valorie> I don't mess with mine