[05:41] is it ok to remove this package : [05:41] The following packages were automatically installed and are no longer required: [05:41] discover discover-data libdiscover2 libkwineffects7 libkwinxrenderutils7 [05:41] Use 'sudo apt autoremove' to remove them. [05:41] The following packages will be REMOVED: [05:41] kactivities libkf5screen6 libkwinglutils7 [05:49] Yes [06:10] good morning [08:36] hi ho, any way to get kmail2 >= 5.2? [11:07] vip: kmail in apps 16.04.1 is 5.2.1 [11:08] to back port it, it will need libical2 [11:10] and thats only available to Yakkety Yak via prposed at the minute - https://launchpad.net/ubuntu/+source/libical [11:14] clivejo: 16.04.1? .? [11:14] .1? [11:15] http://download.kde.org/stable/applications/16.04.1/src/ [11:15] Im running it on Yakkety at the moment [11:15] oh, I've understand as a kubuntu 16.04.1 [11:16] few "issues" with it! [11:17] The red ones are problem packages - http://qa.kubuntu.co.uk/ppa-status/applications/build_status_16.04.1_yakkety.html [11:18] plus KDE PIM needs version 2 of libical to build [11:18] and run too I think === chs is now known as chris17 === chris17 is now known as chs [11:46] Hey folks [11:48] howdy BluesKaj [11:49] Hey clivejo, how goes it today [11:49] ? [11:52] not too bad [11:53] trying to keep the pup out of badness [12:01] valorie: that was fast: http://www.omgubuntu.co.uk/2016/05/install-latest-plasma-desktop-kubuntu-16-04 [12:06] indeed [12:07] even took my screenshot lol [12:08] what does the note say? [12:08] Welcome to Plasma 5.6.4 - The Kubuntu Team [12:09] that Joey guy seems to keep a good eye on Kubuntu [12:09] can you add that KDE video to the news post on Kubuntu.org? [12:11] https://www.youtube.com/watch?v=v0TzoXhAbxg [12:12] nice video! :) [12:12] yea sure [12:15] done [12:16] can anyone figure out what Im doing wrong with krdc ? [12:16] http://qa.kubuntu.co.uk/ppa-status/applications/build_status_16.04.1_yakkety.html [12:16] Ive added that file to not-installed but still failing :/ [12:18] -./usr/lib/x86_64-linux-gnu/libkrdccore.so ? [12:32] holy [12:33] clivejo: he updated the article with the video already [13:00] mm Telegram bug: https://bugs.launchpad.net/ubuntu/+source/ktp-contact-list/+bug/1512135 [13:00] Launchpad bug 1512135 in ktp-contact-list (Ubuntu) "Cannot add Telegram account to Telepathy" [Medium,Confirmed] === alvesadrian is now known as adrian [18:03] anyone able to help with these last few problem apps? [18:07] 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] maybe just take a look [18:09] http://qa.kubuntu.co.uk/ppa-status/applications/build_status_16.04.1_yakkety.html [18:09] I cant see the problem for looking at it [18:09] looking there now... [18:12] searching kdesdk 64b log file for "failed". What other method/strategies should one use to find an error. [18:16] 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] 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] 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] how does our packaging relate to debian? [18:55] 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] no [18:56] KCI uses LP to build the packages [18:58] KCI is a Jenkins box which grabs the packaging (now from LP) and the source code and fires them to LP [18:59] where was packaging previously? [18:59] Debian [18:59] a machine called Alioth [19:00] 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] but not many Kubuntu people have access to that [19:01] thats build status page is just a tool for seeing proplems easier [19:02] its part of the kubuntu-automation tool kit [19:02] was the change from alioth to lp an attempt to reduce packaging issues between debian and canonical? [19:02] no [19:02] the problem was getting enough on the team to have commit access [19:03] Debian are VERY strict [19:03] ah, i see. [19:03] yes, understandable. [19:04] in theory we have better control over who can commit on LP [19:09] 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] have you changed the source? [19:11] file mentioned above says this: https://paste.kde.org/p70xk3ufc [19:12] ummm, not sure. where/how should I do that? [19:19] seems to think you changed the source by building it :/ [19:24] 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] in the rules file, can you bump the packaging tools from 2 to 3? [19:36] changed the 2 to a 3 and tried rebuiding [19:39] failed log here: https://paste.kde.org/ppvzhu1h8 [19:40] I am hacker/scripter as opposed to a real programmer so the build logs and errors are completely foreign to me. [19:42] seems this has been a problem for a while https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=799525 [19:42] Debian bug 799525 in src:kdesdk-kioslaves "kdesdk-kioslaves: FTBFS: error: invalid use of incomplete type 'const svn_sort__item_t {aka const struct svn_sort__item_t}'" [Serious,Open] [19:42] !info kdesdk-kioslaves xenial [19:43] Package kdesdk-kioslaves does not exist in xenial [19:43] we must have just ignored it in the past [19:43] https://launchpad.net/ubuntu/+source/kdesdk-kioslaves [19:44] last in Wily [19:45] and no recent changes upstream - https://quickgit.kde.org/?p=kdesdk-kioslaves.git [19:46] * clivejo sweeps it under the carpet [19:46] How do you find all these links so freakin fast? [19:47] well https://quickgit.kde.org is where all the KDE upstream code lives [19:47] control file should point to the project page and packaging [19:47] * DarinMiller bookmarking.... [19:47] yup [19:48] I bookmark a lot of stuff too [19:48] Kubuntu packaging lives here - https://code.launchpad.net/~kubuntu-packagers/+git [19:49] it really needs a search feature! [19:49] but if you setup your working environment you can get it to use shortcodes [19:50] ie git clone lp:kdesdk-kioslaves [19:50] Yes! search feature should be mandatory for all current web projects! [19:51] once you know the upstream source name, it should match [19:52] is that replaces apt-get source kdesdk-kioslaves [19:52] no [19:52] they are different [19:53] apt-get will only be able to get the packages that are in the archive [19:53] I did not use the git method when I dl'd the source. I used apt-get. [19:53] a lot of the time we are using new sources [19:54] Back to my "wrong tree" comment. I was not even in the correct forest. [19:54] apt-get source kdesdk-kioslaves will be grabbing whats in the archive [19:55] that status page is for apps 16.04.1 [19:55] the source code tarballs are located here - http://download.kde.org/stable/applications/16.04.1/src/ [19:58] 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] how does git clone lp:kdesdk-kioslaves know to pull from 16.04.1? Config file somewhere? [19:59] the changelog [19:59] you need to checkout kubuntu_yakkety_archive [20:00] https://git.launchpad.net/~kubuntu-packagers/kubuntu-packaging/+git/kdesdk-kioslaves/tree/debian/changelog?h=kubuntu_yakkety_archive [20:01] changelog tells us that the version we are working on is kdesdk-kioslaves (4:16.04.1-0ubuntu1) [20:03] the script look in the watch file [20:03] https://git.launchpad.net/~kubuntu-packagers/kubuntu-packaging/+git/kdesdk-kioslaves/tree/debian/watch?h=kubuntu_yakkety_archive [20:04] and tries to download the version we have told it should exist [20:09] we can do that manually ourselves by "uscan --download-current-version --destdir=../" [20:49] mm clivejo Telepathy works with Google now [21:01] Huh? [21:02] I logged in [21:02] With my google account [21:13] 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] Javabean: there is bug 1576930 - but we're waiting for a fix from oracle essentially [21:57] bug 1576930 in mysql-5.7 (Ubuntu) "Excessive consumption RAM of mysqld daemon in Kubuntu 16.04" [High,Triaged] https://launchpad.net/bugs/1576930 [21:57] huh? [21:58] oh, yofel that wasn't me [21:59] Javabean: oooops, sorry :D [21:59] jimarvan: [22:03] ;) [22:04] thanks! :D