[00:00] <sgclark> Now if we could just figure out the magic Jonathan did to get those approved so fast.
[00:01] <sgclark> anyway, I am off, migraine all day. Need rest.
[00:01] <sgclark> wow what is with all the merge fails..
[00:11] <sgclark> wtf
[00:12]  * sgclark runs off and cries
[00:13] <valorie> so strange!
[00:15] <sgclark> Every single one has - There is no stable or unstable branch! so what do we have... are all these qt4 apps?
[00:15] <sgclark> no I am seeing qt5 apps going across
[00:15] <sgclark> something is very broken.. again.. sigh..
[00:15] <sgclark> ktux? really?
[00:16] <sgclark> come on give me a break!?!
[00:16] <sgclark> kfloppy.. 
[00:17] <valorie> sitter, any insight?
[00:17] <valorie> things were going so green.....
[00:17] <sgclark> these are all first time builds
[00:18] <sgclark> why are they even there is what i want to know
[00:18] <sgclark> valorie: it is not quite as tragic as it looks, these are git branch merges not builds.
[00:19] <valorie> oh good
[00:19] <sgclark> but depressing non the less.
[00:19] <valorie> still, red FAILUREs across the screen.....
[00:19] <sgclark> I don't know what changed to trigger these, most of them should not be merging at all.
[00:20] <sgclark> we do not maintain qt4 apps in git, which is why there is no stable or unstable branches... point of failure
[00:21] <sgclark> anyway, head hurts to much right now to even attempt debugging
[00:23] <valorie> sgclark: {{{{{{{{{{{{{{{{{{{{{{{{{{{{hugs}}}}}}}}}}}}}}}}}}}}}}}}}}}}}}}}}}
[00:23] <valorie> get a nice lie-down in some quiet dark place
[00:24] <sgclark> ty
[00:24]  * valorie puts on the soft music and hot tea
[00:24] <sgclark> :)
[00:51] <ahoneybun> damn!
[00:53] <sgclark> these are all branch failures. I don't know what changed... but it has to do with backports. clivejo yofel ^^
[08:57] <sitter> oO
[08:58] <sitter> I should make optimizations while doing updates I guess
[08:58] <valorie> everybody left and kci blew up
[08:59] <sitter> nah it's my fault
[08:59] <sitter> it created jobs it shouldn't create
[09:00] <valorie> poor overworked kci
[09:23] <sitter> going through it with a flamethrower now
[09:24] <valorie> thank you darling
[10:38] <clivejo> sitter: care to share the flame thrower, Id take great pleasure in roasting KCI!
[10:41] <clivejo> sitter: also, we have a few packages need their debian git URL changed/updated
[10:42] <clivejo> can you show one of us how to do that?
[10:52] <sitter> clivejo: debian git url updated?
[10:52] <sitter> the jobs derive themself from the debian git repo
[10:52] <sitter> https://github.com/blue-systems/pangea-tooling/blob/master/ci-tooling/data/projects/kci.yaml
[10:53] <clivejo> sitter: KCI is using these http://anonscm.debian.org/cgit/pkg-kde/kubuntu/
[10:53] <clivejo> but debian have created their own 
[10:54] <sitter> fork and change https://github.com/blue-systems/pangea-tooling/blob/master/ci-tooling/data/projects/kci.yaml
[10:54] <clivejo> we dont have the resources to maintance separate ones, so need to use the debian maintances repos
[10:54] <sitter> then have someone with admin access setup an envrionment and run ./update-projects.rb --> https://github.com/blue-systems/pangea-tooling/wiki/Getting-Started
[11:22] <clivejo> sitter: could you update the following https://anonscm.debian.org/git/pkg-kolab/libkolab.git https://anonscm.debian.org/git/pkg-kolab/libkolabxml.git and http://anonscm.debian.org/cgit/pkg-kde/kde-extras/libkgapi.git/
[11:23] <clivejo> and Ill make a start on getting the branches setup
[11:24] <sitter> won't make a difference as long as the other repos have CI branches
[11:25] <clivejo> sitter: just trying to tidy up other packaging
[11:25] <clivejo> our
[11:28] <clivejo> sitter: also is it possible to add other KDE projects to KCI?
[11:28] <clivejo> ie calligra, kdevelop, digikam?
[11:36] <sitter> sure
[11:36] <sitter> need packaging
[11:45] <clivejo> sitter: any ETA on when KCI will be working again?
[11:57]  * clivejo sings to himself
[12:17] <clivejo> sitter: why is executor 1 showing as dead?
[12:17] <sitter> thraed dead
[12:17] <clivejo> how come?
[12:17] <sitter> no clue
[12:57] <sitter> clivejo: https://paste.kde.org/pad3p04s4 flamethrower. not that it has any use outside what I did :P
[13:19] <BluesKaj> Hiyas all
[13:20] <clivejo> hi BluesKaj
[13:20] <BluesKaj> hi clivejo
[14:33] <ghostcube> meh srsly? https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=815060
[14:45] <marco-parillo> It does seem analogous (though obviously not identical) to the current ZFS dust-up.
[14:46] <marco-parillo> But, until anything chages, maybe better suited to -offtopic
[16:30] <aseques> I just upgraded my laptop to current kde using kubuntu-backports and got my first crash 
[16:30] <aseques> Apparently drkonky is not triggering the install of the debug packages
[16:31] <aseques> Is there any shortcut to install all the required packages for kde debugging (basically to get useful traces)
[16:38] <soee> hmm i'm not sure
[16:38] <soee> but their size would be huge :)
[20:08] <ahoneybun> I can't install ubuntu-sdk
[20:08] <ahoneybun> dep hell
[20:09] <sgclark> installs fine here
[20:09] <ahoneybun> what?
[20:10] <ahoneybun> I'm getting "Some packages could not be installed"
[20:11] <ahoneybun> unmet dependecies
[20:11] <sgclark> dunno. did not get that and it is installling
[20:11] <ahoneybun> mm
[20:11] <sgclark> though I am on xenial, you?
[20:11] <ahoneybun> I cleaned install 15.10 yesterday, updated, added backports, updated
[20:11] <ahoneybun> oh
[20:12] <ahoneybun> did you install a daily or upgraded?
[20:14] <sgclark> this particular install has survived upgrades since vivid haha.
[20:14] <ahoneybun> oh wow
[20:22] <ahoneybun> mm do-release-upgrade -d did not find a new release
[20:23] <ahoneybun> tw
[20:32] <acheron88> ahoneybun: on a fairly fresh wily VM, I get: http://i.imgur.com/RQ16X4S.png
[20:33] <ahoneybun> same thing here acheron88 
[20:33] <ahoneybun> even with the backports ppa
[20:33] <acheron88> xenial seems fine, though didn't actually do the install
[20:34] <ahoneybun> a few packages must not be in wily for some reason
[20:34] <ahoneybun> very weird
[20:35] <acheron88> or qt5 version?
[20:35] <ahoneybun> maybe
[20:35] <ahoneybun> but Ubuntu 15.10 works fine
[20:36] <sgclark> isn't 15.10 wily?
[20:36] <ahoneybun> yea
[20:36] <acheron88> was a newer qt built in the ppa though?
[20:37] <acheron88> dunno to be honest. I skipped wily
[20:50]  * ahoneybun starts his move to xenial
[21:04] <soee> vote please https://plus.google.com/u/0/110954078302330754910/posts/QxzTjSopu9x :)
[21:04] <ghostcube> #kubuntu-devel-offtopic
[21:07] <ghostcube> oh wrong channel wrong window.. sorry guys :D  ... and i wondered why nothing happend
[23:12]  * clivejo kicks kidentitymanagement
[23:13] <clivejo> stupid thing
[23:25]  * sgclark kicks all of wily
[23:30] <valorie> oh dear, sitter's fix didn't fix everything
[23:31] <clivejo> what fix?
[23:32] <sgclark> valorie: we are down to actual build failures. I am fixing.
[23:33] <valorie> clivejo: he showed you the code last night
[23:33] <valorie> sgclark: \o/ and {{{{{{{{{{{{{{{{{{{{{{{{{hugs}}}}}}}}}}}}}}}}}}}}}}}}}}}}}
[23:33] <sgclark> what code where?
[23:34] <sgclark> I would like to know how to fix that mess to
[23:34] <valorie> when they were discussing the "flamethrower"
[23:34] <valorie> above
[23:35] <sgclark> looks like my bouncer decided it was not important
[23:35] <sgclark> :(
[23:36] <valorie> I'll paste, sgclark
[23:38] <clivejo> sgclark: https://paste.kde.org/pixjtbiqx/yvurvr
[23:40] <valorie> or that!
[23:40] <valorie> lol
[23:49] <clivejo> about time!
[23:52] <valorie> yay for green!
[23:55] <clivejo> sgclark: http://kci.pangea.pub/job/xenial_unstable_akonadi/
[23:55] <clivejo> lots of missing files
[23:55] <clivejo> you know what to do with them?