[05:41] <ejat> is it ok to remove this package : 
[05:41] <ejat> The following packages were automatically installed and are no longer required:
[05:41] <ejat>   discover discover-data libdiscover2 libkwineffects7 libkwinxrenderutils7
[05:41] <ejat> Use 'sudo apt autoremove' to remove them.
[05:41] <ejat> The following packages will be REMOVED:
[05:41] <ejat>   kactivities libkf5screen6 libkwinglutils7
 Yes
[06:10] <soee> good morning
[08:36] <vip> hi ho, any way to get kmail2 >= 5.2?
[11:07] <clivejo> vip: kmail in apps 16.04.1 is 5.2.1
[11:08] <clivejo> to back port it, it will need libical2
[11:10] <clivejo> and thats only available to Yakkety Yak via prposed at the minute - https://launchpad.net/ubuntu/+source/libical
[11:14] <vip> clivejo: 16.04.1? .?
[11:14] <vip> .1?
[11:15] <clivejo> http://download.kde.org/stable/applications/16.04.1/src/
[11:15] <clivejo> Im running it on Yakkety at the moment
[11:15] <vip> oh, I've understand as a kubuntu 16.04.1
[11:16] <clivejo> few "issues" with it!
[11:17] <clivejo> The red ones are problem packages - http://qa.kubuntu.co.uk/ppa-status/applications/build_status_16.04.1_yakkety.html
[11:18] <clivejo> plus KDE PIM needs version 2 of libical to build
[11:18] <clivejo> and run too I think
[11:46] <BluesKaj> Hey folks
[11:48] <clivejo> howdy BluesKaj
[11:49] <BluesKaj> Hey clivejo, how goes it today 
[11:49] <BluesKaj> ?
[11:52] <clivejo> not too bad
[11:53] <clivejo> trying to keep the pup out of badness
[12:01] <ahoneybun> valorie: that was fast: http://www.omgubuntu.co.uk/2016/05/install-latest-plasma-desktop-kubuntu-16-04
[12:06] <clivejo> indeed
[12:07] <ahoneybun> even took my screenshot lol
[12:08] <clivejo> what does the note say?
[12:08] <ahoneybun> Welcome to Plasma 5.6.4 - The Kubuntu Team
[12:09] <clivejo> that Joey guy seems to keep a good eye on Kubuntu
[12:09] <clivejo> can you add that KDE video to the news post on Kubuntu.org?
[12:11] <clivejo> https://www.youtube.com/watch?v=v0TzoXhAbxg
[12:12] <jimarvan> nice video! :)
[12:12] <ahoneybun> yea sure
[12:15] <ahoneybun> done
[12:16] <clivejo> can anyone figure out what Im doing wrong with krdc ?
[12:16] <clivejo> http://qa.kubuntu.co.uk/ppa-status/applications/build_status_16.04.1_yakkety.html
[12:16] <clivejo> Ive added that file to not-installed but still failing :/
[12:18] <ahoneybun> -./usr/lib/x86_64-linux-gnu/libkrdccore.so ?
[12:32] <ahoneybun> holy
[12:33] <ahoneybun> clivejo: he updated the article with the video already
[13:00] <ahoneybun> mm Telegram bug: https://bugs.launchpad.net/ubuntu/+source/ktp-contact-list/+bug/1512135
[18:03] <clivejo> anyone able to help with these last few problem apps?
[18:07] <DarinMiller> clivejo: I assume you want assistance from who has a clue.  I will be glad to assist, but my current level of expertise is officially "rubber ducky".
[18:09] <clivejo> maybe just take a look
[18:09] <clivejo> http://qa.kubuntu.co.uk/ppa-status/applications/build_status_16.04.1_yakkety.html
[18:09] <clivejo> I cant see the problem for looking at it
[18:09] <DarinMiller> looking there now...
[18:12] <DarinMiller> searching kdesdk 64b log file for "failed".  What other method/strategies should one use to find an error.
[18:16] <DarinMiller> how does the package builder know to use "Overriding sources.list in build-PACKAGEBUILD-9780698"?  Is that in one of the config files in the kubuntu-automation setup?
[18:22] <DarinMiller> Nevermind, I just grep'd to answer my own question (grep -r  9780698) from the top level of the kubuntu-automation folder and found nothing.  Which still begs the question, where is the alternate source.list specified.  A KCI config?
[18:49] <DarinMiller> OK, downloaded kdesdk-kioslaves source and check the debian/rules file as debian/rules build error was listed at the bottom of the log file.  I think I am barking up the wrong tree as the debian/rules file in the package contains almost nothing bu an inlcude command and 2 overrides.
[18:53] <clivejo> how does our packaging relate to debian?
[18:55] <DarinMiller> I don't understand the big picutre.  As I still do not have my head wrapped around KCI vs launchpad.  They both seem to be package build systems. Does LP replace KCI?
[18:56] <clivejo> no
[18:56] <clivejo> KCI uses LP to build the packages
[18:58] <clivejo> KCI is a Jenkins box which grabs the packaging (now from LP) and the source code and fires them to LP 
[18:59] <DarinMiller> where was packaging previously?
[18:59] <clivejo> Debian
[18:59] <clivejo> a machine called Alioth
[19:00] <clivejo> http://anonscm.debian.org/cgit/pkg-kde/
[19:00]  * DarinMiller building kdesdk-kioslaves on my YY box to see if I can produce the same error...
[19:00] <clivejo> but not many Kubuntu people have access to that
[19:01] <clivejo> thats build status page is just a tool for seeing proplems easier
[19:02] <clivejo> its part of the kubuntu-automation tool kit
[19:02] <DarinMiller> was the change from alioth to lp an attempt to reduce packaging issues between debian and canonical?
[19:02] <clivejo> no
[19:02] <clivejo> the problem was getting enough on the team to have commit access
[19:03] <clivejo> Debian are VERY strict
[19:03] <DarinMiller> ah, i see.
[19:03] <DarinMiller> yes, understandable.
[19:04] <clivejo> in theory we have better control over who can commit on LP
[19:09] <darin> OK,  kdesdk-kioslaves is literally the 3rd or 4th package I have every build manually from source.  I get a different build error than on the apt status page and my build log is much shorter.  It says dpkg-source: error: aborting due to unexpected upstream changes, see /tmp/kdesdk-kioslaves_16.04.1-0ubuntu1~ubuntu16.10~ppa1.diff.qFlXor" 
[19:11] <clivejo> have you changed the source?
[19:11] <darin> file mentioned above says this: https://paste.kde.org/p70xk3ufc
[19:12] <darin> ummm, not sure. where/how should I do that?
[19:19] <clivejo> seems to think you changed the source by building it :/
[19:24] <darin> I used a redirect and wrote the log file to the current directory.... I guess that's not recommended.... I tried again and routed the output to my home directory....
[19:31] <clivejo> in the rules file, can you bump the packaging tools from 2 to 3?
[19:36] <darin> changed the 2 to a 3 and tried rebuiding
[19:39] <darin> failed log here: https://paste.kde.org/ppvzhu1h8
[19:40] <darin> I am hacker/scripter as opposed to a real programmer so the build logs and errors are completely foreign to me.
[19:42] <clivejo> seems this has been a problem for a while https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=799525
[19:42] <clivejo> !info kdesdk-kioslaves xenial
[19:43] <clivejo> we must have just ignored it in the past
[19:43] <clivejo> https://launchpad.net/ubuntu/+source/kdesdk-kioslaves
[19:44] <clivejo> last in Wily
[19:45] <clivejo> and no recent changes upstream - https://quickgit.kde.org/?p=kdesdk-kioslaves.git
[19:46]  * clivejo sweeps it under the carpet
[19:46] <DarinMiller> How do you find all these links so freakin fast?
[19:47] <clivejo> well https://quickgit.kde.org is where all the KDE upstream code lives
[19:47] <clivejo> control file should point to the project page and packaging
[19:47]  * DarinMiller bookmarking....
[19:47] <clivejo> yup
[19:48] <clivejo> I bookmark a lot of stuff too
[19:48] <clivejo> Kubuntu packaging lives here - https://code.launchpad.net/~kubuntu-packagers/+git
[19:49] <clivejo> it really needs a search feature!
[19:49] <clivejo> but if you setup your working environment you can get it to use shortcodes
[19:50] <clivejo> ie git clone lp:kdesdk-kioslaves
[19:50] <DarinMiller> Yes! search feature should be mandatory for all current web projects!
[19:51] <clivejo> once you know the upstream source name, it should match
[19:52] <DarinMiller> is that replaces apt-get source kdesdk-kioslaves
[19:52] <clivejo> no
[19:52] <clivejo> they are different
[19:53] <clivejo> apt-get will only be able to get the packages that are in the archive
[19:53] <DarinMiller> I did not use the git method when I dl'd the source.  I used apt-get.  
[19:53] <clivejo> a lot of the time we are using new sources
[19:54] <DarinMiller> Back to my "wrong tree" comment.  I was not even in the correct forest.
[19:54] <clivejo> apt-get source kdesdk-kioslaves will be grabbing whats in the archive
[19:55] <clivejo> that status page is for apps 16.04.1
[19:55] <clivejo> the source code tarballs are located here - http://download.kde.org/stable/applications/16.04.1/src/
[19:58] <clivejo> so we use the scripts/tools in kubuntu-automation to grab the tarball and combine it with the packaging and then we upload it to the staging PPA
[19:59] <DarinMiller> how does git clone lp:kdesdk-kioslaves know to pull from 16.04.1?  Config file somewhere?
[19:59] <clivejo> the changelog
[19:59] <clivejo> you need to checkout kubuntu_yakkety_archive
[20:00] <clivejo> https://git.launchpad.net/~kubuntu-packagers/kubuntu-packaging/+git/kdesdk-kioslaves/tree/debian/changelog?h=kubuntu_yakkety_archive
[20:01] <clivejo> changelog tells us that the version we are working on is kdesdk-kioslaves (4:16.04.1-0ubuntu1)
[20:03] <clivejo> the script look in the watch file
[20:03] <clivejo> https://git.launchpad.net/~kubuntu-packagers/kubuntu-packaging/+git/kdesdk-kioslaves/tree/debian/watch?h=kubuntu_yakkety_archive
[20:04] <clivejo> and tries to download the version we have told it should exist
[20:09] <clivejo> we can do that manually ourselves by "uscan --download-current-version --destdir=../"
[20:49] <ahoneybun> mm clivejo Telepathy works with Google now
 Huh?
 I logged in
 With my google account
[21:13] <jimarvan> Is there any update about: http://askubuntu.com/questions/762062/akonadi-services-and-mysqld-use-too-much-memory-in-kubuntu-16-04? It seems i started experiencing this issue too. Is the shutting down akonadi-server the only temporary workaround?
[21:57] <yofel> Javabean: there is bug 1576930 - but we're waiting for a fix from oracle essentially
[21:57] <Javabean> huh?
[21:58] <Javabean> oh, yofel that wasn't me
[21:59] <yofel> Javabean: oooops, sorry :D
[21:59] <yofel> jimarvan: 
[22:03] <jimarvan> ;)
[22:04] <jimarvan> thanks! :D