[02:53]  * mamarley kicks LP.
[09:31] <yofel> clivejo: did you merge kubuntu_unstable during the plasma stage?
[09:32] <yofel> clivejo: did you merge kubuntu_unstable during the plasma stage?
[09:32] <yofel> meh
[09:33] <yofel> oh hm, the merge defaults are rather non-obvious
 I didn't merge them manually, I thought the script did that or was supposed to?
[09:45] <yofel> the default is kubuntu_stable for plasma and apps. You need to tell it to merge _unstable instead for major updates
[09:45] <yofel> but that's explained nowhere, I'll put something in the readme
 In the past ive seen it merge unstable automatically
 Has the script logic changed?
[09:51] <yofel> defaults are: frameworks -> unstable, plasma -> stable, apps -> stable
 Oh
 I thought it worked it out on version number
[09:52] <yofel> nope, and even then "5.7.1" is somewhere where I would expect it to select "stable"
[09:53] <yofel> *something
 Cause we skipped 5.7.0?
[09:54] <yofel> even for that. The branch selection is based on CI semantics, and that depends on the upstream branching which happens for the first beta release
 I have all the git repos locally. I could do an unstable merge and upload ppa10
[09:55] <yofel> so technically. For things to be correct, we would always need to merge kubuntu_unstable into kubuntu_stable the moment upstream does the release branching
[09:55] <yofel> if you do, please try it
 Do you reckon there are many fixes in unstable for plasma?
[09:57] <yofel> there are at least some, + some random fixes that people just put into unstable and not release
 I know I haven't been paying much attention to unstable for recently
[09:57] <yofel> yeah, me neither, that's why I'm trying to fix the CI ;)
 Wonder has Rik pushed any fixes for plasma
 I won't be able to look at it until later
[10:00] <yofel> I don't think there are that many for plasma, but for apps there are a couple at least once we get to that
[10:00] <yofel> although all the new app tars in 16.04 are still missing from CI
[10:00] <yofel> need to figure out how to add those
[14:14] <BluesKaj> hi all
[14:45] <santa_> yofel: thanks for merging the KA patches, now I have this https://code.launchpad.net/~panfaust/+git/kubuntu-automation/+ref/work for dev-package-name-lists
[14:45] <santa_> the way to use would be dev-package-name-list -r frameworks -d yakkety
[14:46] <santa_> and it would produce the json file
[14:46] <santa_> I think this way it would work as you want/expect
[14:50] <santa_> yofel: ↑
[14:50] <santa_> oops
[14:50] <santa_> I meant clivejo ↑
[16:27]  * jimarvan mumbles
[17:44] <jimarvan> see ya laters :D
[18:01] <acheronuk> oooooh. someone uploaded some plasma 5.7.1 :D
 I didn't merge with unstable though :(
[20:12] <clivejo> hi DarinMiller
[20:12] <DarinMiller> Hi clivejo!
[20:12] <clivejo> how are you?
[20:13] <DarinMiller> Quite fine thanks.  Still recovering for time change due holiday on your side of the planet.
[20:13] <DarinMiller> And you?
[20:14] <clivejo> tired and sore
[20:14] <DarinMiller> Sore?
[20:15] <clivejo> been stooped over doing pressure washing for about 5 hours this afternoon
[20:16] <DarinMiller> That will do it.
[20:17] <clivejo> anyone fancy helping on plasma 5.7.1?
[20:18] <DarinMiller> Be glad to... How can I help? 
[20:18] <clivejo> fix the red ones ==> http://qa.kubuntu.co.uk/ppa-status/plasma/build_status_5.7.1_yakkety.html
[20:23] <yofel> did you do the merges?
[20:25] <clivejo> I did
[20:25] <clivejo> but not sure what to do with them
[20:25] <yofel> push to _archive and upload?
[20:25] <clivejo> ok, Ill pause KCI
[20:26] <clivejo> oh, how come the queue is clear today
[20:26] <clivejo> thats odd
[20:26] <yofel> launchpad was cooperative I guess ^^
[20:27] <clivejo> or just failed them all
[20:27] <yofel> there were a bunch of those, but it doesn't look that bad
[20:29] <clivejo> yofel: so how should my staging command have looked like to trigger an unstable merge?
[20:29] <yofel> it should've included "-b unstable"
[20:29] <yofel> see --help (and now: also see readme)
[20:31] <clivejo> Ill build these as ppa10
[20:33] <yofel> sitter: what does update-projects.rb do?
[20:34] <yofel> I ran it with --help expecting *something*, then it actually started doing *something else* and I killed it
[20:35] <clivejo> yofel: is there an easier way to setup new projects in KCI?
[20:35] <clivejo> for new packages?
[20:36] <yofel> clivejo: that's what I'm trying to find out
[20:36] <clivejo> ah
[20:36] <yofel> but this tooling is.. not too descriptive
[20:46] <clivejo> ah
[20:46] <clivejo> thats gonna mess up xenial for a bit!
[20:47] <yofel> how so?
[20:47] <clivejo> not having Qt 5.6.1
[20:47] <yofel> it should have
[20:47] <clivejo> oh
[20:47] <clivejo> when did that happen?
[20:48] <yofel> no idea how good it is though, I just copied what acheronuk had in his ppa :P
[20:48] <yofel> sometime last week
[20:48] <clivejo> so FW 5.24 cant be back ported
[20:48] <clivejo> can
[20:48] <clivejo> ?
[20:48] <yofel> yeah, at least it can be worked on
[20:49] <clivejo> maybe wait until plasma is sorted
[20:49] <clivejo> there is no way to test it yet
[20:49] <clivejo> ok all are uploaded
[20:50] <clivejo> now for the LP wait of doom and gloom
[20:50] <yofel> that's why I said "worked on" ;P
[20:50] <clivejo> hummm my ethernet is down
[20:51] <yofel> ok, I don't get how you should add something to the CI
[20:51] <yofel> sitter: heeeeeeeeeelp
[20:52] <clivejo> magic
[20:53] <clivejo> turn Haralds dicky-bow once clockwise 
[20:53] <yofel> lol
[20:53] <clivejo> and listen to all the clockwork cogs turn and click into place
[20:54] <jimarvan> did I hear "test"?
[20:54] <jimarvan> :)
[20:55] <clivejo> afraid not!
[20:57] <clivejo> maybe in a few days when LP actually builds and publishes stuff
[21:00] <mamarley> I already have a VM ready for that!  (Since this is such a major change, Qt, Frameworks, and Plasma all at the same time, I figure it will be best to try it in a VM first.)
[21:00] <clivejo> from the test install acheronuk did on his VM, looks like few other packages need building too
[21:01] <clivejo> http://paste.ubuntu.com/19414594/
[21:03] <clivejo> sddm wanting to be removed is worrying
[21:08] <mamarley> clivejo: sddm depends on a theme (sddm-theme-breeze being the only one installed) which depends on plasma-workspace, which is build-dep on kscreenlocker-dev. 
[21:08] <mamarley> It looks like kscreenlocker is built, so once plasma-workspace 5.7.1 builds and therefore becomes installable, it shouldn't want to remove sddm anymore.
[21:11] <jimarvan> :D
[21:26] <jimarvan> good night peeps :)
[21:26] <jimarvan> see ya tomorrow
[21:26] <clivejo> gn jim