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