[00:18] <mparillo> valorie: Now that you mention it, Dropbox was not running. Not sure how long it has not been running.
[00:22] <mparillo> I just stated Dropbox from my shell script, and it looks like it has not run since sometime between 4/13 and 4/28.
[00:23] <mparillo> So nothing to do with the plasma upgrade.
[00:25] <clivejo> sgclark: fixed a few apps, but need sleep.  I don’t understand PIM or marble so I might have to leave them to someone more knowledgeable
[00:29] <sgclark> clivejo: sleep well. I will look at those tomorrow for you.
[00:29] <clivejo> thanks
[00:29] <sgclark> and of course tel, you how to fix :)
[00:29] <clivejo> there are a few oranges I can fix
[00:30] <clivejo> looks like symbols
[00:30] <sgclark> yeah there were tons of symbols updates
[00:30] <sgclark> pim I think has more split out packages tbh
[00:31] <sgclark> I am giving another attempt at fixing stable CI since we don't use namespaces it is really breaking things.
[00:38] <stepan> testing landing on xenial for a day, everything works well, thank you :)
[00:45] <soee> ;]
[04:54] <valorie> finished the YY upgrade (staging-plasma, frameworks) and then removed them, and did auto-clean & auto-remove, then the shutdown choice wouldn't work
[04:55] <valorie> not sure it's important
[04:59] <valorie> https://www.dropbox.com/s/q07h2ic8ga0ja8a/error%20upgrade%20with%20staging-plasma%20%26%20frameworks?dl=0 - one error message
[04:59] <valorie> warnings after removing the PPAs, etc.: https://www.dropbox.com/s/ttmxczgg8716mbq/warnings%20after%20removing%20staging%20%26%20cleaning?dl=0
 Good morning.
[09:30]  * clivejo yawns
 Morning clivejo
[09:30] <clivejo> o/ Rick
[10:23] <clivejo> Riddell: my membership of kubuntu-ninjas-yellow-belts expires in 7 days, do I need to get that renewed?  LP email says to contact you :P
[10:25] <Riddell> clivejo: hmm probably not, I just used that team to keep track of people I'd given training to
[10:26] <Riddell> yofel: got any use for that team or shall I kill it?
[10:26] <clivejo> we should probably keep it
[10:27] <clivejo> its like handing out coloured stars to children :P
[10:27] <clivejo> sense of achievement
[10:31] <soee> weee :)
[10:31] <soee> i have my PC + 2 screens at home now
[10:32] <soee> tomorrow SSD + Kubutnu 16.04 on it
[10:41] <clivejo> sgclark: any idea why krdc is missing from apps PPA?
[10:52]  * clivejo sees why, cant apply the patch!
[11:11] <yofel> Riddell: I agree with clive that we should keep it, even if I'm not really using it either right now
[11:12] <yofel> Riddell: btw. could you make a snapshot of weegie sometime in the near future so we can attempt to upgrade that thing onto a non-EOL release?
[11:14] <Riddell> yofel: voila, I made kubuntu-council owner of team
[11:14] <yofel> thanks!
[11:14] <Riddell> yofel: yes making it get set up with chef and moving to a new release is on my todo
[11:14] <yofel> ok thanks
 Re Yellow belts
 I have the Dojo starting next week
 Would Yellow Belts be useful for that ?
[11:17] <soee> who had this problem with windows going underpanel ?
[11:17] <ahoneybun> mparillo I think soee
[11:18] <soee> mparillo: ping
[11:29] <BluesKaj> Hey folks
[11:29] <acheron88> I could replicate that panel bug in VBox
[11:36] <yofel> @Sick_Rimmit: Well, it's currently just a badge-collection team with not practical purpose. If you can think of one feel free to suggest it
 I think it could be very useful for that very purpose
[11:37] <clivejo> yofel: give people a sense of achievement
[11:37] <yofel> well yes, that's why I said badge-collecting and why I said to keep the team :P
 Really I am picking up on the work done by Riddell: and Sitter: the Dojo is based on their original Wiki posting
[11:37] <yofel> well, KC is owner now, so any KC member can add people
[11:37] <clivejo> ie the first step at becoming a might ninja
[11:37] <clivejo> mighty
 It would be good if I had some access to add LP users,
 Part of Dojo is getting em setup on LP, and I could put them into Yellow belts
 We can sort the details later, just hang on to it 😃
[11:38] <Riddell> yofel: it's not just badge collecting, it was to help my memory on who had started package training too
[11:39] <yofel> ah, well, that too
[11:39] <yofel> @Sick_Rimmit: now you can
[11:39] <clivejo> Riddell: do you have a link to that KDE components chart, ie how all the packages fit together?
 Awesome !! Cool I will take a look later
[11:40] <clivejo> whats the min level for LP git access?
[11:40] <yofel> ninjas
[11:40] <yofel> or member
[11:40] <clivejo> is there a way to allow for limited access?
[11:41] <ahoneybun> LP tells me I can dput to the ppas
[11:41] <clivejo> ie the yellow belts could do an actual commit, but it would have to be reviewed before going in?
[11:41] <Riddell> clivejo: only ones I know are at https://gitlab.com/siduction-tools/pkg-kde-graphs/tree/master
[11:41] <yofel> no. But we could use the team for forked repositories that the students would be able to commit to (as a team), and then file merge requests against the real ones
[11:42] <yofel> which is essenitally what you just said just worded in LP terminology
[11:42] <clivejo> I think KCI is great tool for learning
[11:42] <clivejo> ie fixing minor packaging issues
[11:42] <clivejo> and you get to see the results pretty soon
[11:42] <yofel> I would still prefer a manual review *somewhere*
[11:43] <yofel> if we make a cronjob that would auto-merge into kubuntu_unstable (would be possible), then we would need to change staging-upload to include a manual review of each merge
[11:44] <yofel> or we make the script add some kind of needs-review marker, that makes the package appear read on the QA page
[11:44] <yofel> until someone reviewed the merge and removed the marker
[11:44] <yofel> that would take the load off of the intial uploader
[11:45] <yofel> *appear red
[11:45] <ahoneybun> I still think the CI bot should have it's own channel
[11:45] <clivejo> ahoneybun: it does
[11:45] <clivejo> #kubuntu-ci
[11:46] <yofel> problem was that nobody payed attention to it there
[11:46] <ahoneybun> but it does not put it's output there
[11:46] <yofel> sure it does
[11:46] <clivejo> it does
[11:46] <clivejo> but its gets more attention here :)
[11:46] <ahoneybun> kinda bad to have all the red here
[11:47] <clivejo> why?
[11:47] <clivejo> we want to know about the red
[11:47] <ahoneybun> people might be thrown off
[11:47] <ahoneybun> by the red
[11:47] <yofel> well that's kind of the point. Show it here so that people feel like they need to fix it
[11:47] <yofel> uhm, this is a CI, that's how a CI works...
[11:48] <clivejo> if Im not doing much, or notice a package in the red that I know about, it reminds me to go fix it
[11:48] <clivejo> can take a few days to see the results
[11:48] <clivejo> cause KCI seems to be constantly busy
[11:50] <clivejo> soee_: you need to become a yellow belt
[11:51] <clivejo> and acheron88 and I few others who my brain wont remember right now
[11:51]  * clivejo needs help with PIM
[11:52] <ahoneybun> I have no idea about that
[12:05] <clivejo> yofel: would you give me a quick how-to regarding copying a git repo from Debian to LP?
[12:06] <shadeslayer> Git clone --mirror
[12:06] <shadeslayer> Git push --mirror
[12:06] <BluesKaj> well, got the 4.6 kernel and plasma 5.6.4 installed and all is well so far on both Xenial and Yakkety
[12:06] <shadeslayer> clivejo: I heard you need packages sponsored ?
[12:06] <yofel> that, + edit the remote in between
[12:06] <acheron88> clivejo: yellow belt? this? http://kubuntu.org/news/kubuntu-dojo-ninja-developer-training/
[12:06] <clivejo> rm origin and set it up to LP?
[12:07] <clivejo> yes, its like the first step
[12:07] <clivejo> and you get a little team icon on your LP page :)
[12:07] <clivejo> https://launchpad.net/~kubuntu-ninjas-yellow-belts
[12:08] <clivejo> I expire soon
[12:09] <clivejo> shadeslayer: yes, Scarlett put a shout out on the ML
[12:09] <shadeslayer> Link to tars plz
[12:12] <acheron88> clivejo: ah. would need to set up another LP ID for that if I did.
[12:13] <clivejo> shadeslayer: Im not sure how that all works
[12:13] <clivejo> sgclark can upload existing packages, but new ones need sponsorship
[12:13] <shadeslayer> And I'm asking for a link to what needs uploading :P
[12:14] <clivejo> so I dont know if they are in some pending queue somehwere
[12:14] <shadeslayer> I doubt it
[12:14] <shadeslayer> You need to be MOTU to upload to approval queue last I checked
[12:14] <clivejo> and I dont know how it works with our workflow
[12:15] <yofel> clivejo: you clone git, checkout the tag she crated, build a package, upload that to people.ubuntu.com or wherever so that he can dget it
[12:15] <shadeslayer> Uhm OK, will wait for sgclark then
[12:16] <clivejo> there are four packages need sponsorship - plasma-integration, kactivitymanagerd, breeze-plymouth, breeze-grub
[12:16] <acheron88> clivejo: is LP done under Ubuntu One account still?
[12:16] <clivejo> acheron88: I believe so
[12:16] <clivejo> hence why I was stuck with my aol email address
[12:17] <shadeslayer> clivejo: yeah but I have no clue where they are packaged xD
[12:17] <shadeslayer> Or how to get them :P
[12:17] <shadeslayer> So if you give me dsc's that's the best
[12:17] <acheron88> clivejo: have one, but under a random name, so would probably need to set up a fresh one.
[12:18] <clivejo> acheron88: maybe best to get a fresh one
[12:18] <yofel> you can change the ID as long as you don't have any PPA's IIRC
[12:18] <clivejo> acheron88: Rick should be explaining all that in the Dojo session
[12:19]  * clivejo cant even remember doing it
[12:20] <acheron88> a fresh one sounds better all round in long run, but I'll have a look
[12:20] <clivejo> yofel: when Scarlett run the upload script doesnt it mod git and do what it needs to do?
[12:23] <yofel> clivejo: that's why I said check out the tags that the script created
[12:23] <yofel> then you'll get the same packages she generated
[12:23] <yofel> (that's what the tag is for...)
[12:24] <clivejo> I have to go for a bit, but I need to learn this, never done it before
[13:34] <marco-parillo> soee_: Were you asking about https://bugs.kde.org/show_bug.cgi?id=362105
[14:54] <yofel> ovidiuflorin: could you maybe wire the telegram<>trello integration to the dev channel? I don't think it makes much sense to keep it in offtopic
[14:54] <yofel> (probably just got forgotten?)
[15:04] <clivejo> yofel: Theres a new package called kdepim-apps-libs available from download.kde.org, but it builds package called kf5-kdepim-apps-libs
[15:04] <clivejo> how do I tell KA about it
 Yofel, I tried
 I shall try again
[15:09] <yofel> clivejo: is that a renamed source or just the binary name?
[15:10] <clivejo> seems to be just binary
[15:10] <clivejo> the end package
 @integram info
 It's dead here
[15:12] <yofel> clivejo: then just add the source name to the application list (the list update script should've already done that?!?)
[15:13] <clivejo> yofel: I dont know, Im working on apps
[15:13] <clivejo> I assumed Scarlett would do that?
[15:13] <yofel> did she upload apps?
[15:14] <clivejo> not ready yet
[15:14] <clivejo> in staging
[15:14] <yofel> yes, I meant to staging
[15:14] <clivejo> http://qa.kubuntu.co.uk/ppa-status/applications/build_status_16.04.1_yakkety.html
[15:14] <clivejo> Im been trying to fix that I can
[15:15] <clivejo> what
[15:15] <yofel> ok, so I don't understand what your original question was about?
[15:16] <clivejo> kdepim has been divided out into new packages
[15:16] <yofel> yes
[15:16] <clivejo> Im copying those from debian git to LP
[15:16] <yofel> okay?
[15:16] <clivejo> and want to monitor build issues on qa
[15:17] <yofel> right
[15:17] <clivejo> but they need added to the package lists
[15:17] <yofel> ok, but this should've been done before staging-upload was run
[15:17] <yofel> so you know what packages are new
[15:17] <yofel> and to update the list
[15:17] <clivejo> I know, but obviously wasnt
[15:18] <yofel> ok, then run the list updater now
[15:18] <clivejo> but this package kdepim-apps-libs available from download.kde.org, will be built and monitored on the build page as kf5-kdepim-apps-libs
[15:20] <clivejo> so run ./package-name-list -d yakkety -r applications -v 16.04.1?
[15:23] <yofel> probably, readme should say how
[15:25] <clivejo> but how do I point kdepim-apps-libs ==> kf5-kdepim-apps-libs so the build page can see it?
[15:28] <yofel> the build page cares about source names?
[15:28] <clivejo> I thought it did
[15:29] <clivejo> thats waht we had to map discover to plasma-discover?
[15:29] <yofel> yes
[15:30]  * clivejo is confused
[15:32] <yofel> well what's the source name? and what's the upstream tarball name?
[15:32] <yofel> (I did not look at the ppa)
[15:33] <clivejo> the upstream tarball is kdepim-apps-libs
[15:34] <clivejo> amd64 build of kf5-kdepim-apps-libs 4:16.04.1-0ubuntu1~ubuntu16.10~ppa1
[15:34] <clivejo> how the hell has it an epoch
[15:34] <clivejo> FFS
[15:37] <clivejo> why?!?
[15:37] <clivejo> http://anonscm.debian.org/cgit/pkg-kde/applications/kdepim-apps-libs.git/tree/debian/changelog
[15:38] <clivejo> my head hurts too much, need a break
[16:38] <soee_> yofel: where are we with backports ?
[16:38] <yofel> Done from a technical POV I believe, now it depends on what people say about how well it runs
[16:39] <soee_> all testers say its fine :)
[16:40] <soee_> i would say .. release the kraken
[16:49] <darwin_> test
[16:49] <darwin_> plasma 5.6.4 coming out?????????????
[16:50] <soee_> hiho darwin_
[16:50] <soee_> darwin_: soon
[16:51] <darwin_> cool
[16:52] <darwin_> thx
[17:43] <clivejo> !info kf5-kdepim-apps-libs
[17:43] <soee_> Scarlett said this pim is pretty hard :/
[17:46] <clivejo> !info libkf5kaddressbookgrantlee5
[18:07] <sgclark> clivejo: sorry internet was down. looks like PIM needs a new package for libgravatar
[18:07] <clivejo> hi sgclark
[18:07] <clivejo> need to update you on what Ive done
[18:07] <clivejo> so I run the package updater script
[18:08] <clivejo> and there are lot of new packages by the looks of it
[18:08] <clivejo> Ive been mirror cloning from debian and bringing them over to LP
[18:09] <clivejo> but Ive run into a few problems
[18:09] <clivejo> http://qa.kubuntu.co.uk/ppa-status/applications/build_status_16.04.1_yakkety.html
[18:10] <clivejo> very end of that page are the "missing" packages
[18:10] <clivejo> however some of them arent missing, just got different names
[18:11] <clivejo> for example kdepim-apps-libs ==> kf5-kdepim-apps-libs
[18:11] <sgclark> mirror cloning?
[18:12] <clivejo> baloo-widgets ==> baloo-widgets5 etc
[18:12] <clivejo> do you know how to fix that mapping in KA?
[18:12] <clivejo> git clone --mirror
[18:12] <sgclark> what did you do, why are so many apps missing now?
[18:13] <clivejo> run the package-name-list script
[18:14] <clivejo> it grabs all the tarball package names and compares them
[18:14] <sgclark> on your own, I do not know what that is sorry
[18:14] <clivejo> its part of the KA scripts
[18:15] <clivejo> we supposed to run that before staging
[18:15] <clivejo> so we can see removed or new packages
[18:16] <sgclark> well that has never been told to me.
[18:17] <sgclark> In short I cannot help you with itl.
[18:17] <sgclark> all the apps were there and now they gone missing
[18:17] <clivejo> dont think its mattered much in the past, it only cause there has so much code moved about to new packages
[18:18] <clivejo> gone missing?
[18:18] <sgclark> oh all those are new?
[18:19] <clivejo> well kinda
[18:19] <clivejo> some are actually in the PPA
[18:19] <clivejo> but I cant figure out how to map them
[18:20] <clivejo> I also dont understand how brand new packages have epochs
[18:20] <sgclark> map them? I think they just need to be added to package list somewhere?
[18:20] <clivejo> they are in the package list
[18:20] <sgclark> dunno then
[18:20] <clivejo> but there is a way to map them
[18:21] <clivejo> for example KDE call the source tar discover, but we call it plasma-discover
[18:21] <sgclark> in folder build-status-conf those files are updated?
[18:22] <clivejo> thats to do with the status page?
[18:22] <sgclark> yes
[18:22] <sgclark> well I assume so with the build-status in the folder name
[18:23] <clivejo> Im thinking its something to do with https://git.launchpad.net/~kubuntu-packagers/+git/kubuntu-automation/tree/upstream-names.json
[18:23] <sgclark> my guess with the epochs is the package was copied from another package that had an epoch
[18:24] <sgclark> sorry in several conversations, what to do with what??
[18:24] <clivejo> cause thats where the discover thing is mapped
[18:24] <clivejo> "plasma-discover": "discover",
[18:25] <clivejo> Im thinking if I added
[18:25] <clivejo> "kf5-kdepim-apps-libs":"kdepim-apps-libs" to that file it might work?
[18:25] <sgclark> sounds reasonable
[18:25] <sgclark> try it :)
[18:26] <clivejo> I dont wanna break it!
 I'm having an issue with apt-get build-dep
 sudo apt-get build-dep qtbase5-dev
 Reading package lists... Done
 Picking 'qtbase-opensource-src' as source package instead of 'qtbase5-dev'
[18:26] <sgclark> well it is already broken, can't get worse haha
 E: Unable to find a source package for qtbase5-dev
 on xenial
 with apt search I can find the package qtbase5-dev
[18:26] <clivejo> !info qtbase5-dev
[18:27] <clivejo> I think its a virtual package
 sudo apt-get build-dep qtbase-opensource-src
 Reading package lists... Done
 E: Unable to find a source package for qtbase-opensource-src
 am I missing something?
[18:28] <clivejo> https://launchpad.net/ubuntu/+source/qtbase-opensource-src
 so, do I just install that?
[18:30] <clivejo> what are you looking for?
 doing this: http://kfunk.org/2016/02/16/building-kdevelop-5-from-source-on-ubuntu-15-10/
[18:31] <clivejo> I think qtbase5-dev is a virtual package that installs all of the base dev packages
[18:32] <sgclark> apt-get -y build-dep qtbase5-dev is what I use in my dockerfile for kde-ci
[18:32] <sgclark> but it is still wily, maybe something changed? let me try in my chroot
 I'm on xenial
[18:33] <sgclark> worked fine for me in xenial chroot
[18:34] <sgclark> ovidiuflorin: you know you can build kdevelop from source using kdebuild-src right?
[18:35] <sgclark> oh that is whaht it is doing nm
 that does not bring in all dependencies
[18:40] <sgclark> right
[18:40] <sgclark> sorry I don't know. wfm
 I might me missing some ppas
[18:41] <sgclark> maybe missing something in sources
[18:41] <acheron88> 'apt-get build-dep qtbase5-dev' work here on xenial as well
[18:41] <sgclark> no no ppas in my chroot
 https://paste.kde.org/ptwe8t6ln
[18:45] <clivejo> eakk "libkf5.*-dev"
[18:45] <clivejo> just install whats listed in the build dep list for the main package
 fixed it
 source code wasn't checked in software manager
[18:55] <clivejo> yofel: ping
 just install whats listed in the build dep list for the main package
[19:23] <kfunk> there's no kdevelop 5 package yet
[19:23] <kfunk> easy
[19:23] <clivejo> kfunk: was ovidiuflorin was asking
[19:24] <clivejo> he didnt have sources enabled
 kfunk add clang to the list of dependencies
[20:01] <sgclark> and I recall it was a specific clang before I could get it to work
[20:01] <sgclark> don't recall which though :(
[20:13] <clivejo> well I added two to the upstream-names.json file and they wont appear on the build status page
[20:40] <clivejo> does anyone here understand kubuntu-automatic?
[20:40] <clivejo> automation
[20:43] <shadeslayer> clivejo: ssup
[20:43] <shadeslayer> I haven't looked at it in a while
[20:43] <clivejo> hi shadeslayer
[20:43] <shadeslayer> but I might be able to help
[20:44] <clivejo> Ive added a few new packages but the upstream (KDE) name and package names are different
[20:45] <clivejo> for example KDE tarball is discover which maps to plasma-discover
[20:46] <clivejo> I have KDE tar called kdepim-apps-libs which maps to kf5-kdepim-apps-libs
[20:46] <shadeslayer> uh huh? and?
[20:46] <clivejo> I need it to appear here http://qa.kubuntu.co.uk/ppa-status/applications/build_status_16.04.1_yakkety.html
[20:46] <shadeslayer> where's the code for this?
[20:47] <clivejo> https://git.launchpad.net/~kubuntu-packagers/+git/kubuntu-automation/
[20:47] <shadeslayer> might make sense to normalize the names btw
[20:47] <clivejo> used to be in bzr
[20:47] <shadeslayer> right
[20:48] <shadeslayer> https://git.launchpad.net/~kubuntu-packagers/+git/kubuntu-automation/tree/upstream-names.json
[20:48] <clivejo> yes, I added the bottom two
[20:48] <clivejo> but still wont work
[20:49] <clivejo> baloo-widgets5 is here https://launchpad.net/~kubuntu-ppa/+archive/ubuntu/staging-kdeapplications/+build/9768185
[20:49] <clivejo> but the page wont pick it up
[20:49] <shadeslayer> https://launchpad.net/~kubuntu-ppa/+archive/ubuntu/staging-kdeapplications/+packages?field.name_filter=kdepim-apps-libs&field.status_filter=published&field.series_filter=yakkety
[20:49] <shadeslayer> there is no https://launchpad.net/~kubuntu-ppa/+archive/ubuntu/staging-kdeapplications/+packages?field.name_filter=kdepim-apps-libs&field.status_filter=published&field.series_filter=yakkety
[20:49] <shadeslayer> er
[20:49] <shadeslayer> there is no kdepim-apps-libs
[20:50] <clivejo> upstream call it that
[20:50] <shadeslayer> then why is it looking for that
[20:50] <clivejo> http://download.kde.org/stable/applications/16.04.1/src/kdepim-apps-libs-16.04.1.tar.xz
[20:50] <shadeslayer> (see end of the qa link )
[20:50] <clivejo> and git is same name
[20:51] <clivejo> but the source package is called kf5-kdepim-apps-libs
[20:52] <clivejo> there is some way to map it
[20:52] <clivejo> for example KDE source is called discover
[20:52] <clivejo> but source-package is plasma-discover
[20:52] <clivejo> and I thought upstream-names.json was the file that did the mapping
[20:53] <shadeslayer> when in doubt grep is your friend
[20:53] <clivejo> hes not being very friendly
[20:54] <shadeslayer> package-name-lists/applications-yakkety
[20:54] <shadeslayer> looks important
[20:54] <clivejo> it is
[20:55] <shadeslayer> ok, give me a moment to read how this works
[20:55] <clivejo> it holds the list of all the app packages in yakkety
[20:55] <clivejo> actually, I think Ive just found something
[20:55] <shadeslayer> hm?
[20:55] <clivejo> in package-name-list
[20:56] <clivejo> packagesRenamedFromUpstram =
[20:56] <shadeslayer> ah indeed
[20:56] <shadeslayer> why isn't that json parsed from that list
[20:56] <clivejo> that looks like a more logical mapping
[20:56] <shadeslayer> why are there 2 lists :P
[20:56] <shadeslayer> there's also a type
[20:56] <shadeslayer> *typo
[20:56] <clivejo> shadeslayer: your guess is as good as mine!
[20:57] <shadeslayer> to the blame machine!
[20:57] <shadeslayer> 45c86cb5 (Jonathan Riddell 2015-06-29 13:29:58 +0200  13) packagesRenamedFromUpstram = {"kwallet": "kwallet-kf5",
[20:57] <shadeslayer> *backs away slowly*
[20:57] <clivejo> its Scottish!
[20:57] <clivejo> Stream translates to Stram
[20:58] <shadeslayer> :P
[20:58] <shadeslayer> not only is the script in python, var names are in Scottish :D
[21:00] <clivejo> indeed
[21:00] <clivejo> great fun this packaging lark
[21:01] <clivejo> right, lets see if that works!
[21:02] <clivejo> I cant seem to get the logical in these scripts
[21:02] <clivejo> and when it says upstream is the debian or KDE
[21:03] <clivejo> well debian is now LP
[21:03] <clivejo> now have to wait for the cron job on weegie
[21:04] <clivejo> more scotish slag!
[21:04] <clivejo> slang
[21:07] <clivejo> soee: hows the testing going?
[21:07] <soee> clivejo: testing what?
[21:07] <clivejo> plasma 5.6.4
[21:07] <soee> clivejo: it is tested pretty solid. all fine
[21:08] <soee> imo. we could push it to backports
[21:08] <clivejo> how many testers are using it?
[21:08] <soee> ~8
[21:08] <soee> some on severl machines
[21:08] <soee> i have it on 2 also (laptop and PC)
[21:08] <clivejo> any install issues?
[21:08] <soee> nope
[21:09] <soee> i did today upgrade on my PC from 5.5.5
[21:09] <clivejo> and can you see everything in Polish?
[21:09] <soee> ;D
[21:10] <clivejo> are you actually in Poland?
[21:10] <soee> yes
[21:10] <clivejo> interesting
[21:11] <soee> is it safe to install kernel 4.5 in Xenial?
[21:11] <clivejo> no idea
[21:11]  * clivejo is on Yakkety
[21:13] <acheron88> 4.5 from where?
[21:14] <acheron88> 24hrs on plasma 5.6.4, and not crashed it yet :)
[21:17]  * clivejo high-fives shadeslayer
[21:17] <shadeslayer> ^5
[21:18] <clivejo> they are appearing http://qa.kubuntu.co.uk/ppa-status/applications/build_status_16.04.1_yakkety.html
[21:18] <soee> gosh ... ** (appstreamcli:15884): WARNING **: Exception: Unable to get write lock on /var/cache/app-info/xapian/default: already locked
[21:18] <shadeslayer> clivejo: would recommend perhaps making it so that it loads that json fole
[21:18] <clivejo> I wonder do we also have to map it back again in upstream-names
[21:19] <soee> brb reboot
[21:20] <clivejo> in maps "spectacle": "kde-spectacle" in package-name-list, then "kde-spectacle": "spectacle" in upstream-names
[21:20] <clivejo> so weird
[21:22] <shadeslayer> clivejo: clearly key/values are switched
[21:22] <shadeslayer> so it needs changing in the code logic too
[21:22] <shadeslayer> to make it all consistent
[21:22] <clivejo> so I need both?
[21:25] <clivejo> oh I can kinda see the logic now
[21:26] <clivejo> that script is querying depot
[21:26] <clivejo> for all the packages listed in application 16.04.1
[21:27] <clivejo> so when it finds spectacle, thats mapped to our package name kde-spectacle
[21:27] <clivejo> and the upstream-names.json file maps it back again!
[21:38] <shadeslayer> ok, I'm off for the day
[21:38] <shadeslayer> sgclark: clivejo if you email me a link with the tars to upload, I can sponsor them
[22:36]  * clivejo yawns
[22:37] <clivejo> this is soee bored!
[22:37] <soee_> :<
[22:37] <soee_> Kubuntu does not like me
[22:37] <clivejo> boring even
[22:37] <clivejo> why you think that?
[22:37] <soee_> i can update packages list
[22:37] <soee_> if freezes and doing nothing :<
[22:38] <clivejo> xenial?
[22:39] <soee_> yes
[22:39] <clivejo> come help me package apps :)
[22:39] <clivejo> then it will love you
[22:39] <soee_> and again ** (appstreamcli:10695): WARNING **: Exception: Unable to get write lock on /var/cache/app-info/xapian/default: already locked
[22:39] <soee_> fuuu xapian
[22:40] <clivejo> never seen that before
[22:40] <soee_> clivejo: the only one who knows it enough is yofel or sgclark (the apps package stuff) :(
[22:41] <clivejo> soee_: you can learn how to do some of the more routine stuff
[22:41] <clivejo> takes the pressure off them to deal with other stuff
[22:42] <clivejo> soee_: you coming to the party tomorrow
[22:43] <genii> soee_: Does lsof show whats using it?
[22:45] <soee_> i killed whole /var/cache content
[22:45] <soee_> is tarted to work now
[22:54] <clivejo> sgclark: ping
[22:58] <sgclark> clivejo: whats up?
[22:58] <clivejo> did you see shadeslayer offer to sponsor those new packages?
[22:58]  * sgclark scrolls
[22:58] <sgclark> ah ok
[22:59] <clivejo> are you ok with me tottering away at these apps?
[23:00] <ahoneybun> btw soee autohide and cover work in 5.6.4 with intel
[23:00] <sgclark> please do. I have no time
[23:00] <ahoneybun> have not tried nvidia yet
[23:01] <ahoneybun> can
[23:01] <clivejo> if you ever got a chance, would you add the new packages into KCI?
[23:01] <soee> im on new 367  driver
[23:01] <ahoneybun> can't reboot atm trying to work on my app in QML
[23:01] <ahoneybun> mm
[23:01] <ahoneybun> apt update is stopping
[23:01] <ahoneybun> never finishing
[23:01] <sgclark> ScottK: you around?
[23:01] <ahoneybun> even apt-get
[23:01] <genii> Looks like some appstream issue, they are discussing it in #ubuntu right npw
[23:02] <soee> yea on #kubuntu user already reported it
[23:02] <ahoneybun> oh the apt issue?
[23:02] <genii> Yep
[23:02] <sgclark> clivejo: can you email me a list of what needs to be added I am sgclark at kubuntu
[23:03] <ScottK> sgclark: Sort of.
[23:03] <ahoneybun> in an LTS thats
[23:03] <ahoneybun> that's bad
[23:03] <sgclark> ah the apps are in https://launchpad.net/~kubuntu-ppa/+archive/ubuntu/staging-plasma would that work?
[23:03] <sgclark> ScottK: ^
[23:03] <ahoneybun> no staging-apps?
[23:04] <ScottK> sgclark: Which packages and you've reviewed them?
[23:04] <sgclark> they have been in testing and no I have not personally reviewed them
[23:04] <sgclark> I am going into  retirement
[23:04] <ScottK> OK.
[23:05] <ScottK> I'll upload them if some Kubuntu dev says they are OK but I don't have time to review them.
[23:05] <sgclark> ok shadeslayer said he would. thank though for the offer :)
[23:06] <ScottK> OK.
[23:29] <acheron88> Have an error in 5.6.4 when clicking on an recent document/item in kicker/kickoff recent docs/history
 Some upstream bug?
[23:31] <acheron88> "Could not find any application or handler" for the document path, plasma error message popup
[23:31] <acheron88> in VM and real machine
[23:32] <acheron88> marcinsago: could not find bugs.kde
[23:32] <acheron88> just going to check in another distro VM for 5.6.4
[23:34] <acheron88> OK. bug not present in chakra plasma 5.6.4 VM
[23:38] <acheron88> reproducible in a yakkety VM with plasma 5.6.4 as well
[23:41] <clivejo> acheron88: same here
[23:41] <clivejo> any ideas what might be wrong?
[23:41]  * soee has to uninstall mainline kernel
[23:42] <acheron88> actually I fibbed about chakra. it's on 5.6.3. I'll see if I can update that to double check against their 5.6.4
[23:43] <sgclark> I can confirm acheron88. Can you create a bug? and link it so I can confirm
[23:44] <acheron88> error is generated by this I think? http://api.kde.org/frameworks-api/frameworks5-apidocs/kio/html/krun_8cpp_source.html
[23:44] <acheron88> sgclarke: can someone else? Not got around to making new LP ID yet
[23:45] <sgclark> I see. I do not have time I am afraid.
[23:47] <acheron88> at moment trying to work out if it's kde bug, or a packaging one, anyway
[23:49] <soee> for those that use chromium/vivaldi + intel gpu: there is some  bug that makes screen blinking/flickering. As a workaround add to chromium/browser startup command: --disable-gpu-driver-bug-workarounds --enable-native-gpu-memory-buffers
[23:49] <clivejo> acheron88: on chakra what frameworks are installed?
[23:50] <clivejo> !info kio-dev
[23:51] <clivejo> but plasma 5.6.4 was built against 5.22
[23:53] <acheron88> chakra package naming is not very familiar to me, but - http://i.imgur.com/eBPify8.png
[23:54] <clivejo> looks like a mix of 5.19 and 5.21
[23:54] <clivejo> which is odd
[23:55] <acheron88> with as I said, plasma 5.6.3. thought they had 5.6.4, but clearly not yet
[23:55] <clivejo> acheron88: would you ask in #kde-neon
[23:56] <acheron88> OK. I did have a kde-neo VM, but wiped it. annoyingly
[23:57] <clivejo> Id be interested to know if its there
[23:57] <clivejo> they are using FW5.22 and Plasma 5.6.4
[23:59] <clivejo> Neon folks are EU based so might be a while before someone answers
[23:59] <clivejo> unless a user tries it


[00:34] <nhaines> Good grief, these french fries are salty!
[00:34] <nhaines> Wienerschnitzel has $0.61 mustard, kraut, and chili dogs today.
[00:37] <DonkeyHotei> McD's fries are saltier
[00:42] <nhaines> Oh no they're not.
[00:43] <nhaines> These fries are made wrong.
[00:47] <DonkeyHotei> then they have uniqueness points


[06:12] <TripWIki> hi
[06:42] <ScottK> doko_: kde4libs still FTBFS on armhf with that latest gcc-4.8, but now it says, "The bug is not reproducible, so it is likely a hardware or OS problem.".
[06:42] <ScottK> Suggestions?
[08:15] <doko> ScottK, try again
[08:40]  * ScottK does.
[09:45]  * Noskcaj is away: I'm either at school or soccer. or i just don't like you.
[09:46] <Noskcaj> stupid xchat
[10:20] <hacktus0> how can I pubblish my apps
[10:21] <hacktus0> ?
[10:22] <mitya57> hacktus0: you probably want #ubuntu-app-devel or something like that
[10:23] <hacktus0> OK
[15:13] <nonickname2> slangasek: regarding #1187318 and #1173320 : i assume you read in my report (the latter one, comment #8) that it's (at least here and at the time i tested) depending on the plymouth theme if text is shown or not (so these might be something to look at, too)? also: yes, i was using/installed from i386 .isos - obviously don't know about the commenting people though ...
[22:10] <infinity> Oh joy, now bamfdaemon crashes and takes out my desktop.  So many exciting ways to kill my workflow.
[23:15] <optimisme> hi, do you know wich signal is emited when a menu_item is shown in gtk/indicatorwidget ? i want to pisition the "popup window" properly after the submenu is shown but it moves back to its original position using "show" or "focus" signals ... or prevent its repositioning to defaults overwitting a method, i can position it properly when allocating
[23:25] <optimisme> nevermind, I found a workarround, thanks