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