[09:52] <acheron_uk> clivejo: ping
[09:53] <acheron_uk> for http://kci.pangea.pub/job/yakkety_unstable_ark/31/parsed_console/
[09:53] <acheron_uk> maybe? http://paste.ubuntu.com/17058496/
[11:23] <BluesKaj> Hi folks
[11:53] <shadeslayer> yofel_: clivejo https://anonscm.debian.org/cgit/pkg-kde/kde-extras/kdeconnect-plasma.git/tree/debian/control?h=kubuntu_unstable#n43
[11:53] <shadeslayer> The recommends apparently comes for the KIO plugin
[11:54] <shadeslayer> but doesn't kdeconnect-plasma have it's own?
[11:54] <yofel_> dunno, clive knows more about that
[11:54] <shadeslayer> oh Jon did that commit
[11:54] <shadeslayer> Riddell: ^^
[11:55] <shadeslayer> Riddell: https://anonscm.debian.org/cgit/pkg-kde/kde-extras/kdeconnect-plasma.git/commit/?h=kubuntu_unstable&id=9afacba37965f0c8cc651aab59f0c866080e9812
[11:55] <shadeslayer> Riddell: was that perhaps for KDE4 times?
[11:55] <Riddell> something like that yes
[11:56] <shadeslayer> ok, can be dropped then?
[11:56] <Riddell> I recommend using this packaging now http://packaging.neon.kde.org/cgit/kde-extras/kdeconnect.git/
[11:56] <shadeslayer> ack
[11:57] <Riddell> kdeconnect-plasma should die
[11:59] <shadeslayer> Riddell: did you update the deps in purpose et all too?
[11:59] <Riddell> shadeslayer: I think harald did most of that, probably just by merging from debian. it's all building and working fine in neon
[12:00] <shadeslayer> Depends: kdeconnect-plasma,
[12:00] <shadeslayer> it was missed
[12:00] <Riddell> hmm?
[12:00] <shadeslayer> Riddell: purpose, Neon/release branch, qml-modules-org-kde-purpose
[12:00] <shadeslayer> Depends: kdeconnect-plasma,
[12:01] <shadeslayer> that should be kdeconnect ?
[12:02] <Riddell> shadeslayer: oh yes, well spotted, I'll fix that up
[12:03] <shadeslayer> cheers
[12:11] <acheron_uk> clivejo: you pushed that change for ark. thank you
[12:27] <acheron_uk> some unstable builds are failing as they bumped ECM upstream to v 5.23. is it possible to prod KCI to rebuild ECM to pick that up?
[12:51] <clivejo> acheron_uk: no prob, Im in and out at the moment and if the patch makes sense Ill push it for you :)
[12:54] <clivejo> yofel_: I was playing with KCI yesterday and created a new job for kdeconnect on yakkety.  I copied the old job for xenial and edited the settings to build for yakkety, is that the right way to do it?
[12:54] <clivejo> also made a new view for yakkety FIX
[12:54] <yofel_> I don't know, sgclark ^
[12:55] <clivejo> Id like to add in the new packages, but unsure how to do it
[12:56] <clivejo> another think, could I purge the queue now and again to get time to work on it?
[12:56] <clivejo> thing
[12:56] <clivejo> at this rate, I only get an hour or so at night before the queue fills up and I cant do anything
[12:59] <clivejo> everythings going to fail today
[12:59] <clivejo> really is no point in building stuff
[13:02] <acheron_uk> clivejo: http://kci.pangea.pub/job/yakkety_unstable_artikulate/33/
[13:02] <acheron_uk> http://paste.ubuntu.com/17060493/
[13:02] <acheron_uk> possibly....
[13:13] <acheron_uk> clivejo: hmmm. I tried wrap and sort on artikulate, and it made some changes I wasn't sure off. So chickened out and reversed it
[13:13] <clivejo> wrap and sort just makes it look nice
[13:14] <clivejo> I tend to run it when I add to install files and add new build deps
[13:14] <clivejo> saves me sorting it manually :)
[13:14] <acheron_uk> yes, I think I misread some of the changes it did
[13:15] <acheron_uk> now I read it a second time I see
[13:15] <clivejo> so I have bumped ECM to 5.22, and rebuilding it
[13:15] <clivejo> reckon that will sort out those build failures?
[13:16] <acheron_uk> It 'should' sort out THAT point of failure on configure
[13:16] <yofel_> note that wrap-and-sort can misbehave if some files aren't properly formatted. So it's a good idea to review the changes it makes every time
[13:16] <acheron_uk> TY yofel :)
[13:17] <clivejo> yofel: diod you get your home internet fixed?
[13:17] <yofel> no, although it works fine ~90% of the day now
[13:18] <yofel> and I can wire through my pone for cases where I need stability
[13:18] <clivejo> yofel: any idea why these mergers are failing - http://kci.pangea.pub/job/merger_kactivities-stats/
[13:19] <clivejo> Seen branch in repository origin/kubuntu_stable
[13:19] <clivejo> yet checkout 'kubuntu_stable'  2>&1:error: pathspec 'kubuntu_stable' did not match any file(s) known to git. (Git::GitExecuteError)
[13:21] <yofel> hm... 
[13:21] <yofel> not really. Did you try wiping the workspace?
[13:22] <clivejo> nope
[13:22] <yofel> Might just be a cache issue... I do remember seeing that in the past
[13:22] <clivejo> seems to be since we moved to LP
[13:23] <clivejo> so wipe out current workspace?
[13:24] <yofel> also
[13:24] <clivejo> yippeeee
[13:24] <yofel>                archive | backports -> stable | unstable (xenial)               
[13:24] <yofel> [E] merger: There is no stable or unstable branch!
[13:24] <yofel> shouldn't it only be doing that for yakkety?
[13:25] <yofel> or am I misremembering something?
[13:25] <clivejo> I dont know how to config that
[13:25] <clivejo> with ECM we only build unstable
[13:26] <clivejo> so how does the ECM get copied over into the stable PPA?
[13:26] <clivejo> it seems to be automatic for xenial, but not yakkety
[13:28] <clivejo> that should be plasma-discover ?
[15:11] <acheron_uk> ^^^ cheer :)
[15:11] <clivejo> congrats!
[15:15] <acheron_uk> small victory, but getting there
[15:34] <clivejo> we seem to have discover and plasma-discover, how do I delete the discovery merger and projects
[18:08] <sgclark> clivejo: yofel no creating new projects involves  creating the unstabe and stable branches add them to https://github.com/ScarlettGatelyClark/pangea-tooling/blob/master/ci-tooling/data/projects/ and running update-projects.rb ruby script. Honestly You shoud fork that.
[18:09] <sgclark> I don't know that I will have time to maintain that anymore :(
[18:09] <sgclark> stable in fact is still broken.
[18:10] <clivejo> yeah yakkety stable doesnt seem to be working properly
[18:10] <sgclark> might want to disable it all together till someone can fix the code to work without namespaces
[18:11] <sgclark> launchpad does not allow for shh logins so large chunks of sitters code does not work with launchpad I am afraid
[18:11] <clivejo> so you fork BlueSystems repo?
[18:11] <sgclark> I did yeah
[18:11] <sgclark> you can fork my fork though
[18:11] <clivejo> how do you push that back to KCI?
[18:12] <sgclark> you can ssh to kci right?
[18:12] <clivejo> I dont know, never tried it
[18:12] <sgclark> actually no need.
[18:13] <sgclark> fork my fork, then in kci jenkins settings change the url to your new fork
[18:13] <sgclark> a suggestion: create a kubuntu profile
[18:13] <clivejo> if its a git repo cant we move that to LP git to have everything in the same place?
[18:14] <sgclark> I do not see why not. THat is probably the best plan
[18:15] <clivejo> what happens to projects made from within Jenkins?
[18:15] <sgclark> I reckon they go poof when run that script? not sure sitter would know.
[18:16] <sgclark> maybe not.
[18:16] <clivejo> for example I made a new kdeconnect-plasma for yakkety by copying the xenial one and changing the build settings and workspace
[18:16] <clivejo> http://kci.pangea.pub/job/yakkety_unstable_kdeconnect-plasma/
[18:17] <clivejo> does the script reverse the projects to?
[18:18] <sgclark> I don't know sorry.
[18:18] <clivejo> ie next time the box is rebooted etc, will that project disappear
[18:19] <clivejo> Im keen to learn how it works, but for our setup there is very little documentation
[18:19] <clivejo> did you learn by doing and asking Harald?
[18:20] <sgclark> nah I would think not. I reckon you can do everything in jenkins if that is your desire. But fixing the scripts to automate would likely be the best going forward solution for the long run.
[18:21] <clivejo> Im just afraid of fixing stuff which will be lost if a script is run 
[18:21] <sgclark> that is entirely possible.
[18:21] <clivejo> need to fix it properly, not just a temp patch
[18:22] <sgclark> like I said, most of that brilliance is sitters. So he will need to answer these questions sorry :(
[18:22] <clivejo> also need to understand the mechanism that copies unstable binaries into stable
[18:23] <sgclark> Yeah that is totally broken
[18:23] <clivejo> only for yakkety
[18:23] <clivejo> xenial seems to be still ok
[18:24] <sgclark> all his code used namespaces aka debian git structure. I tried to fix it. And failed. I did not have time to succeed sorry. Ruby is not my expertise yet.
[18:24] <clivejo> do you know if the source git is retained?
[18:24] <clivejo> source code
[18:24] <sgclark> I do not understand the quetsion sorry.
[18:25] <sgclark> err question
[18:25] <clivejo> well the debian packaging git seems to be held locally in the workspace
[18:25] <sgclark> basically what is happening is it is pulling kde master and using packaging for the release, hense failure.
[18:25] <clivejo> I was wondering if the KDE Source code git has a local copy too
[18:26] <sgclark> again, this is sitters code. He will need to help here.
[18:26] <clivejo> okay :)
[18:27] <clivejo> just thinking outloud :)
[18:27] <sgclark> it had something to do with overrides
[18:27] <clivejo> how the Debian work going?
[18:27] <sgclark> no worries.
[18:27] <clivejo> you having fun?
[18:27] <sgclark> It is good so far
[18:28] <clivejo> Im glad :)
[18:28] <clivejo> I hope you teach us all you learn :)
[18:31] <clivejo> acheron_uk: Can you see why this is failing?  http://kci.pangea.pub/job/yakkety_unstable_kcalcore/
[18:33] <clivejo> sgclark: where do you point KCI to your github fork?
[18:34] <sgclark> jenkins settings
[18:34] <clivejo> Manage Jenkins?
[19:40] <clivejo> looks like KCI died a horrible death
[21:51] <jimarvan> helloz :)
[21:51] <clivejo> hi jimarvan
[22:12] <clivejo> theres LP crapping out again