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