[00:02] <clivejo> noooo
[00:03] <clivejo> KCI is gonna blame me again
[00:03] <clivejo> in one minute!
[00:05] <clivejo> valorie: are you on wily?
[00:16] <valorie> yes, wily
[00:17] <valorie> since the alpha
[00:17] <valorie> gah, I can't remember the correct invocation to upgrade to xenial
[00:18] <clivejo> could you test kvkbd in my ppa?
[00:18] <valorie> ah, got it
[00:18] <clivejo> valorie: kubuntu-devel-release-upgrade
[00:18] <valorie> sec, laundry and such
[00:24] <valorie> ok, can test on this wily box while the other one is upgrading
[00:25] <valorie> how to test?
[00:25] <clivejo> you can either add my PPA or just download and install the package
[00:26] <clivejo> 32 or 64 bit?
[00:26] <valorie> 64
[00:26] <clivejo> https://launchpad.net/~clivejo/+archive/ubuntu/wily/+build/8303071
[00:26] <valorie> this? ppa:clivejo/wily
[00:26] <clivejo> yup
[00:29] <valorie> hmmm: 
[00:29] <valorie> The following packages will be upgraded:
[00:29] <valorie>   amarok amarok-common amarok-utils kdeconnect-plasma
[00:29] <valorie> that ok?
[00:29] <valorie> why do you have a newer amarok in there?
[00:29] <clivejo> amarok, isnt mine
[00:29] <valorie> did it not get uploaded?
[00:29] <valorie> ah
[00:29] <valorie> ok
[00:30] <valorie> I was confused because the lp page didn't list that
[00:30] <clivejo> dont install those
[00:30] <valorie> but I *just* did update && full-upgrade
[00:30] <valorie> with no amarok
[00:31] <valorie> well, I can always uninstall amarok
[00:31] <valorie> I wonder if I have the beta ppa enabled or something
[00:32] <clivejo> it could be in my LP, I was playing about with it
[00:33] <clivejo> I play about with KF5 builds to see if I can get them to build
[00:34] <valorie> last time I tried building amarok, I failed
[00:35] <valorie> fortunately, the porting effort continues
[00:35] <clivejo> do you use kdeconnect?
[00:36] <valorie> yes
[00:36] <clivejo> would you test that for me too please?
[00:36] <valorie> and I basically upgraded to be able to test that on both boxes
[00:37] <clivejo> with it, make sure you are using the latest version on your phone as well
[00:39] <valorie> well, I signed up for the testing group, but unsure how to check that on my phone
[00:39] <valorie> sec
[00:56] <valorie> kdeconnect seems to be working -- this computer sees my phone and reports the battery status
[00:57] <clivejo> :)
[01:01] <valorie> on screen kbd typed this
[01:02] <valorie> but how do I get rid of it?
[01:02] <valorie> clivejo: please urge the author to get that code into kde git
[01:02] <valorie> looks a bit oxygenish, but works for me
[01:02] <clivejo> there is an icon in the system tray
[01:02] <clivejo> can change the colour
[01:02] <valorie> cool
[01:03] <clivejo> and exit it
[01:03] <valorie> now to check the upgrade to xenial
[01:03] <valorie> then dinner, I think
[01:04] <valorie> still in the setup phase
[01:04] <clivejo> bit slow?
[01:04] <valorie> it's just a lil computer
[01:04] <valorie> 65% done
[02:58] <valorie> kdeconnect is working on xenial
[03:05] <valorie> kvkbd working on xenial as well
[08:25] <stefan__> hi guys
[08:26] <stefan__> why does kubuntu-ci stable depend on qt packages which are unavailable in wily?
[08:27] <stefan__> kubuntu-ci unstable actually has newer versions of qt...
[09:25] <lordievader> Good morning.
[09:28] <stefan__> is this the right place to askabout kubuntu-ci packages?
[09:39] <valorie> stefan__: yes, but there are few devels here right now
[09:40] <valorie> if you can't stay around until they arrive, you can always ask on the kubuntu-devel mail list
[09:47] <stefan__> valorie: thanks
[09:48] <valorie> best of luck
[10:10] <soee> hiho
[11:20] <stefan__> hi guys
[11:20] <stefan__> why does kubuntu-ci stable depend on qt packages which are unavailable in wily?
[11:20] <stefan__> kubuntu-ci unstable actually has newer versions of qt...
[11:25] <yofel> because I obviously messed up and only copied them for unstable, sorry about that.
[11:25] <yofel> I'll fix that in a big
[11:25] <yofel> *bit
[11:26] <sitter> yofel: I think stable will need a size bump to accomodate qt
[11:26] <tsdgeos> tx
[11:26] <tsdgeos> wops, wrong channel :D
[11:28] <yofel> sitter: really? we have 9G left
[11:29] <sitter> unstable overshot substantially from qt
[11:29] <sitter> I am preping the wipe now though, so it might be fine
[11:29] <sitter> then again most of xenial doesn't build anyway, so it can't use that much space yet
[11:29] <yofel> right
[11:31] <sitter> anyway. purge running now
[11:38] <pursuivant> muon (master) v5.4.3-168-ge8746ea * Aleix Pol: CMakeLists.txt
[11:38] <pursuivant> Trim dependencies
[11:38] <pursuivant> Remove those from Discover and backends.
[11:38] <pursuivant> http://commits.kde.org/muon/e8746ea278754b2bf65708176f4b6560f6e58552
[11:52] <sitter> yofel: removal requested for everything. no clue when that will finish
[11:52] <sitter> yofel: shall I remove weekly entirely?
[11:54] <yofel> thanks
[11:55] <yofel> sitter: rather leave it empty for the time being. Removing it completely annoys apt
[11:55] <yofel> and plasma beautifullness: https://kyofel.de/owncloud/index.php/s/kZCGY5UB6ncaLiP
[12:01] <sitter> :/
[12:08] <ahoneybun> mm google auth works on my desktop
[12:31] <BluesKaj> Hey all
[12:42] <mrvanes> Could any of the devs tell me why I see "Failed to establish shared memory mapping, will fallback to private memory -- memory usage will increase" for any plasma application launched (from terminal)
[12:42] <mrvanes> I have /de/shm mounted (tempfs)
[12:42] <mrvanes> I have /dev/shm mounted (tempfs)
[12:45] <shadeslayer> Do we have a agenda for Munich?
[12:46] <yofel> we have CI future, otherwise not really
[12:47] <shadeslayer> yofel: well, depends on what that means
[12:47] <shadeslayer> technical details of CI or CI infrastructure?
[12:48] <shadeslayer> and what do we do about this http://dci.pangea.pub/job/plasma/view/Failing/job/step_binary_unstable/arch=amd64/61/console
[12:50] <yofel> well, both, as we'll have to set up our own CI instance eventually and nobody know how to do that
[12:50] <yofel> I also want to talk about changelog generation and file tracking
[12:50] <shadeslayer> for CI infrastructure I think sitter said someone needs to talk to starbuck1
[12:51] <shadeslayer> and work out something
[12:51] <shadeslayer> or mentioned something along those lines
[12:51] <shadeslayer> yofel: file tracking?
[12:51] <sitter> changelogs :@
[12:52] <yofel> CI verifying that we're not missing breaks/replaces
[12:52] <sitter> yofel: all jobs gone; all ppas got vivid sources wiped; weekly got wiped entirely
[12:52] <yofel> sitter: <3
[12:53] <clivejo> sitter: Do you know what the status of kvkbd is?
[12:53] <sitter> yofel: short term file movement is implicitly tracked through the promotion QA http://kci.pangea.pub/job/mgmt_daily_promotion_wily_unstable/
[12:53] <shadeslayer> hurray, libkwineffects has so version bump
[12:53] <sitter> yofel: since it hasn't passed since May that ought to tell you why we have file movement problems :P
[12:53] <sitter> clivejo: no
[12:54] <yofel> sitter: "short term" ?
[12:54] <yofel> ah, between stable/unstable ?
[12:54] <sitter> autopromotion takes the previous daily ppa (last good set of builds) and attempts to upgrade from that to what is the supposedly new set of builds (!daily ppa)
[12:55] <sitter> if apt can not upgrade daily to the new builds the job fails
[12:55] <yofel> yes, but I would like something that doesn't depend on the apt dependency resolving order
[12:56] <sitter> sure, that's more tricky though :P
[12:56] <yofel> right, should still be solvable by throwing a hashmap of files into a mongodb and checking that after a build
[12:57] <yofel> or something in that direction
[12:57] <shadeslayer> mongodb, such hipster
[12:58] <sitter> shadeslayer: mongodb is yesterday's jam
[12:58] <yofel> says the guy who wrote the CI in ruby :P
[12:59] <shadeslayer> xD
[12:59] <sitter> still a step up from writing perl :P
[12:59] <yofel> sitter: what's the latest stuff? In-memory DBs on persistent memory?
[12:59] <sitter> shadeslayer: btw. g+ had something kewl today
[13:00] <sitter> yofel: I lost track
[13:00] <sitter> yofel: why do we need a db anyway
[13:00] <sitter> yofel: IMO the value of a tracking system would be 100% persistency so I'd actually dump raw data into json into a git repo
[13:00] <sitter> it could entirely be loaded into a database from there for actual runtime processing
[13:00] <yofel> sitter: because I would like something more long-term where a file can vanish for a month before someone upstream remembers to add it back to some random other component
[13:00] <sitter> but as actual storage I'd avoid any specific solution 
[13:01] <sitter> yofel: right. I'd dump to json :P
[13:01] <yofel> well, fine with me, which is why I wanted to talk the implementation out in munich
[13:01] <sitter> yup
[13:02] <sitter> btw, I think nosql is no longer hip altogether
[13:02] <sitter> as far as nosql is concerned I think redis is the one I hear about the most
[13:07] <yofel> well, redis is more cache than db, but yeah, it's usually the thing you want if you need performance. So most people just go with that.
[13:09] <sitter> yofel: I literally do not care enough to even have looked into what it does :P
[13:10] <yofel> it's the same damn thing implemented from a different POV :P
[13:11] <shadeslayer> sitter: what was the cool G+ thing
[13:11] <sitter> ah yes
[13:11] <sitter> distracted
[13:11] <shadeslayer> I'm looking at the EU IOT Agenda
[13:11] <sitter> shadeslayer: https://github.com/bundler/gemstash
[13:11] <shadeslayer> some of the silly things on here
[13:11] <shadeslayer> plus, some of the domains have expired
[13:11] <shadeslayer> http://cordis.europa.eu/fp7/ict/enet/projects_en.html
[13:12] <shadeslayer> first link, dead, 3rd link, dead, 5th link, dead
[13:13] <shadeslayer> someone dislikes prime numbers
[13:13] <shadeslayer> er
[13:13] <shadeslayer> odd numbers
[13:13] <shadeslayer> sitter: ooog
[13:13] <shadeslayer> ooh
[13:56] <Riddell> clivejo: seen http://download.kde.org/unstable/kdeconnect/0.9/src/ ?
[13:56] <Riddell> annoyingly he hasn't changed that tar name
[14:18] <yofel> ok, our packageset in xenial looks fixed - if it weren't for ECM
[14:19] <yofel> and I need to merge 6 packages with the archive, grrr
[14:35] <mck182> any updates on the workspace package for wily?
[14:35] <shadeslayer> why this is fun
[14:36] <shadeslayer> https://www.gnu.org/licenses/gpl-faq.html#BitTorrent
[15:06] <sgclark> morning
[15:07] <yofel> I just deleted kscreenlocker in ci/unstable for wily, that should get the CI build accepted I hope
[15:47] <shadeslayer> so uh, apparently armhf is now building libkwinglutils.so
[15:47] <shadeslayer> but we go all : Architecture: amd64 arm64 i386 powerpc ppc64el
[15:47] <shadeslayer> for that package
[15:47] <yofel> what does the package architecture have to do with the cmake configuration?
[15:47] <shadeslayer> mgraesslin: did kwin recently enable building of libkwinglutils on armhf?
[15:48] <yofel> he did post something about runtime gl/es detection
[15:48] <shadeslayer> yeah
[15:48] <mgraesslin> shadeslayer: yes, as yofel says: there is no kwinglesutils more
[15:49] <shadeslayer> right, kwinglutils is now combined?
[15:49] <mgraesslin> one kwinglutils to bind them, one to rule them all
[15:49] <shadeslayer> roger
[15:49] <yofel> XD
[15:49] <shadeslayer> can drop Arch here then
[15:49] <mgraesslin> yep
[15:49] <mgraesslin> I pointed that out in the blog post
[15:49] <shadeslayer> right, I just re read it
[15:50] <shadeslayer> https://anonscm.debian.org/cgit/pkg-kde/plasma/kwin.git/commit/?h=kubuntu_unstable&id=42dddbb6d42b8dc0ecd98b979120c38194d7c278
[15:50] <shadeslayer> ;)
[16:29] <clivejo> Riddell: I did see it and I packaged it, but Ive used the maintainer verison number.  The previous versions are 0.0+git 
[16:30] <clivejo> not sure if that was wise to do or not
[16:33] <Riddell> clivejo: use the upstream version number
[16:34] <clivejo> Riddell: its in my PPA as kdeconnect-plasma 0.9-0ubuntu1~ubuntu15.10~ppa1
[16:34] <Riddell> clivejo: that looks good yes
[16:34] <clivejo> but I think Ive found a bug
[16:34] <clivejo> need someone else to verify it though
[16:35] <clivejo> do you use it?
[16:35] <Riddell> yes
[16:35] <clivejo> can you still browse your phone via dolphin?
[16:36] <Riddell> clivejo: where do I install it from?
[16:36] <clivejo> Ive recently changed my LAN config, so it might be that causing problems
[16:36] <clivejo> either wily or xenial in my PPA
[16:36] <Riddell> browing from dolphin is done with kio-mtp isn't it?
[16:37] <Riddell> oh no there's a kdeconnect:// kioslave
[16:37] <clivejo> Im getting an error messaging saying that the file or folder doesnt exist
[16:37] <Riddell> ok browsing works good with 0.0+git20150810-0ubuntu1
[16:38] <clivejo> but Im on xenial at the moment
[16:40] <Riddell> clivejo: yep still working good on wily
[16:40] <Riddell> clivejo: but in my experience kio-mtp is kindae flakey and doesn't work sometimes with the error you said
[16:40] <Riddell> so I expect kdeconnect will be the same
[16:40] <Riddell> which might be the fault of the phone or something lower down the stack on linux
[16:41] <clivejo> I think its a local issue
[16:44] <clivejo> strange
[16:45] <clivejo> Riddell: do you know what is going on with kvkbd ?
[16:45] <Riddell> clivejo: nothing as far as I know
[16:45] <clivejo> is it part of KDE or 3rd party?
[16:46] <clivejo> https://launchpad.net/kvkbd
[16:46] <clivejo> would be very handy with touch screens!
[16:49] <clivejo> *pokes ahoneybun to see if he would test it on ubuntu phone*
[16:52] <Riddell> clivejo: we use malitt I think it is on the phone
[16:53] <clivejo> ah, so obsolete
[16:54] <clivejo> well I packaged the 2014 version yesterday and it appears to work
[18:09] <yofel> mck182: ^
[18:09] <mck182> yofel: YESSSS!!!!!! YOU HEROOO!!!!
[18:09] <mck182> also, thank you.
[19:10] <clivejo> Riddell: how do I go about getting kdeconnect-plasma tested/QA and get it into the archives?
[19:11] <clivejo> The author says on the andriod app that Kubuntu is slow about rolling out new features
[19:13] <Riddell> clivejo: ask for testers here with !testers and on the mailing list and get someone with upload privilages to upload it, you can also build it for wily and put it into backports ppa and actual backports
[19:14] <clivejo> its in both my wily and xenial PPA
[19:16] <clivejo> and how do I link the LP page to KDE, or is that possible?
[19:16] <clivejo> https://launchpad.net/ubuntu/+source/kdeconnect-plasma
[19:17] <clivejo> should I build one for vivid too?
[19:18]  * clivejo would have to make a vivid pbuilder to do that
[19:26]  * clivejo feels like hes talking to himself again and wanders off
[19:27]  * genii makes a large tasty pot of coffee, washes out everyone's mugs and leaves them next to the coffeepot
[19:31]  * yofel hands clivejo the "You have mastered the secrets of IRC" scroll and goes back into hiding
[19:35] <Riddell> clivejo: don't bother with vivid, supporting more than one version for backports isn't sustainable
[19:49] <soee> hiho, im finaly back after some ban :/
[21:48] <alket> hi, who is the release manager now ?
[21:49] <mparillo> yofel: and sgclark
[21:49] <alket> thanks mparillo 
[21:53] <alket> lets hope they do a fine release for 16.05
[21:53] <alket> *04
[21:53] <yofel> that's the plan ;)
[21:58] <sgclark> yep!
[22:08] <alket> please don't get me wrong, im just saying because its going to be my distro for work for the next 2 years
[22:09] <alket> thank you for you hard work
[22:39] <valorie> soee: ban?
[22:40] <valorie> ooops, gotta go, but perhaps tell about it in -offtopic?
[22:48] <clivejo> o/ valorie
[22:53] <clivejo> Riddell: do you know how to figure out why my KDEConnect file browser isnt working?