[03:59] <tsimonq2> yofel: please take a look: https://bugs.launchpad.net/ubuntu/+source/casper/+bug/1582270
[10:59] <sakrecoer> greetings kubuntu, i was wondering if Ubuntu Studio could get a bit of your advice.
[10:59] <sakrecoer> we are troubles building the ISO. last error is:
[10:59] <sakrecoer> "kactivitymanagerd : Breaks: kactivities (< 5.20~) but 5.18.0-0ubuntu1  is to be installed
[11:01] <sakrecoer> Laney told me the following in -release: "libkactivities6 has a Recommends on kactivities, which is a package that kactivities-kf5 has dropped"
[11:02] <sakrecoer> is this something you are experiencing too, and would you know how we can fix it?
[11:22] <acheronuk> sakrecoer: that looks wrong to me, and probably explains a grumble I had last time I did an upgrade to yakkety packages.
[11:23] <acheronuk> sakrecoer: yofel will need to take a look I imagine, and he'll be at work for European working hrs at the moment
[11:26] <sakrecoer> acheronuk: thanks for your response! i'll try reach out to yofel later then :)
[11:34] <apol> hey, can you guys look into this bug? https://bugs.kde.org/show_bug.cgi?id=366029
[11:49] <BluesKaj> 'Morning folks
[14:44] <clivejo> acheronuk: did you work on kirigami?
[14:46] <acheronuk> clivejo: I've not touched either of those imports yet. Decided to fix kwin on CI, as that was completely failing to build
[14:52] <acheronuk> Is it needed for anything?
[16:12] <sakrecoer> greeting, is yofel arround perhaps? :)
[16:12] <tsimonq2> o/ sakrecoer ;)
[16:12] <sakrecoer> ohaj tsimonq2 ! :)
[16:12] <sakrecoer> \o
[16:12] <tsimonq2> clivejo: do YOU know yofel's hiding spot?
[16:13] <tsimonq2> :P
[16:13] <clivejo> a make believe world called real life :P
[16:14] <tsimonq2> :O take me to this magical place!
[16:14] <clivejo> Im afraid you arent old enough yet
[16:16] <tsimonq2> :(
[16:17] <clivejo> I would reckon he’s commuting and depending how his day has been he might be on later
[16:18] <tsimonq2> ok
[16:18] <clivejo> sakrecoer: what version of Ubuntu is that?
[16:19] <tsimonq2> clivejo: we're working on Beta 1 together
[16:19] <tsimonq2> (I'm helping him with the flavor side of things)
[16:19] <sakrecoer> clivejo: Studio, we are having troubles with "kactivitymanagerd : Breaks: kactivities (< 5.20~) but 5.18.0-0ubuntu1  is to be installed
[16:20] <clivejo> in Xenial?
[16:20] <sakrecoer> clivejo: no yakkety
[16:20] <clivejo> !info kactivitymanagerd
[16:20] <clivejo> !info kactivities
[16:20] <clivejo> hummm
[16:21] <clivejo> maybe still stuck in proposed?
[16:22] <clivejo> oh that package isnt a thing any more
[16:23] <blaze> some people say that kdepim 5.3 is a mess, extremely unstable
[16:23] <sakrecoer> clivejo: 13:00 < sakrecoer> Laney told me the following in -release: "libkactivities6 has a  Recommends on kactivities, which is a package that kactivities-kf5 has  dropped"
[16:25] <clivejo> yes, the whole activities got a big update 
[16:28] <sakrecoer> clivejo: any idea how we can solve this?
[16:28] <clivejo> we jumped from 5.18 in xenial to 5.24 which is current yakkety archive version
[16:30] <clivejo> Im guessing you guys dont use plasma
[16:32] <sakrecoer> clivejo: tbh, i am not very technical... 
[16:33]  * tsimonq2 steps in here
[16:33] <tsimonq2> !info libkactivities6 yakkety
[16:33] <tsimonq2> !info libkactivities7 yakkety
[16:33] <tsimonq2> ...I thought that was bumped to 7
[16:33] <tsimonq2> anyways
[16:34] <tsimonq2> clivejo: what do you think needs to happen if libkactivities6 recommends kactivities but can't be fulfilled?
[16:34] <clivejo> we dont use that any more
[16:34] <tsimonq2> what don't you use?
[16:35] <clivejo> is Studio based on Unity?
[16:35] <sakrecoer> when i checked the germinate page.. it seemed like plasma framework was in there..
[16:35] <sakrecoer> clivejo: no on xfce... or xubuntu..
[16:36] <clivejo> but you are using kdenlive?
[16:36] <sakrecoer> clivejo: yes
[16:37] <clivejo> well libkactivities was for activities in Plasma 
[16:39] <clivejo> what is pulling it in on your system?
[16:41] <sakrecoer> clivejo: i'm looking at this, but i'm fairly uncomfortable interpreting it: https://people.canonical.com/~ubuntu-archive/germinate-output/ubuntustudio.yakkety/all
[16:44] <sakrecoer> calligra seem to pull kactivites, which in turn seems to pull plasma.. but i'm very much an00b with these dependencies things..
[16:50] <clivejo> this is our new activities lib
[16:50] <clivejo> !info libkf5activities5
[16:51] <mhall119> sitter: ping
[16:54] <clivejo> what does it say when you "apt install kactivitymanagerd"
[16:54] <sakrecoer> clivejo: we have no working iso to test with.. :/
[16:56] <clivejo> you dont have a version in VM?
[16:58] <sakrecoer> available ISO fail to install...
[16:59] <clivejo> is this your seed -> https://people.canonical.com/~ubuntu-archive/germinate-output/ubuntustudio.yakkety/all
[17:01] <clivejo> and where are you seeing the output ""kactivitymanagerd : Breaks: kactivities (< 5.20~) but 5.18.0-0ubuntu1  is to be installed"
[17:01] <sakrecoer> clivejo: https://launchpadlibrarian.net/280490101/buildlog_ubuntu_yakkety_amd64_ubuntustudio_BUILDING.txt.gz
[17:01] <sakrecoer> or here if you prefer: https://launchpad.net/~ubuntu-cdimage/+livefs/ubuntu/yakkety/ubuntustudio
[17:03] <clivejo> where is the seed list?
[17:04] <clivejo> something much be installing kactivities 
[17:04] <clivejo> msut
[17:04] <clivejo> must
[17:05] <sakrecoer> https://code.launchpad.net/~ubuntustudio-dev/ubuntu-seeds/ubuntustudio.yakkety ...? i'm sorry, i'm not very knowledgeable on this seed germination process..
[17:06] <sakrecoer> clivejo: that link you pasted above was refered to me as a way to see what depends on what...
[17:06] <clivejo> do you guys make use of calligra?
[17:07] <clivejo> ah you pull in krita
[17:07] <clivejo> !info krita
[17:07]  * clivejo face palms
[17:08] <clivejo> krita was moved into its own source package
[17:09] <clivejo> sakrecoer: do you have MOTU on your team?
[17:09] <sakrecoer> clivejo: you mean a MOTU member?
[17:10] <clivejo> someone who can upload stuff
[17:10] <sakrecoer> yeah..
[17:10] <sakrecoer> zequence
[17:11] <clivejo> krita and calligra really need to be updated
[17:12] <sakrecoer> ok..
[17:16] <clivejo> unfortunately Feature Freeze was last week and it would need a FFE to get it uploaded now 
[17:17] <sakrecoer> so better remove it altogether for now i reckon?
[17:17] <clivejo> well I personally would like to see it updated
[17:17] <clivejo> Krita 3 is amazing
[17:17] <sakrecoer> oh, me too...
[17:17] <sakrecoer> yeah, the best
[17:17] <clivejo> and deserves to be in yakkety
[17:17] <clivejo> but I dont have upload rights
[17:18] <clivejo> I have the one in my PPA installed locally
[17:18] <clivejo> https://launchpad.net/~clivejo/+archive/ubuntu/krita/+packages
[17:18] <sakrecoer> maybe with a little luck we can find a sponsor before final release?
[17:19] <clivejo> maybe
[17:19] <clivejo> Im got man flu at the moment and not prepared to beg or make bribes to get a sponsor
[17:21] <clivejo> you could open a LP bug as an FFE for krita explaining that its too old and needs updating
[17:22] <clivejo> https://wiki.ubuntu.com/FreezeExceptionProcess if you want to help
[17:22] <sakrecoer> thank you clivejo 
[17:23] <tsimonq2> I'm in the mood to bribe for a sponsor
[17:23] <tsimonq2> XD
[17:23] <clivejo> The problem is it is a brand new package as it was split from calligra
[17:24] <tsimonq2> o/ jimarvan 
[17:24] <jimarvan> hello from sunny Zakynthos! :)
[17:24] <jimarvan> I cannot believe I am on holidays after a year lol
[17:25] <clivejo> you would probably need to file the FFE here - https://bugs.launchpad.net/ubuntu/+source/calligra
[17:25] <clivejo> tsimonq2: will you work with sakrecoer on this?
[17:25] <tsimonq2> totally :)
[17:25] <clivejo> Packaging is here - https://code.launchpad.net/~kubuntu-packagers/kubuntu-packaging/+git/krita
[17:26] <sakrecoer> sure, i can help... make coffee and cheer up :)
[17:26]  * tsimonq2 hints at genii 
[17:26] <sakrecoer> i can even be human embarassment shield...
[17:26] <clivejo> I dont know how many people tested my version, but Ive been uisng it on my system up
[17:26] <clivejo> can you cure man flu?
[17:26]  * genii skedaddles to the coffeepot and gets to making a fresh batch!
[17:27] <sakrecoer> clivejo: yes, no problem.
[17:28]  * clivejo goes for something to eat knowing he cant taste anything :(
[17:28] <sakrecoer> you need: thymes, honey, garlic
[17:28] <sakrecoer> its a discgusting potion, but it works.
[17:29] <sakrecoer> clivejo: make some very strong tee with thymes, press 3 garlic portions in it. add honey to cover the taste (and for throat) serve hot.
[17:30] <sakrecoer> i'm serious btw. that is how i've been doing all my life.
[17:32] <zequence> Hi. Can't do uploads, I'm afraid, but perhaps if I understand the problem with krita I may be of some assistance.
[17:32] <zequence> It seems it has been removed from debian unstable
[17:33] <sakrecoer> good to see you here zequence :) i think clivejo just went for food...
[17:34] <sakrecoer> but perhaps tsimonq2 can fill you in? i was pointed towards yofel also..
[17:34] <sakrecoer> regarding Krita/calligra that is.
[17:35] <zequence> Are those the packages causing the ISO building issues for Ubuntu Studio, then?
[17:36] <zequence> Or, rather krita
[17:38] <sakrecoer> zequence: yes, they seem to be pulling in kactivities
[17:39] <sakrecoer> zequence: 19:07 < clivejo> krita was moved into its own source package
[17:39] <sakrecoer> so i guess that means calligra is no longer the source... but yeah.. little do i know
[17:40] <zequence> No, I think it is. Just checking the git repos at https://anonscm.debian.org/cgit/
[17:40] <zequence> (which is where you get from http://git.debian.org)
[17:40] <zequence> The packaging team for calligra in Debian is pkg-kde
[17:41] <zequence> It seems the last update to that package was 8 months
[17:41] <zequence> ..ago
[17:41] <zequence> I can't do any uploads there. I only have access to pkg-multimedia repos
[17:44] <zequence> 2.9 was never released
[17:44] <zequence> So, what's going on. Is it abandoned?
[17:45] <sakrecoer> krita is defenitly not abandoned..
[17:46] <sakrecoer> but i don't know how it looks in debian or ubuntu...
[17:46] <sakrecoer> zequence: https://krita.org/en/item/krita-3-0-released/ this was in may this year..
[17:47] <zequence> krita is available as a snap package, so that is a way out for us. Not sure how we could include a snap on the ISO though
[17:47] <zequence> Yes, krita is alive and well, but in Debian it seems another story.
[17:48] <sakrecoer> yeah... and te snap is broken for nvidia users.
[17:48] <zequence> Ubuntu does not maintain calligra. It is auto-imported
[17:48] <zequence> Ok, that's too bad
[17:48] <sakrecoer> zequence: good question raised though: how does snap work with iso?
[17:48] <zequence> Well, no matter how we do it, an upgrade to 16.10 will break if krita is not compatible
[17:49] <sakrecoer> yeah... the easy way out for now is to remove it...
[17:49] <zequence> What one could do is subscribe to the pkg-kde mail list and ask around a bit, as well as search the archive
[17:50] <zequence> sakrecoer: A job for you, perhaps :)
[17:50] <sakrecoer> zequence: :) yes!
[17:53] <blaze> oh krita, why did they do beta for patch release?
[17:55] <jimarvan> I had also problems with krita 3.0 :/ using an old nvidia card, it was breaking bad
[17:56] <blaze> well, it seems they've mistyped something https://krita.org/en/item/krita-3-0-1-beta-builds/
[17:56] <blaze> it's not 3.0.1 beta, it is 3.1 beta
[17:57] <soee_> Plasm 5.7.4 out
[17:58]  * mamarley slaps soee_ around a bit with a large trout.
[17:59] <soee_> ;)
[18:42] <clivejo> zequence: yes krita has been moved out of calligra source
[18:42] <zequence> clivejo: It seems to be there still. Just that the whole thing has been dropped from Debian Unstable
[18:42] <clivejo> calligra is being ported to Kf5
[18:43] <zequence> I was just looking at the Debian git repo for calligra. Couldn't find one for krita
[18:43] <clivejo> I have some initial packaging for krita here - https://git.launchpad.net/~kubuntu-packagers/kubuntu-packaging/+git/krita/
[18:43] <zequence> clivejo: Oh.
[18:43] <clivejo> zequence: because it was part of calligra
[18:43] <clivejo> dont think the have new packaging yet
[18:44] <zequence> clivejo: So, are you about to get krita in for yakkety?
[18:44] <clivejo> zequence: I dont like upload rights
[18:44] <clivejo> have
[18:44] <zequence> clivejo: It's a bit late to get a new original package in for yakkety, I guess
[18:45] <zequence> Our concern is to get an updated krita in for yakkety, or the package needs to be removed from the archive all together.
[18:46] <clivejo> zequence: we really should try and get krita 3 and calligra 2.9.11 into yakkety
[18:46] <clivejo> but for me that requires opening FFE and begging to get it sponsored
[18:47] <zequence> clivejo: If your package is ok, we can help test it and do some noise
[18:47] <clivejo> sure, its in my ppa
[18:47] <sakrecoer> i can do the beggin part :)
[18:48] <clivejo> https://launchpad.net/~clivejo/+archive/ubuntu/krita
[18:48] <clivejo> have been since June
[18:48] <zequence> clivejo: But, I wonder how this affects the Debian imports
[18:48] <zequence> And, what are Debian packagers planning to do?
[18:49] <clivejo> I dont know, I havent seen any movement
[18:49] <clivejo> we (kubuntu) have been moving our packaging from Alioth to LP
[18:51] <zequence> clivejo: You don't do any team work with them?
[18:52] <clivejo> we do, but had problems getting new contributors access to Alioth
[18:52] <zequence> Isn't Scott K around there? I know he used to be here as well. I'm pretty ignorant about what happened just a few months ago though.
[18:52] <zequence> Really? That's too bad.
[18:53] <clivejo> hes about but has gone back to Debian
[18:55] <clivejo> I also attempted to get calligra into xenial but didnt manage it
[18:55] <clivejo> https://launchpad.net/~clivejo/+archive/ubuntu/calligra
[18:56] <clivejo> so I just package it and point people who want to test it to my PPA
[18:56] <tsimonq2> clivejo: what's up with apps 16.04.3?
[18:57] <clivejo> tsimonq2: needs looked over and uploaded
 File the FFE clivejo
[18:57] <clivejo> http://qa.kubuntu.co.uk/ppa-status/applications/build_status_16.04.3_yakkety.html
[18:58] <tsimonq2> clivejo: uploaded where?
[18:58] <clivejo> tsimonq2: archive
[18:58] <clivejo> ahoneybun: Im in really bad form at the moment and in no way have the patients to do so
[18:58] <tsimonq2> clivejo: but doesn't that require a metric sh*tton of paperwork?
[18:59] <clivejo> tsimonq2: of course
[18:59] <tsimonq2> because of FFE :/
[19:00] <tsimonq2> clivejo: W: dolphin4: package-name-doesnt-match-sonames libdolphinprivate4-4
[19:00] <tsimonq2> clivejo: does that need to be corrected?
[19:00] <clivejo> but when they change the default compiler a week or so before FF which introduces issues with symbols, what are we to do
 So you have Calligra in a ppa?
[19:01] <clivejo> I havent looked at calligra since xenial
 Mm not sure if we can add things to a LTS
 But we still have a chance with yakkety
[19:02] <clivejo> ahoneybun: thats what backports are for
 If not ZZ
 Ours but not the main archive
 Back ports for sure
[19:02] <clivejo> we're had bigger fish to fry
 I'd +1 for sure for backports
[19:02] <clivejo> ie Qt5.6 and PIM
 Personally I'd drop PIM as its more of a pain then anything
 But I'm bias as I rarely use it
[19:03] <clivejo> well its working fine in 16.04.3
[19:04] <clivejo> but gcc6 was dropped and throw a ton of problems with symbols
 Of course
[19:04] <clivejo> Im still on the pre-gcc6 builds
[19:05] <mamarley> They also just uploaded GCC 6.2 for yakkety.  As I understand it, however, that is more of a minor release so it shouldn't cause as many problems.
[19:05] <tsimonq2> yeah bugfix
[19:08] <clivejo> our packaging for calligra was kept here - https://code.launchpad.net/~kubuntu-packagers/kubuntu-packaging/calligra
 Cool
[19:11] <blaze> gcc -v tells me that 6.1.1 is my default one now
[19:11] <mamarley> blaze: It is still in -proposed.
[19:12] <blaze> never enabled proposed here
[19:12] <blaze> o.O
[19:12] <tsimonq2> gcc version 6.1.1 20160815 (Ubuntu 6.1.1-12ubuntu11) 
[19:12] <tsimonq2> that's mine
[19:13] <mamarley> 6.2.0 is in -proposed and will presumably be copied to the main archive at some point in the near future.
[19:13] <blaze> so what does that mean?
[19:14] <mamarley> Just an explanation as to why your systems still have 6.1.1.
[19:16] <blaze> I just don't understand what can be possible problems due to transition to 6.x
[19:17] <clivejo> the problems were caused from 5 to 6
[19:19] <blaze> are there some packages that cannot be rebuilt?
[19:20] <santa_> they were 5 frameworks still failing to build, I have the patches awaiting in launchpad
[19:20] <blaze> or the problem is to rebuild in a certain sequence?
[19:20] <santa_> everything wrt gcc 6 in applications is already fixed
[19:21] <santa_> clivejo: btw note that I still have like 3 patches for apps 16.04.3
[19:21] <santa_> awaiting for yofels approval
[19:22] <blaze> so the problem is in the code which is not compiler-agnostic, right?
[19:22] <santa_> not allways
[19:23] <santa_> anyway this is the usual stuff when you work on a linux distribution
[19:23] <santa_> with a major gcc version there's allways some packages to fix because they fail to build
[19:25] <blaze> i realize they're not binary compatible, that's pretty normal
[19:25] <blaze> but the build should be tested against more than one compiler version
[19:26] <blaze> before being released
[19:26] <tsimonq2> blaze: well not all packages are released after GCC6
[19:27] <tsimonq2> what about GCC7? let's test against that! :P
[19:29] <acheronuk> santa_: if everything in apps 16.04.3 is now GCC 6 safe, and any changes for that merged into kubuntu_unstable, I guess that makes unstable as safe as it gets in that respect as well 
[19:30] <santa_> acheronuk: for apps 16.04.3 yes
[19:31] <santa_> unless there are new upstream changes which doesn't work with gcc 6, but that's unlikely
[19:32] <santa_> anyway the KCI is working already with gcc6 because it's already the default compiler, so if anything, you will notice
[19:33] <acheronuk> santa_: yes, I realise that, but as you say unlikely, and you have to at some point stop overly worrying on what would happen if compiled with the previous default.
[19:33] <clivejo> KCI should also use -proposed
[19:34] <clivejo> note that kubuntu_unstable branch will be working with lastest git from KDE
[19:35] <acheronuk> clivejo: not -proposed according to https://launchpad.net/~kubuntu-ci/+archive/ubuntu/unstable/+edit-dependencies
[19:35] <clivejo> oh, maybe just our staging
[19:35] <santa_> acheronuk: right now you have to care about 2 "defaults" the gcc 5 for xenial and the gcc 6 for yakkety
[19:36] <santa_> but it's not difficult to do that
[19:37] <acheronuk> fortunately both are in kci at get builds from the same source, so can compare if needed
[19:46] <tsimonq2> so...kubuntu_stable?
[19:46] <tsimonq2> what was the point?
[19:46] <tsimonq2> and what now?
[19:48] <blaze> still it seems to me more like organizational problem that can be avoided, rather than some technical problem
[19:52] <santa_> blaze: it's not. when a new major version of gcc is going to be set as default we get a mail from the gcc maintainer linking to test rebuilds so we can see what's failing if we have time, we fix them in advance. that simple
[20:19] <clivejo> acheronuk: ping
[20:19] <acheronuk> clivejo: pong
[20:19] <clivejo> do you have notes on moving bzr to git?
[20:20] <tsimonq2> I have an idea
[20:21] <tsimonq2> y'all know about packages.debian.org?
[20:21] <acheronuk> clivejo: no. I gave it that quick test with amarok, but wasn't sure if it was very really satisfactory. + the way suggested on LP gave me an error I think
[20:22] <tsimonq2> I'm constantly frustrated that I have to search the respective PPAs we have and I have to go to a lot of different places just to find the freaking packages in the PPAs
[20:22] <tsimonq2> that and what version is in Debian etc.
[20:22] <tsimonq2> what if I took a crack at customizing the source code for that to be able to search Debian, Ubuntu, AND all of our active PPAs?
[20:23] <acheronuk> tsimonq2: that could be useful
[20:23] <clivejo> I would like a way to search PPA
[20:23] <tsimonq2> and if I get it working, maybe we can host it at packages.qa.kubuntu.co.uk
[20:23] <tsimonq2> great \o/
[20:25] <valorie> what a great idea
[20:25] <valorie> since I think we have a few secret packagers who stash stuff in PPAs and never tell anybody
[20:25] <tsimonq2> hehehehe ;)
[20:33] <ahoneybun> can you do that?
[20:33] <ahoneybun> pack.qa.ubuntu.co.uk
[20:33] <ahoneybun> lots of dots
[20:38] <tsimonq2> yep
[20:38] <tsimonq2> I believe so
[20:39] <tsimonq2> if not we can just do packages.kubuntu.co.uk
[20:40] <ahoneybun> do we need a whole site for it?
[20:40] <ahoneybun> well domain
[20:40] <ahoneybun> we have http://qa.kubuntu.co.uk/
[20:40] <ahoneybun> with a few links
[20:41] <acheronuk> just a search page on that would be fine?
[20:41] <tsimonq2> acheronuk: well I figured it might be easy enough to make it identical to packages.debian.org except for some CSS tweaks and additional archive sections
[20:44] <clivejo> acheronuk: up to much?
[20:44] <acheronuk> clivejo: not hugely. what have you in mind?
[20:45] <clivejo> have a play with calligra on your container
[20:46] <acheronuk> what needs doing with that?
[20:46] <clivejo> packaging
[20:47] <clivejo> Im assuming that krita will disappear somewhere too
[20:49] <acheronuk> ok.
[20:49] <clivejo> do you want to?
[20:49] <ahoneybun> tsimonq2: sent you access to the kubuntu-manual on github
[20:50] <ahoneybun> let me review before you make the final push of anything
[20:50] <clivejo> its ok, I can hop on my own container if you are busy
[20:50] <tsimonq2> k thx ahoneybun 
[20:50] <ahoneybun> master = +1 16.04-LTS is well that's clear
[20:51] <ahoneybun> ex at this moment master is 16.10
[20:51] <acheronuk> clivejo: no, we can do that if you like
[20:51] <clivejo> plus you can do the typing while Im crying and blowing my nose
[20:52] <acheronuk> still that bad? urgh
[20:52] <valorie> clivejo: I just excavated my laptop with broken hinge
[20:53] <valorie> 128GB SSD, SATA 3 GB HD, and some memory
[20:54] <clivejo> oh nice
[20:54] <valorie> not sure how one knows what the memory sticks are
[20:54] <clivejo> what kind of laptop is it?
[20:54] <clivejo> wee sticker on them normally
[20:54] <valorie> but as I recall, it was a LOT
[20:55] <valorie> well, sticker starts with DIMM-CT
[20:55] <acheronuk> nice indeed
[20:55] <valorie> but that's just the type
[20:55] <valorie> you want it all?
[20:55] <clivejo> wouldnt say no
[20:56] <valorie> ok, I'll have to trust you to erase my password/key files and such
[20:56] <clivejo> mine is getting past it
[20:56] <valorie> since it basically died
[20:56] <clivejo> of course
[20:56] <valorie> including the HD?
[20:57] <valorie> I might even have a lil sata box for that
[20:57] <tsimonq2> LINUX UNPLUGGED TIME! :D
[20:57] <valorie> it was an HP laptop
[20:58] <valorie> loooved that box
[21:00] <acheronuk> my toshiba laptop hinge broke. well the surround on the lid it mounted into really. had to take a drill to it and basically make a new fixing with some spare bit of metal and nuts and bolts
[21:04] <valorie> my attempts to fix failed 
[21:04] <valorie> two laptops in a row
[21:04] <valorie> :(
[21:05] <acheronuk> it looks a bit ugly but it works. buying a whole new lid/surround was a daft price for what it was
[21:14] <valorie> well, since my son keeps getting new gaming laptops, getting his "old" ones has been an option for me
[21:14] <valorie> for the past few years
[21:14] <valorie> now he's given up on laptops and is back at his fancy homebuilt tower
[21:15] <valorie> so I'd better make this MSi last
[21:16] <soee> !!
[21:16] <soee> https://www.kdevelop.org/news/kdevelop-500-released
[21:16] <clivejo> sorry, lost internet again
[21:16] <acheronuk> clivejo: still about?
[21:16] <acheronuk> ahhh
[21:18] <valorie> yeah, they spiffed their website too
[21:18] <valorie> they are excited about this release
[21:27] <clivejo> santa_: what was the reason for modifying git-buildpackage-ppa?
[21:28] <clivejo> for release type?
[21:38] <kfunk> yeah, new website it is. you like it? :)
[21:40] <acheronuk> I like that you get a screenshot of what you are going to get bang straight away.
[21:42] <acheronuk> I've only briefly dabbled with kdevelop in the past, but now there is a decent 5 version I may try more
[21:45] <clivejo> have debian packaged it?
[21:45] <valorie> kfunk: it's awesome!
[21:45] <valorie> very clean and attractive
[21:45] <kfunk> acheronuk: yep. it's very user-oriented now.
[21:45] <kfunk> that was our focus
[21:46] <kfunk> the old one... didn't really have any focus :)
[22:04] <santa_> clivejo: which modification? they are various. if you are speaking in general what I did so far was fixing bugs and making it compatible with the new tooling
[22:05] <santa_> so now it's suposed to work well with depot.kde.org
[22:05] <clivejo> it used to work from any git repo
[22:05] <santa_> and now it doesn't?
[22:05] <clivejo> nope
[22:06] <santa_> which repository?
[22:06] <clivejo> calligra
[22:28] <ahoneybun> wow the KDevelop AppImage works
[22:28] <ahoneybun> built using Frameworks 5.25 and Qt 5.7.0
[22:30] <acheronuk> off to try that. I have the one from blaze's ppa
[22:32] <ahoneybun> guessing this is what they are trying with snaps
[22:33] <acheronuk> 118MB
[22:35] <acheronuk> ah, yes, runs. using fusion Qt widgets, so not the prettiest, but there you go
[22:41] <kfunk> yeah, we didn't include the breeze style, that's something on our todo
 Sorry rik. Internet is like a yoyo tonight and I've had enough of it
[22:44] <acheronuk> clivejo: no probs. staring at compilation errors is probably not my fave thing to do at this time of night anyway :P
 Really gauls me paying £37 a moment for a rubbish connection
[22:47] <acheronuk> gauls me that 3 years ago I saw BT laying fibre 200 yards away, and I still don't have it!
 *kicks stupid predictive text*
 Yeah they are lying bar stewards
[22:48] <santa_> clivejo: thank you very much for reporting  this, please try the fix done here: https://code.launchpad.net/~panfaust/+git/kubuntu-automation/+ref/work3
 They have got millions from local and national government to provide a broadband service and didn't deliver
 Rik would you test that patch?
 Someone turn down the damn linode machine
 It went over 100% cpu
 Well 146% some how
[23:02] <acheronuk> is it still?
 For the last 2 hours
 Lower the jobs on KCI to 150 or something
[23:05] <acheronuk> compiling calligra office on my container probably didn't help
 Yea most likely
[23:05] <acheronuk> though that finished 1hr ago
 (Photo, 720x1280) https://irc-attachments.kde.org/l0270XoA/file_191.jpg
[23:06] <acheronuk> and only just had to reboot container as it went unresponsive a few mins ago
[23:07] <ahoneybun> that might be the reason for the unreponsive
[23:07]  * ahoneybun seems to have forgotten the pw
[23:07] <ahoneybun> unless yofel changed it
[23:08] <acheronuk> yes. as said the compilation fished ok, so if it was my container maxing it out after that, then I have no clue what it was
[23:08] <acheronuk> seems ok now
[23:09] <ahoneybun> just try to limit the KCI jobs a bit please
[23:09] <ahoneybun> I'd rather not blow the machine up lol
[23:10] <acheronuk> KCI was doing nothing much. the scheduled huge job doesn't trigger for another hr
[23:11] <ahoneybun> then what caused the huge CPU use?
[23:12] <acheronuk> pbuilder doing calligra on the actual container I would guess. clive and me were testing a build
[23:13] <acheronuk> but as said, that finished over an hr ago
[23:13] <ahoneybun> mm
[23:13] <acheronuk> so something else odd must have been in play
[23:19] <acheronuk> clivejo: sorry for delay. just testing that git-buildpackage-ppa
[23:22] <acheronuk> clivejo & santa - seemed to download source and build ok with a fresh git clone of calligra
[23:23] <acheronuk> santa_ ^^
 Cool can you push it to ka git please
[23:30] <acheronuk> clivejo: so ok to merge that whole branch?
[23:33] <jbicha> please add bug 1612835 to your todo list
 The merge request above
[23:36] <santa_> acheronuk, clivejo: like rik says there's more stuff in the work3 branch awaiting merge, not just that fix
 #feelathome wow amazing as I am at home *face palms*
 Has it been tested?
[23:37] <santa_> yes, I made a whole rebuild of frameworks/plasma/applications
 In kubuntu workflow?
[23:37] <acheronuk> when I saw how many changes the merge made locally, I stopped
[23:42] <santa_> clivejo: it was tested. what you mean kubuntu workflow?
 How we use the tools
[23:46] <ahoneybun> I love how people file these bugs right before the freeze
[23:47] <santa_> clivejo: well, that's irrelevant. the script in question to bump the build depends was tested
[23:49] <santa_> clivejo: just see the diff of the commits in question please