[01:50] <claydoh> wowzers, ppa much? -> https://www.kubuntuforums.net/showthread.php?69521-Sometimes-after-updating-my-kwin_x11-nor-kwin_wayland-doesnt-want-to-start
[01:52] <claydoh> this exagerated instance does highlight the fact that we have too many ppas in the same place, imnsho 
[04:05] <RoninLIfe> hello
[05:52] <RoninLIfe> welcome
[05:53] <RoninLIfe> why somtimes the konsole bugs and gives cpu load even when its closed ? 
[06:33] <soee> hiho
[09:15] <christol_> Hi Everybody
[09:15] <valorie> hi christol_
[09:58] <vip> hi ho
[09:59] <clivejo> hi vip
[10:01] <clivejo> ark is failing on autotests - 4/4 Test #2: kerfuffle-archivetest ............***Exception: Other  0.26 sec
[10:02] <clivejo> any ideas how to fix that?
[10:02] <bshah> clivejo: what is output?
[10:03] <freeflying> sorry for a silly question, what's the best practice of building package locally? used to use pbuilder-dist, seems its not available any more
[10:03] <clivejo> bshah: buildlog --> https://launchpadlibrarian.net/233005127/buildlog_ubuntu-xenial-amd64.ark_4%3A15.12.0+git20160105.0940+16.04-0_BUILDING.txt.gz
[10:04] <clivejo> freeflying: pbuilder
[10:04] <freeflying> clivejo, thanks
[10:04] <yofel> really? pbuilder-dist was in ubuntu-dev-tools, maybe you're missing that?
[10:04] <yofel> freeflying: ^
[10:05] <clivejo> freeflying: https://wiki.ubuntu.com/PbuilderHowto the kubuntu hooks are handy too
[10:06] <freeflying> yofel, correct, I missed that, thanks 
[10:06] <freeflying> clivejo, thanks
[10:06] <yofel> :)
[10:07] <clivejo> yofel: is there a way of defering autotests?
[10:08] <yofel> defering?
[10:09] <yofel> the tests that fail on your are executed by dh_auto_test, that's part of the build chain
[10:09] <yofel> you can ofc. override that
[10:11] <clivejo> with the new frameworks due out are we going to skip 5.17.0?
[10:12] <yofel> lets actually finish 5.17 first, after that we can go with 5.18 for the archive upload
[10:15] <clivejo> yofel: I wish I knew how to finish them!
[10:17] <clivejo> oxygen-icons5 -> https://launchpadlibrarian.net/230082461/buildlog_ubuntu-xenial-amd64.oxygen-icons5_4%3A5.17.0-0ubuntu1~ubuntu16.04~ppa2_BUILDING.txt.gz
[10:17] <clivejo> what does it even mean?!?
[10:19] <yofel> that package is rather broken, AFAIR not even the git repo is correct
[10:19] <yofel> ping me in the evening, then I can maybe look at it
[10:19] <clivejo> that file is being made in extra-cmake-modules -> -rw-r--r-- root/root     24793 2015-12-06 14:09 ./usr/share/ECM/kde-modules/KDEInstallDirs.cmake
[10:20] <clivejo> in package extra-cmake-modules_5.17.0-0ubuntu1~ubuntu16.04~ppa1_amd64.deb
[10:21] <clivejo> why is ECM yellow?
[10:27] <soee_> yofel: wha about Plasma 5.5.2, are we going to finish it to or just jump to 5.5.3 (should be released today) ?
[10:39] <yofel> I would also tend to finishing that. The remaining problems aren't going to go away with .3, and once we've fixed those updating to .3 should be a no-brainer
[10:40] <soee_> yofel: ok, Riddell also says he might delay 5.5.3 by one day or so
[10:54] <Mirv> bshah: qtfeedback and qtsystems up-to-date
[10:56] <bshah> Mirv: <3 thanks
[11:15] <Roninlife> hey
[11:20] <soee_> Roninlife: hiho :)
[11:22] <Roninlife> whats up soee
[11:23] <soee_> all good Roninlife :) how about you ?
[11:46] <Roninlife> welcome back
[11:53] <Roninlife> wb soee
[11:53] <Roninlife> lol
[12:32] <BluesKaj> Hiyas all
[13:02] <clivejo> hi  BluesKaj
[13:04] <BluesKaj> hey clivejo, seems we're getting closer to plasma 5.5?
[13:04] <kfunk> I hope so! *waits*
[13:05] <clivejo> so close, but so far!
[13:05] <clivejo> hi apol_
[13:06] <apol_> hi, I thought somebody might want to answer this https://www.reddit.com/r/kde/comments/3zfkvi/can_somebody_clarify_on_the_current_situation_of/
[13:08] <clivejo> apol_: are you a KDE dev?
[13:09] <BluesKaj> apol_:  to be clear plasma 5.5 is not ready for kubuntu yet. Read the topic 
[13:09] <apol_> clivejo: yes
[13:09] <clivejo> thought so
[13:09] <clivejo> maybe you can help :)
[13:10] <clivejo> kscreenlocker wants to install *.mo files
[13:10] <apol_> BluesKaj: I don't care, I don't use kubuntu, but your users need to know in better places than the IRC chatroom topic
[13:11] <clivejo> apol_: there are a few issues with packaging 5.5.2
[13:12] <clivejo> yofel: has been trying to get some answers from upstream
[13:12] <apol_> clivejo: kscreenlocker is part of plasma-workspace
[13:12] <yofel> not from upstream
[13:12] <yofel> .mo files go into arch-indep data packages usually
[13:12] <apol_> false
[13:12] <apol_> sorry
[13:13] <BluesKaj> apol_:  agreed, but the devs have been very busy trying to get 5.5 ready so there's hasn't been much time for posting the status in forums
[13:13] <yofel> I'm not too happy with kscreenlocker in general, and I didn't ping maxy again if he had a look
[13:13] <yofel> (I assume he hasn't yet)
[13:13] <apol_> clivejo: that's what kscreenlocker installs http://pastebin.com/q7b6AWbc
[13:13] <clivejo> you meant upstream as in debian *face palm*
[13:13] <clivejo> sorry yofel and apol
[13:13] <yofel> oh. right.
[13:13] <apol_> :D ok
[13:13] <yofel> that counts as upstream, somewhat
[13:14] <clivejo> we have a lot of upstreams!
[13:14] <apol_> we are the cool ones though
[13:14] <clivejo> yes you are
[13:14] <clivejo> KDE make the best software!
[13:15] <soee> so we are stuck with plasma and frameworks because of upstreams ?
[13:15] <clivejo> yofel: there was something we had to ask KDE thought?
[13:16] <clivejo> was it discover?
[13:16] <yofel> oh right, good memory you have
[13:16] <clivejo> I know, my memory is so bad, I need to make notes
[13:17] <yofel> apol_: regarding kscreenlocker, what of the data files in /usr/share are specific to the kcm? (other than the ones with kcm in their path/name)
[13:17] <yofel> the ksmserver, kservice, etc. stuff belong to the lib, right?
[13:18] <apol_> yofel: ksmserver belongs to plasma-workspace
[13:18] <apol_> it's one of the main processes that are started when plasma boots
[13:18] <yofel> apol_: I mean from your paste, e.g. /home/kde-devel/kde5/share/ksmserver/screenlocker/org.kde.passworddialog
[13:19] <yofel> that's for the lib, not for the kcm, right?
[13:20] <apol_> yofel: I'd ask mgraesslin, I don't know what org.kde.passworddialog is
[13:20] <yofel> ok
[13:20] <bshah> its screen locker theme IIRC
[13:20] <bshah> moment, let me check
[13:21] <mgraesslin> looks like a left over
[13:21] <mgraesslin> it's just a metadata.desktop
[13:21] <bshah> yeh..
[13:22] <bshah> should be killed
[13:24] <apol_> looks like a murder candidate, yes
[13:26] <yofel> ok, aside from that, the knotification rc, dbus interface as well as kcheckpass and kscreenlocker_greet are used by plasma, right? And not by  the kcm
[13:27] <yofel> mgraesslin: ^
[13:27] <mgraesslin> yofel: sorry I don't understand the question
[13:27] <mgraesslin> yofel: are you trying to split the package?
[13:28] <yofel> mgraesslin: yes, would the screen locker work if any of that is missing?
[13:28] <mgraesslin> yofel: if you remove anything of that you destroy the lockscreen
[13:28] <yofel> thanks, that's what I wanted to know 
[13:28] <bshah> knotification rc wouldn't be required?
[13:29] <mgraesslin> yofel: as that is security relevant I suggest to not perform any splitting without consulting us
[13:29] <yofel> mgraesslin: right, someone already tried to split things and made a seperate kcm and lib package (which is good), but also bundled all data files with the kcm, which is wrong
[13:29] <mgraesslin> bshah: it's emitting screen locked/unlocked notifications, no idea whether that breaks
[13:30] <mgraesslin> yofel: the greeter must be together with the lib
[13:30] <mgraesslin> yofel: also all files used by the greeter must be together with the lib
[13:31] <mgraesslin> my suggestion would be: don't split
[13:34] <yofel> well, multiarch kind of requires us to, but now I at least know for certain that the current split is broken
[13:34] <yofel> so thanks for clearing that up
[13:34] <yofel> (or at least the package naming if we make everything required in the end)
[13:48] <yofel> o.O
[13:48] <yofel> how did kscreenlocker end up with 3 UNRELEASED changelog entries
[13:52] <yofel> ah, maxy did already go into fixing mode for kscreenlocker after all
[13:54] <BluesKaj> wth is all this trouble with screenlocker anyway?, seems like you guys are stuck on this thing
[13:54] <yofel> BluesKaj: do you want to have a working screen lock or a broken one?
[13:54] <yofel> if the packaging is wrong you'll end up with latter
[13:55] <BluesKaj> yofel: well , frankly I don't use it 
[13:55] <bshah> yofel: thing is screenlocker is split from plasma-workspace..
[13:55] <bshah> so maybe do exactly what plasma-workspace did?
[14:38] <yofel> clivejo: kscreenlocker DONE
[14:38] <soee> ;o
[14:38] <yofel> (mostly just merged in maxy's work that he just pushed)
[14:44] <soee> yofel: so what is left in 5.5.2 ?
[14:45] <yofel> not much, a bunch of yellow stuff, oxygen from frameworks, the ksnapshot release so it doesn't conflict with the new thing whose name I can't remember
[14:46] <yofel> and I think there was some kconf stuff to be looked at, but that's not that important
[14:47] <marco-parillo> The replacement for ksnapshot is Spektakle, spelled Spectacle (https://www.kde.org/announcements/announce-applications-15.12.0.php)
[14:48] <yofel> right, THAT THING
[14:49] <yofel> curious that everyone seems fine with "kscreenlocker", but "kspectacle"... no, we don't like stuff that starts with a k...
[14:51] <soee> ;D
[14:53] <mamarley> Maybe I am in the minority, but I always thought the application names with Ks were, well, Kute.
[14:53] <soee> Kinda
[14:54] <soee> yofel: but wait, so we have ksnapshot and spectacle now, both ?
[14:54] <yofel> kompletely true
[14:55] <yofel> soee: no, but there was one last ksnapshot release which has some transtition-relevant changes I believe
[14:55] <yofel> can't remember the whole email contents right now
[14:56] <soee> kscreenlocker builds fine
[14:59] <mamarley> I have noticed that kwin 5.5 dramatically improves an issue that has existed ever since buffer age support was added, laggy window dragging.
[14:59] <yofel> mgraesslin: is there any point in us building kwin with libhybris?
[14:59] <mamarley> It also fixes some relatively severe stability problems I was getting with 5.4.2.
[15:00] <mgraesslin> yofel: the libhybris in Ubuntu is too old. We need upstream, not Ubuntu's fork
[15:00] <yofel> ok, thanks
[15:02] <ScottK> yofel: FYI, detrout uploaded sddm 0.13 to Debian yesterday.  I see Kubuntu's a couple of releases behind.
[15:03] <yofel> ScottK: thanks. _Groo tried to update it to .13 recently, but we never finished it. We'll go with her work then
[15:20]  * yofel wonders if we want to give sddm on tty1 another try
[15:21] <yofel> might as well
[15:22] <yofel> oh, debian switches to 7 in a different patch
[16:00] <yofel> Mirv: is there some docs how to replicate those autopkgtests? I'm rather clueless about what's wrong with kdepimlibs and kdepim-runtime for qtbase, and kdelibs4support has an acc failure but no build artifacts :/
[16:00] <yofel> and there seem to be a couple "testsuite            FAIL timed out" kind of regressions, however that happens
[16:08]  * yofel puts on his "I don't care" hat and goes on with his life
[16:10] <clivejo> awww dont do that!
[16:10] <clivejo> you do care!
[16:10]  * clivejo makes yofel "I care toio much" hat
[16:10] <yofel> heh
[16:11] <yofel> lolwhat, the rocs amd64 autopackagetest regression is a g++ ICE o.O
[16:11] <yofel> haven't seen that in a while
[16:11] <clivejo> sorry I had to run off, had to take the pup to the vet and then took him on a walk
[16:11] <clivejo> will you be free later yofel?
[16:12] <yofel> after 8pm utc probably, if I feel motivated
[16:12] <clivejo> Id like to try packaging sddm
[16:13] <yofel> oh, then you're too late, I just did the merge ^^
[16:13] <clivejo> awwww
[16:13]  * clivejo cries
[16:14] <clivejo> will it be in staging, or testing?
[16:14] <yofel> you could try if the thing actually works: https://launchpad.net/~yofel/+archive/ubuntu/ppa/+sourcepub/5933756/+listing-archive-extra
[16:14] <yofel> in my ppa right now
[16:15] <yofel> I'll try it later 
[16:18] <clivejo> Ill install it
[16:18] <yofel> hm, I forgot to generate the full changelog, need to remember that for the archive upload
[16:24] <soee> with the current Plasma 5.5.2 and Frameworks 5.17, plasmashell crashes each time when running apt  update
[16:24] <yofel> update or upgrade o.O?
[16:25] <soee> update
[16:25] <soee> plasmashell crashes when starting this  action and finishing
[16:25] <yofel> got the stacktrace...? That's rather weird
[16:26] <Mirv> yofel: http://packaging.ubuntu.com/html/auto-pkg-test.html is the official documentation
[16:26] <soee> http://paste.ubuntu.com/14411714/
[16:26] <yofel> Mirv: thanks!
[16:27] <yofel> oh, muon, great *-.-
[16:27] <Mirv> yofel: if you look below the tests, you see "Should wait ... but forced" lines, so you can skip those ie currently kwayland rocs kdelibs4support kaccounts-integration kdepim-runtime kservice. the others however are what do block the migration.
[16:27] <yofel> aaah, right
[16:28] <Mirv> yofel: kdepimlibs fails at 41/62 Test #41: akonadi-sqlite-itemsynctest .................***Failed  according to the log so one can also try to execute that test from within the source tree instead of the full adt machinery
[16:28] <soee> also muon was removed before, and now when i try to install it: muon : Depends: libmuon (= 4:5.4.3-0ubuntu1) but it is not going to be installed
[16:28] <Mirv> and of course ideally you/someone at Kubuntu would force others too if decided they are not real regressions
[16:29] <yofel> soee: muon is gone officially, I'm not quite sure what happened to the fork that people wanted to keep alive
[16:29] <Mirv> for asking to rerun tests that seem flaky, pitti is afaik still the main contact
[16:29] <yofel> ok
[16:30] <yofel> bbl
[16:31] <genii> yofel: So this means back to Synaptic then?
[16:32] <yofel> genii: for GUI *package* management, yeah. Simply not enough of a use case these days to justify the maintenance it seems
[16:32] <BluesKaj> yofel:  I still have muon on plasma 5.4.3
[16:32] <BluesKaj> xenial
[16:33] <yofel> right, that's still there, but that'll be the last version of it
[16:33] <yofel> now really gone
[16:35] <BluesKaj> bummer I like muon as a package reference guide, sometimes I even use it to install packages 
[16:40]  * genii goes to check the -devel mailing list to find out who took over the muon packaging so he can pester them
[16:42] <genii> Hm, "Rick"
[16:43] <BluesKaj> genii:  good, why remove a perfectly good package manager in favour of some called "software center" gui that gives very little info about packages
[16:45] <genii> BluesKaj: Apparently the current maintainer is supposed to be Rick Timmis, aka Sick_Rimmit on IRC
[16:45]  * BluesKaj nods
[16:52] <snele> i much much much prefer muon over synaptic so i have to ask because i didn't understand well: are muon be going to be available in 16.04?
[16:53] <snele> or it is going to be removed from achive?
[17:01]  * ovidiu-florin is sexy and he knows it 
[17:01] <ovidiu-florin> ;-P
[17:02] <ovidiu-florin> hello humans
[17:03] <ovidiu-florin> clivejo yofel https://paste.kde.org/pord0vftl
[18:17] <mamarley> yofel: I just installed your sddm 0.13 package and it works fine for me. :)
[18:23] <genii> Ouch, 4 hours
[19:06] <yofel> snele: undecided yet I guess. Depends if we get something maintaned before release. Shipping software that nobody cares about for the next 5 or so years isn't something I like doing
[19:06] <yofel> mamarley: thanks for testing!
[19:08] <mamarley> The SDDM update did break the systemd unit I wrote for x11vnc, but that isn't your problem.
[19:13] <genii> I have lightdm as my default dm, but for some reason sddm keeps running also
[19:14] <mamarley> My problem is that the auth file was previously /var/run/sddm/:0, but the new one is a randomly-generated name that I can't hardcode...
[19:21] <yofel> genii: I've seen a bug report for that actually, I wonder why that happens
[19:21] <yofel> systemd internals are a mystery :S
[19:26] <genii> Maybe I should just chmod -x it for now
[19:56] <claydoh> re: muon package manager, I remember talk of discover being split, or something along those lines, but I don't recall mention of Muon package manager going away.
[19:58] <claydoh> that won't go down well. 
[19:58]  * claydoh goes and looks at octopi.....
[19:59] <marco-parillo> Can Octopi handle Ubuntu Archives?
[20:00] <claydoh> i dunno,  but it is used by Kaos
[20:04] <marco-parillo> I do not think it is packaged: apt-cache policy octopi 
[20:04] <claydoh> so it probab ly can be made to, or at least allow hooking into software-properties-kde like Muon and Synaptic can
[20:04] <claydoh> no, it is not in Ubuntu.
[20:04] <marco-parillo> N: Unable to locate package octopi (at least on xenial)
[20:05] <marco-parillo> So then it is off-topic, but what is nice is that (on Manjaro at least), it can also search the AUR.
[20:08] <claydoh> well nevermind for some reason I was thinking that kaos was somehow debian based
[20:14] <yofel> Riddell: do you know what exactly oxygen-icons5 is compared to oxygen-icons?
[20:14] <yofel> the same thing renamed or what?
[20:35] <Riddell> yofel: yes but released with frameworks instead of plasma
[20:35] <Riddell> yofel: yes but released with frameworks instead of applications
[20:35] <yofel> meh, oh well
[20:35] <Riddell> renamed cos applications version is 15.x while frameworks is 5.x
[20:36] <Riddell> so drop oxygen-icons and pick up oxygen-icons5
[20:36] <yofel> I still haven't decided whether it makes sense to rename the binary..
[20:37] <yofel> lets see what maxy prefers when he comes back
[20:40] <yofel> oh, fun, discover also has a name conflict
[20:40] <yofel> yay
[20:41]  * clivejo dances
[20:42] <yofel> people need to stop it with these overly simplistic names. It's as if everyone already forgot the systemsettings mess
[20:42] <clivejo> !info gfortran-5
[20:42] <yofel> you're interested in ancient programming languages? ^^
[20:43]  * clivejo wonders why he needs a fortran compiler
[20:44]  * clivejo is doing an upgrade and for some reason thats being installed
[20:45] <yofel> curious
[20:45] <clivejo> very curious, verging on crazy
[20:45] <yofel> and discover also has multiple unreleased changelogs..
[20:47] <clivejo> !info poppler
[20:48] <yofel> that's pdf stuff
[20:48] <clivejo> Id better put the bins out before I forget
[20:50] <yofel> grr, who comes up with unversioned libs in discover *-.-
[20:56] <denza242> Is -CI usable yet :x
[20:58] <yofel> I'll just go with the epoch for oxygen-icons, if debian decides to rename the binary we won't have a problem anyway
[21:00] <clivejo> ovidiu-florin: can you send me a changelog with your signature please
[21:00] <yofel> now to sort out that library mess in discover
[21:01]  * clivejo gives yofel a puppy treat
[21:06] <clivejo> anyone else having issues with git.debian.org?
[21:06] <yofel> WFM right now
[21:07] <clivejo> fatal: The remote end hung up unexpectedly
[21:07] <yofel> shlib-without-versioned-soname libDiscoverNotifiers.so
[21:07] <yofel> target_link_libraries(DiscoverNotifierDeclarativePlugin
[21:07] <yofel> Discover::Notifiers
[21:07] <yofel> why do people do stuff like this :'(
[21:10] <clivejo> ovidiu-florin: pokes
[21:52] <soee_> yofel: this discover mess is related to the plasma crash i mentioned ?
[22:16] <clivejo> anyone know what KCI is doing?
[22:17] <clivejo> and why builds seem to be timing out after 4 hours
[22:33] <soee_> not me 
[22:33] <soee_> i see a lot of apps packages have been fixed
[22:34] <soee_> so we almost have Plasma 5.5.2, have already  Frameworks 5.17
[22:34] <soee_> and apps are WIP
[22:34] <soee_> :)
[22:34] <clivejo> depends what you call a lot
[22:34] <soee_> clivejo: lot of green
[22:35] <clivejo> yofel: ping
[22:39] <soee_> does it make sens for you guys: http://wstaw.org/m/2016/01/05/snapshot46.png
[22:39] <soee_> (the notification content)
[22:40] <clivejo> soee_: what you mean?
[22:40] <soee_> clivejo: notification title suggest that there are some updates
[22:40] <soee_> but the message says that system is up to date ..
[22:41] <clivejo> which is it?
[22:41] <soee_> ??
[22:42] <clivejo> if you do an apt-get is there updates?
[22:43] <soee_> clivejo: this one pops up after updates are applied
[22:43] <soee_> so the title should be something like: All updates installed
[22:43] <soee_> or something
[22:45] <soee_> ill try to catch tomorrow some Plasma dev 
[22:45] <soee_> and suggest changing it
[22:45] <clivejo> could be something to do with the muon issues
[22:46] <soee_> looks more like wrong label used here
[23:11] <soee_> mamarley: do you plan to add it t drivers ppa: http://www.phoronix.com/scan.php?page=news_item&px=NVIDIA-361.16-Beta ?
[23:11] <mamarley> soee_: Ah, another NVIDIA beta, fun fun.  Yep, I am on it! :)
[23:12] <soee_> :D
[23:12] <soee_> im up to test them when ready
[23:12] <valorie> gosh I hope that Muon package manager doesn't disappear
[23:12] <valorie> so much better than synaptic
[23:13] <soee_> true :(
[23:13] <mamarley> I actually never tried Muon.  No point in it now, I guess...
[23:14] <clivejo> didnt Rick and some others volenteer to maintain it?
[23:14] <soee_> for e it was just easiest way to search for packages and install them, though it can be done from terminal to
[23:14] <soee_> clivejo: yes i think
[23:15] <valorie> sure, I use the term most of the time, because it's faster
[23:16] <valorie> but muon has nice tabs about changelogs and so
[23:16] <valorie> I'm sure there are cli equivalents, but Muon Just Works
[23:16] <soee_> mamarley: any idea if upgrading kernel might be an issue for existing nvidia driver?
[23:17] <mamarley> soee_: It sometimes is, though I am pretty sure that most of what we have in the PPA right now is compatible with 4.3 in Xenial.  Let me or ricotz know if you have any issues.
[23:18] <mamarley> Hopefully they won't have changed file paths or added new modules this time like they did last time...
[23:20] <soee_> mamarley: ok. i'm also talking about scenario i had last day: i moved from 358 to 355 and it worked pretty good (switching profile to intel also worked). Than i did kernel update via normal xenial updates and couldn't switch to nvidia. So i tried prime-select command etc. and it switched somehow to nvidia but then system crashed when booting .. than:
[23:20] <mamarley> Hmm, that's odd...
[23:21] <soee_> i booted with older kernel version (it worked), purged 355, installed 358 and now all works on this new kernel
[23:23] <soee_> what is the log file for system booting (after plymouth - before sddm) ?
[23:37] <clivejo> wonder will KCI fail these after 4 hours
[23:37] <genii> The last one seemed to be 50 minutes instead of 4 hours
[23:38] <clivejo> there are a lot in the queue 3 hours 50mins old
[23:39] <clivejo> 13 of them
[23:39] <clivejo> I think there is something wrong
[23:40] <clivejo> last build of cantor took 20 mins
[23:45] <clivejo> 3 minutes and counting ....
[23:47] <soee_> :)
[23:51] <mamarley> soee_: Sorry, this is taking longer because Nvidia went and changed file paths/symlinks again.  As I sure you all are aware, packaging is Fun®. :)
[23:51] <clivejo> weird - stderr: ssh: connect to host git.debian.org port 22: No route to host
[23:51] <soee_> sure thing :)
[23:52] <clivejo> sitter: whats wrong with KCI?
[23:55] <clivejo> yofel: I need help. Ive done something to knavalbattle and I cant see whats wrong - https://launchpad.net/~kubuntu-ppa/+archive/ubuntu/staging-kdeapplications/+build/8805754/+files/buildlog_ubuntu-xenial-amd64.knavalbattle_4%3A15.12.0-0ubuntu1~ubuntu16.04~ppa3_BUILDING.txt.gz