[07:39]  * soee 5% fingers crossed...
[08:57] <soee> how can i fix this after 15.10 -> 16.04 upgrade: http://paste.ubuntu.com/15446225/ ?
[09:03] <totof-at-work> hi soee
[09:04] <totof-at-work> if i remeber correctly you need to unistal libkipi-data for install libkf5kipi-data
[09:04] <totof-at-work> but before you need to uninstall ksnapshot too and replace it by kde-spectacle wihch is his replacement :)
[09:08] <soee> ok ill try to fix this
[10:00] <soee> totof-at-work: yes removing libkipi-data fixed the probem, thank you
[10:00] <soee> yofel: ^ are we aware of tis issue ?
[10:02] <totof-at-work> soee: u're welcome ... test on my 16.04 vbox
[10:02] <totof-at-work> :)
[12:24] <BluesKaj> Hiyas all
[14:14] <yofel> soee: yes we are
[14:19] <soee> yofel: ok :) my upgrade today 15.10->16.04 failed a bit. I had to run apt-get -f install than apt full-upgrade than fix gwenview :)
[14:24] <yofel> soee: I uploaded something that should fix things
[14:25] <yofel> clivejo: I took care of kipi - I think...
[14:25] <clivejo> good, my solution is a sledge hammer
[14:26] <yofel> should ironically also "solve" the non-functional printscrn button - by simply not removing ksnapshot
[14:28] <clivejo> when will the button start using spectacle?
[14:29] <clivejo> Ive been openning spectacle manually to take screenshots, seems to work fine
[14:29] <yofel> As understand it by now:
[14:29] <yofel> 1) Fresh installs
[14:29] <yofel> 2) People manually switching the functionality to be covered by spectacle
[14:29] <yofel> 3) Someone finding out why the auto-switch doesn't work (or if it even exists)
[14:30] <yofel> /usr/bin/germinate-update-metapackage: Installed debootstrap is older than in the previous version! (1.0.72ubuntu1 < 1.0.78+nmu1)
[14:30] <yofel> seriously..
[14:30] <clivejo> Veco 200 1180 SPA
[14:30] <clivejo> oups
[14:32] <soee> :)
[14:50] <yofel> sgclark: kubuntu-meta refreshed again and uploaded
[14:52] <sgclark> yofel: thanks
[14:52] <sgclark> sorry very distracted by kde CI explosions. hopefully all is going well here
[14:53] <yofel> just do your thing, we'll manage
[17:11] <yofel> FYI: kubuntu-desktop should be installable in xenial again. Shout if that's not the case for someone
[17:15] <genii> "gain" ?
[17:16] <genii> Hm, already installed here
[17:25] <yofel> it was fixed in the ppa for a couple days already actually..
[19:14] <mamarley> yofel: It looks like plasma-workspace 4:5.5.5.2-0ubuntu1~ubuntu16.04~ppa3 has just started appearing in the "local or obsolete" list in Synaptic.  Was it deleted or something?
[19:15] <yofel> o.O
[19:15] <yofel> looking
[19:19] <yofel> mamarley: hm, the staging ppa has ~ppa2, not sure where you got ~ppa3 from... 
[19:19] <mamarley> yofel: Oops, my bad.  That was something I had upload to my own PPA previously to test a patch I had backported.  Sorry to bother you.
[19:20] <yofel> np
[19:20]  * mamarley slaps himself around a bit with a large trout.
[19:20] <yofel> do you thing you'll be done with 364.12 tomorrow? ^^
[19:20] <mamarley> yofel: https://launchpad.net/~mamarley/+archive/ubuntu/staging/+packages :)
[19:21] <yofel> <3
[19:21] <mamarley> Don't thank me, thank tseliot.
[19:21] <mamarley> I just uploaded it.
[19:21] <yofel> ah right
[20:17] <vlad376> JOIN
[20:27]  * clivejo yawns
[20:28] <clivejo> anyone here?
[20:28]  * mamarley has been using Applications 15.12.3 from the staging PPA on multiple systems for a while now and has had no problems. :)
[20:29]  * mamarley isn't here.
[20:29] <clivejo> oh no, voices in my head again
[20:29]  * yofel whispers ghostly words about the image live session having a folderview widget that's too small to show any contents
[20:30] <clivejo> its weird, when I read your messages I can hear your accent!
[20:31] <yofel> IKR :D
[20:31] <clivejo> how does that work?!?
[20:32]  * clivejo wonders what yofel is up to
[20:32] <clivejo> some uber complicated packaging Im guessing
[20:35] <yofel> more like wondering what to do about the remaining autopkgtests and what keeps breeze in proposed
[20:36] <clivejo> could I try to stage fw 5.20?
[20:36] <yofel> I wonder if we should patch out the wayland tests in kwin until we know how to run those
[20:36] <yofel> no
[20:36] <yofel> I mean, you can, but don't put it in git, as I don't plan to ever release that
[20:37] <clivejo> I understand that bit
[20:37] <clivejo> could they be pushed to unstable?
[20:39] <yofel> ah right, the version gets pulled from the changelog... we need a plan for that in xenial+1...
[20:39] <clivejo> yofel: you dont plan to release 5.20 to xenial_backports?
[20:40] <clivejo> like after release date
[20:40] <yofel> possibly. But if you put it into _archive now I have even more changelogs that I need to work around if I fix something in the archive
[20:40] <clivejo> I know it cant go into xenial_archive, thats in freeze now
[20:41] <clivejo> but was thinking if I could push to kubuntu_unstable branch somehow
[20:41] <clivejo> maybe learn how the script works
[20:42] <yofel> you will get merge conflicts every time someone fixes something in _archive, but yes, that would work
[20:42] <yofel> it would fix the package versions in CI at least
[20:42] <clivejo> eakk, merge conflicts
[20:42] <sgclark> noooooooo
[20:42] <clivejo> well that was my plan
[20:43] <clivejo> yet to get CI fixed up
[20:43] <clivejo> try
[20:43] <clivejo> all this red makes me sad
[20:43] <sgclark> red? 
[20:43] <sgclark> what happened? how will staging frameworks help?
[20:44] <yofel> Lets talk about the CI in May after all of us went on vacation
[20:44] <sgclark> lol
[20:44] <clivejo> lot of changes in new frameworks
[20:45] <sgclark> that can still be fixed in unstable branch. how is staging frameworks we can't use in archive going to fix things?
[20:46] <clivejo> they cant go in the archive
[20:46] <clivejo> but they might be able to go into backports
[20:46] <sgclark> exactly, freeze
[20:46] <clivejo> Im not saying for them to go in the archive, just stage them
[20:46] <sgclark> yeah but that will cause a merge tastic pile of mess. while archive stuff is still being worked on
[20:47] <sgclark> well it is all yours to fix then :) I am distracted by kde ci atm :(
[20:48] <clivejo> will it create merge conflicts with two different versions?
[20:49] <clivejo> it unstable is say 5.20 and archive is 5.18?
[20:49] <clivejo> if
[20:49] <yofel> in debian/changelog, yes
[20:49] <clivejo> :(
[20:50]  * clivejo sees why you say "NO"
[20:50] <sgclark> yeah and then getting changes back inot xenial archive branch will be a disaster
[20:51] <clivejo> I might stage them and upload to my PPA 
[20:51]  * yofel adds gcc and make to desktop recommends
[20:51] <yofel> someone scream if they want to object
[20:51] <yofel> ...
[20:52] <clivejo> yofel: how come?
[20:52] <clivejo> arent they dev tools?
[20:52] <yofel> let me c&p the xubuntu comment
[20:52] <yofel> +Here we provide a minimal development environment sufficient to build kernel
[20:52] <yofel> +drivers, so that this is possible on the live CD and in scenarios where
[20:52] <yofel> +it is problematic to get these packages onto the installed system in order
[20:52] <yofel> +to compile a driver. -mdz
[20:52] <sgclark> yofel please do. we can close that bug for gcc with virtualbox... tired of arguing haha
[20:52] <yofel> right, and they *do* have a point
[20:52] <sgclark> yea
[20:53] <sgclark> I say do it
[20:53] <clivejo> does desktop not have limits?
[20:54] <yofel> we're already like 200m over the limit - do we care?
[20:54] <yofel> it's a soft limit anyway
[20:54] <clivejo> LOL then no :P
[20:54] <clivejo> I thought that was a hard limit
[20:54] <sgclark> I don't think 2 more will kill us hhaha
[20:54] <yofel> from yesterday:
[20:54] <yofel> kubuntu/daily-live: xenial-desktop-amd64.iso oversized by 308822016 bytes (1592279040)
[20:54] <yofel> kubuntu/daily-live: xenial-desktop-i386.iso oversized by 329629696 bytes (1613086720)
[20:54] <clivejo> gcc not pretty big?
[20:55] <yofel> so make that 300
[20:55] <yofel> not sure, will be ~40m at least
[20:55] <clivejo> why does desktop "recommend" it?
[20:55] <yofel> so that you can remove it?
[20:56] <clivejo> is it needed for normal desktop operation?
[20:56] <yofel> no, but recommends is the lowest "default" priority, so you need that to have it on the image
[20:56] <clivejo> is there come components need compiled on the fly or something?
[20:57] <sgclark> no. just convenient to install virtualbox drivers ( and other drivers) after install
[20:57] <yofel> that ^ mosty
[20:57] <yofel> if you use the internal vbox installer then it'll build its own drivers, not the dkms ones
[20:57] <clivejo> I see
[20:58] <yofel> we probably have a bunch of stuff on the image that we don't need though, if someone wants to read through the manifest
[20:59] <sgclark> there was stuff on there that made me go hmmm. BUt I did not wnat to mess stuff up. Maybe one meeting we can go through that together.
[21:23] <yofel> sgclark: do I see correctly that build.kde.org has no useful kopete builds?
[21:23] <yofel> the matrix setup is giving me a headache..
[21:31] <sgclark> yofel: some explosions occurred last night.
[21:31] <sgclark> hense why I am distracted.
[21:32] <yofel> that included a history wipe? or just failures?
[21:32] <sgclark> yes
[21:32] <yofel> ok
[21:33] <sgclark> yofel: https://build-sandbox.kde.org/job/kopete master latest-qt4/
[21:34] <sgclark> my sandbox did not explode
[21:35] <yofel> sgclark: thanks!
[21:35] <yofel> so the test is broken upstream, that's what I wanted to know
[21:54] <soee> hiho
[21:58] <clivejo> hi soee
[21:58] <soee> news of the day http://www.phoronix.com/scan.php?page=news_item&px=NVIDIA-364.12-Linux
[21:59] <soee> Today's NVIDIA 364.12 Linux driver does deliver on Wayland and Mir support! 
[21:59] <yofel> [    10.253] (II) NVIDIA GLX Module  364.12  Wed Mar 16 20:39:46 PDT 2016
[21:59] <yofel> ;P
[22:00] <soee> woot ?
[22:00] <yofel> not that I can test the modesetting stuff on optimus though. Will try that on my other pc tomorrow
[22:08] <mamarley> Sadly, it doesn't do a high-res framebuffer yet. :/
[22:09] <yofel> bummer
[22:09]  * yofel dreams of a time where you can run modesetting with glamor on nvidia
[22:09] <soee> well im waiting for tearing fixes  :(
[22:11] <mamarley> soee: Just put "export __GL_YIELD="USLEEP"" in your ~/.profile and run kwin with compositing turned on and set to "Automatic" tearing prevention.
[22:14] <soee> mamarley: im not sure if it will fix extra huge problems on second (TV) screen
[22:15] <mamarley> I have no idea there.  I have a couple of systems with dual monitors, but the monitors are identical.
[23:51] <yofel> sgclark: are there any 32bit kde ci builds?
[23:52] <sgclark> yofel: no
[23:52] <yofel> hm ok
[23:52] <sgclark> no resources
[23:53] <yofel> I'm looking at the baloo test failure, and so far the only parallel I can see is that it fails on the 2 32bit archs that get tested (i386, armhf)