[00:17] -kubuntu-ci:#kubuntu-devel- Project mgmt_merger build #665: SUCCESS in 17 min: http://kci.pangea.pub/job/mgmt_merger/665/
[00:35] -kubuntu-ci:#kubuntu-devel- Project xenial_unstable_kdepim-runtime build #177: STILL FAILING in 15 min: http://kci.pangea.pub/job/xenial_unstable_kdepim-runtime/177/
[00:35] -kubuntu-ci:#kubuntu-devel- Project xenial_unstable_kde-baseapps build #68: STILL FAILING in 11 min: http://kci.pangea.pub/job/xenial_unstable_kde-baseapps/68/
[00:40] -kubuntu-ci:#kubuntu-devel- Project xenial_unstable_kdepim-addons build #44: STILL FAILING in 17 min: http://kci.pangea.pub/job/xenial_unstable_kdepim-addons/44/
 Anyone having connection issues on WiFi?
[00:53] -kubuntu-ci:#kubuntu-devel- Project xenial_unstable_marble build #201: STILL FAILING in 29 min: http://kci.pangea.pub/job/xenial_unstable_marble/201/
[00:55] -kubuntu-ci:#kubuntu-devel- Project yakkety_unstable_marble build #165: STILL FAILING in 31 min: http://kci.pangea.pub/job/yakkety_unstable_marble/165/
[01:00] -kubuntu-ci:#kubuntu-devel- Project yakkety_unstable_kirigami build #17: STILL FAILING in 39 min: http://kci.pangea.pub/job/yakkety_unstable_kirigami/17/
[01:00] -kubuntu-ci:#kubuntu-devel- Project yakkety_unstable_kdelibs4support build #78: STILL FAILING in 42 min: http://kci.pangea.pub/job/yakkety_unstable_kdelibs4support/78/
[01:32] <darin> ahoneybun: regarding wifi and 16.10 with staging-ppas.  I had one laptop that did not conect to wifi when brought out of sleep right after the staging update, but subsequent no issues with the next few sleep awakes.
[01:33] <darin> ahoneybun: I was able to recover the failed wifi with nmcli command....
[01:34] -kubuntu-ci:#kubuntu-devel- Project xenial_unstable_kopete build #56: STILL UNSTABLE in 58 min: http://kci.pangea.pub/job/xenial_unstable_kopete/56/
[01:34] -kubuntu-ci:#kubuntu-devel- Project yakkety_unstable_kppp build #58: STILL UNSTABLE in 59 min: http://kci.pangea.pub/job/yakkety_unstable_kppp/58/
[01:34] -kubuntu-ci:#kubuntu-devel- Project yakkety_unstable_akonadi build #166: STILL FAILING in 1 hr 10 min: http://kci.pangea.pub/job/yakkety_unstable_akonadi/166/
[01:34] <darin> ahoneybun: Another 16.10 laptop with staging ppa is running fine with wifi but have not put it to sleep yet.... will test shortly
[01:34] -kubuntu-ci:#kubuntu-devel- Project xenial_unstable_kleopatra build #45: NOW UNSTABLE in 1 hr 10 min: http://kci.pangea.pub/job/xenial_unstable_kleopatra/45/
[01:34] -kubuntu-ci:#kubuntu-devel- Project xenial_unstable_kdesdk-kioslaves build #54: STILL UNSTABLE in 59 min: http://kci.pangea.pub/job/xenial_unstable_kdesdk-kioslaves/54/
[01:34] -kubuntu-ci:#kubuntu-devel- Project yakkety_unstable_okular build #68: STILL UNSTABLE in 58 min: http://kci.pangea.pub/job/yakkety_unstable_okular/68/
[01:34] -kubuntu-ci:#kubuntu-devel- Project xenial_unstable_kirigami build #15: STILL FAILING in 1 hr 10 min: http://kci.pangea.pub/job/xenial_unstable_kirigami/15/
[01:34] -kubuntu-ci:#kubuntu-devel- Project yakkety_unstable_kleopatra build #18: STILL UNSTABLE in 1 hr 10 min: http://kci.pangea.pub/job/yakkety_unstable_kleopatra/18/
[01:34] -kubuntu-ci:#kubuntu-devel- Project xenial_unstable_kde-runtime build #140: STILL FAILING in 1 hr 14 min: http://kci.pangea.pub/job/xenial_unstable_kde-runtime/140/
[01:35] -kubuntu-ci:#kubuntu-devel- Project yakkety_unstable_kde-runtime build #146: STILL FAILING in 1 hr 11 min: http://kci.pangea.pub/job/yakkety_unstable_kde-runtime/146/
[01:35] -kubuntu-ci:#kubuntu-devel- Project xenial_unstable_plasma-nm build #201: STILL FAILING in 1 hr 11 min: http://kci.pangea.pub/job/xenial_unstable_plasma-nm/201/
[01:49] <DarinMiller> ahoneybun: wifi on 2nd laptop with 16.10 and staging ppa's is working fine even after sleep.  Wish I could same the same for the NVidia 370.28 driver  and it seem to fall off the bus about every other sleep attempt.
 I don't have staging on though
[01:54] <DarinMiller> ahoneybun: my other laptop has occasionly had reconnection issues after sleep for it's entire life so I doubt the connection issue after sleep had anything to do with 16.10 or the staging PPA's
[01:55] <ahoneybun> a few reboots seemed to fix it
[01:55] <ahoneybun> works fine on ethernet though
[02:02] <DarinMiller> ahoneybun:  did you try:  nmcli -p con up "<your network name>" ifname <your wireless card name> 
[02:02] <DarinMiller> ahoneybun: i.e. nmcli -p con up "Millers_5G" ifname wlp1s0
[02:03] <DarinMiller> ahoneybun: works for me everytime-no reboot needed.
[02:24] -kubuntu-ci:#kubuntu-devel- Project yakkety_unstable_kauth build #129: STILL UNSTABLE in 45 min: http://kci.pangea.pub/job/yakkety_unstable_kauth/129/
[02:25] -kubuntu-ci:#kubuntu-devel- Project xenial_unstable_kde-runtime build #141: STILL FAILING in 45 min: http://kci.pangea.pub/job/xenial_unstable_kde-runtime/141/
[02:25] -kubuntu-ci:#kubuntu-devel- Project yakkety_unstable_kde-runtime build #147: STILL FAILING in 45 min: http://kci.pangea.pub/job/yakkety_unstable_kde-runtime/147/
[03:12] -kubuntu-ci:#kubuntu-devel- Project xenial_unstable_kidletime build #253: STILL UNSTABLE in 46 min: http://kci.pangea.pub/job/xenial_unstable_kidletime/253/
[03:12] -kubuntu-ci:#kubuntu-devel- Project xenial_unstable_kdevelop-pg-qt build #19: STILL UNSTABLE in 46 min: http://kci.pangea.pub/job/xenial_unstable_kdevelop-pg-qt/19/
[05:53] -kubuntu-ci:#kubuntu-devel- Project yakkety_unstable_akonadi build #167: STILL FAILING in 44 min: http://kci.pangea.pub/job/yakkety_unstable_akonadi/167/
[05:53] -kubuntu-ci:#kubuntu-devel- Project yakkety_unstable_umbrello build #59: STILL UNSTABLE in 44 min: http://kci.pangea.pub/job/yakkety_unstable_umbrello/59/
[06:48] -kubuntu-ci:#kubuntu-devel- Yippee, build fixed!
[06:48] -kubuntu-ci:#kubuntu-devel- Project yakkety_unstable_kcalcore build #111: FIXED in 55 min: http://kci.pangea.pub/job/yakkety_unstable_kcalcore/111/
[06:49] -kubuntu-ci:#kubuntu-devel- Yippee, build fixed!
[06:49] -kubuntu-ci:#kubuntu-devel- Project yakkety_unstable_baloo-widgets build #115: FIXED in 55 min: http://kci.pangea.pub/job/yakkety_unstable_baloo-widgets/115/
[06:50] -kubuntu-ci:#kubuntu-devel- Project yakkety_unstable_kde-baseapps build #72: STILL FAILING in 1 min 7 sec: http://kci.pangea.pub/job/yakkety_unstable_kde-baseapps/72/
[06:54] -kubuntu-ci:#kubuntu-devel- Project yakkety_unstable_kdepim-runtime build #121: STILL FAILING in 5 min 47 sec: http://kci.pangea.pub/job/yakkety_unstable_kdepim-runtime/121/
[06:56] -kubuntu-ci:#kubuntu-devel- Project yakkety_unstable_kde-baseapps build #73: STILL FAILING in 46 sec: http://kci.pangea.pub/job/yakkety_unstable_kde-baseapps/73/
[06:57] -kubuntu-ci:#kubuntu-devel- Project yakkety_unstable_kdepim-addons build #56: STILL FAILING in 8 min 55 sec: http://kci.pangea.pub/job/yakkety_unstable_kdepim-addons/56/
[07:03] -kubuntu-ci:#kubuntu-devel- Project yakkety_unstable_kdepim-runtime build #122: STILL FAILING in 3 min 52 sec: http://kci.pangea.pub/job/yakkety_unstable_kdepim-runtime/122/
[07:06] -kubuntu-ci:#kubuntu-devel- Project yakkety_unstable_kdepim-addons build #57: STILL FAILING in 3 min 51 sec: http://kci.pangea.pub/job/yakkety_unstable_kdepim-addons/57/
[07:06] -kubuntu-ci:#kubuntu-devel- Project yakkety_unstable_marble build #166: STILL FAILING in 18 min: http://kci.pangea.pub/job/yakkety_unstable_marble/166/
[07:09] -kubuntu-ci:#kubuntu-devel- Project yakkety_unstable_kdevplatform build #18: STILL FAILING in 21 min: http://kci.pangea.pub/job/yakkety_unstable_kdevplatform/18/
[07:24] -kubuntu-ci:#kubuntu-devel- Project yakkety_unstable_kdeconnect-kde build #46: STILL UNSTABLE in 36 min: http://kci.pangea.pub/job/yakkety_unstable_kdeconnect-kde/46/
[07:24] -kubuntu-ci:#kubuntu-devel- Project yakkety_unstable_kirigami build #18: STILL FAILING in 36 min: http://kci.pangea.pub/job/yakkety_unstable_kirigami/18/
[07:24] -kubuntu-ci:#kubuntu-devel- Yippee, build fixed!
[07:24] -kubuntu-ci:#kubuntu-devel- Project yakkety_unstable_kscreenlocker build #117: FIXED in 36 min: http://kci.pangea.pub/job/yakkety_unstable_kscreenlocker/117/
[07:26] -kubuntu-ci:#kubuntu-devel- Project yakkety_unstable_plasma-nm build #106: STILL FAILING in 38 min: http://kci.pangea.pub/job/yakkety_unstable_plasma-nm/106/
[07:30] -kubuntu-ci:#kubuntu-devel- Project yakkety_unstable_kdevplatform build #19: STILL FAILING in 16 min: http://kci.pangea.pub/job/yakkety_unstable_kdevplatform/19/
[08:14] -kubuntu-ci:#kubuntu-devel- Project yakkety_unstable_ktp-common-internals build #112: STILL UNSTABLE in 48 min: http://kci.pangea.pub/job/yakkety_unstable_ktp-common-internals/112/
[08:14] -kubuntu-ci:#kubuntu-devel- Project yakkety_unstable_discover build #28: STILL FAILING in 48 min: http://kci.pangea.pub/job/yakkety_unstable_discover/28/
[08:14] -kubuntu-ci:#kubuntu-devel- Project yakkety_unstable_plasma-nm build #107: STILL FAILING in 42 min: http://kci.pangea.pub/job/yakkety_unstable_plasma-nm/107/
[08:17] -kubuntu-ci:#kubuntu-devel- Project yakkety_unstable_kwin build #114: STILL UNSTABLE in 52 min: http://kci.pangea.pub/job/yakkety_unstable_kwin/114/
[08:31] <lordievader> Good morning
[08:57] -kubuntu-ci:#kubuntu-devel- Project yakkety_unstable_ktp-auth-handler build #113: STILL UNSTABLE in 42 min: http://kci.pangea.pub/job/yakkety_unstable_ktp-auth-handler/113/
[08:57] -kubuntu-ci:#kubuntu-devel- Project xenial_unstable_umbrello build #62: STILL UNSTABLE in 43 min: http://kci.pangea.pub/job/xenial_unstable_umbrello/62/
[08:58] -kubuntu-ci:#kubuntu-devel- Project xenial_unstable_kstars build #234: STILL UNSTABLE in 43 min: http://kci.pangea.pub/job/xenial_unstable_kstars/234/
[09:14] -kubuntu-ci:#kubuntu-devel- Project xenial_unstable_kdevplatform build #16: STILL FAILING in 16 min: http://kci.pangea.pub/job/xenial_unstable_kdevplatform/16/
[09:22] -kubuntu-ci:#kubuntu-devel- Yippee, build fixed!
[09:22] -kubuntu-ci:#kubuntu-devel- Project yakkety_unstable_plasma-workspace build #132: FIXED in 1 hr 4 min: http://kci.pangea.pub/job/yakkety_unstable_plasma-workspace/132/
[09:37] -kubuntu-ci:#kubuntu-devel- Project xenial_unstable_kdevplatform build #17: STILL FAILING in 17 min: http://kci.pangea.pub/job/xenial_unstable_kdevplatform/17/
[09:48] -kubuntu-ci:#kubuntu-devel- Project xenial_unstable_kdeconnect-kde build #55: STILL UNSTABLE in 49 min: http://kci.pangea.pub/job/xenial_unstable_kdeconnect-kde/55/
[09:48] -kubuntu-ci:#kubuntu-devel- Project xenial_unstable_ktp-auth-handler build #160: STILL UNSTABLE in 49 min: http://kci.pangea.pub/job/xenial_unstable_ktp-auth-handler/160/
[09:48] -kubuntu-ci:#kubuntu-devel- Yippee, build fixed!
[09:48] -kubuntu-ci:#kubuntu-devel- Project yakkety_unstable_khotkeys build #54: FIXED in 26 min: http://kci.pangea.pub/job/yakkety_unstable_khotkeys/54/
[09:48] -kubuntu-ci:#kubuntu-devel- Project yakkety_unstable_plasma-sdk build #95: STILL FAILING in 26 min: http://kci.pangea.pub/job/yakkety_unstable_plasma-sdk/95/
[10:19] -kubuntu-ci:#kubuntu-devel- Project xenial_unstable_kde-baseapps build #69: STILL FAILING in 1 min 33 sec: http://kci.pangea.pub/job/xenial_unstable_kde-baseapps/69/
[11:03] -kubuntu-ci:#kubuntu-devel- Project xenial_unstable_akonadi build #250: STILL UNSTABLE in 45 min: http://kci.pangea.pub/job/xenial_unstable_akonadi/250/
[11:03] -kubuntu-ci:#kubuntu-devel- Project yakkety_unstable_plasma-sdk build #96: STILL FAILING in 45 min: http://kci.pangea.pub/job/yakkety_unstable_plasma-sdk/96/
[11:03] -kubuntu-ci:#kubuntu-devel- Project xenial_unstable_kirigami build #16: STILL FAILING in 45 min: http://kci.pangea.pub/job/xenial_unstable_kirigami/16/
[11:03] -kubuntu-ci:#kubuntu-devel- Project xenial_unstable_plasma-nm build #202: STILL FAILING in 46 min: http://kci.pangea.pub/job/xenial_unstable_plasma-nm/202/
[11:10] -kubuntu-ci:#kubuntu-devel- Project xenial_unstable_kdepim-addons build #45: STILL FAILING in 7 min 3 sec: http://kci.pangea.pub/job/xenial_unstable_kdepim-addons/45/
[11:12] -kubuntu-ci:#kubuntu-devel- Project xenial_unstable_discover build #24: STILL FAILING in 9 min 9 sec: http://kci.pangea.pub/job/xenial_unstable_discover/24/
[11:16] -kubuntu-ci:#kubuntu-devel- Project xenial_unstable_kdepim-runtime build #178: STILL FAILING in 13 min: http://kci.pangea.pub/job/xenial_unstable_kdepim-runtime/178/
[11:18] <BluesKaj> Hiyas all
[11:23] -kubuntu-ci:#kubuntu-devel- Project xenial_unstable_marble build #202: STILL FAILING in 20 min: http://kci.pangea.pub/job/xenial_unstable_marble/202/
[11:29] -kubuntu-ci:#kubuntu-devel- Project xenial_unstable_discover build #25: STILL FAILING in 12 min: http://kci.pangea.pub/job/xenial_unstable_discover/25/
 Afternoon :)
 /me yawns
 I woke up at 6:30 AM on a SATURDAY?!?
 @tsimonq2, I was wondering why on earth you are about yet!
[12:02] -kubuntu-ci:#kubuntu-devel- Project xenial_unstable_kwin build #230: STILL UNSTABLE in 59 min: http://kci.pangea.pub/job/xenial_unstable_kwin/230/
[12:57] -kubuntu-ci:#kubuntu-devel- Yippee, build fixed!
[12:57] -kubuntu-ci:#kubuntu-devel- Project xenial_unstable_plasma-workspace build #233: FIXED in 55 min: http://kci.pangea.pub/job/xenial_unstable_plasma-workspace/233/
[15:56] <acheronuk> santa_: ping
[16:15] <santa_> acheronuk: pong. brb in ~20 mins and we will fix something in plasma 5.7.5 ok?
[16:16] <acheronuk> santa_: actually, call it 40 mins as just decided I better eat 1st. ok?
[16:16] <santa_> ok, no problem
[16:51] <acheronuk> santa_: ok. whenever you are ready
[16:52] <santa_> acheronuk: ok, let me explain
[16:53] <santa_> the official ppas have a couple of important limitations
[16:53] <acheronuk> you are not kidding!
[16:54] <santa_> nope, 1. they don't put packages on hold properly when you need to get one package to build another because of versioned build depends
[16:55] <santa_> 2. when build depends aren't properly bumped the builds may or may not fail to build
[16:55] <santa_> I want to focus on 2.
[16:56] <santa_> as you know I have a "ppa simulation" in one of my computers
[16:56] <santa_> this "ppa simulation" (which is actually a wannabuild/buildd setup doesn't have that limitations)
[16:57] <santa_> for this setup I have a fork of the status page
[16:57] <santa_> so I have something similar to the official ppas
[16:58] <santa_> and I made a test rebuild of plasma, status page: http://gpul.grupos.udc.es/buildstatus_ubuntu-exp2/ubuntu-exp2_status_plasma.html
[16:59] <acheronuk> yes
[16:59] <santa_> so lets see what happened with plasma-integration
[16:59] <acheronuk> breeze
[17:01] <acheronuk> wanted dep on that of 5.7.5, but only 5.7.2 available at build time
[17:01] <santa_> correct
[17:02] <santa_> it build depends right now on breeze-dev (>= 4:5.7.2~)
[17:02] <acheronuk> yep, I get why that is wrong
[17:02] <santa_> so the official ppas fail or not fail randomly on this
[17:02] <santa_> my unofficial stuff is right now configured so it would fail allways
[17:03] <santa_> because it would pull latest breeze-dev from yakkety archive
[17:04] <acheronuk> you mean fail even if the deps in the control, file are lower and satisfiable?
[17:04] <acheronuk> but not consistent with the version you are building
[17:04] <santa_> it would pull stuff from my "ppa" only if I set a higher version than the archive
[17:04] <acheronuk> ok
[17:05] <santa_> so if I change the thing to breeze-dev (>= 4:5.7.5~)
[17:05] <santa_> it would pull breeze-dev from the "ppa"
[17:06] <acheronuk> clearly, yes
[17:06] <santa_> so that's one of the reasons why I'm doing this stuff in my "ppa simulation", because I can do stuff that can't done in the official ppas
[17:06] <santa_> * can't be done in the official ppas
[17:07] <santa_> now, regarding the wrong build depends bumping there's another issue to consider
[17:08] <santa_> this is just an hypothetical example but supose we have a source package called libfoo being part of both plasma 5.7.2 and 5.7.5
[17:09] <santa_> lets supose we have a package libfoo1 produced by the source package libfoo version 5.7.2
[17:10] <santa_> lets supose that the libfoo version 5.7.5 produces libfoo2 because there was a soname bump
[17:10] <santa_> now lets suposed we have another package being part of plasma called "bar"
[17:11] <santa_> "bar" uses libfoo
[17:12] <acheronuk> https://media.giphy.com/media/3EUgWmcX2NOBa/giphy.gif
[17:13] <santa_> haha, now consider we have "libfoo-dev (>= 5.7.2)" in the bar source package 5.7.5 (i.e. we didn't bump the version of the build depends)
[17:14] <santa_> so if we build bar in an official ppa we could get it depending on libfoo1 or libfoo2 depending on the build order
[17:14] <santa_> and that's a problem
[17:14] <acheronuk> yes
[17:15] <santa_> so I would suggest to re-bump all the build depends of plasma 5.7.5 and apps 16.04.3
[17:15] <santa_> not just the ones failing to build in my ppa simulation
[17:15] <santa_> what do you think?
[17:16] <acheronuk> yes, as soon a you pointed out that it had been forgotten, I did realise most of that. knew most already, and thought damn!
 So we need to add what ppas to YY to test?
[17:17] <santa_> yeah, just wanted to make sure you were aware of the possible situations
[17:18] <acheronuk> ahoneybun: I would hold off for now if we are going to rebuild some
[17:18] <santa_> ahoneybun: we will fix the things in staging, but we didn't yet, we will keep you posted about the progress
 OK np
[17:20] <santa_> acheronuk: one last thing, there's a missing feature in the build depend bumping stuff
[17:20] <acheronuk> santa_: yeah, I know it in theory but until you get used to putting that into practice time after time, it's just a case of forgetting to apply it when you are concentration on other parts of it.
[17:20] <santa_> don't worry it's very easy to fix
[17:21] <acheronuk> yes, I had a play with the bump script
[17:22] <santa_> ok, I have pushed the feature no
[17:22] <santa_> * now
[17:22] <acheronuk> before we get going I just want to ask....
[17:22] <santa_> it's the -u/--update-mode for dev-package-names-list
[17:23] <acheronuk> in frameworks, did you deliberately not push your latest kio changes to git for some reason?
[17:24] <acheronuk> I notice you uploaded a fixed package, but not the changes to git
[17:24] <santa_> oh, sorry let me check...
[17:25] <acheronuk> thought I'd better ask now before it slips my mind
[17:26] <santa_> pushed now, thanks for noticing
[17:26] <acheronuk> np
[17:27] <santa_> ok, so about the plasma build depends fixing
[17:27] <acheronuk> yes
[17:27] <santa_> the build depends map was generated with "dev-package-name-list -d yakkety -r plasma -m qt frameworks"
[17:28] <santa_> however if you run that command again, it would put frameworks 5.26 in the map and we don't actually want that
[17:28] <acheronuk> no, I was going to say, as at the moment we don't know if 5.26 will even get a FFe
[17:29] <santa_> if you run "dev.package-name-list -d yakkety -r plasma" it would re-create the map, so it would remove the qt and fw build dependencies we put there previously
[17:29] <santa_> so that's what the "-u" option is for
[17:30] <acheronuk> so leave the version already there
[17:30] <acheronuk> for ones you don't specify I mean
[17:33] <santa_> yes, just pushed a small fix for KA right now
[17:33] <santa_> "dev-package-name-list -d yakkety -r plasma -u" will do the right thing
[17:34] <santa_> (for this particular case)
[17:34] <acheronuk> "Update mode. With this mode you will update only the binary packages specified with '-r' and '-m' keeping any extra old packages"
[17:35] <acheronuk> indeed
[17:36] <santa_> acheronuk: so that being said feel free to fix the thing
[17:36] <santa_> we could re-upload plasma 5.7.5 and stage it for xenial as well
[17:36] <acheronuk> we could
[17:37] <santa_> so how do you want to proceeed, you fix plasma and I fix apps?
[17:38] <acheronuk> I would rather both go through plasma if you can spare the time. 
[17:39] <santa_> sure, lets go to the shared terminal then?
[17:39] <acheronuk> yep. I think it relatively trivial, but since you are here. reassurance thing
[17:40] <santa_> np
[18:01] <fenris-> mamarley: r u here?
[18:02] <mamarley> pong
[18:02] <fenris-> fenris@x240:~⟫ quasselclient -d Enabling compression... Using the DataStream protocol... Starting encryption... "no registered receiver for sync call: IrcChannel::joinIrcUsers (objectName=\"2/#kl\"). Params are:" (QVariant(QStringList, ("seeking4prettywife")), QVariant(QStringList, ("")))
[18:03] <fenris-> the client freeze
[18:03] <mamarley> How long has this been going on?  Which core and client versions are you using?
[18:04] <fenris-> after i recent update yakkety 
[18:05] <fenris-> previously i used 0.12.4-2ubuntu2
[18:05] <fenris-> now im trying the git version 
[18:05] <fenris-> 0.13.x
[18:06] <fenris-> and im in unity now .. 
[18:06] <mamarley> What about the core?  Which version is that running?  Has it been updated recently?
[18:07] <fenris-> core running 0.12.2-0ubuntu1
[18:08] <fenris-> u suggest i upgrade the core as well ?
[18:08] <mamarley> Have you been able to connect successfully with any clients since you started having the problem?
[18:09] <fenris-> not
[18:09] <fenris-> nope*
[18:09] <fenris-> a few days back the client works
[18:10] <mamarley> Have you tried connecting with any other clients (like on different computers or something)?
[18:11] <fenris-> my quasseldroid working fine 
[18:12] <fenris-> from my mobile phone
[18:12] <ejat> Hi mamarley
[18:12] <ejat> It me 
[18:13] <ejat> It's working fine here
[18:13] <mamarley> OK, that means the core is working properly.  You said the client quit after an update.  What was updated?
[18:13] <ahoneybun> can you move this to #kubuntu?
[18:14] <ejat> Okie ahoneybun
[18:14] <mamarley> How about #quassel?  I'm not in #kubuntu.
[18:14] <ahoneybun> (I know I was talking about issues with kickoff yesterday, so I'm bad at it)
[18:15] <fenris-> okie
[18:37] <santa_> acheronuk: hmm, wait
[18:37] <santa_> we didn't commited the changes, did we?
[18:37] <acheronuk> kill it?
[18:37] <acheronuk> no
[18:37] <santa_> yeah
[18:37] <santa_> lets commit it and repeat
[18:38] <santa_> just a do-all git commit -am 'whatever' will do the thing
[19:10] <acheronuk> santa_: done
 @tsimonq2 so where is the meeting going to happen?
[19:50] <santa_> +1
 @ovidiuflorin In our Big Blue BUtton room :)
 *Button
 which room?
[19:51] <tsimonq2> http://kubuntu.blindsidenetworks.net/kubuntu/
[19:51] <tsimonq2> password is welcome
[19:51] <tsimonq2> room 1
 thank you
 Mm darn flash
 😜
 you stay out
 Fine!
 they are talking about britney spears
[20:37] <acheronuk> you don't want to hear about britney!
[21:34] -kubuntu-ci:#kubuntu-devel- Project xenial_unstable_kwin build #231: STILL UNSTABLE in 1 hr 12 min: http://kci.pangea.pub/job/xenial_unstable_kwin/231/
[21:45] <acheronuk> I forgot how awful I am with those sorts of meetings. :P
[21:46] <tsimonq2> me too lol :P
[21:46] <tsimonq2> but hey, I only said "um" 20 times :P
[21:46] <acheronuk> my mind just goes blank!
[21:49] <tsimonq2> ahoneybun: what is the current status of the slideshow?
[21:49] <tsimonq2> we discussed you at the meeting :P
[21:49] <santa_> acheronuk: oh, I have just remember something important about apps
[21:50] <santa_> some packages were synced with debian so we probably should merge in git and bump the changelog version
[21:50]  * acheronuk also remembers why he didn't sort out a microphone for ages. I hate talking on those things
[21:51] <acheronuk> santa_: I vaguely recall some being done, yes you are surely correct.
[21:53] <santa_> acheronuk: ok, so we could try to get that done after we get the build depends versioning fixed
[21:54] <santa_> I will be afk soon, good night everyone
[21:55] <acheronuk> yes, on all that. Good night santa
 And I'm getting dinner
 o/ santa_
[22:06] <acheronuk> no subs
[22:12] <acheronuk> notes https://notes.kde.org/p/kubuntu-ninja-meeting-september-17-2016
[22:13] <acheronuk> which should say with an asterisk at the bottom * Rik sat there for most of it not sure what to say
 Getting there: https://wiki.ubuntu.com/RikMills
[22:19] <acheronuk> Going to try to get that done next few days, so comments welcome
[22:20] -kubuntu-ci:#kubuntu-devel- Project yakkety_unstable_kwin build #115: STILL UNSTABLE in 50 min: http://kci.pangea.pub/job/yakkety_unstable_kwin/115/
 Broken
 The slideshow that is