[00:01] -kubuntu-ci:#kubuntu-devel- Project merger_kdeconnect-kde build #107: FAILURE in 49 sec: http://kci.pangea.pub/job/merger_kdeconnect-kde/107/
[00:03] -kubuntu-ci:#kubuntu-devel- Project merger_kdiamond build #619: STILL FAILING in 2 min 31 sec: http://kci.pangea.pub/job/merger_kdiamond/619/
[00:05] -kubuntu-ci:#kubuntu-devel- Yippee, build fixed!
[00:05] -kubuntu-ci:#kubuntu-devel- Project merger_kdesdk-thumbnailers build #109: FIXED in 3 min 58 sec: http://kci.pangea.pub/job/merger_kdesdk-thumbnailers/109/
[00:07] -kubuntu-ci:#kubuntu-devel- Project mgmt_merger build #703: STILL UNSTABLE in 6 min 12 sec: http://kci.pangea.pub/job/mgmt_merger/703/
[00:07] -kubuntu-ci:#kubuntu-devel- Project mgmt_progenitor build #689: STILL UNSTABLE in 6 min 15 sec: http://kci.pangea.pub/job/mgmt_progenitor/689/
[00:23] -kubuntu-ci:#kubuntu-devel- Project xenial_unstable_kdesdk-kioslaves build #92: STILL UNSTABLE in 15 min: http://kci.pangea.pub/job/xenial_unstable_kdesdk-kioslaves/92/
[00:28] -kubuntu-ci:#kubuntu-devel- Project xenial_unstable_okular build #29: STILL UNSTABLE in 11 min: http://kci.pangea.pub/job/xenial_unstable_okular/29/
[00:28] -kubuntu-ci:#kubuntu-devel- Project xenial_unstable_kde-runtime build #218: STILL FAILING in 20 min: http://kci.pangea.pub/job/xenial_unstable_kde-runtime/218/
[00:29] -kubuntu-ci:#kubuntu-devel- Project xenial_unstable_kppp build #19: STILL UNSTABLE in 20 min: http://kci.pangea.pub/job/xenial_unstable_kppp/19/
[00:29] -kubuntu-ci:#kubuntu-devel- Project yakkety_unstable_kdesdk-kioslaves build #53: STILL UNSTABLE in 20 min: http://kci.pangea.pub/job/yakkety_unstable_kdesdk-kioslaves/53/
[00:29] -kubuntu-ci:#kubuntu-devel- Yippee, build fixed!
[00:29] -kubuntu-ci:#kubuntu-devel- Project xenial_unstable_analitza build #199: FIXED in 11 min: http://kci.pangea.pub/job/xenial_unstable_analitza/199/
[00:29] -kubuntu-ci:#kubuntu-devel- Project yakkety_unstable_kppp build #96: STILL UNSTABLE in 21 min: http://kci.pangea.pub/job/yakkety_unstable_kppp/96/
[00:35] -kubuntu-ci:#kubuntu-devel- Project xenial_unstable_kcoreaddons build #275: STILL UNSTABLE in 17 min: http://kci.pangea.pub/job/xenial_unstable_kcoreaddons/275/
[00:35] -kubuntu-ci:#kubuntu-devel- Project yakkety_unstable_kauth build #165: STILL UNSTABLE in 17 min: http://kci.pangea.pub/job/yakkety_unstable_kauth/165/
[00:42] -kubuntu-ci:#kubuntu-devel- Project yakkety_unstable_kdevelop-pg-qt build #29: STILL UNSTABLE in 24 min: http://kci.pangea.pub/job/yakkety_unstable_kdevelop-pg-qt/29/
[00:42] -kubuntu-ci:#kubuntu-devel- Project xenial_unstable_kopete build #96: STILL UNSTABLE in 34 min: http://kci.pangea.pub/job/xenial_unstable_kopete/96/
[00:42] -kubuntu-ci:#kubuntu-devel- Project yakkety_unstable_kde-runtime build #224: STILL FAILING in 33 min: http://kci.pangea.pub/job/yakkety_unstable_kde-runtime/224/
[00:48] -kubuntu-ci:#kubuntu-devel- Project xenial_unstable_kcrash build #286: STILL UNSTABLE in 13 min: http://kci.pangea.pub/job/xenial_unstable_kcrash/286/
[00:49] -kubuntu-ci:#kubuntu-devel- Project xenial_unstable_kauth build #293: STILL UNSTABLE in 13 min: http://kci.pangea.pub/job/xenial_unstable_kauth/293/
[00:49] -kubuntu-ci:#kubuntu-devel- Project yakkety_unstable_okular build #107: STILL UNSTABLE in 20 min: http://kci.pangea.pub/job/yakkety_unstable_okular/107/
[00:49] -kubuntu-ci:#kubuntu-devel- Project yakkety_unstable_kopete build #73: STILL UNSTABLE in 41 min: http://kci.pangea.pub/job/yakkety_unstable_kopete/73/
[00:57] -kubuntu-ci:#kubuntu-devel- Project yakkety_unstable_kcrash build #162: STILL UNSTABLE in 14 min: http://kci.pangea.pub/job/yakkety_unstable_kcrash/162/
[00:57] -kubuntu-ci:#kubuntu-devel- Project xenial_unstable_kde-runtime build #219: STILL FAILING in 23 min: http://kci.pangea.pub/job/xenial_unstable_kde-runtime/219/
[01:04] -kubuntu-ci:#kubuntu-devel- Project yakkety_unstable_kde-runtime build #225: STILL FAILING in 17 min: http://kci.pangea.pub/job/yakkety_unstable_kde-runtime/225/
[01:26] -kubuntu-ci:#kubuntu-devel- Project xenial_unstable_kwallet build #300: STILL UNSTABLE in 10 min: http://kci.pangea.pub/job/xenial_unstable_kwallet/300/
[01:32] -kubuntu-ci:#kubuntu-devel- Project yakkety_unstable_kwallet build #139: STILL UNSTABLE in 10 min: http://kci.pangea.pub/job/yakkety_unstable_kwallet/139/
[01:38] <ScottK> clivejo: I'm traveling for work this week, so likely not anytime soon
[02:01] <tsimonq2> kde bug 369665
[02:02] <tsimonq2> !info plasmashell
[02:02] <tsimonq2> !info plasma-workspace
[02:02] <tsimonq2> Ok cool.
[02:04] <tsimonq2> clivejo: Please upload my fixed SDDM to zesty when you get a minute. It's in ppa:tsimonq2/sddm-fixes.
[02:04] <ahoneybun> tsimonq2: you need to go into #kde-sysadmin
[02:04] <tsimonq2> ahoneybun: I went in there the other day. No results...
[02:04] <ahoneybun> well that's where the people with power hangout
[02:05] <ahoneybun> unless sgclark has some time, I think she is an admin on there somewhere
[02:06] <ahoneybun> tsimonq2: till then you could just make a pastebin and I could put it in
[02:07] <tsimonq2> ahoneybun: Minor edits. That would mean giving me permission to annoy you. :P
[02:07] <ahoneybun> it's going to happen anyway, might as well be productive
[02:07] <tsimonq2> XD
[02:08] <tsimonq2> ahoneybun: Tomorrow.
[02:08] <ahoneybun> k
[02:32] -kubuntu-ci:#kubuntu-devel- Project xenial_unstable_spectacle build #115: STILL UNSTABLE in 16 min: http://kci.pangea.pub/job/xenial_unstable_spectacle/115/
[02:34] <tsimonq2> !info plasma-workspace yakkety
[02:34] <tsimonq2> !info plasma-workspace zesty
[02:34] <tsimonq2> Good.
[02:37] -kubuntu-ci:#kubuntu-devel- Project xenial_unstable_umbrello build #101: STILL UNSTABLE in 22 min: http://kci.pangea.pub/job/xenial_unstable_umbrello/101/
[02:37] -kubuntu-ci:#kubuntu-devel- Project xenial_unstable_kstars build #266: STILL UNSTABLE in 22 min: http://kci.pangea.pub/job/xenial_unstable_kstars/266/
[02:37] -kubuntu-ci:#kubuntu-devel- Project yakkety_unstable_spectacle build #94: STILL UNSTABLE in 10 min: http://kci.pangea.pub/job/yakkety_unstable_spectacle/94/
[02:43] -kubuntu-ci:#kubuntu-devel- Project xenial_unstable_okteta build #123: STILL UNSTABLE in 18 min: http://kci.pangea.pub/job/xenial_unstable_okteta/123/
[02:48] -kubuntu-ci:#kubuntu-devel- Project yakkety_unstable_umbrello build #86: STILL UNSTABLE in 23 min: http://kci.pangea.pub/job/yakkety_unstable_umbrello/86/
[02:48] -kubuntu-ci:#kubuntu-devel- Project yakkety_unstable_kstars build #134: STILL UNSTABLE in 23 min: http://kci.pangea.pub/job/yakkety_unstable_kstars/134/
[02:52] <tsimonq2> santa_: Not sure what you've been up to so far, but plasma-framework is FTBFS because of symbols, which is causing krunner to be FTBFS due to a dep wait. This is in ppa:kubuntu-ppa/staging-frameworks , and if you could fix that, that would be great. ;)
[02:54] <tsimonq2> acheronuk: ^^^^
[02:55] -kubuntu-ci:#kubuntu-devel- Project xenial_unstable_ktp-common-internals build #217: STILL UNSTABLE in 17 min: http://kci.pangea.pub/job/xenial_unstable_ktp-common-internals/217/
[03:00] -kubuntu-ci:#kubuntu-devel- Project yakkety_unstable_okteta build #114: STILL FAILING in 22 min: http://kci.pangea.pub/job/yakkety_unstable_okteta/114/
[03:00] -kubuntu-ci:#kubuntu-devel- Project yakkety_unstable_kirigami build #48: STILL UNSTABLE in 11 min: http://kci.pangea.pub/job/yakkety_unstable_kirigami/48/
[03:00] -kubuntu-ci:#kubuntu-devel- Project yakkety_unstable_ktp-common-internals build #143: STILL UNSTABLE in 11 min: http://kci.pangea.pub/job/yakkety_unstable_ktp-common-internals/143/
[03:01] -kubuntu-ci:#kubuntu-devel- Yippee, build fixed!
[03:01] -kubuntu-ci:#kubuntu-devel- Project merger_kdeconnect-kde build #108: FIXED in 18 sec: http://kci.pangea.pub/job/merger_kdeconnect-kde/108/
[03:01] -kubuntu-ci:#kubuntu-devel- Project yakkety_unstable_plasma-mediacenter build #111: STILL UNSTABLE in 11 min: http://kci.pangea.pub/job/yakkety_unstable_plasma-mediacenter/111/
[03:01] -kubuntu-ci:#kubuntu-devel- Yippee, build fixed!
[03:01] -kubuntu-ci:#kubuntu-devel- Project merger_kdiamond build #620: FIXED in 19 sec: http://kci.pangea.pub/job/merger_kdiamond/620/
[03:02] -kubuntu-ci:#kubuntu-devel- Starting build #1 for job iso_yakkety_unstable_amd64
[03:02] -kubuntu-ci:#kubuntu-devel- Project iso_yakkety_unstable_amd64 build #1: FAILURE in 9.5 sec: http://kci.pangea.pub/job/iso_yakkety_unstable_amd64/1/
[03:02] <tsimonq2> Hah lol
[03:02] <tsimonq2> Ok.
[03:02] <tsimonq2> Night for real. o/
[03:06] -kubuntu-ci:#kubuntu-devel- Project xenial_unstable_libkcompactdisc build #57: STILL UNSTABLE in 10 min: http://kci.pangea.pub/job/xenial_unstable_libkcompactdisc/57/
[03:06] -kubuntu-ci:#kubuntu-devel- Project xenial_unstable_ktp-auth-handler build #191: STILL UNSTABLE in 10 min: http://kci.pangea.pub/job/xenial_unstable_ktp-auth-handler/191/
[03:06] -kubuntu-ci:#kubuntu-devel- Project xenial_unstable_gwenview build #178: FAILURE in 10 min: http://kci.pangea.pub/job/xenial_unstable_gwenview/178/
[03:06] -kubuntu-ci:#kubuntu-devel- Project xenial_unstable_kirigami build #44: STILL UNSTABLE in 9 min 43 sec: http://kci.pangea.pub/job/xenial_unstable_kirigami/44/
[03:16] -kubuntu-ci:#kubuntu-devel- Project yakkety_unstable_kde-baseapps build #110: STILL FAILING in 4 min 53 sec: http://kci.pangea.pub/job/yakkety_unstable_kde-baseapps/110/
[03:17] -kubuntu-ci:#kubuntu-devel- Project xenial_unstable_cantor build #201: STILL UNSTABLE in 21 min: http://kci.pangea.pub/job/xenial_unstable_cantor/201/
[03:17] -kubuntu-ci:#kubuntu-devel- Project xenial_unstable_kde-baseapps build #105: STILL FAILING in 4 min 56 sec: http://kci.pangea.pub/job/xenial_unstable_kde-baseapps/105/
[03:17] -kubuntu-ci:#kubuntu-devel- Project xenial_unstable_plasma-sdk build #236: STILL UNSTABLE in 11 min: http://kci.pangea.pub/job/xenial_unstable_plasma-sdk/236/
[03:17] -kubuntu-ci:#kubuntu-devel- Project yakkety_unstable_plasma-sdk build #130: STILL UNSTABLE in 16 min: http://kci.pangea.pub/job/yakkety_unstable_plasma-sdk/130/
[03:17] -kubuntu-ci:#kubuntu-devel- Project xenial_unstable_plasma-mediacenter build #194: STILL UNSTABLE in 21 min: http://kci.pangea.pub/job/xenial_unstable_plasma-mediacenter/194/
[03:18] -kubuntu-ci:#kubuntu-devel- Project yakkety_unstable_plasma-integration build #12: STILL UNSTABLE in 17 min: http://kci.pangea.pub/job/yakkety_unstable_plasma-integration/12/
[03:18] -kubuntu-ci:#kubuntu-devel- Project yakkety_unstable_ktp-auth-handler build #144: STILL UNSTABLE in 17 min: http://kci.pangea.pub/job/yakkety_unstable_ktp-auth-handler/144/
[03:21] -kubuntu-ci:#kubuntu-devel- Project xenial_unstable_plasma-integration build #12: STILL UNSTABLE in 8 min 55 sec: http://kci.pangea.pub/job/xenial_unstable_plasma-integration/12/
[03:22] -kubuntu-ci:#kubuntu-devel- Yippee, build fixed!
[03:22] -kubuntu-ci:#kubuntu-devel- Project xenial_unstable_gwenview build #179: FIXED in 10 min: http://kci.pangea.pub/job/xenial_unstable_gwenview/179/
[03:27] -kubuntu-ci:#kubuntu-devel- Project yakkety_unstable_okteta build #115: STILL FAILING in 21 min: http://kci.pangea.pub/job/yakkety_unstable_okteta/115/
[03:27] -kubuntu-ci:#kubuntu-devel- Project xenial_unstable_discover build #13: STILL FAILING in 5 min 55 sec: http://kci.pangea.pub/job/xenial_unstable_discover/13/
[03:28] -kubuntu-ci:#kubuntu-devel- Project yakkety_unstable_discover build #12: STILL UNSTABLE in 10 min: http://kci.pangea.pub/job/yakkety_unstable_discover/12/
[03:28] -kubuntu-ci:#kubuntu-devel- Project xenial_unstable_kde-baseapps build #106: STILL FAILING in 5 min 51 sec: http://kci.pangea.pub/job/xenial_unstable_kde-baseapps/106/
[03:28] -kubuntu-ci:#kubuntu-devel- Project yakkety_unstable_kde-baseapps build #111: STILL FAILING in 6 min 51 sec: http://kci.pangea.pub/job/yakkety_unstable_kde-baseapps/111/
[03:32] -kubuntu-ci:#kubuntu-devel- Project xenial_unstable_akonadi-contacts build #48: STILL UNSTABLE in 14 min: http://kci.pangea.pub/job/xenial_unstable_akonadi-contacts/48/
[03:38] -kubuntu-ci:#kubuntu-devel- Project xenial_unstable_discover build #14: STILL FAILING in 5 min 52 sec: http://kci.pangea.pub/job/xenial_unstable_discover/14/
[03:41] -kubuntu-ci:#kubuntu-devel- Project xenial_unstable_kwin build #21: STILL UNSTABLE in 28 min: http://kci.pangea.pub/job/xenial_unstable_kwin/21/
[03:41] -kubuntu-ci:#kubuntu-devel- Project yakkety_unstable_kwin build #23: STILL UNSTABLE in 23 min: http://kci.pangea.pub/job/yakkety_unstable_kwin/23/
[03:47] -kubuntu-ci:#kubuntu-devel- Project yakkety_unstable_akonadi-calendar build #12: STILL UNSTABLE in 8 min 51 sec: http://kci.pangea.pub/job/yakkety_unstable_akonadi-calendar/12/
[03:57] -kubuntu-ci:#kubuntu-devel- Project xenial_unstable_messagelib build #11: STILL FAILING in 4 min 51 sec: http://kci.pangea.pub/job/xenial_unstable_messagelib/11/
[04:02] -kubuntu-ci:#kubuntu-devel- Project yakkety_unstable_messagelib build #13: STILL FAILING in 4 min 52 sec: http://kci.pangea.pub/job/yakkety_unstable_messagelib/13/
[04:07] -kubuntu-ci:#kubuntu-devel- Project xenial_unstable_messagelib build #12: STILL FAILING in 4 min 49 sec: http://kci.pangea.pub/job/xenial_unstable_messagelib/12/
[04:11] -kubuntu-ci:#kubuntu-devel- Project yakkety_unstable_messagelib build #14: STILL FAILING in 3 min 53 sec: http://kci.pangea.pub/job/yakkety_unstable_messagelib/14/
[07:45] <acheronuk> tsimonq2: plasma-framework is another example of the KCI unstable branch being ahead of 5.27 now, so having symbols didn't exist when 5.27 was releases. will sort that this afternoon I expect
[08:28] <jimarvan> gooooood morning :)
 @tsimonq2, Please show me where this has been packaged and tested.
[11:25] <tsimonq2> Later @CliffordTheBigRedDoggie
[11:25] <tsimonq2> !info taglib zesty
[11:30] <BluesKaj> Hi Folks
[11:32] <tsimonq2> o/ BluesKaj 
[11:33] <BluesKaj> hi tsimonq2
[11:34] <tsimonq2> Off to school. o/
[11:46] <jimarvan> see ya tsimonq2
[11:46] <jimarvan> hi BluesKaj
[11:46] <jimarvan> ^^
[11:57] <BluesKaj> Hi jimarvan
[13:36] -kubuntu-ci:#kubuntu-devel- Project xenial_unstable_kwallet build #301: STILL UNSTABLE in 9 min 57 sec: http://kci.pangea.pub/job/xenial_unstable_kwallet/301/
[13:36] -kubuntu-ci:#kubuntu-devel- Project yakkety_unstable_kwallet build #140: STILL UNSTABLE in 9 min 59 sec: http://kci.pangea.pub/job/yakkety_unstable_kwallet/140/
[14:18] <acheronuk> frameworks 5.27 built. still needs some oranges sorting and merges if we are doing them
[14:18]  * acheronuk plucks up courage to install
[14:35]  * mamarley 's ears perk up.
[15:21] <acheronuk> that installed ok. :)
[15:21] <mamarley> \o/
[15:21] <clivejo> new icons?
 Link?
[15:21] <acheronuk> a few
 I forgot where to find the staging PPA statuses
[15:22] <clivejo> should be in the topic, thats if someone hasnt removed them
[15:22] <acheronuk> http://qa.kubuntu.co.uk/ppa-status/frameworks/build_status_5.27.0_zesty.html
[15:29] <acheronuk> ok folks. back later 
[15:34] <jimarvan> see ya acheronuk
[15:48] <clivejo> Trello card for FW5.27 Debian merge - https://trello.com/c/6dxq5OzZ
[15:50] <clivejo> Please check/tick the package you are working on, and make comments on its status
 eek. telegram notification for each item. wondered what the **** was going on :P
[15:56] <santa_> clivejo: please let me handle the debian merges like we discussed the other day
[15:57] <santa_> we need some tooling improvements for that, doing it the way we are now it's going to be a waste of time
[15:58] <santa_> clivejo: so please delete the card, if you want to do something productive work on fw 5.27 or plasma 5.8.2 or the issues reported by the KCI there's plently of work to do
[18:01] <soee> o/
[18:03] <acheronuk> evening soee :)
[18:56] <ahoneybun> did anyone see that bug about kmahjongg?
[18:57] <clivejo> just
[18:57] <ahoneybun> ok
[18:57] <ahoneybun> clivejo: think I could try to fix it 
[18:57] <ahoneybun> looks like a very junior job
[18:57] <clivejo> sure
[18:58] <ahoneybun> so do I grab the source from our archive?
[18:58] <ahoneybun> for kmahjongg
[18:58] <clivejo> if you fix it for zesty and then open a SRU to fix it in yakkety
[18:59] <ahoneybun> but I'm not on ZZ
[19:00] <clivejo> but you can fix it for zesty
[19:00] <ahoneybun> clivejo: do I download the orig.tar file?
[19:00] <ahoneybun> I'm very rusty
[19:00] <clivejo> and I can upload to zesty and acheronuk can test it
[19:03] <ahoneybun> clivejo: I'm looking at editing the control file right?
[19:03] <clivejo> yup
[19:03] <ahoneybun> just add: kdegames-mahjongg-data-kf5
[19:04] <ahoneybun> under build-deps?
[19:04] <clivejo> append the correct package name
[19:05] <clivejo> not build deps
[19:05] <ahoneybun> ohh
[19:05] <ahoneybun> where?
[19:06] <ahoneybun> http://pastebin.ubuntu.com/23385028/
[19:06] <ahoneybun> that's what it looks like by default
[19:07] <clivejo> https://anonscm.debian.org/cgit/pkg-kde/applications/kmahjongg.git/tree/debian/control?h=debian/16.04.0-1
[19:07] <ahoneybun> wait 
[19:07] <ahoneybun> did someone fix it already?
[19:08] <clivejo> in debian
[19:08] <clivejo> not in kubuntu
 that is debian
[19:08] <clivejo> https://git.launchpad.net/~kubuntu-packagers/kubuntu-packaging/+git/kmahjongg/tree/debian/control?h=kubuntu_unstable
[19:08] <ahoneybun> so what do I do?
[19:08] <ahoneybun> nothing>
[19:09] <clivejo> I would fix it in _unstable branch
[19:09] <ahoneybun> they also added a new build dep
[19:09] <ahoneybun> qtbase5-dev (>= 5.2.0~)
[19:10] <clivejo> might be better to do a debian merge then
[19:10] <ahoneybun> they changed a few things
[19:11] <ahoneybun> 3 new deps
[19:11] <clivejo> Id do a debian merge on zesty branch, add a new changelog entry
[19:11] <clivejo> saying what you have done
[19:11] <ahoneybun> mm not sure how to do that
[19:12] <clivejo> put it to a PPA and ask acheronuk to test it
[19:12] <ahoneybun> :(
[19:12] <clivejo> and if it installs and works for him Ill upload it to zesty
[19:12] <acheronuk> clivejo: are you not on zesty as well?
[19:12] <clivejo> not yet
[19:13] <clivejo> usually wait to the toolchain has been fixed
[19:13] <acheronuk> oh. I thought you had switched. np
[19:13] <clivejo> or frose
[19:14] <mamarley> I'm pretty sure it is unfrozen now.
[19:15]  * acheronuk opens a beer
 @acheronuk, Same here. Lol
 (responding to a Telegram message, I'm not opening a beer :P)
 @tsimonq2, I should hope not! :P
[20:14] <valorie> sorry ahoneybun, I missed your comment yesterday about code-in. will you participate with Ubuntu, or KDE?
 Not sure
 Tbh KDE has been a little tough to find a space to help other then coding
 I've already out with a Alex L in VDG
[20:27] <valorie> ? Code-in tasks have to be in four areas, only one of them coding
[20:36] <valorie> we need mentors, and we need task descriptions
[20:37] <valorie> and responsive mentors who will tell the admins when to make their tasks "active" and work with the students while they are doing them
[20:37] <valorie> sub to kde-soc-mentor if you are interested
 I think I might be
[21:32]  * valorie goes off to buy chocolate for the mentor summit, so I don't have to so it on the way to the airport
[21:32] <valorie> yes, one of the tracks is the Chocolate Room
 http://blog.broulik.de/2016/10/global-menus-returning/?_utm_source=1-2-2
 I saw that, can't wait
[23:00] <santa_> clivejo: around?
[23:01] <clivejo> just logged in
[23:01] <tsimonq2> santa_: Hai. :)
[23:01] <santa_> yo
[23:01] <santa_> I wanted to update you about my stuff
[23:02] <santa_> 1. I have a quick and cheap solution to check which packages have failing autopkgtests
[23:02] <santa_> (this is one of the things which hindered more the inclusion of new packages in the end of yakkety cicle)
[23:03] <santa_> 2. related to that, I will work tomorrow on the new scriptery to handle the debian merges
[23:03] <santa_> (this way we can see if merging from debian fixes the autopkgtest or not)
[23:04] <santa_> (many times I synced the autopkgtests with debian at the end of yakkety cicle to fix some failures, but I had to fix on my own a few ones)
[23:05] <clivejo> 1) how can this be done?  within LP?
[23:06] <santa_> 3. related to that I have a script to update the vcs fields of our packaging, so to make the scriptery mentioned in 2. I need to update the vcs fields in _zesty_archive first
[23:06] <santa_> 1. is done in my build box
[23:06] <santa_> yes, kind of unofficial and fast and cheap solution
[23:07] <santa_> the proper thing would be setting the thing up on an "official kubuntu server"
[23:07] <clivejo> RE 1) is there any way we can precipitate what your box is doing on a linode container? 
[23:08] <clivejo> replicate 
[23:08] <santa_> you would need 3 containers, but with some time we could replicate it, yes
[23:08] <santa_> I have my own wannabuild/buildd setup
[23:08] <santa_> have you ever heard about this?
[23:09] <tsimonq2> santa_: We should also set up a complete OpenStack setup to run a Britney setup on.
[23:09] <tsimonq2> That would be fun.
[23:09] <santa_> that would be the "premium" solution
[23:09] <clivejo> the end solution needs to be something we can document and have others able to configure and use
[23:09] <tsimonq2> santa_: Hire pleia2 to do it. XD
[23:09] <tsimonq2> (kidding)
[23:10] <valorie> yes! on the document and replication
[23:10] <valorie> docs I mean
[23:12] <santa_> so insinting with my question, about wannabuild and buildd, do you know what it is or how it works?
[23:12] <clivejo> RE 2) I'm not keen on having a totally automatic merge at this time.  With a manual merge in involve thinking and looking into the best option to solve the issue.  Debian isnt always right in these cases, and there is a lot to be learned by doing the merges manually if we have the person power to do it
[23:12] <santa_> * insisting
[23:13] <clivejo> acheronuk and myself dont mind doing in manually and can learn a lot by doing it
[23:14] <santa_> clivejo: RE 2) fine I will finish the script. it can be executed manually for one package
[23:14] <santa_> so if you want to go one by one for learning, fine
[23:15] <santa_> but in the end I think the thing will be that it would be executed by just one person with do-all and fixning manually the conflitcts
[23:15] <clivejo> now if your tooling can somehow make the merge go easier (ie you talked about pre-processing the debian/master into a temp branch with the VCS matching ours then I can see that would be a great help
[23:15] <santa_> (more or less the same we do when we merge kubuntu_unstable)
[23:15] <santa_> clivejo: yes, that's the idea
[23:16] <santa_> hence why I asked you to wait a bit
[23:16] <santa_> (just a bit)
[23:16] <clivejo> Ill wait a bit, but I do want to get on with this
[23:16] <santa_> of course
[23:16] <acheronuk> some manual sanity checking of changelogs is unavoidable anyway
[23:17] <santa_> it's almost done, I have been busy today with the autopkgtrolling, because one thing will help with the other
[23:18] <clivejo> when we merge with debian, will the script auto-detect a debian version and bump the ubuntu one ie to 1ubuntu1?
[23:18] <santa_> nope
[23:18] <santa_> but it's pretty easy to write an ad-hoc script for this case
[23:19] <santa_> (now we are behind debian, but usually we will be ahead)
[23:19] <santa_> clivejo: and that's indeed the thing to do to get the changelog entries in the correct order, the date of the changelog block trailer isn't taken into account
[23:20] <santa_> (read the fabulous man of dpkg-mergechangelogs)
[23:20] <clivejo> yes, but I also feel that ninja's need some hands on experience, so that they can detect and know how to fix these things
[23:21] <acheronuk> I gave a couple a test merge earlier today, and changelogs order was the only biggish thing to sort
[23:21] <clivejo> a smaller set of packages like frameworks is good practice
[23:22] <acheronuk> ^^ for later, when we have 200+ do do for applications! eek!
[23:23] <clivejo> by the time we get to applications we'll be crying out for automation!
[23:23] <santa_> I smell a do-all there, indeed
[23:23] <santa_> so, getting back to the item 3. ....
[23:24] <clivejo> I dont understand that one
[23:24] <acheronuk> automation is great, but we need to understand what it does and how to replicate manually. not just a black box
[23:24] <clivejo> the VCS should be pointing to LP git?
[23:25] <acheronuk> some got changed to http? is that it?
[23:25] <clivejo> I thought Simon batch changed those?
[23:27] <tsimonq2> Yup, but I may have not gotten them all.
[23:27] <santa_> https://paste.kde.org/phfszaatb
[23:28] <santa_> ↑ so if don't mind I'm going to push one commit like this for all the frameworks
[23:28] <santa_> * if you don't mind
[23:29] <santa_> + I will put "NOCI" in the commit message in order to not trigger non-sense rebuilds on the KCI
[23:29] <clivejo> what is the reasoning behind this?
[23:29] <santa_> http*s*
[23:31] <tsimonq2> *PLEASE* confirm with the others, but lgtm
[23:32] <santa_> even if its worng it would be trivial to fix
[23:32] <santa_> * wrong
[23:32] <clivejo> does your tooling need it somewhere?
[23:34] <clivejo> or is it a change Debian have made and you are mirroring it?
[23:35] <santa_> you mean the merger script? yes, it would preprocess the debian branch altering the vcs fields to avoid conflicts which aren't actually conflicts
[23:35] <santa_> I'm not "mirroring" anything because our vcs fields are just different
[23:35] <clivejo> no, I mean debian are doing that too eg - https://anonscm.debian.org/cgit/pkg-kde/applications/akonadi.git/tree/debian/control
[23:36] <santa_> oh, well, I didn't mind about that as I said
[23:37] <santa_> our fields are different so I'm just caring about *ours*
[23:37] <clivejo> I guess what Im asking is what are the advantages to us by changing them
[23:37] <clivejo> why not ssh: for example?
[23:38] <santa_> that would be for authenticated users only
[23:38] <santa_> git+ssh doesn't support anonymous access
[23:39] <santa_> and the Vcs-Git field is suposed to provide an anonymous url for cloning, if I'm not mistaken
[23:40] <clivejo> I have no objections to you doing that, but I would like to see it applied to all of our packaging in one quick pass
[23:41] <acheronuk> so to be clear, switching the remaining ones would make things consistent, and allow for less hiccups in the merge script
[23:41] <santa_> ↑ THIS
[23:42] <santa_> clivejo: about that, the closest thing we have now for this kind of "crusades" is applying it with do-all for frameworks, the plasma, then applications and finally manually on the non fw/plasma/apps packages
[23:42] <clivejo> so you would be only doing frameworks initially?
[23:43] <santa_> yes, it's the way it is now, so let's not try to fix the world in one day
[23:43] <clivejo> Simon has code to pull all packages in our git repo's
[23:43] <santa_> ah, ok
[23:43] <santa_> where is that code then?
[23:43] <clivejo> which is why I asked him to investigate a way of making master = kubuntu_yakkety_archive
[23:43] <santa_> tsimonq2: ↑
[23:43] <tsimonq2> I do?!?
[23:44] <tsimonq2> clivejo: What do you speak of?!? :P
[23:44] <clivejo> you KNOW what I speak of
[23:44] <tsimonq2> What script?!?
[23:44] <tsimonq2> And how hacky? :P
[23:46] <clivejo> I would like to see all KDE apps/software being looked at and updated in ZZ
[23:46] <valorie> grrr, I just found that we don't have peruse yet
[23:46] <clivejo> with packaging all nicely in LP git
[23:48] <santa_> tsimonq2: so do you have the script to clone all the repositories or not?
[23:48] <acheronuk> valorie: I saw Neon doing peruse the other day
[23:48] <valorie> ok
[23:48] <valorie> I just bought the Doctor Who comic humble bundle
[23:49] <acheronuk> ah, comic book reader?
[23:49] <santa_> what's peruse?
[23:49] <valorie> yup
[23:49] <clivejo> !info peruse unstable
[23:49] <valorie> https://www.humblebundle.com/books/doctor-who-comics-2
[23:49] <santa_> !info peruse zesty
[23:49] <santa_> !info peruse yakkety
[23:49] <santa_> :/
[23:49] <valorie> it's new
[23:50] <santa_> is it a comick book reader?
[23:50] <valorie> yes
[23:50] <santa_> oh, ok
[23:50] <clivejo> humm that will be a nightmare to get into ubuntu archive
[23:50] <acheronuk> https://twitter.com/KdeNeon/status/790577260826857472
[23:50] <clivejo> good project for simon
[23:50] <valorie> well, should go into Debian first
[23:51] <valorie> hopefully shadeslayer and sgclark will do that
[23:51] <clivejo> I think scarlett is more involve snapping them
[23:51] <tsimonq2> XD
[23:51] <valorie> oops, time for dinner
[23:52] <valorie> well, a snap would hold me over
[23:52] <clivejo> tsimonq2: can you nag someone about getting new packages into ubuntu?
[23:52] <tsimonq2> clivejo: I'm good at nagging, yes. :P
[23:52] <acheronuk> I noticed
[23:53] <tsimonq2> XD
[23:53] <clivejo> we need kirigami too
[23:53] <clivejo> and some others
[23:53] <clivejo> to do with PIM
[23:53] <acheronuk> we need a hit list
[23:53] <tsimonq2> Yeah, gimme a TODO list. :P
[23:54] <clivejo> start a trello card?
[23:54] <tsimonq2> "Simon's TODO list (AKA things that nobody wants to do)"
[23:54] <tsimonq2> :D
[23:54] <clivejo> we'll need kirigami for plasma 5.8
[23:55] <clivejo> just a "New Package" list
[23:55] <clivejo> but with you as owner
[23:55] <ahoneybun> debian just put it in no?
[23:55] <clivejo> !info kirigami unstable
[23:56] <acheronuk> was in their approval queue? or was that something else?
[23:56] <ahoneybun> I saw it somewhere
[23:57] <clivejo> yeah, I pinged ScottK so he could poke it on a bit, but think hes busy with other stuff
[23:57] <ScottK> Quite.
[23:57] <clivejo> ScottK: if you have a big stick, feel free to beat kirigami with it :)
[23:57] <tsimonq2> clivejo: Seriously. Y'all should make a "To Package" list.
[23:58] <ScottK> -ENOTIME.
[23:58] <acheronuk> yep. it's in their 'new' queue still
[23:58] <acheronuk> oh, hi ScottK :)
[23:58] <clivejo> it is packaged, just stuck in Debian's innards 
[23:59] <clivejo> and until Debian spit it out, we cant sync with it and get it into ubuntu archive