[09:49] <mparillo> Minor annoyance, but if somebody has a fully upgraded YY, could you please open a konsole, and type. Does the block cursor seem a bit to the right?
[09:54] <acheronuk> maparillo: bug with the default font in konsole I think. try changing to a different one?
[09:54] <acheronuk> mparillo I mean ^^
[09:59] <mparillo> acheronuk: And once again, you came to my help. Switching to Liberation Mono 10 (green on black, for old times sake), solved it for me.
 Shall I put the kettle on ?
[10:38]  * acheronuk will hardly ever refuse coffee
[10:51] <sick_rimmit> Coffee's ready :-D
[10:52] <acheronuk> Ta! lovely
[11:08] <BluesKaj> Hiyas all
[12:10] <yofel> clivejo: yes, copy them for now. That's what CI is supposed to do anyway
[12:10] <clivejo> any ideas on how to automate it again?
[12:10] <clivejo> without the git repo name spaces?
[13:07] <acheronuk> with failures such as E: kscreen: debian-revision-should-not-be-zero 4:5.6.4+p16.10+git20160610.1449-0 would that be an issue with KCI versioning, or something to be overidden? 
[13:15] <clivejo> acheronuk: they are automatically ignored by KCI
[13:29] <acheronuk> so http://kci.pangea.pub/job/yakkety_unstable_kscreen/37/parsed_console/ reports "Got a build failure" and is red
[13:30] <acheronuk> but logs say build and debs are done, with only errors being 3 "debian-revision-should-not-be-zero" and "out-of-date-standards-version 3.9.6"
[13:32] <acheronuk> KCI thinks the ppa build "failed" for which?
 @Valoriez are you and Scarlett going to seagl?
 (Photo, 960x1280) https://irc-attachments.kde.org/0d5ST8at/file_135.jpg
[17:06]  * acheronuk thinks KCI has a few screws loose
[17:10] <acheronuk> !info partitionmanager
[17:50] <acheronuk> plasma-integration unstable now needs a dep on breeze-dev. considering that KCI is building breeze with a v of 5.6.4.., should that dep be added unversioned?
 * knows KCI has a few screws loose *
[18:22] <acheronuk> lol
[18:22] <clivejo> few massive bolts too
[18:28] <acheronuk> or the whole thing is about to fall off the wall
[18:30] <acheronuk> is partitionmanager not to be updated any more? no new version since vivid
[18:32] <clivejo> acheronuk: https://code.launchpad.net/~acheron/kubuntu-packaging/+git/kcalc/+merge/297127
[18:32] <clivejo> because its unreleased there no need to bump the ubuntu version
[18:33] <acheronuk> didn't notice it had, or I would have put it back to 1
[18:34] <clivejo> and this one does need a new entry - https://code.launchpad.net/~acheron/kubuntu-packaging/+git/plasma-integration/+merge/297129
[18:35] <clivejo> that version has been released to yakkety, so we shouldnt touch it
[18:35] <clivejo> we need to make a brand new UNRELEASED version
[18:35] <acheronuk> gotcha
[18:36] <clivejo> you can bump the ubuntu version in that one
[18:37] <acheronuk> stupidly, that is what I did originally, then decided to undo.
[18:37] <clivejo> not stupid, just takes a while to understand the versions
[18:37] <clivejo> and thats the nice thing about these merges
[18:42] <acheronuk> I'll redo both then
[18:43] <clivejo> did my kopy work?
[18:49] <acheronuk> not sure
[18:50] <clivejo> BTW Id version that breeze-dev
[18:51] <clivejo> but maybe our scripts would be best doing it
[18:54] <acheronuk> so something like http://paste.ubuntu.com/17224540/
[18:55] <clivejo> looks good
[18:56] <acheronuk> harold didn't version it on neon I notice, so I guess it's ok like that
[19:08] <clivejo> ok pushed
[19:08] <clivejo> and kicked KCI
[19:08] <acheronuk> hope you have steel toecaps
[19:08] <clivejo> yup
[19:23] <clivejo> oh apps 16.04.2 are available
[19:24]  * clivejo wonders if korganizer is fixed
[19:24] <acheronuk> yeah, I saw the pre-release email the other day
[19:24]  * acheronuk has started reading them now
[19:24] <clivejo> LOL
[19:59] <yofel> clivejo: well, offhand 3 ideas: 1) use a trial-and-error cascade to detect what something is by existing upstream branch names. 2) wire the CI up to our KA files. 3) Wire the CI up to the upstream kdesrc metadata
[20:00] <valorie> ahoneybun: did you get that flier at SELF?
[20:00] <clivejo> I dont know how to implement any of them, but I prefer number 3 personally
[20:02]  * clivejo wonders if we should just try and setup our own KCI?
[20:03] <valorie> how is neon doing the above jobs?
[20:03] <yofel> using namespaces IIRC
[20:03] <valorie> ah
[20:03] <valorie> is the metadata good quality?
[20:03] <clivejo> they cloned debian and use their own repo and build machines
[20:04] <valorie> seems like there are up and down sides to each of the alternatives
[20:04] <clivejo> Im always in fear of breaking KCI
[20:05] <valorie> my houseguests are gone for now, and I've caught up on sleep
[20:06] <valorie> seems like weeks since I was caught-up with what's going on here
[20:06] <yofel> I guess we could also try to use jenkins job settings for that. But that would mean manually setting that for all jobs (would be a one-time thing though)
[20:07] <clivejo> there seems to be a build complete trigger
[20:08] <clivejo> could that be used to do the kopy
[20:08] <yofel> no, IIRC the tooling chain itself triggers that
[20:09] <yofel> well, "no" IIRC
[20:26] <clivejo> acheronuk: any more merge requests?