[00:03] -kubuntu-ci:#kubuntu-devel- Project merger_kcoreaddons build #773: FAILURE in 1 min 35 sec: http://kci.pangea.pub/job/merger_kcoreaddons/773/
[00:04] -kubuntu-ci:#kubuntu-devel- Yippee, build fixed!
[00:04] -kubuntu-ci:#kubuntu-devel- Project merger_kdesdk-thumbnailers build #100: FIXED in 2 min 20 sec: http://kci.pangea.pub/job/merger_kdesdk-thumbnailers/100/
[00:05] -kubuntu-ci:#kubuntu-devel- Yippee, build fixed!
[00:05] -kubuntu-ci:#kubuntu-devel- Project merger_kdiamond build #610: FIXED in 2 min 54 sec: http://kci.pangea.pub/job/merger_kdiamond/610/
[00:07] -kubuntu-ci:#kubuntu-devel- Project mgmt_merger build #694: STILL UNSTABLE in 5 min 47 sec: http://kci.pangea.pub/job/mgmt_merger/694/
[00:07] -kubuntu-ci:#kubuntu-devel- Project mgmt_progenitor build #680: STILL UNSTABLE in 5 min 49 sec: http://kci.pangea.pub/job/mgmt_progenitor/680/
[00:08] <tsimonq2> ARGHHHH
[00:08] <tsimonq2> Nightly :(
[00:09] <acheronuk> thought kcoreaddons merge was fixed
[00:16] <tsimonq2> acheronuk: Did you ever see my spreadsheet?
[00:17] <acheronuk> saw, yes, read, no
[00:17] <tsimonq2> acheronuk: Let's keep that up to date until KCI is fully fixed.
[00:18] <acheronuk> got the link again?
[00:18] <tsimonq2> https://docs.google.com/spreadsheets/d/1sDfr6pwLRtaJXkgKJ6WXDLklq6FF47cqtGcTdEUo0S0/edit?usp=sharing
[00:18] <tsimonq2> I can put it in the topic?
[00:19] <tsimonq2> Argh
[00:19] <tsimonq2> bah
[00:20] <tsimonq2> There
[00:20] <tsimonq2> We really need to slim down the topic at one point.
[00:20] <acheronuk> it's getting silly
[00:21] <tsimonq2> Yeah. In fact, let's remove Qt from there...
[00:21] <tsimonq2> THere
[00:21] <tsimonq2> *There
[00:21] <tsimonq2> One less thing to worry about.
[00:23] <tsimonq2> acheronuk: Thoughts on the spreadsheet?
[00:24] -kubuntu-ci:#kubuntu-devel- Project yakkety_unstable_kajongg build #68: STILL FAILING in 14 min: http://kci.pangea.pub/job/yakkety_unstable_kajongg/68/
[00:25] <acheronuk> I can't make up my mind if I think that is a good idea, or slightly OCD
[00:26] <tsimonq2> Lol
[00:26] -kubuntu-ci:#kubuntu-devel- Project xenial_unstable_kajongg build #73: STILL FAILING in 17 min: http://kci.pangea.pub/job/xenial_unstable_kajongg/73/
[00:27] -kubuntu-ci:#kubuntu-devel- Yippee, build fixed!
[00:27] -kubuntu-ci:#kubuntu-devel- Project merger_kcoreaddons build #774: FIXED in 18 sec: http://kci.pangea.pub/job/merger_kcoreaddons/774/
[00:28] <acheronuk> ^^^^ silly glitch on previous failure then
[00:29] <acheronuk> I may give the spreadsheet a go, but I can't guarantee I won't lose patience with it :P
[00:29] <tsimonq2> :P
[00:35] -kubuntu-ci:#kubuntu-devel- Project xenial_unstable_kppp build #9: STILL UNSTABLE in 26 min: http://kci.pangea.pub/job/xenial_unstable_kppp/9/
[00:35] -kubuntu-ci:#kubuntu-devel- Project xenial_unstable_kdesdk-kioslaves build #83: STILL UNSTABLE in 26 min: http://kci.pangea.pub/job/xenial_unstable_kdesdk-kioslaves/83/
[00:35] -kubuntu-ci:#kubuntu-devel- Project yakkety_unstable_kdesdk-kioslaves build #44: STILL UNSTABLE in 26 min: http://kci.pangea.pub/job/yakkety_unstable_kdesdk-kioslaves/44/
[00:37] -kubuntu-ci:#kubuntu-devel- Project yakkety_unstable_kajongg build #69: STILL FAILING in 7 min 13 sec: http://kci.pangea.pub/job/yakkety_unstable_kajongg/69/
[00:37] -kubuntu-ci:#kubuntu-devel- Project xenial_unstable_kajongg build #74: STILL FAILING in 5 min 27 sec: http://kci.pangea.pub/job/xenial_unstable_kajongg/74/
[00:43] -kubuntu-ci:#kubuntu-devel- Yippee, build fixed!
[00:43] -kubuntu-ci:#kubuntu-devel- Project xenial_unstable_palapeli build #32: FIXED in 17 min: http://kci.pangea.pub/job/xenial_unstable_palapeli/32/
[00:43] -kubuntu-ci:#kubuntu-devel- Project yakkety_unstable_kde-runtime build #205: STILL FAILING in 33 min: http://kci.pangea.pub/job/yakkety_unstable_kde-runtime/205/
[00:43] -kubuntu-ci:#kubuntu-devel- Yippee, build fixed!
[00:43] -kubuntu-ci:#kubuntu-devel- Project yakkety_unstable_palapeli build #37: FIXED in 18 min: http://kci.pangea.pub/job/yakkety_unstable_palapeli/37/
[00:44] -kubuntu-ci:#kubuntu-devel- Project yakkety_unstable_kopete build #63: STILL UNSTABLE in 35 min: http://kci.pangea.pub/job/yakkety_unstable_kopete/63/
[00:44] -kubuntu-ci:#kubuntu-devel- Project yakkety_unstable_kppp build #86: STILL UNSTABLE in 35 min: http://kci.pangea.pub/job/yakkety_unstable_kppp/86/
[00:44] -kubuntu-ci:#kubuntu-devel- Project xenial_unstable_kde-runtime build #199: STILL FAILING in 34 min: http://kci.pangea.pub/job/xenial_unstable_kde-runtime/199/
[00:45] -kubuntu-ci:#kubuntu-devel- Project yakkety_unstable_breeze-icons build #174: STILL FAILING in 10 min: http://kci.pangea.pub/job/yakkety_unstable_breeze-icons/174/
[00:47] -kubuntu-ci:#kubuntu-devel- Project xenial_unstable_breeze-icons build #290: STILL FAILING in 11 min: http://kci.pangea.pub/job/xenial_unstable_breeze-icons/290/
[00:51] -kubuntu-ci:#kubuntu-devel- Project yakkety_unstable_kauth build #155: STILL UNSTABLE in 16 min: http://kci.pangea.pub/job/yakkety_unstable_kauth/155/
[00:51] -kubuntu-ci:#kubuntu-devel- Yippee, build fixed!
[00:51] -kubuntu-ci:#kubuntu-devel- Project xenial_unstable_solid build #278: FIXED in 16 min: http://kci.pangea.pub/job/xenial_unstable_solid/278/
[00:51] -kubuntu-ci:#kubuntu-devel- Project xenial_unstable_okular build #19: STILL UNSTABLE in 16 min: http://kci.pangea.pub/job/xenial_unstable_okular/19/
[00:52] -kubuntu-ci:#kubuntu-devel- Project xenial_unstable_kcoreaddons build #265: STILL UNSTABLE in 17 min: http://kci.pangea.pub/job/xenial_unstable_kcoreaddons/265/
[00:52] -kubuntu-ci:#kubuntu-devel- Project xenial_unstable_kopete build #86: STILL UNSTABLE in 43 min: http://kci.pangea.pub/job/xenial_unstable_kopete/86/
[00:55] -kubuntu-ci:#kubuntu-devel- Project yakkety_unstable_breeze-icons build #175: STILL FAILING in 5 min 8 sec: http://kci.pangea.pub/job/yakkety_unstable_breeze-icons/175/
[00:58] -kubuntu-ci:#kubuntu-devel- Project xenial_unstable_breeze-icons build #291: STILL FAILING in 5 min 56 sec: http://kci.pangea.pub/job/xenial_unstable_breeze-icons/291/
[00:59] -kubuntu-ci:#kubuntu-devel- Project yakkety_unstable_okular build #97: STILL UNSTABLE in 24 min: http://kci.pangea.pub/job/yakkety_unstable_okular/97/
[00:59] -kubuntu-ci:#kubuntu-devel- Project yakkety_unstable_kwayland build #72: FAILURE in 24 min: http://kci.pangea.pub/job/yakkety_unstable_kwayland/72/
[00:59] -kubuntu-ci:#kubuntu-devel- Yippee, build fixed!
[00:59] -kubuntu-ci:#kubuntu-devel- Project xenial_unstable_kwidgetsaddons build #299: FIXED in 24 min: http://kci.pangea.pub/job/xenial_unstable_kwidgetsaddons/299/
[00:59] -kubuntu-ci:#kubuntu-devel- Project yakkety_unstable_kdevelop-pg-qt build #20: STILL UNSTABLE in 24 min: http://kci.pangea.pub/job/yakkety_unstable_kdevelop-pg-qt/20/
[01:05] -kubuntu-ci:#kubuntu-devel- Project xenial_unstable_kde-runtime build #200: STILL FAILING in 21 min: http://kci.pangea.pub/job/xenial_unstable_kde-runtime/200/
[01:06] <tsimonq2> acheronuk: ping
[01:12] -kubuntu-ci:#kubuntu-devel- Project xenial_unstable_kcrash build #276: STILL UNSTABLE in 20 min: http://kci.pangea.pub/job/xenial_unstable_kcrash/276/
[01:12] -kubuntu-ci:#kubuntu-devel- Project xenial_unstable_kauth build #283: STILL UNSTABLE in 20 min: http://kci.pangea.pub/job/xenial_unstable_kauth/283/
[01:12] -kubuntu-ci:#kubuntu-devel- Project yakkety_unstable_kde-runtime build #206: STILL FAILING in 29 min: http://kci.pangea.pub/job/yakkety_unstable_kde-runtime/206/
[01:13] -kubuntu-ci:#kubuntu-devel- Project yakkety_unstable_kcrash build #152: STILL UNSTABLE in 20 min: http://kci.pangea.pub/job/yakkety_unstable_kcrash/152/
[01:20] <valorie> spots of green, good to see
[01:26] <tsimonq2> valorie: See our spreadsheet? :D
[01:29] <valorie> yes, has it changed since last night?
[01:30] <valorie> looks like you've made some progress
[01:31] <valorie> I suggest adding the link to a trello card so that those who go there for a task can find it that way
[01:32] -kubuntu-ci:#kubuntu-devel- Project xenial_unstable_kde-runtime build #201: STILL FAILING in 22 min: http://kci.pangea.pub/job/xenial_unstable_kde-runtime/201/
[01:34] <tsimonq2> oh HAYLL no
[01:34] <tsimonq2> [01:34] <tsimonq2> usr/
[01:34] <tsimonq2> >>>>>>> kubuntu_yakkety_archive
[01:34] <tsimonq2> WHO did that?!?
[01:34] <tsimonq2> that's kscreen.install
[01:34] <tsimonq2> clivejo, acheronuk, santa_: fess up ^^^^^^^^^^
[01:36] <tsimonq2> valorie: where in Trello?
[01:39] -kubuntu-ci:#kubuntu-devel- Project yakkety_unstable_kwayland build #73: STILL FAILING in 12 min: http://kci.pangea.pub/job/yakkety_unstable_kwayland/73/
[01:39] -kubuntu-ci:#kubuntu-devel- Project yakkety_unstable_kde-runtime build #207: STILL FAILING in 21 min: http://kci.pangea.pub/job/yakkety_unstable_kde-runtime/207/
[01:41] <valorie> in ToDo I suppose
[01:41] <valorie> https://trello.com/b/lAVvKdKF/kubuntu
[01:42] <valorie> or Doing might be better
[01:42] <tsimonq2> Ok
[01:42] <valorie> is this doubling the ninjas notepad?
[01:44] <valorie> that's my only concern
[01:44] <valorie> One More Place to check, report, keep up
[01:44]  * ahoneybun added a ToDo item
[01:44] <tsimonq2> valorie: Nope, this is more of a WIP TODO list where I think the ninja notepad is more generic.
[01:45] <tsimonq2> Etherpad isn't a good place for this sort of thing
[01:45] <tsimonq2> it would be hell
[01:47] <valorie> ok
[01:48] <valorie> I'm no ninja, so I was just asking
[01:48] <tsimonq2> ok :)
[01:51] <valorie> hey, it's my job
[01:54] <tsimonq2> Yep :P
[02:01] -kubuntu-ci:#kubuntu-devel- Project merger_kcoreaddons build #775: FAILURE in 49 sec: http://kci.pangea.pub/job/merger_kcoreaddons/775/
[02:03] -kubuntu-ci:#kubuntu-devel- Project yakkety_unstable_kwallet build #129: STILL UNSTABLE in 10 min: http://kci.pangea.pub/job/yakkety_unstable_kwallet/129/
[02:04] -kubuntu-ci:#kubuntu-devel- Project xenial_unstable_kwallet build #290: STILL UNSTABLE in 11 min: http://kci.pangea.pub/job/xenial_unstable_kwallet/290/
[02:06] -kubuntu-ci:#kubuntu-devel- Project mgmt_merger build #695: STILL UNSTABLE in 5 min 32 sec: http://kci.pangea.pub/job/mgmt_merger/695/
[02:06] -kubuntu-ci:#kubuntu-devel- Project mgmt_progenitor build #681: STILL UNSTABLE in 5 min 34 sec: http://kci.pangea.pub/job/mgmt_progenitor/681/
[02:15] <ahoneybun> wow 189.5% on that server
[02:17] <valorie> ?
[02:18] <valorie> what server?
[02:19] -kubuntu-ci:#kubuntu-devel- Project xenial_unstable_kdesdk-kioslaves build #84: STILL UNSTABLE in 12 min: http://kci.pangea.pub/job/xenial_unstable_kdesdk-kioslaves/84/
[02:20] <ahoneybun> the linode one
[02:21] <valorie> good
[02:21] <valorie> we gotta use that sucker after giving it all that time off
[02:26] -kubuntu-ci:#kubuntu-devel- Project xenial_unstable_kde-runtime build #202: STILL FAILING in 17 min: http://kci.pangea.pub/job/xenial_unstable_kde-runtime/202/
[02:26] -kubuntu-ci:#kubuntu-devel- Project yakkety_unstable_kdesdk-kioslaves build #45: STILL UNSTABLE in 19 min: http://kci.pangea.pub/job/yakkety_unstable_kdesdk-kioslaves/45/
[02:27] -kubuntu-ci:#kubuntu-devel- Project xenial_unstable_kppp build #10: STILL UNSTABLE in 20 min: http://kci.pangea.pub/job/xenial_unstable_kppp/10/
[02:29] <tsimonq2> yeah LOL
[02:35] -kubuntu-ci:#kubuntu-devel- Project yakkety_unstable_okular build #98: STILL UNSTABLE in 15 min: http://kci.pangea.pub/job/yakkety_unstable_okular/98/
[02:35] -kubuntu-ci:#kubuntu-devel- Project yakkety_unstable_kppp build #87: STILL UNSTABLE in 27 min: http://kci.pangea.pub/job/yakkety_unstable_kppp/87/
[02:45] <tsimonq2> valorie: do you think that for 17.04 we should stick with Plasma 5.8 LTS or go on to Plasma 5.9?
[02:45] <tsimonq2> Just asking for a quick opinion.
[02:46] <tsimonq2> The only concern would be, we would either ship with 5.9.4 or or 5.8.6 LTS
[02:48] <DarinMiller> tsimonq2: Since you are fishing for opinions, I recommend 5.9  since 17.04 is not a LTS release.  We can test each under the Neon releases when the trigger must pulled to decide what's best for KDE.
[02:48] -kubuntu-ci:#kubuntu-devel- Project yakkety_unstable_kopete build #64: STILL UNSTABLE in 40 min: http://kci.pangea.pub/job/yakkety_unstable_kopete/64/
[02:48] -kubuntu-ci:#kubuntu-devel- Project xenial_unstable_okular build #20: STILL UNSTABLE in 21 min: http://kci.pangea.pub/job/xenial_unstable_okular/20/
[02:48] -kubuntu-ci:#kubuntu-devel- Project yakkety_unstable_kde-runtime build #208: STILL FAILING in 39 min: http://kci.pangea.pub/job/yakkety_unstable_kde-runtime/208/
[02:48] -kubuntu-ci:#kubuntu-devel- Project xenial_unstable_kopete build #87: STILL UNSTABLE in 41 min: http://kci.pangea.pub/job/xenial_unstable_kopete/87/
[02:48] <tsimonq2> DarinMiller: Even when we would only ship 5.9.4?
[02:49] <DarinMiller> tsimonq2:  5.9.4 is what I meant....
[02:49] <tsimonq2> DarinMiller: we would miss out on shipping 5.9.5
[02:50]  * DarinMiller searching for plasma road  map....
[02:50] <tsimonq2> https://community.kde.org/Schedules/Plasma_5
[02:51]  * DarinMiller Simon searches are just as fast as google searches :)
[02:52] <DarinMiller> tsimonq2: any way I can help with https://docs.google.com/spreadsheets/d/1sDfr6pwLRtaJXkgKJ6WXDLklq6FF47cqtGcTdEUo0S0/edit#gid=0?
[02:53] <tsimonq2> DarinMiller: What sort of development work have you done so far?
[02:53] <DarinMiller> I know very little about packaging, but I need to jump in and get my feet wet somewhere.  Maybe that's not a good place to start....
[02:53] <tsimonq2> DarinMiller: Sure it is! :)
[02:53] <tsimonq2> DarinMiller: I can help you fix something if you want. :)
[02:54] <tsimonq2> DarinMiller: If you want to get started, read over https://www.debian.org/doc/debian-policy/ to get familiar with the terms, then I can help you fix some things. :)
[02:55] <DarinMiller> warning: I will need lots of help at first.  I attempting to go through all the kde dev. setup guidelines.  But I have never uploaded anything to git (only cloned).
[02:55] <valorie> tsimonq2: for starters, 5.8, obv
[02:55] <valorie> 5.9.x if possible
[02:56] <tsimonq2> valorie: Well of course, but I was just looking over the release schedule so I wanted a quick, not-set-in-stone opinion. :)
[02:56] <valorie> that's my quick
[02:57] <valorie> in 4 months, I've have more information
[02:57] <valorie> :-)
[02:57] <tsimonq2> valorie: Do you think we could convince the release team to let us get 5.9.5 in if we follow the usual SRU procedure? :P
[02:57] <valorie> that depends
[02:57] <valorie> on Qt dependencies
[02:57] <tsimonq2> valorie: Or the Plasma release team to put back the schedule by a few weeks? :P
[02:57] <valorie> on our record with the release team
[02:58] <valorie> and on the Plasma team
[02:58] <tsimonq2> I mean is there any possible way we can shove 5.9.5 in?
[02:58] -kubuntu-ci:#kubuntu-devel- Project xenial_unstable_kcoreaddons build #266: STILL UNSTABLE in 23 min: http://kci.pangea.pub/job/xenial_unstable_kcoreaddons/266/
[02:58] -kubuntu-ci:#kubuntu-devel- Project yakkety_unstable_kdevelop-pg-qt build #21: STILL UNSTABLE in 23 min: http://kci.pangea.pub/job/yakkety_unstable_kdevelop-pg-qt/21/
[02:59] -kubuntu-ci:#kubuntu-devel- Project yakkety_unstable_kauth build #156: STILL UNSTABLE in 23 min: http://kci.pangea.pub/job/yakkety_unstable_kauth/156/
[02:59] -kubuntu-ci:#kubuntu-devel- Project xenial_unstable_kde-runtime build #203: STILL FAILING in 28 min: http://kci.pangea.pub/job/xenial_unstable_kde-runtime/203/
[02:59] <valorie> maybe
[02:59] <valorie> that's quite aways off
[02:59] <tsimonq2> Of course.
[03:01] <valorie> it would be awesome and if we're ready, and everything is already in, I think the last-minute bugfix changes will slide in with no issue
[03:01] <valorie> s
[03:05] <tsimonq2> Ywah
[03:05] <tsimonq2> *Yeah
[03:06] <DarinMiller>  tsimonq2I read through the debian policy several months ago and was impressed by the level of detail/complexity.  What is the safest way to practice ?  Should I attempt to replicate what you did a couple weeks ago in your packaging video?
[03:06] <DarinMiller> There is no way I can remotely do that off the top of my head like you did.
[03:06] <tsimonq2> DarinMiller: First I'd suggest just grabbing the source of several packages and just reading.
[03:07] <tsimonq2> DarinMiller: Read, read, and read some more. :)
[03:07] <tsimonq2> DarinMiller: If you refer to the Debian policy, you can see why packagers made decisions as they did.
[03:08] <tsimonq2> DarinMiller: Remove something, add something, mess with a package. As long as you do it all locally, you're safe, and you can always clone from the repositories again. :)
[03:09] <tsimonq2> DarinMiller: Then once you think you are comfortable enough with identifying what parts of a package do what, try to fix something in KCI. Come here and ask for help, and we'll be more than happy to help you. If we think it's too much (like symbols, like I haven't even mastered yet) then we'lll tell you to pick a different one. :)
[03:09] <tsimonq2> *we'll
[03:11] <DarinMiller> tsimonq2: that's part of my problem.  I have no background with so many parts of the process, I get lost chasing down the tangent topics that are new to me.  I usually end up entirely lost and forget what attempting to learn when I was 1st side tracked.
[03:12] <tsimonq2> DarinMiller: Ask. Ask until you are blue in the face. And I (at the very minimum) can help you understand. :)
[03:14] -kubuntu-ci:#kubuntu-devel- Project yakkety_unstable_kcrash build #153: STILL UNSTABLE in 15 min: http://kci.pangea.pub/job/yakkety_unstable_kcrash/153/
[03:14] -kubuntu-ci:#kubuntu-devel- Project yakkety_unstable_kde-runtime build #209: STILL FAILING in 20 min: http://kci.pangea.pub/job/yakkety_unstable_kde-runtime/209/
[03:14] -kubuntu-ci:#kubuntu-devel- Project xenial_unstable_kcrash build #277: STILL UNSTABLE in 16 min: http://kci.pangea.pub/job/xenial_unstable_kcrash/277/
[03:15] -kubuntu-ci:#kubuntu-devel- Project xenial_unstable_kauth build #284: STILL UNSTABLE in 16 min: http://kci.pangea.pub/job/xenial_unstable_kauth/284/
[03:27] <tsimonq2> valorie: One more thing I want to bounce off of you.
[03:27] <tsimonq2> We look at the existing release schedules and off of that, make our own mini release schedule.
[03:28] <valorie> sounds like an idea, but you should probably bounce it off your fellow packagers
[03:28] <tsimonq2> "Plasma x.y.z was released on Tuesday" "Plasma x.y.z should be ready for testing on Thursday" "Plasma x.y.z will be in backports/archive on the next Monday"
[03:29] <tsimonq2> Ok. :)
[03:29] <valorie> if we get the tooling effective enough
[03:29] <valorie> and people trained to look at the right stuff
[03:29] <valorie> I'm sure it is doable
[03:29] <tsimonq2> valorie: Wouldn't it be awesome if we could just press a button and it would automatically stage into a PPA?
[03:29] <valorie> otoh, testing is key for us
[03:30] <tsimonq2> Yeah, we would then test it.
[03:30] <tsimonq2> But still.
[03:30] <valorie> remember, neon is made for testing
[03:30] <valorie> we test *before* release
[03:31] <tsimonq2> Sometimes bugfixes are released on the same day as it's available to packagers I believe...
[03:31] <tsimonq2> valorie: That's why it would be good to have a release schedule, so we can release on the same day as KDE does.
[03:31] <tsimonq2> WOW that would be awesome.
[03:31] <valorie> we test before *our* releases, I mean
[03:31] <tsimonq2> Well of course that too/
[03:31] <valorie> and yes, we've released hours behind the bugfix releases before
[03:32] <tsimonq2> See, so there you go.
[03:32] <valorie> first, even
[03:32] <valorie> but I'm pretty sure that neon is tooled to always beat us because they do not test with actual testers first
[03:32] <tsimonq2> Well of course.
[03:33] <valorie> but that
[03:33] <tsimonq2> But if it's just a bugfix release, if we carefully scan the diffs and test the part of the packages that were changed, we could go through that in a few hours.
[03:33] <tsimonq2> I don't think we'll beat Neon (and if we do we're SPEEDY)
[03:33] <valorie> s fine
[03:33] <tsimonq2> ?
[03:34] <valorie> i doubt we can ever beat neon
[03:34] <valorie> they have full-time employees on it
[03:35] <tsimonq2> We might once or twice, but still, yeah.
[03:35] <valorie> speed is not our leading value
[03:35] <valorie> quality is
[03:35] <valorie> friendliness is
[03:35] <valorie> if people want to drop by and help, we take time to help them
[03:36] <tsimonq2> That too. :)
[03:36] <tsimonq2> valorie: But if it's just simply a bugfix release, I don't think there's any harm in quickly testing it and getting it out the door if it's a whole team effort.
[03:37] <tsimonq2> And yes, helping is good. ;)
[03:37] <tsimonq2> valorie: One day we should teach you packaging. :P
[03:38] <tsimonq2> One day...
[03:40] <tsimonq2> clivejo, acheronuk, santa_: If we haven't done it already, we can safely remove these KCI jobs:
[03:40] <tsimonq2> * kdegraphics-strigi-analyzer
[03:40] <tsimonq2> * kdenetwork-strigi-analyzers
[03:40] <tsimonq2> * kdepimlibs
[03:40] <tsimonq2> * kdesdk-strigi-analyzers
[03:40] <tsimonq2> * libkdeedu
[03:40] <tsimonq2> * mplayerthumbs
[03:40] <tsimonq2> Maybe I'm just slow on pointing that out there...
[03:41]  * tsimonq2 shrugs
[03:42] <valorie> tsimonq2: when I have some spare hours, I want to learn some basic packaging, so I can improve the packaging docs
[03:42] <valorie> no harm in quick testing as long as it is thorough (well-stated testing scenarios)
[03:42] <tsimonq2> Yeah.
[03:43] <valorie> packagers reading the release notes can often craft those scenarios
[03:44] <tsimonq2> Well of course.
[03:44] <valorie> "fixes x, y, z, and blah-blah"
[03:44] <tsimonq2> Yeah.
[03:44] <valorie> test x, y, z, blah-blah
[03:44] <tsimonq2> Well, I think I'm going to hit the hay.
[03:44] <valorie> but of course any change *could* have unintended consequences
[03:44] <tsimonq2> Good night.
[03:44] <valorie> like our latest
[03:45] <tsimonq2> Yeah of course, totally.
[03:45] <valorie> sweet dreams
[03:45] <tsimonq2> Nini o/
[03:45] <valorie> thanks for poking that fix in, by the way
 No problem, somebody just needed a big poke in the rear... :P
[03:48] <tsimonq2> Just a poke in general
[03:48] -kubuntu-ci:#kubuntu-devel- Project yakkety_unstable_kwallet build #130: STILL UNSTABLE in 9 min 59 sec: http://kci.pangea.pub/job/yakkety_unstable_kwallet/130/
[03:48] -kubuntu-ci:#kubuntu-devel- Project xenial_unstable_kwallet build #291: STILL UNSTABLE in 9 min 52 sec: http://kci.pangea.pub/job/xenial_unstable_kwallet/291/
[04:26] -kubuntu-ci:#kubuntu-devel- Project yakkety_unstable_minuet build #27: STILL FAILING in 8 min 56 sec: http://kci.pangea.pub/job/yakkety_unstable_minuet/27/
[04:37] -kubuntu-ci:#kubuntu-devel- Project yakkety_unstable_minuet build #28: STILL FAILING in 5 min 43 sec: http://kci.pangea.pub/job/yakkety_unstable_minuet/28/
[04:39] -kubuntu-ci:#kubuntu-devel- Project xenial_unstable_minuet build #23: STILL FAILING in 12 min: http://kci.pangea.pub/job/xenial_unstable_minuet/23/
[04:51] -kubuntu-ci:#kubuntu-devel- Project xenial_unstable_minuet build #24: STILL FAILING in 6 min 47 sec: http://kci.pangea.pub/job/xenial_unstable_minuet/24/
[04:53] -kubuntu-ci:#kubuntu-devel- Project yakkety_unstable_spectacle build #86: STILL UNSTABLE in 18 min: http://kci.pangea.pub/job/yakkety_unstable_spectacle/86/
[05:09] -kubuntu-ci:#kubuntu-devel- Project yakkety_unstable_umbrello build #78: STILL UNSTABLE in 16 min: http://kci.pangea.pub/job/yakkety_unstable_umbrello/78/
[05:09] -kubuntu-ci:#kubuntu-devel- Project xenial_unstable_spectacle build #107: STILL UNSTABLE in 14 min: http://kci.pangea.pub/job/xenial_unstable_spectacle/107/
[05:17] -kubuntu-ci:#kubuntu-devel- Project yakkety_unstable_plasma-framework build #148: STILL FAILING in 7 min 4 sec: http://kci.pangea.pub/job/yakkety_unstable_plasma-framework/148/
[05:23] -kubuntu-ci:#kubuntu-devel- Project xenial_unstable_umbrello build #93: STILL UNSTABLE in 22 min: http://kci.pangea.pub/job/xenial_unstable_umbrello/93/
[05:23] -kubuntu-ci:#kubuntu-devel- Project xenial_unstable_kstars build #258: STILL UNSTABLE in 22 min: http://kci.pangea.pub/job/xenial_unstable_kstars/258/
[05:30] -kubuntu-ci:#kubuntu-devel- Project xenial_unstable_plasma-framework build #283: FAILURE in 5 min 51 sec: http://kci.pangea.pub/job/xenial_unstable_plasma-framework/283/
[05:30] -kubuntu-ci:#kubuntu-devel- Project yakkety_unstable_plasma-framework build #149: STILL FAILING in 7 min 54 sec: http://kci.pangea.pub/job/yakkety_unstable_plasma-framework/149/
[05:30] -kubuntu-ci:#kubuntu-devel- Project yakkety_unstable_ktp-common-internals build #135: STILL UNSTABLE in 21 min: http://kci.pangea.pub/job/yakkety_unstable_ktp-common-internals/135/
[05:31] -kubuntu-ci:#kubuntu-devel- Project yakkety_unstable_kstars build #126: STILL UNSTABLE in 38 min: http://kci.pangea.pub/job/yakkety_unstable_kstars/126/
[05:37] -kubuntu-ci:#kubuntu-devel- Project xenial_unstable_ktp-common-internals build #209: STILL UNSTABLE in 13 min: http://kci.pangea.pub/job/xenial_unstable_ktp-common-internals/209/
[05:44] -kubuntu-ci:#kubuntu-devel- Project xenial_unstable_plasma-framework build #284: STILL FAILING in 8 min 54 sec: http://kci.pangea.pub/job/xenial_unstable_plasma-framework/284/
[05:44] -kubuntu-ci:#kubuntu-devel- Project xenial_unstable_okteta build #115: STILL UNSTABLE in 35 min: http://kci.pangea.pub/job/xenial_unstable_okteta/115/
[05:44] -kubuntu-ci:#kubuntu-devel- Project yakkety_unstable_ktp-auth-handler build #136: STILL UNSTABLE in 13 min: http://kci.pangea.pub/job/yakkety_unstable_ktp-auth-handler/136/
[05:45] -kubuntu-ci:#kubuntu-devel- Project yakkety_unstable_plasma-pa build #104: STILL FAILING in 14 min: http://kci.pangea.pub/job/yakkety_unstable_plasma-pa/104/
[05:45] -kubuntu-ci:#kubuntu-devel- Project yakkety_unstable_kirigami build #39: STILL UNSTABLE in 14 min: http://kci.pangea.pub/job/yakkety_unstable_kirigami/39/
[05:45] -kubuntu-ci:#kubuntu-devel- Project yakkety_unstable_plasma-mediacenter build #103: NOW UNSTABLE in 14 min: http://kci.pangea.pub/job/yakkety_unstable_plasma-mediacenter/103/
[05:45] -kubuntu-ci:#kubuntu-devel- Project yakkety_unstable_plasma-nm build #119: STILL FAILING in 14 min: http://kci.pangea.pub/job/yakkety_unstable_plasma-nm/119/
[05:50] -kubuntu-ci:#kubuntu-devel- Project yakkety_unstable_libkgeomap build #3: STILL FAILING in 5 min 21 sec: http://kci.pangea.pub/job/yakkety_unstable_libkgeomap/3/
[05:51] -kubuntu-ci:#kubuntu-devel- Project xenial_unstable_ktp-auth-handler build #183: STILL UNSTABLE in 13 min: http://kci.pangea.pub/job/xenial_unstable_ktp-auth-handler/183/
[05:51] -kubuntu-ci:#kubuntu-devel- Project xenial_unstable_libkcompactdisc build #49: STILL UNSTABLE in 14 min: http://kci.pangea.pub/job/xenial_unstable_libkcompactdisc/49/
[05:57] -kubuntu-ci:#kubuntu-devel- Project yakkety_unstable_akonadi-calendar build #4: STILL UNSTABLE in 12 min: http://kci.pangea.pub/job/yakkety_unstable_akonadi-calendar/4/
[05:57] -kubuntu-ci:#kubuntu-devel- Project yakkety_unstable_plasma-integration build #4: STILL UNSTABLE in 12 min: http://kci.pangea.pub/job/yakkety_unstable_plasma-integration/4/
[05:57] -kubuntu-ci:#kubuntu-devel- Project xenial_unstable_kirigami build #35: STILL UNSTABLE in 13 min: http://kci.pangea.pub/job/xenial_unstable_kirigami/35/
[05:57] -kubuntu-ci:#kubuntu-devel- Project xenial_unstable_plasma-mediacenter build #186: NOW UNSTABLE in 13 min: http://kci.pangea.pub/job/xenial_unstable_plasma-mediacenter/186/
[05:58] -kubuntu-ci:#kubuntu-devel- Project xenial_unstable_plasma-nm build #214: STILL FAILING in 13 min: http://kci.pangea.pub/job/xenial_unstable_plasma-nm/214/
[05:58] -kubuntu-ci:#kubuntu-devel- Project yakkety_unstable_plasma-sdk build #122: STILL UNSTABLE in 13 min: http://kci.pangea.pub/job/yakkety_unstable_plasma-sdk/122/
[05:58] -kubuntu-ci:#kubuntu-devel- Project xenial_unstable_kwin build #3: STILL FAILING in 1 min 19 sec: http://kci.pangea.pub/job/xenial_unstable_kwin/3/
[05:58] -kubuntu-ci:#kubuntu-devel- Project yakkety_unstable_plasma-workspace build #7: STILL FAILING in 1 min 20 sec: http://kci.pangea.pub/job/yakkety_unstable_plasma-workspace/7/
[06:01] -kubuntu-ci:#kubuntu-devel- Project xenial_unstable_libkgeomap build #3: STILL FAILING in 4 min 21 sec: http://kci.pangea.pub/job/xenial_unstable_libkgeomap/3/
[06:02] -kubuntu-ci:#kubuntu-devel- Project yakkety_unstable_libkgeomap build #4: STILL FAILING in 6 min 51 sec: http://kci.pangea.pub/job/yakkety_unstable_libkgeomap/4/
[06:03] -kubuntu-ci:#kubuntu-devel- Project yakkety_unstable_plasma-pa build #105: STILL FAILING in 13 min: http://kci.pangea.pub/job/yakkety_unstable_plasma-pa/105/
[06:04] -kubuntu-ci:#kubuntu-devel- Project xenial_unstable_plasma-integration build #4: STILL UNSTABLE in 7 min 0 sec: http://kci.pangea.pub/job/xenial_unstable_plasma-integration/4/
[06:04] -kubuntu-ci:#kubuntu-devel- Project yakkety_unstable_plasma-nm build #120: STILL FAILING in 13 min: http://kci.pangea.pub/job/yakkety_unstable_plasma-nm/120/
[06:04] -kubuntu-ci:#kubuntu-devel- Project yakkety_unstable_plasma-workspace build #8: STILL FAILING in 55 sec: http://kci.pangea.pub/job/yakkety_unstable_plasma-workspace/8/
[06:04] -kubuntu-ci:#kubuntu-devel- Project xenial_unstable_kwin build #4: STILL FAILING in 52 sec: http://kci.pangea.pub/job/xenial_unstable_kwin/4/
[06:05] -kubuntu-ci:#kubuntu-devel- Project xenial_unstable_plasma-workspace build #7: STILL FAILING in 51 sec: http://kci.pangea.pub/job/xenial_unstable_plasma-workspace/7/
[06:11] -kubuntu-ci:#kubuntu-devel- Project xenial_unstable_plasma-workspace build #8: STILL FAILING in 45 sec: http://kci.pangea.pub/job/xenial_unstable_plasma-workspace/8/
[06:12] -kubuntu-ci:#kubuntu-devel- Project xenial_unstable_libkgeomap build #4: STILL FAILING in 5 min 17 sec: http://kci.pangea.pub/job/xenial_unstable_libkgeomap/4/
[06:12] -kubuntu-ci:#kubuntu-devel- Project xenial_unstable_plasma-sdk build #228: STILL UNSTABLE in 14 min: http://kci.pangea.pub/job/xenial_unstable_plasma-sdk/228/
[06:18] -kubuntu-ci:#kubuntu-devel- Project xenial_unstable_discover build #3: STILL FAILING in 6 min 5 sec: http://kci.pangea.pub/job/xenial_unstable_discover/3/
[06:22] -kubuntu-ci:#kubuntu-devel- Project yakkety_unstable_discover build #4: STILL UNSTABLE in 18 min: http://kci.pangea.pub/job/yakkety_unstable_discover/4/
[06:22] -kubuntu-ci:#kubuntu-devel- Project xenial_unstable_plasma-nm build #215: STILL FAILING in 19 min: http://kci.pangea.pub/job/xenial_unstable_plasma-nm/215/
[06:28] -kubuntu-ci:#kubuntu-devel- Project xenial_unstable_discover build #4: STILL FAILING in 4 min 57 sec: http://kci.pangea.pub/job/xenial_unstable_discover/4/
[06:29] -kubuntu-ci:#kubuntu-devel- Project xenial_unstable_akonadi-contacts build #40: STILL UNSTABLE in 25 min: http://kci.pangea.pub/job/xenial_unstable_akonadi-contacts/40/
[06:36] -kubuntu-ci:#kubuntu-devel- Project yakkety_unstable_pimcommon build #3: STILL FAILING in 15 min: http://kci.pangea.pub/job/yakkety_unstable_pimcommon/3/
[06:42] <Mirv> acheronuk: yeah unfortunately since I don't have too many work weeks left this year and I'm currently eg firefighting on arm64 QML issues and need to work on 5.6.2 too. it will be fast in January if 5.7.1 doesn't break anything anywhere... 5.7.0 just segfaulted with qmlplugindump for me all over
[06:54] -kubuntu-ci:#kubuntu-devel- Project xenial_unstable_pimcommon build #3: STILL FAILING in 17 min: http://kci.pangea.pub/job/xenial_unstable_pimcommon/3/
[07:00] <acheronuk> Mirv: understood. you are a hero taking that on each cycle
[07:01] -kubuntu-ci:#kubuntu-devel- Project yakkety_unstable_pimcommon build #4: STILL FAILING in 19 min: http://kci.pangea.pub/job/yakkety_unstable_pimcommon/4/
[07:18] -kubuntu-ci:#kubuntu-devel- Project yakkety_unstable_mailcommon build #3: STILL FAILING in 3 min 50 sec: http://kci.pangea.pub/job/yakkety_unstable_mailcommon/3/
[07:27] -kubuntu-ci:#kubuntu-devel- Project yakkety_unstable_mailcommon build #4: STILL FAILING in 3 min 51 sec: http://kci.pangea.pub/job/yakkety_unstable_mailcommon/4/
[07:30] -kubuntu-ci:#kubuntu-devel- Project xenial_unstable_pimcommon build #4: STILL FAILING in 31 min: http://kci.pangea.pub/job/xenial_unstable_pimcommon/4/
[07:48] -kubuntu-ci:#kubuntu-devel- Project xenial_unstable_mailcommon build #3: STILL FAILING in 3 min 47 sec: http://kci.pangea.pub/job/xenial_unstable_mailcommon/3/
[07:58] -kubuntu-ci:#kubuntu-devel- Project xenial_unstable_mailcommon build #4: STILL FAILING in 4 min 45 sec: http://kci.pangea.pub/job/xenial_unstable_mailcommon/4/
[08:42] <jimarvan> γοοδ μορνινγ!
[08:43] <jimarvan> oops... good morning! :)
[08:45] <acheronuk> lol. morning :)
 Good Morning
[10:16] <acheronuk> Morning Rick :)
[10:52] <acheronuk> clivejo: maybe a bit early for this, but please remember the git for discover
[10:52] <clivejo> acheronuk: Im lost and confused
[10:53] <clivejo> https://code.launchpad.net/~kubuntu-packagers/+git
[10:53] <clivejo> what happened 9-10 hours ago?
[10:53] <acheronuk> seems Simon pushed yakkety_archive to master for most repos?
 Hai
 Yup
[10:54]  * clivejo face palms
 As discussed
[10:54] <clivejo> I thought I said before I went to bed, not to push to git
 :/
 You did?!?
[10:55] <clivejo> a few times
 Does it really matter now?
[10:57] <clivejo> yes, we all use those repos
[10:57] <clivejo> and need to kn ow what state they are in
[10:57] <clivejo> what have you done?
[10:57] <acheronuk> [23:33] <clivejo> dont push anything to the LP repos until we have a chance to look at it
[10:57] <clivejo> did any of them fail the merge?
 A lot actually
 Like 10 of them
[10:58] <clivejo> whats being done to fix the failed merges
 I fixed a few of them by hand
 But there's a few that I would rather have you or Rik mess with
[11:00] <clivejo> what about non fw, plasma, apps packages?
[11:00] <clivejo> they dont appear to have been done?
[11:00] <clivejo> also, what have you done with KCI nightly trigger
 I just used git-clone-all, that didn't do everything?
[11:01] <clivejo> its no longer starting at 00:00 UTC
 Kicked it forward the night before last night because I was working on stuff and needed an empty queue, and I thought you put it back because things started at 7 like usual
[11:03] <clivejo> what?
 What about it?
[11:03] <clivejo> on the 17th it triggered at 03:01 UTC
[11:04] <clivejo> on 18th 02:01 UTC
 Oh, then I need to set that bakc I guess.
 *back
[11:04] <clivejo> but why change it at all
[11:04] <acheronuk> I had to manually start it last night as I thought the timer was broken
 Because I was working on jobs at midnight server time on Sunday
 And I intentionally didn't want it to go off then
 I needed an empty queue
 clivejo: you set it back?
[11:07] <clivejo> no, I didnt change it!
 Look, I gotta get ready for school
 I'll do it tonight then I guess
[11:09] <clivejo> please just think about things before you do them, they have consequences for us all
[11:11] <acheronuk> tsimonq2: you asked the other day if we could change the time to 3 hrs later. it was said/decided no. then we find that it seems you went and did it anyway.
[11:11] <acheronuk> think about how that looks, even if your intentions were good :)
[11:13] <clivejo> I also stated a few times last night, not to push back to LP git and again you ignored my advice
[11:14] <clivejo> and now Ive wasted time looking into what the flute it going on, and am pretty miffed off right now
[11:16] <clivejo> is there another channel for the SRU team?
[11:20] <acheronuk> not sure, but SRU team should see any upload in due course as it would get added to http://people.canonical.com/~ubuntu-archive/pending-sru
[11:21] <acheronuk> or ask in #ubuntu-release as you just did :)
 pretend there is a devel update coming :)
[11:28] <acheronuk> yep, that is more or less what I thought. when the archive is in limbo like that
[11:30] <clivejo> acheronuk: can you remind me about git later?
[11:30] <clivejo> you could be my PA :P
[11:31] <acheronuk> I would not make a good PA :P
[11:31] <acheronuk> but yes, I will remind you. if I remember myself.....
[11:32] <clivejo> want to get yakkety sorted first
[11:32] <clivejo> get it uploaded
[11:33] <clivejo> and then make sure git is updated
[11:33] <clivejo> I was unsure of the version which is why I been holding off
[11:35] <acheronuk> I was reasonably sure, but still pays to ask
[11:38] <clivejo> ooo
[11:39] <clivejo> need to glue the wig down
[11:39] <acheronuk> huh?
[11:39] <clivejo> getting windy!
[11:39] <clivejo> https://www.windytv.com/?56.849,-4.438,4
[11:39] <clivejo> look at that beast to the west of me!
[11:41] <acheronuk> remains of yet another hurricane I think?
[11:41] <clivejo> pulling down cold air
[11:41] <acheronuk> Hurricane Nicole
[11:42] <clivejo> where did Matthew go?
[11:42] <acheronuk> dunno. sex change?
[11:43] <clivejo> maybe
[11:43] <clivejo> spinning the other direction?
[11:43] <acheronuk> lol
[11:44] <clivejo> see, this is what happens when you make assumptions!
[11:44] <acheronuk> British press being their usual responsible alarmist selves http://www.express.co.uk/news/weather/722165/Hurricane-Nicole-UK-sea-surge-flood-alert-weather-warning
[11:46] <clivejo> ewww
[11:46] <clivejo> WATCH: Expert doctor squeezes ENORMOUS ‘cheesy’ cyst from woman’s back
[11:46] <acheronuk> ick!
[12:52] -kubuntu-ci:#kubuntu-devel- Project yakkety_unstable_plasma-workspace build #9: STILL FAILING in 7 min 3 sec: http://kci.pangea.pub/job/yakkety_unstable_plasma-workspace/9/
[12:53] -kubuntu-ci:#kubuntu-devel- Project xenial_unstable_plasma-workspace build #9: STILL FAILING in 7 min 27 sec: http://kci.pangea.pub/job/xenial_unstable_plasma-workspace/9/
[13:05] -kubuntu-ci:#kubuntu-devel- Project xenial_unstable_plasma-workspace build #10: STILL FAILING in 6 min 59 sec: http://kci.pangea.pub/job/xenial_unstable_plasma-workspace/10/
[13:05] -kubuntu-ci:#kubuntu-devel- Project yakkety_unstable_plasma-workspace build #10: STILL FAILING in 7 min 32 sec: http://kci.pangea.pub/job/yakkety_unstable_plasma-workspace/10/
[13:17] <clivejo> acheronuk: ping
[13:18] <acheronuk> clivejo: pong
[13:18] <clivejo> I uploaded a test package for plasma-discover to my PPA - https://launchpad.net/~clivejo/+archive/ubuntu/yakkety/
[13:18] <clivejo> but its failing on the i386 build
[13:19] <clivejo> oh, never mind
[13:19] <clivejo> thats not good!
[13:20] <clivejo> I had kci unstable PPA enabled!
[13:21] <acheronuk> that would do it!
[13:21] <clivejo> wonder how long I have to wait before the package deletion takes affect
[13:27] -kubuntu-ci:#kubuntu-devel- Project yakkety_unstable_kwayland build #74: STILL FAILING in 14 min: http://kci.pangea.pub/job/yakkety_unstable_kwayland/74/
[13:27] <acheronuk> pick a random number between 1 & 120 minutes
[13:30] <clivejo> does it disappear from the PPA ?
[13:30] <clivejo> https://launchpad.net/~clivejo/+archive/ubuntu/yakkety/+packages?field.name_filter=discover&field.status_filter=&field.series_filter=
[13:30] <clivejo> Removal requested 5 minutes ago.
[13:31] <acheronuk> before soee_ gets here :P https://www.kde.org/announcements/plasma-5.8.2.php
[13:31] <clivejo> LOL
[13:33]  * clivejo giggles
[13:33] <clivejo> https://git.launchpad.net/~kubuntu-packagers/kubuntu-packaging/+git/plasma-workspace/commit/?id=aeba9a5b4a532ef5e3ea53314833b97d802b6c14
[13:34] <acheronuk> took me a while to twig to the commit message! lol
[13:46] -kubuntu-ci:#kubuntu-devel- Project yakkety_unstable_kwayland build #75: STILL FAILING in 14 min: http://kci.pangea.pub/job/yakkety_unstable_kwayland/75/
[14:05] <sheytan> heya
[14:05] <sheytan> http://imgur.com/iIYoYG1
[14:05] <sheytan> what's worng? :D
[14:08] <mamarley> sheytan: https://launchpad.net/bugs/1633692 ?
[14:09] -kubuntu-ci:#kubuntu-devel- Project yakkety_unstable_kwayland build #76: STILL FAILING in 10 min: http://kci.pangea.pub/job/yakkety_unstable_kwayland/76/
[14:11] <acheronuk> yes, it will also impact launching the kde release upgrade backend via the command line
[14:17] <sheytan> not a big deal. Doing the upgrade via konsole
[14:32] -kubuntu-ci:#kubuntu-devel- Project yakkety_unstable_kwayland build #77: ABORTED in 18 min: http://kci.pangea.pub/job/yakkety_unstable_kwayland/77/
[14:56] -kubuntu-ci:#kubuntu-devel- Yippee, build fixed!
[14:56] -kubuntu-ci:#kubuntu-devel- Project yakkety_unstable_kwayland build #78: FIXED in 23 min: http://kci.pangea.pub/job/yakkety_unstable_kwayland/78/
[15:16] -kubuntu-ci:#kubuntu-devel- Project xenial_unstable_plasma-workspace build #11: STILL FAILING in 43 min: http://kci.pangea.pub/job/xenial_unstable_plasma-workspace/11/
[15:36] -kubuntu-ci:#kubuntu-devel- Project yakkety_unstable_plasma-workspace build #11: STILL FAILING in 40 min: http://kci.pangea.pub/job/yakkety_unstable_plasma-workspace/11/
[15:45] -kubuntu-ci:#kubuntu-devel- Yippee, build fixed!
[15:45] -kubuntu-ci:#kubuntu-devel- Project xenial_unstable_plasma-workspace build #12: FIXED in 27 min: http://kci.pangea.pub/job/xenial_unstable_plasma-workspace/12/
[15:58] -kubuntu-ci:#kubuntu-devel- Yippee, build fixed!
[15:58] -kubuntu-ci:#kubuntu-devel- Project yakkety_unstable_plasma-workspace build #12: FIXED in 21 min: http://kci.pangea.pub/job/yakkety_unstable_plasma-workspace/12/
[18:44]  * acheronuk yawns
[18:52] <ahoneybun> oh LP tried to build kubuntu-web-shortcuts
[18:53] <ahoneybun> for zesty
[18:53] <ahoneybun> ZZ
[19:11] <acheronuk> clivejo: reminder about pushing plasma-discover to git :P
[19:11] <acheronuk> ahoneybun: not quite sure what you are saying there
[19:15] <ahoneybun> acheronuk: https://launchpadlibrarian.net/289963393/buildlog_ubuntu-zesty-amd64.kubuntu-web-shortcuts_16.10.0_BUILDING.txt.gz
[19:25] <acheronuk> ummmm. looking for a .pm midule in pkg-kde-tools that was depreciated and merged into other parts at the beginning of Xenial I think?
[19:25] <acheronuk> *module
[19:26] <ahoneybun> yea
[19:26] <ahoneybun> translation stuff
[19:28] <ahoneybun> someone fixed something in it in a bug report during Yakkety
[20:22] <ahoneybun> valorie: http://imgur.com/a/vLqiq
[20:22] <ahoneybun> ;)
[20:25] <acheronuk> something odd about the beak on that :/
[20:26] <acheronuk> with a bit of tweaking that could be very cool
[20:28] <ahoneybun> first draft so you know lol
[20:28] <ahoneybun> always could be improved
[20:28] <ahoneybun> the creator of it loves it though
[20:29] <acheronuk> I saw the post somewhere one the old linux tux being outdated
[20:30] <acheronuk> *on the
[20:30] <ahoneybun> maybe omgubuntu?
[20:30] <ahoneybun> I mean I do love a clean design
[20:30] <ahoneybun> one reason I really like Plasma 5
[20:31] <acheronuk> possibly. I have too many feeds to remember right now
[20:31] <ahoneybun> lol
[20:32] <acheronuk> so do I.was why I liked that kubuntu sticker I found. simple and clean but looked great
[20:33] <acheronuk> I am *carp at design, but I hope I can at least recognise good ones from others
[20:33] <ahoneybun> mm I want to make a zombie one
[20:34] <acheronuk> kubuntu/linux Halloween edition
[20:35] <ahoneybun> XD
[20:35] <acheronuk> if ZZ had been something Zombie, we could have had so much fun with that! :)
[20:37] <valorie> uh, what is the creature supposed to be? a penguin?
[20:37] <valorie> sorry, today is my prep day for tomorrow's colonoscopy so I'll be on and off here without notice
[20:38] <valorie> lol
[20:38] <ahoneybun> yep a penguin
[20:38] <valorie> nice and simple
[20:38] <valorie> but the staring eyes make it a big ghostly too
[20:38] <acheronuk> but sill slightly malformed
[20:39] <valorie> maybe it needs feet
[20:39] <ahoneybun> valorie: are we giving out 16.04 or 16.10 iso at seagl?
[20:40] <valorie> we'll burn whatever people want IMO
[20:40] <valorie> there are not many people wanting ISOs there however
[20:40] <acheronuk> is there an svg of that logo?
[20:40] <valorie> at least there were not last year
[20:40] <ahoneybun> oh then there is no reason to make those covers
[20:40] <valorie> ahoneybun: people will take covers omg yet
[20:40] <valorie> yes
[20:40] <clivejo> cute wee kubuntu USB with Kubuntu on it, I want one!"
[20:40] <ahoneybun> dear god
[20:41] <acheronuk> clivejo: push discover to git
[20:41] <clivejo> like the wee ubuntu ones at Akademy
[20:41]  * ahoneybun wishes the design team would get off the damn PSD
[20:41] <valorie> you can get them printed locally if you want and have me pick them up
[20:41]  * acheronuk has done his PA job
[20:41] <clivejo> grrrr
[20:41] <clivejo> totally went out of my mind
[20:42] <clivejo> lot has happened since then!
[20:42] <valorie> clivejo: we investigated making usb keys and it was either too expensive or too fiddly
[20:42] <clivejo> how do ubuntu do it?
[20:42] <ahoneybun> lots of fault units
[20:42] <valorie> too expensive if you have them write 'em
[20:42] <ahoneybun> and money
[20:42] <valorie> too fiddly if we have to do it
[20:42] <acheronuk> seems a bit 2014
[20:43] <ahoneybun> tbh I know someone who could write them
[20:43] <ahoneybun> he writes a ton for work
[20:43] <valorie> giveaway thumb drives are usually crap
[20:43] <clivejo> what about Id like some blue usb sticks with kubuntu logo on it
[20:43] <ahoneybun> has a setup to format 20-30 at a time
[20:43] <ahoneybun> valorie: ^
[20:43] <clivejo> especially the new logo CRogers made
[20:43] <ahoneybun> what logo?
[20:43]  * clivejo likes the clean crispness of it
[20:44] <ahoneybun> would we be allowed to use the konqi on printed material?
[20:44] <acheronuk> the smoothing out of the wobbly bits on the gears
[20:44] <acheronuk> that? ^^
[20:45] <clivejo> yes
[20:45] <acheronuk> ok, I didn't another new logo then
[20:45] <acheronuk> didn't miss
[20:47] <valorie> I wish I could get those on the tiny stickers for the "win" key
[20:47] <valorie> but now I have a few expensive KDE ones so whatever
[20:48]  * acheronuk looks at his laptop stickers
[20:48] <acheronuk> whoops!
[20:48] <clivejo> http://whitecatgraphics.com/opendesignstudio/free_graphics/kubuntu/kubuntu_gear_logo_fix.svg
[20:50] <acheronuk> that does look great
[20:50] <ahoneybun> that's the default one though
[20:51] <clivejo> no thats the fixed one
[20:51] <ahoneybun> looks the same as the old one
[20:52] <clivejo> put it side by side
[20:52] <ahoneybun> no same one
[20:52] <valorie> hmmm, I can't enlarge that one
[20:52] <valorie> that's where you really see the diff
[20:52] <ahoneybun> http://imgur.com/a/cd6J0
[20:53] <ahoneybun> just messing around
[20:53] <acheronuk> the old has oddly curved lines on the gear teeth when zoomed in
[20:54]  * clivejo slaps aaron with a potato masher
[20:54] <ahoneybun> XD
[20:56] <ahoneybun> why this time clivejo?
[20:56] <clivejo> this time?
[20:56] <ahoneybun> well why with a potato masher though?
[20:57] <clivejo> oh
[20:57] <clivejo> you didnt hear about Phil being handed a potato masher as a key?
[20:57] <ahoneybun> why do I need a key then?
[20:57] <clivejo> when we went to pickup his and Ovi's bag?
[20:58] <clivejo> I dunno, just first think popped into my head
[20:58] <clivejo> thing
[20:58] <ahoneybun> mm odd
[20:58] <ahoneybun> might be thinking I'm Simon
[20:59] <ahoneybun> XD
[20:59] <clivejo> I could have beaten him to a bloody pulp this morning with it
[21:00] <clivejo> but Ive calmed down a bit
[21:00] <ahoneybun> oh dear
[21:00] <clivejo> mashed Simon
[21:00] <tsimonq2> clivejo: Thanks. :(
[21:00] <ahoneybun> mm I'd really like to know who keeps trying to log into my blog
[21:01] <clivejo> ahoneybun: probably hackers
[21:01] <ahoneybun> keeps locking me out for 20+ hours
[21:01] <clivejo> do you have a static IP?
[21:01] <ahoneybun> I should turn off the locking
[21:01] <ahoneybun> a domain yes
[21:01] <clivejo> did Simon just storm off?
[21:01] <ahoneybun> seems like it
[21:04]  * ahoneybun needs a new chair badly
[21:09] <valorie> simon had to got to school!
[21:11] <valorie> heh: http://blog.dustinkirkland.com/2016/10/canonical-livepatch.html
[21:11] <valorie> sounds pretty cool for servers
[22:39] <ahoneybun> acheronuk or clivejo what packages from KF5 are needed for an app?
[22:39] <ahoneybun> https://github.com/KDE/minuet
[22:39] <ahoneybun> this app in this case
[22:39] <clivejo> look in the control file
[22:40] <ahoneybun> it's not a debian package
[22:40] <clivejo> it is :/
[22:40] <clivejo> apps
[22:40] <ahoneybun> it's not in p.u.com
[22:40] <clivejo> oh, yeah
[22:40] <clivejo> it didnt get into yakkety
[22:41] <clivejo> https://code.launchpad.net/~kubuntu-packagers/kubuntu-packaging/+git/minuet
[22:41] <clivejo> its in staging if you wanted it
[22:41] <ahoneybun> trying to snap it
[22:42] <clivejo> https://launchpad.net/~kubuntu-ppa/+archive/ubuntu/staging-kdeapplications/+packages?field.name_filter=minuet&field.status_filter=published&field.series_filter=yakkety
[22:42] <clivejo> it needs an updated libdrumstick
[22:42] <ahoneybun> that we don't have?
[22:42] <clivejo> dont ask, its a sorry subject#
[22:43] <acheronuk> oh. that package!
[22:43] <ahoneybun> my bad
[22:43]  * ahoneybun rides off
[22:43] <clivejo> LP 1584310
[22:44] <acheronuk> "thoughtfully designed to push your musical skills to the next level."
[22:45] <acheronuk> you probably need some "skills" in the first place, which I definitely don't have!
[22:45] <clivejo> yup
[22:46] <clivejo> I tried to use it, but didnt understand what it was saying!
[22:46] <valorie> http://www.portalprogramas.com/software-libre/premios/proyecto/Minuet
[22:46] <valorie> it's relatively new, and we should try to get it in
[22:47] <acheronuk> will they sync a new enough librumstick from debian this time?
[22:47] <clivejo> strangely I got more questions wrong than statistically I should have
[22:47] <clivejo> acheronuk: I have no idea!
[22:48] <valorie> https://minuet.kde.org/
[22:48] <clivejo> and as I said to Simon, Im not paid enough to care!
[22:51] <acheronuk> true. it is hard to care about everything when it's not really your thing
[22:52] <clivejo> https://bugs.launchpad.net/ubuntu/+source/plasma-discover/+bug/1633692/comments/7
[22:52] <clivejo> oh hes left
[22:55] <valorie> oooo, flames_in_paradise is back
[22:55] <valorie> sgclark: ^^^
[22:56] <clivejo> shadeslayer sgclark ScottK yofel could you give your thoughts on the above comment?
[22:57] <valorie> "Adding a dependency to Discover that it doesn't need at all" I don't understand
[22:57] <valorie> it needs it to work, right?
[22:58] <acheronuk> that is why I initially said maybe another package when I reported.
[22:58] <valorie> and what else would need it?
[22:58] <yofel> read it as in "does discover actually open the upgrader or does something else?"
[22:58] <acheronuk> but the upgrade button on discover does NOT work without it
[22:58] <yofel> then it's at least a recommends, and for the SRU it's ~fine IMO
[22:59] <yofel> you can find a proper fix in the dev release upload
[22:59] <acheronuk> discover launches the command in the pic here: https://help.ubuntu.com/community/YakketyUpgrades/Kubuntu?action=AttachFile&do=get&target=snapshot7.png
[22:59] <clivejo> ah hi yofel
[23:02] <clivejo> dev release upload?
[23:03] <valorie> zz?
[23:03] <yofel> zz
[23:03] <clivejo> but its the same?
[23:03] <clivejo> did you upload to ZZ?
[23:04] <clivejo> [queuebot] Unapproved: plasma-discover (zesty-proposed/universe) [5.7.5-0ubuntu2 => 5.7.5-0ubuntu3] (kubuntu)
[23:04] <clivejo> that was me?
[23:04] <clivejo> or do you mean we will fix it in ZZ?
[23:04] <yofel> no, I'm just saying that his objection sounds somewhat valid, but I would only care about it for zz
[23:05] <clivejo> ah, got ya
[23:05] <clivejo> yes, I agree
[23:05] <clivejo> well I guess discover doesnt care what distro its on
[23:05] <valorie> is it working for the LTS?
[23:06] <clivejo> could be running on rpm for all it cares
[23:07] <clivejo> just triggers the system upgrade procedure and lets it deal with it
[23:08] <acheronuk> valorie: just tested on Xenial and confirmed it fixes it here on a default install
[23:09] <valorie> cool
[23:09] <acheronuk> I do get the point though, as someone could remove discover an never get the fix
[23:10] <valorie> ah
[23:10] <acheronuk> which would leave 'do-release-upgrade -f kdebackendwhatever' broken
[23:11] <clivejo> does the upgrade in muon package manager work without that package installed?
[23:11] <valorie> that's uncool
[23:11] <acheronuk> but 'do-release-upgrade' without GUI would still work
[23:12] <acheronuk> and launching the GUI from the command line is not the usual way
[23:14] <valorie> corner case indeed
[23:14] <acheronuk> clivejo: let me test muon
[23:14] <acheronuk> 2 secs
[23:16] <acheronuk> clivejo: is Muon meant to offer a distribution upgrade? don't see the option here?
[23:16] <clivejo> that I dont know :/
[23:17] <acheronuk> nor do I, as I don't really use it
[23:18] <valorie> I usually use it to look stuff up, because the tabs make it convenient
[23:18] <valorie> occasionally test it by using it to upgrade
[23:19] <valorie> but haven't tried it as a major upgrader
[23:19] <valorie> I mean, from one version to the next
[23:19] <acheronuk> I got too used to synaptic over the years I think
[23:20] <valorie> I switched away from synaptic to muon package manager as soon as it worked
[23:20] <valorie> I've not seen the appeal of a "software store" approach
[23:21] <valorie> but I guess I'm out of step
[23:23] <acheronuk> a software store can be good for it's own purpose. If it's done ok. sadly most are pretty awful, even at what they are supposed to be good for
[23:28] <clivejo> acheronuk: can you change the tag from verification-needed to verification-done.
[23:29] <acheronuk> clivejo: I've not had the YY proposed update yet, so not sure if I should?
[23:30] <clivejo> the comment seems to be about XX only
[23:30] <clivejo> or am I reading it wrong?
[23:31] <clivejo> yofel: still about?
[23:34] <acheronuk> grr... now I changed it, I'm wondering again.
 (Document) https://irc-attachments.kde.org/0VIK5ptU/file_857.desktop
[23:39] <acheronuk> going to kill the damn plasma panel for dragging stuff again ^^^
[23:39] <acheronuk> clivejo: how did you extend the click --> drag delay for that? you said you did the other day
[23:44] <Snowhog> acheronuk: Muon Package Manager will offer a Distribution Upgrade of it is set to Normal Releases and not LTS.
[23:44] <Snowhog> ^^if it is set
[23:45] <acheronuk> Snowhog: doesn't seem to here
[23:49] <Snowhog> Settings > Configure Software Sources > Updates > Release upgrade > Show new distribution releases: Normal Releases. On my 14.04.1, I've got it set to that, and on each boot up, Muon Updater (I beleive that is the correct package) informs my that a new release is available.
[23:49] <Snowhog> ^^informs me that
[23:50] <acheronuk> This is 16.04 and muon updated no longer exists
[23:50] <acheronuk> *updater
[23:50] <Snowhog> Ah. Firing up my 16.04 VM.
[23:51] <acheronuk> well, the package exists, but it's just a transitional dummy for plasma-discover-updater
[23:53] <acheronuk> so the systray notification is that. while muon is a standalone app which does not seem to have an release upgrade notification or function
[23:59]  * acheronuk waits for KCI


[04:45] <ScottK> Riddell: Any SRU team member can do stuff for Kubuntu, it's just the service is better when I'm around.
[07:11] <soee> good morning
[07:26] <lordievader> Good morning.
[08:30] <soee> 4.11.4 is out :)
[09:49] <apachelogger> shadeslayer_, yofel: soooooooooo, kf5 apparently is building on trusty now all and entirely which means once we have gotten a last weekly snapshot we can kill raring
[09:49] <apachelogger> unless there's objections
[09:50] <yofel> not from me
[10:10] <apachelogger> tsdgeos: which script generates kde's xx translations?
[10:15] <apachelogger>  trusty doesn't start -.-
[10:16] <soee> kill raring :O
[10:25] <apachelogger> kickoffrc bugged -.-
[10:25] <apachelogger> anyways
[10:25] <apachelogger> firefox transition complete, however there's integration matters that need to be taken care of
[10:27] <apachelogger> Riddell: bug 1257675
[10:30] <apachelogger> Does anyone want to handle the announcement part of the firefox transition https://trello.com/c/M5jFkU98
[11:03] <Riddell> apachelogger: I'd much rather it was left unannounced
[11:03] <apachelogger> Riddell: why?
[11:06] <Riddell> apachelogger: because it's a failure of KDE software to be any good
[11:06] <Riddell> "Tm_T (Jussi Kekkonen) (tmt) renewed their own membership in the Kubuntu Membership" yay Tm_T still loves us
[11:08] <apachelogger> Riddell: a success of us listening to our users ;)
[11:09] <jussi> I guess if we put it that this is a temporary fix until kde brings out more awsomeness...
[11:09] <apachelogger> I'd not go into detail about this at all TBH
[11:10] <apachelogger> just "yo, ye asked for it, here it is."
[11:11] <unicodesnowman> Hi, I'd like to do the 'Package KFileBox for Kubuntu' GCI task. I can compile programs from the command line, althrough I haven't packaged an application before. I'd like to try through.
[11:11] <apachelogger> we cannot just hide the change, because we need testing, because we just changed the flipping browser in the cycle leading to an LTS release
[11:12] <Tm_T> Riddell: ofcourse, even if I'm busy
[11:12] <apachelogger> so all political nonsense aside we do need some degree of announcement and testing request
[11:12] <apachelogger> otherwise we might as well ship no browser
[11:14] <Riddell> unicodesnowman: sweet
[11:14] <Riddell> unicodesnowman: first thing would be to compile it on your system and check it works and is useful
[11:14] <unicodesnowman> Riddell: yep, this guide should help? http://packaging.ubuntu.com/html/packaging-new-software.html
[11:15] <Riddell> unicodesnowman: but tell me about you, what's your name and what have you done already?
[11:15] <Riddell> unicodesnowman: yeah that's a good page to start, I can or someone else can also take your through it when you've read that
[11:16] <unicodesnowman> I'm Danny, I've done quite a few tasks, I was planning on cloning kfilebox and building it
[11:17] <Riddell> unicodesnowman: good start, go for it
[11:17] <Riddell> unicodesnowman: do you run Kubuntu 13.10?
[11:17] <unicodesnowman> yup! should I claim the task?
[11:17] <Riddell> unicodesnowman: go for it, do I need to do something to assign you?
[11:18] <unicodesnowman> You need to accept the claim, I think. I'll get started :)
[11:19] <shadeslayer_> Riddell: apachelogger yofel apparently Alex has a C++ replacement for kde-config-touchpad
[11:19] <shadeslayer_> his GSoC student wrote a replacement
[11:19] <Riddell> shadeslayer_: alex the party?
[11:19] <shadeslayer_> yep
[11:19] <Riddell> interesting
[11:19] <shadeslayer_> I'll have a look at this past Lunch
[11:19] <apachelogger> shadeslayer_: GIVE IT TO ME
[11:19] <unicodesnowman> eek, svn code doesn't build
[11:20] <apachelogger> shadeslayer_: what's with your tail btw?
[11:20] <shadeslayer> I grew a tail while I was sleeping
[11:20] <shadeslayer> I thought that was normal human behaviour
[11:20] <Riddell> "☃ snowman has left the following comment at Package KFileBox for Kubuntu"  I guess that's you unicodesnowman :)
[11:21] <Riddell> unicodesnowman: oh hi I'm Jonathan
[11:22] <Riddell> unicodesnowman: my girlfriend wonders if you've read Margaret Atwood books
[11:22] <unicodesnowman> figured that out :) ; I haven't, does that book strangely have a reference to a unicode snowman?
[11:23] <apachelogger> shadeslayer: not convinced it is :P
[11:24] <apachelogger> Riddell: so.... since todays image doesn't boot properly anyway I'd be ok with simply having a testing request once alpha gets released
[11:24] <unicodesnowman> I'll need to get it compile first :P the svn fails to compile
[11:24] <apachelogger> then people can actually test stuff xD
[11:25] <Peace-> mmm virtualbox kubuntu 14.04 black screen ?
[11:25] <Riddell> unicodesnowman: um, that might put a stop to it (but we can find something else to package if that doesn't work)
[11:25] <Peace-> i picked the daily build this morning
[11:25] <Riddell> Peace-: bah, yesterday was fine
[11:25] <apachelogger> Peace-: that's what I was talkign about just now :P
[11:26] <Peace-> lol
[11:26] <apachelogger> lightdm doesn't start for some reason
[11:26] <Riddell> unicodesnowman: grab the source tar file https://sourceforge.net/projects/kdropbox/files/kfilebox-0.4.9/Source/
[11:27] <unicodesnowman> Riddell: yup, this compiles. the svn one is dirty :P - I'll follow the guide now
[11:27]  * Riddell cycles into the office
[11:28] <Peace-> apachelogger: to pick another tty ? windows key + alt f5 doesn't work
[11:28] <Peace-> or i remember bad?
[11:28] <apachelogger> right ctrl
[11:28] <Peace-> ah
[11:28] <apachelogger> rctrl+f1
[11:29] <Peace->  :) yesterday i have upgraded windows 8 to windows 8.1 = grub devasted ,  everytime i see kubuntu spaslsh screen i fell at home
[11:30] <apachelogger> Riddell, ScottK: did we sign up for alpha1?
[11:31] <Peace-> mmm it seems that in the menu firefox has not icon
[11:31] <apachelogger> fixed in bzr
[11:38] <Peace-> apachelogger:  i tried to add some widets ==> error http://wstaw.org/m/2013/12/04/plasma-desktopn16279.png
[11:41] <unicodesnowman> Riddell: sorry but I already encountered an issue :/ when I try to do bzr dh-make, I get "tar: This does not look like a tar archive"
[11:41] <unicodesnowman> I'm passing the tar.gz to it, and I've tried passing just the .tar after ungzing it, and I can untar it with tar -zxvf
[11:41] <apachelogger> Peace-: how did you start the session?
[11:41] <Peace-> apachelogger: startx
[11:41] <apachelogger> maybe some envrionment vars aren't set
[11:42] <Peace-> ah
[11:42] <apachelogger> or someone screwed up the packaging xD
[11:42] <Peace-> xD
[11:43] <apachelogger> on my saucy install that module is not present
[11:43] <apachelogger> !find org.kde.telepathy trusty
[11:44] <apachelogger> !find PythonQt.h
[11:50] <unicodesnowman> anyone got clues on why bzr dh-make barks at a valid .tar.gz file?
[11:53] <apachelogger> Peace-: that's the quick chat plasmoid?
[11:54] <soee> Peace-, this contact list doesnt work for you ?
[11:54] <Peace-> one moment
[11:55] <soee> its broke a long time
[11:55] <Peace-> quick chat
[11:55] <Peace-> it's the widget
[11:55] <Peace-> ah ok ok
[11:55] <Peace-> i was just testing the iso :D
[11:57] <shadeslayer> apachelogger: Riddell so regarding the xapian index, there are comments that say that the xapian index will be rebuilt on the target by apt's cron.daily
[11:59] <shadeslayer> what say you?
[11:59] <Peace-> soee: but that is quick chat, i do not what you are referring   btw if it's on the iso it should work
[12:03] <yofel> shadeslayer: after install? That's broken then as it's obviously not there
[12:04] <shadeslayer> yofel: well, it'll be built once the cron job runs
[12:04] <yofel> then anacron should trigger on first boot, and not after a day
[12:05] <apachelogger> shadeslayer: at a random point in time
[12:05] <apachelogger> what yofel said
[12:06] <apachelogger> technically every qapt user would also rebuild the cache first... in a perfect world... but even so that rebuilding is blocking the user from using his system
[12:07] <apachelogger> and considering we can perfectly build an initial cache as part of target configuration during installation that blockage is utterly pointless
[12:08] <shadeslayer> Riddell: yofel http://i.imgur.com/tIn8YDV.png
[12:08] <shadeslayer> from http://quickgit.kde.org/?p=scratch%2Falexandermezin%2Ftouchpad.git
[12:08] <yofel> not too shabby
[12:09] <shadeslayer> apachelogger: the reasoning that's given is that the target sources.list might be different from the one that's on the ISO
[12:10] <yofel> can't you generate the index in /target ?
[12:10] <apachelogger> ^ that's what you *need to* do
[12:11] <apachelogger> generating stuff on the live session and copying it to the target never ever works
[12:11]  * yofel remembers the cache copying talk in munich ^^
[12:11] <apachelogger> e.g. for sycoca I am reasonable certain we manually rip out certain kded modules
[12:11] <shadeslayer> right
[12:12] <Riddell> unicodesnowman: hi, how did you get on?
[12:12] <unicodesnowman> sorry, what do you mean?
[12:12] <Riddell> shadeslayer: yes it is built by cron but the trouble is if you want to install stuff with muon before cron does its thing
[12:13] <shadeslayer> so there's code that updates the apt-cache on the target, we can generate the xapian index right after that then
[12:13] <Riddell> shadeslayer: sounds good
[12:22] <shadeslayer> tsdgeos: do you have anything that's still at 4.11?
[12:25] <yofel> kde-workspace should be at 4.11
[12:28] <shadeslayer> well, yeah except for that :)
[12:28] <shadeslayer> I don't see anything else on the proposed-migration
[12:28] <shadeslayer> so that's good
[12:28] <shadeslayer> ( might have missed something, so will be good if someone else gives it a go as well )
[12:28] <shadeslayer> I think the seeds need updating though?
[12:31] <shadeslayer> wheee
[12:31] <shadeslayer> current live cd doesn't boot
[12:32] <apachelogger> Peace-: missing dependency it is
[12:34] <Peace-> apachelogger: :) good
[12:34] <Peace-> someone has tried to install kubuntu 14.04 ?
[12:34] <apachelogger> sure
[12:35] <Peace-> all ok ? apachelogger
[12:35] <apachelogger> yeah
[12:35] <apachelogger> except for the lightdm issue
[12:35] <Peace-> good i am going to test too
[12:35] <Peace-> ok that is not a problem
[12:39] <Riddell> unicodesnowman: where did you get to with kfilebox?
[12:39] <unicodesnowman> i'm currently fiddling with compression issues with bzr. I *had* got a .deb file before, but it didn't do anything when I ran it
[12:40] <unicodesnowman> Turns out that was a but with the program, not with my packaging.  :P
[12:42]  * unicodesnowman is trying to figure out how to pass "use -z option" to tar /for/ dpkg-source
[12:43] <BluesKaj> Hiyas all
[12:44] <Riddell> unicodesnowman: I'm setting up an ec2 (cloud) server so we can work on it together, do you have an ssh key?
[12:44] <unicodesnowman> yep, I'll pastebin it?
[12:45] <unicodesnowman> lemmie try and get it working, I untargz'd and re-tar-gz'd, now it I'm able to actually use dh-make
[12:45] <Riddell> unicodesnowman: yes please
[12:46] <unicodesnowman> Riddell: http://pastebin.com/Vc56EAZY
[12:47] <unicodesnowman> thank you by the way :)
[12:49] <unicodesnowman> Riddell: I think I successfully packaged it
[12:49] <Riddell> unicodesnowman: ssh<EMAIL_ADDRESS>
[12:50] <Riddell> unicodesnowman: run  byobu
[12:51] <unicodesnowman> Riddell: I'm in byobu, can you see what I'm typing?
[12:51] <Riddell> unicodesnowman: yay :)
[12:51] <Riddell> unicodesnowman: yes we're now sharing a screen
[12:52] <Riddell> unicodesnowman: from your local computer can you copy over the files you have?   scp *<EMAIL_ADDRESS>[12:54] <apachelogger> ehm
[12:54] <Riddell> unicodesnowman: lovely,let me take a look
[12:55] <unicodesnowman> scping. I believe I've got a working .deb, I'm currently just setting up a new gpg key and such
[12:55] <apachelogger> Riddell: https://errors.ubuntu.com/problem/b674d33a11fddc5b8e414df042f41bb5a9b047af people still have printer-applet on 13.10 and it explodes a lot
[12:55] <unicodesnowman> I had issues with the .tar.gz I downloaded, the build process would complain, I uncompressed and recompressed it into a .tar.gz and it seemed to work
[12:56] <Riddell> apachelogger: ehm
[12:56] <apachelogger> exactly xD
[12:57] <unicodesnowman> (note: I do not think whta changed in v0.4.9 was documented :/ )
[12:57] <Riddell> unicodesnowman: hah you're right, the upstream tar was actually gzipped twice
[12:58] <Riddell> unicodesnowman: well done on figuring that out
[12:59] <apachelogger> bug 1196344 is also occuring a lot on 13.10
[12:59] <Riddell> unicodesnowman: yuck is uses qmake for a build system, qmake is messy
[12:59] <unicodesnowman> Riddell: thanks, and yeah I reckon!
[13:00] <Riddell> unicodesnowman: can you install the package and run the application?
[13:00] <Riddell> unicodesnowman: does the application actually do anything useful? (I've not tried it)
[13:01] <unicodesnowman> yes, it runs, but if you don't complete the setup proecss you need to delete .dropbox in your home directory
[13:01] <unicodesnowman> otherwise it does nothing. the second time I run it (after packaging), I thought something was wrong on my end :/
[13:01] <unicodesnowman> (this has to be the worst program to package for for a beginner, lol)
[13:01] <Riddell> sorry :)
[13:02] <unicodesnowman> I'll create and upload it to my ppa?
[13:02] <Riddell> unicodesnowman: so I think to complete the task there's some tidying up to be done then yep upload to a PPA
[13:03] <Peace-> mmm tryint usb 14.04 it seems blocked
[13:03] <Riddell> unicodesnowman: where does that rules.dh7 come from?
[13:04] <Peace-> computer 5 years old
[13:04] <unicodesnowman> Riddell: generated when I ran dh-make
[13:04] <unicodesnowman> (i think)
[13:04] <Riddell> unicodesnowman: do you know if it works?
[13:05] <Peace-> ok is working
[13:06] <unicodesnowman> it's loading (Downloading Dropbox Daemon)
[13:08] <unicodesnowman> no, it doesn't work :( - it's stuck on dropbox linking.
[13:08] <Riddell> hmm I should have set this server up to be amd64, i386 I can't easily test
[13:08] <unicodesnowman> lemmie see if I get the same issue building from source
[13:12] <Peace-> Riddell: i have this old broadcom 4306 and it doesn't work on kubuntu, it needs firmware i guess
[13:12] <Peace-> 14.04
[13:12] <unicodesnowman> Riddell: GTK installer works!
[13:12] <Riddell> unicodesnowman: umm, what?
[13:12] <Riddell> unicodesnowman: gtk installer?
[13:13] <unicodesnowman> yeah, GTK installer or setup wizard. that worked
[13:13] <unicodesnowman> 'simply link' does not work
[13:15] <Riddell> unicodesnowman: what gtk installer?
[13:15] <unicodesnowman> after you run kfilebox, and it downloads the Dropbox Daemon it asks you:
[13:16] <unicodesnowman> "Run gtk based installer" or "Or simplly (sic) link account"
[13:16] <Riddell> umm, ok, interesting
[13:16] <unicodesnowman> the 'gtk based installer' works, the 'link account' does not. not an issue with the packaging, it just doesn't work when I make it from source (changed API?)
[13:17] <unicodesnowman> should I just remove the option for 'simply link account'?
[13:18] <Riddell> unicodesnowman: patching that out would be good if it doesn't work yes
[13:19] <unicodesnowman> Riddell, ok, what tidying tasks should I do?
[13:22] <Riddell> unicodesnowman: hang on I'm setting up an amd64 server
[13:22] <Riddell> unicodesnowman: use the rules.dh7 file as the rules file, it seems to work fine
[13:23] <Riddell> then you'll need to add an install file listing the files to install (because this is too hard for qmake to do)
[13:24] <Riddell> unicodesnowman<EMAIL_ADDRESS>[13:24] <Riddell> unicodesnowman: copy your stuff up there again
[13:24] <unicodesnowman> ok
[13:24] <Riddell> unicodesnowman: use the dh7 rules file, it's much neater (as you can see it abstracts everything away)
[13:24] <Riddell> add debian/install and list files to be installed and where
[13:25] <unicodesnowman> would I do that by replacing the rules contents with dh7?
[13:25] <Riddell> unicodesnowman: yeah
[13:25] <Riddell> unicodesnowman: tidy up the changelog, no need to keep upstream's stuff, just have one entry for yourself saying "initial package"
[13:25] <unicodesnowman> ok
[13:25] <Riddell> probably the debian/docs and debian/dirs files can go to
[13:26] <Riddell> patch that option away
[13:27] <Riddell> that'll be fiddly
[13:27] <unicodesnowman> currently I just took the low risk option by making that button not visible
[13:28] <Riddell> unicodesnowman: that's the best way, minimal changes are best
[13:28] <Riddell> that patch can go in debian/patches in the packaging
[13:28] <Riddell> unicodesnowman: I need to go for a lunch meeting now
[13:28] <Riddell> if you get stuck get apachelogger or someone to help you
[13:28] <unicodesnowman> ok, thank you for your help!
[13:37] <Sick_Rimmit> Hi everyone
[13:38] <soee> hi Sick_Rimmit
[13:38] <Sick_Rimmit> Received my Kubuntu Business cards, Thank You, I shall be handing these out, with Kubuntu Live / Install dischs at LUG, Raspberry Pi, and some Business meetings too, so very welcome
[13:41] <Sick_Rimmit> I am trying hard to get my head around Kubuntu development process. I think I got the beginnings of Bug fixing, and Documentation I think I'm getting there. Ultimately I want to write an Application for the Ubuntu store using QML and provide support for Touch.
[13:42] <Sick_Rimmit> I can code reasonably OK. But I just get lost in the plethora of pages and links in the Ubuntu / Kubuntu docs...
[13:43] <Sick_Rimmit> If anyone has advice or pointers about what to read and where that would be really useful to me
[13:43] <Sick_Rimmit> My coding origins are BBC Basic, Cobol, Pascal, Assembler..
[13:44] <Sick_Rimmit> Yes I am a born again coder I guess,
[13:45] <Peace-> great
[13:45] <Sick_Rimmit> Most of what I have done before was on 8bit Micro's, But I'm competent with PHP, and OK with Python. I've got the OOP ideas in my head now too, after much scalp scratching
[13:45] <Peace-> kubuntu 14.04 installed properly i was be able to connect to internet this old pc using a wired shared connection with the brand new
[13:45] <Peace-> wifi did not work
[13:46] <Peace-> so i have used the new computer , that with wifi connection , created new wired shared connection  connected via ethernet cable computer 1 to computer 2 :) it just works out of the box
[13:46] <Peace-> nice
[13:47] <Sick_Rimmit> Peace-: Is that using the new Network Manager ?
[13:48] <Peace-> i don't think so
[13:48] <Peace-> kubuntu 13.10 with wifi connection [13:48] <Peace-> so 13.10 should use old network manager
[13:49] <Peace-> Riddell: i got an error  on jokey-kde
[13:49] <Peace-> could not find any typelib for appindicartor3
[13:52] <sem> Riddell:  apachelogger http://wstaw.org/m/2013/12/04/plasma-desktoptN1748.png
[13:52] <sem> always 14. 04
[13:52] <apachelogger> jockey is being replaced
[13:52] <sem> ah ok
[13:52] <apachelogger> on that note
[13:52] <apachelogger> shadeslayer: you may want to hurry up :P
[13:52] <apachelogger> what with needing testing and all
[13:53] <sem> apachelogger: btw the installation was fantastic
[13:54] <sem> i did not know that i could share connection with a  kubuntu wifi-working computer via ethernet cable
[13:54] <sem> even in the installation process
[13:54] <apachelogger> magic
[14:04] <shadeslayer> apachelogger: yep, will give it a shot tomorrow
[14:04] <shadeslayer> image doesn't boot in VBox :(
[14:05] <unicodesnowman> about ubuntu PPAs: after I uploaded a package, is it normal that it doesn't immediately update?
[14:05] <unicodesnowman> do I need to wait a certain amount of time?
[14:05] <unicodesnowman> I get "Successfully uploaded packages.", but it doesn't show up.
[14:10] <apachelogger> unicodesnowman: takes a while, it will send a mail once accepted
[14:11] <unicodesnowman> apachelogger: ok, thank you, going to go to bed now
[14:11] <apachelogger> shadeslayer: tomorrow image doesn't boot in vbox, what?
[14:11] <apachelogger> unicodesnowman: good night
[14:11] <shadeslayer> apachelogger: what
[14:11] <unicodesnowman> I'm now 1000% less scared of creating a new package :P
[14:11] <apachelogger> shadeslayer: exactly
[14:12] <shadeslayer> http://cdimage.ubuntu.com/kubuntu/daily-live/current/trusty-desktop-amd64.iso.zsync
[14:12] <shadeslayer> doesn't work
[14:12] <apachelogger> worked for me
[14:12] <apachelogger> I suspect pebkac
[14:12] <apachelogger> unless a second image was built
[14:12] <apachelogger> in which case you should get to the office earlier and try the image in the mornings :P
[14:17] <shadeslayer> apachelogger: http://i.imgur.com/gD7fbNZ.png
[14:17] <apachelogger> is that after install?
[14:21] <shadeslayer> apachelogger: that's when booting the live cd
[14:21] <shadeslayer> and clicking "Try Kubuntu"
[14:21] <apachelogger> same problem then
[14:22] <apachelogger> lightdm is kaput
[14:22] <shadeslayer> looks like it
[14:22] <shadeslayer> sudo service lightdm start -> start: Job failed to start
[14:23] <shadeslayer> apachelogger: http://paste.ubuntu.com/6519961/
[14:29] <shadeslayer> "Remove lightdm-set-defaults and gdmflexiserver"
[14:40] <shadeslayer> apachelogger: filed a bug against lightdm
[14:40] <shadeslayer> bug 1257760
[14:48] <apachelogger> shadeslayer, Riddell: what do we call that whoopsie thing? Diagnostics?
[14:48] <shadeslayer> sounds good to me
[14:53] <Riddell> apachelogger: why not call it whoopsie?
[14:56] <shadeslayer> Riddell: Whoopsie is the tool that sends diagnostic data, this is just a KCM to interact with Whoopsie
[15:00] <Riddell> Sick_Rimmit: you're welcome, do look at the trello board if you want to get into doing things or help out packaging
[15:01] <Sick_Rimmit> Riddell: Yes, I am just looking at the ZaReason videos on Ubuntu Development.
[15:01] <apachelogger> Riddell: actually the reason is that whoopsie is technobabble :P
[15:01] <Sick_Rimmit> Sort of feel like there is lots of information, but everything is everywhere
[15:01] <Sick_Rimmit> Maybe its just me..
[15:02] <apachelogger> Riddell: the thing is called kde-config-whoopsie, I am asking about what to call it in user facing stuff
[15:02] <Sick_Rimmit> However, fear not I will figure it out
[15:03] <Riddell> apachelogger: oh right, yeah call it Diagnostics then
[15:05] <Riddell> Sick_Rimmit: sounds like you need a task to get started on
[15:05] <Riddell> Sick_Rimmit: you could for example look at merging quassel package with debian
[15:06] <Sick_Rimmit> Riddell: Yes, but if you recall I took on the Watch List task before, and failed! :-(
[15:06] <Sick_Rimmit> Riddell: I sort of feel all disconnected with bits of knowledge everywhere.
[15:06] <Peace-> mm syslog doens't exist anymore ?
[15:07] <Sick_Rimmit> Riddell: My plan was to try to do a Bug Fix, using the Getting Started docs
[15:10] <apachelogger> Riddell: kde:scratch/sitter/kcm-whoopsie now also has packaging and diagnostics as name, should be good for release now
[15:10] <Riddell> apachelogger: ooh lovely
[15:10] <Riddell> apachelogger: need me to do stuff?
[15:11] <apachelogger> just a review if you feel bored
[15:11] <Riddell> Peace-: sure it does
[15:11] <apachelogger> oh layout still needs a change
[15:11] <Riddell> apachelogger: did you work out how it related to apport?
[15:11] <apachelogger> show reports anchors right which looks terrible when having a super wide window
[15:11] <apachelogger> Riddell: not yet, no
[15:11] <shadeslayer> Riddell: apachelogger is it fine if I package the new touchpad KCM in Kubuntu experimental PPA
[15:11] <shadeslayer> for people to try out
[15:11] <apachelogger> sure
[15:12] <Riddell> shadeslayer: awooga
[15:12] <shadeslayer> cool
[15:12] <shadeslayer> do we want the git import to be owned by kubuntu-dev or kubuntu-ppa?
[15:12] <apachelogger> -members
[15:13] <shadeslayer> ack
[15:13] <apachelogger> -dev is only there to manage upload permissions
[15:13] <apachelogger> equally -ppa is only there to provide nice ppa urls ;)
[15:17] <shadeslayer> project .. .hmm
[15:17] <shadeslayer> doesn't have a project for now
[15:17] <shadeslayer> can't put in junk apparently
[15:17] <Riddell> why not?
[15:18] <shadeslayer> form doesn't allow me to
[15:18] <Riddell> kubuntu-packaging
[15:18] <Riddell> if it's packaging
[15:18] <shadeslayer> it's a code importy
[15:19] <shadeslayer> but I've put it in packaging for now
[15:19] <Riddell> ah, then you need to make a project
[15:19] <shadeslayer> ololol
[15:19] <shadeslayer> Form doesn't allow you to change it
[15:19] <shadeslayer> but once you set it to kubuntu-packaging, you can change it to junk on the details page :D
[15:20] <Riddell> good old launchpad, always configurable if you know how
[15:20] <shadeslayer> :)
[15:27] <shadeslayer> can't take the kde-config-touchpad name :/
[15:27] <shadeslayer> kde-config-touchpad-to-be-seen-if-better
[15:33] <Riddell> shadeslayer: why are you doing a code import of it?
[15:33] <shadeslayer> Riddell: daily packages for people to test?
[15:33] <shadeslayer> it doesn't have a release yet
[15:34] <Riddell> okay dokay
[15:35] <shadeslayer> calling it kde-touchpad-config for now
[15:35] <Sick_Rimmit> I use 12.04 LTS on my laptop, I prefer the LTS releases for daily use. I also have a 13.10 in Virtualbox, Ideally I would prefer to setup and use the development tools from 12.04 on my Laptop. Does this sound OK
[15:37] <Riddell> Sick_Rimmit: there's not much need to be using 12.04 when you're developing for 14.04..
[15:38] <Riddell> Sick_Rimmit: but I'm on 13.10 now developing for 14.04 and 12.04 and I use chroots and ec2 servers
[15:38] <Riddell> Sick_Rimmit: use debootstrap to make a chroot would be a good way to start
[15:39] <Sick_Rimmit> Riddell: OK I can setup something for this. From the docs, I got the impression that pbuilder takes care of the build environment.
[15:39] <Riddell> anyone got comments on qt 5 qreal transition? https://lists.ubuntu.com/archives/ubuntu-devel/2013-December/037859.html
[15:40] <Riddell> Sick_Rimmit: depends if you use pbuilder or not, I don't use it except as a final test, I just manage my chroots manually, pbuilder sets up a chroot each time which takes a lot of time
[15:41] <Sick_Rimmit> Riddell: Ah OK I understand now.
[15:43] <Sick_Rimmit> Riddell: For simplicity and so that I can follow the Doc's I will use pbuilder, and accept the time penalty whilst I find my feet, thanks
[15:43] <Riddell> Sick_Rimmit: which docs are you reading?
[15:44] <Sick_Rimmit> Riddell: https://wiki.ubuntu.com/BeginnersTeam/FocusGroups/Development/Devbeginnings#Ubuntu Development Beginnings
[15:45] <Riddell> hmm that also has stuff about bzr in it which I don't think it necessary
[15:45] <Riddell> that's what unicodesnowman was using earlier which I think is just extra faffy
[15:47] <Sick_Rimmit> Well I have bzr setup, and am OK with it, more experience with SVN..
[15:53] <Riddell> mm, but using full source tree bzr branches is just unnecessary
[15:57]  * Peace- http://nowardev.files.wordpress.com/2013/12/verademilo1.jpeg
[15:57] <Peace-> kubuntu 14.04 properly installed
[15:57] <Peace-> i like it
[16:00] <Riddell> umm
[16:00] <Riddell> Peace-: did you sort your blank screen issue out?
[16:01] <Peace-> Riddell: yes
[16:01] <Peace-> Riddell: well sorry i have just started anew tty
[16:01] <Peace-> and it says that there is not a configuration found
[16:03] <Riddell> hmm
[16:03] <Riddell> but it's likely to be not our problem if a kde session still runs fine
[16:03] <sem> Riddell: lighdm error it's here i am Peace- http://paste.kde.org/p25336f27
[16:04] <Peace-> Riddell: there is not lightdm.conf file ?
[16:05] <Peace-> Riddell: btw in my instaallation i have another problem i can't add a wifi connection too
[16:05] <Peace-> i just do add wifi bla bla set password etc but it just doeesnt add it
[16:06] <sem> wifi seems works fine sudo iwlist wlan0 scan does the job find all the stuff
[16:06] <sem> but then i can 't add the wifi :s
[16:07] <Riddell> sem: what are you testing?
[16:08] <sem> 14.04 : add a wifi connection
[16:11] <sem> mmm
[16:11] <sem> [   17.414714] IPv6: ADDRCONF(NETDEV_UP): wlan0: link is not ready
[16:13] <shadeslayer> Riddell: "The owner of the recipe (Kubuntu Members) does not have permission to upload packages into the daily build PPA (Kubuntu Experimental)"
[16:14] <Riddell> mm no it doesn't
[16:15] <Riddell> sem: the only thing that has changed revently on the kubuntu side is a new version of plasma-nm, but possibly something has broken lower down
[16:15] <shadeslayer> Riddell: recipe under my name for now
[16:16] <sem> Riddell: the strange thing it's that there is no way to add the connection here  http://wstaw.org/m/2013/12/04/plasma-desktoplq1556.png
[16:16] <sem> you can configure it but it just doesn't add
[16:17] <Riddell> sem: add button?
[16:19] <Peace-> Riddell: yes the add button you can click set what you want then it will not appear
[16:19] <Peace-> on the connection window
[16:19] <Riddell> Peace-: you could install the old plasma-nm package and see if it works better
[16:19] <Peace-> ok i will try i t
[16:21] <shadeslayer> xnox: I'm confused wrt something about ubiquity, got a moment?
[16:21] <sem> Riddell: i will try this one http://packages.ubuntu.com/saucy/kde/plasma-nm
[16:21] <xnox> shadeslayer: what's up?
[16:22] <shadeslayer> xnox: there's install.py that implements Install.run() and then there's plugininstall which implements Install.run() , which one is called first by ubiquity?
[16:23] <shadeslayer> xnox: I'm trying to make ubiquity populate the xapian cache on the target right after the installer updates the apt cache
[16:25] <xnox> shadeslayer: i am always confused about plugininstall, the fact that there are _multiple_ same named python files does not help, and the fact that their location is shuffled on the installed system also does not help.
[16:25] <shadeslayer> bah
[16:26] <shadeslayer> yeah, I should have said scripts/plugininstall.py
[16:26] <shadeslayer> in the source
[16:26] <xnox> (their location shuffled on the installed system that is on the live cd)
[16:26] <shadeslayer> yep
[16:27] <xnox> the way I understand it is that, after initial squashfs is blasted, "pages" ( i really don't want to use work plugin here) can register a plugininstall hook, such that "plugininstall" can execute the "other plugininstall" which does whole bunch of things.
[16:27] <xnox> the most recent implementation of this is ubuntu-one plugin.
[16:27] <shadeslayer> http://pastebin.kde.org/pbjez8vyt
[16:28] <shadeslayer> is how I was thinking of doing it
[16:28] <genii> Not sure why but some update today pulled in Wayland
[16:28] <xnox> mymicing ubuntuone should be sufficient...... it's just that you actually don't need to wait for any user input /  values
[16:29] <shadeslayer> okay, looking
[16:31] <shadeslayer> xnox: this seems a bit too much for just updating the xapian index since it's not really a page
[16:32] <xnox> shadeslayer:
[16:32] <xnox>   * Remove /target/var/lib/apt-xapian-index per Michael Vogt, since it needs
[16:32] <xnox>     to be rebuilt based on the installed system's sources.list, and apt's
[16:32] <xnox>     cron.daily script and/or synaptic will do this.
[16:32] <xnox> ubiquity (1.12.0) jaunty; urgency=low
[16:32] <shadeslayer> yes, I saw that
[16:34] <shadeslayer> xnox: http://irclogs.ubuntu.com/2013/12/04/%23kubuntu-devel.html#t12:03
[16:35] <Peace-> Riddell: mmm seems that doesn't fix the problem
[16:36] <xnox> shadeslayer: can you try dropping "#!/bin/sh \n chroot /target apt-xapian-index" as /usr/lib/ubiquity/target-config/run-apt-xapian and mark it executable and check if it did run?
[16:38] <shadeslayer> trying
[16:38] <xnox> well "/usr/sbin/update-apt-xapian-index"
[16:38] <shadeslayer> yep, already made that change locally ;)
[16:59] <xnox> shadeslayer: that patch is not correct, as it would run apt-xapian-index in parallel to "apt-get update" which is wrong.
[16:59] <shadeslayer> oh okay
[17:00] <shadeslayer> xnox: I /think/ it works
[17:00] <shadeslayer> waiting for install to finish
[17:00] <shadeslayer> but atleast there is a /target/var/lib/apt-xapian-index folder
[17:00] <xnox> shadeslayer: it would, but it is ugly. but it gives us a time reference where/when it's run.
[17:01] <shadeslayer> oh, why is it ugly?
[17:01] <xnox> shadeslayer: if it takes too long, we'd want to start it early and run it in parallel to the rest of stuff.
[17:01] <xnox> instead of blocking the install / extending the install wall-clock time.
[17:01] <shadeslayer> true
[17:01] <xnox> i think instead of deleting the cache we should incrementally update it.
[17:06] <shadeslayer> so yeah that script does work
[17:12] <shadeslayer> xnox: so what could be done is not remove the index, and just run xapian update with the script which shouldn't take long?
[17:13] <xnox> huh? no
[17:13] <xnox> shadeslayer: remove the code that removes the index from target which got copied from the CD
[17:14] <xnox> shadeslayer: add code to incrementally update the apt-index in target after sources got refreshed.
[17:16] <shadeslayer> xnox: and how do I know that the update cache process has finished?
[17:18] <xnox> shadeslayer: same way one always does, but using Popen module, storing pid, and if not exited kill at the end of ubiquity.......
[17:18] <xnox> see e.g. pid management of all the other processes.....
[17:18] <xnox> shadeslayer: on the other hand i'd like to find where/why the software-center postinst is executed on the ubuntu cd.
[17:22] <shadeslayer> ah, at the end of run() you kill the update process, I can just update the cache incrementally after that
[17:27] <Riddell> "PPA exceeded its size limit (10488.00 of 10240.00 MiB)" bother, ninjas is full up
[17:28]  * Riddell deletes raring 4.11.3 packages
[17:53] <shadeslayer> xnox: I don't suppose there's a way other than printing a debug message to see if the command was actually run
[17:55] <xnox> shadeslayer: it should be in the syslog, prefixed with ubiquity.
[17:55] <xnox> shadeslayer: but note there is a bug over the past few days were syslogd was broken in ubuntu, so there was none.
[17:55] <shadeslayer> yeah, I don't see a /var/log/syslog
[17:58] <shadeslayer> xnox: http://pastebin.kde.org/pgmdv8j64
[17:59] <shadeslayer> oh
[17:59] <shadeslayer> wrong indent
[17:59] <shadeslayer> http://pastebin.kde.org/pwaf0k1j9 < better
[17:59] <xnox> shadeslayer: this is still wrong.
[17:59] <shadeslayer> :O
[18:00] <xnox> shadeslayer: you canno use subprocess.call ()
[18:00] <xnox> shadeslayer: as i told you above.
[18:01] <xnox> shadeslayer: and you cannot be doing it from scripts/install.py at all, now you have moved it from "running in parallel" to "we are about to shutdown" step.
[18:01] <xnox> shadeslayer: the update-apt-xapian-index should be tracking pid and be executed where the delete of the apt-xapian-index used to happen
[18:01] <xnox> or lower down, not sure where though.
[18:02] <xnox> ideally i'd want to place it just before software-centre postinst is executed (that's on ubuntu cds)
[18:02] <xnox> but I can't find where that happens.
[18:04] <shadeslayer> xnox: one other thing that I don't quite get
[18:04] <shadeslayer> update-apt-cache calls apt-get update from the live session
[18:05] <shadeslayer> but then apt-get upgrade is called with the cache placed in /target
[18:05] <xnox> not quite.
[18:05] <shadeslayer> oh?
[18:05] <xnox> there are multiple apt calls, and apt is flexible to one can just exec "apt-get" but set options such that it uses configs e.g. from /target and or places caches there.
[18:06] <xnox> ubiquity installer can receive auto-update notification and self upgrade in the live session from the first screen.
[18:06] <xnox> as a last-resort installer hot-fix option, if there is network connectivity
[18:06] <xnox> and then it does call update/upgrade from live session.
[18:07] <xnox> there are also various calls to install/upgrade -> which actually are no-op, they re-mark things as manually installed instead of automatic such that at the end of the installation they are not auto removed
[18:07] <shadeslayer> http://bazaar.launchpad.net/~ubuntu-installer/ubiquity/trunk/view/head:/scripts/update-apt-cache
[18:08] <shadeslayer> ^^ that to me reads as : update the cache on the live system in /var/cache/apt , but then use the cache on the target, which might be out of date, for upgrading?
[18:08] <xnox> shadeslayer: Note "-d" which is download only.
[18:08] <xnox> shadeslayer: and that script is only called if one ticks "Download updates during installation"
[18:08] <xnox> shadeslayer: note that no upgrade is actually performed.
[18:08] <shadeslayer> sure, but isn't it potentially using a outdated cache?
[18:09] <xnox> shadeslayer: no, it's using live-session cache which was just generated in line 5, but downloads / places .debs into target.
[18:09] <shadeslayer> ahhh
[18:09] <xnox> which is created in line 3 & 4
[18:09] <shadeslayer> okay that makes more sense
[18:10] <xnox> jedi wave - these are not the apt-get update you are looking for =)
[18:10] <shadeslayer> =D
[18:11] <shadeslayer> Riddell: btw where do we want the KDE Developer meta package? in kdelibs?
[18:13] <shadeslayer> apachelogger: ^^
[18:25] <Riddell> shadeslayer: kde-meta ?
[18:26] <Riddell> kubuntu-meta ?
[18:27] <Peace-> Riddell: changed kubuntu-settings-desktop no candidate ?
[18:27] <shadeslayer> meta-kde sounds like the best one so far
[18:38] <shadeslayer> Riddell: http://pastebin.kde.org/px1fc2nqq
[18:42] <shadeslayer> alternatively, we define a variable in debian/rules with : apt-cache showsrc kde4libs | grep -i Build-Depends | cut -b 16-
[18:42] <shadeslayer> and that gets substituted in control
[18:46] <Riddell> shadeslayer: that would miss kdepimlibs-dev and other -devs which are part of kde sc
[18:49] <shadeslayer> Riddell: can be added to Recommends
[18:55] <shadeslayer> Riddell: I can push the initial version, and then we add stuff as required?
[18:57] <Riddell> yeah
[19:01] <shadeslayer> Riddell: http://pastebin.kde.org/pfvxm7l3i < better now?
[19:01] <shadeslayer> with automatic Build-Depends parsing :>
[19:02] <shadeslayer> It's architechture any because the parsing has Build Depends that are only installed on a specific arch
[19:04] <shadeslayer> Riddell: pushed to meta-kde
[19:05] <shadeslayer> Riddell: feel free to add more stuff as required
[19:59] <ovidiu-florin> I have the oportinity to give to a school a laptop with pre installed Kubuntu. How would I change the default desktop settings for all/any users?
[20:00] <ovidiu-florin> I'm logged in the OEM temporary user
[20:00] <ovidiu-florin> can I just change the desktop settings here? od do I have to change something somwhere?
[20:45] <shadeslayer> ovidiu-florin: I believe you have to change them elsewhere
[20:45] <shadeslayer> ovidiu-florin: you can start with /usr/share/kubuntu-desktop-settings
[20:45] <shadeslayer> or whatever it's called
[20:45] <ovidiu-florin> shadeslayer: I found my answer here http://userbase.kde.org/Tutorials/Modify_KDE_Software_Defaults
[20:46] <shadeslayer> sure
[20:46] <shadeslayer> but that might not work for Kubuntu since we override KDE defaults
[20:46] <ovidiu-florin> thank you
[20:46] <kubotu> ::workspace-bugs:: [1257760] Lightdm doesn't launch Plasma on Kubuntu Trusty anymore @ https://bugs.launchpad.net/bugs/1257760 (by Rohan Garg)
[20:46] <shadeslayer> and you *really* don't want skel
[20:47] <ovidiu-florin> why not?
[20:47] <shadeslayer> can cause all sorts of cache issues
[20:47] <shadeslayer> I highly recommend looking at kubuntu-settings
[20:50] <ovidiu-florin> ok, thank you
[21:42] <ovidiu-florin> shadeslayer: for the settings where can I see a documentation on how to edit the panel settings? for example how do I set the digital clock to show the long date?
[21:43] <shadeslayer> search for plasma desktop scripting
[22:04] <ovidiu-florin> shadeslayer: I think I've found it
[22:04] <shadeslayer> ;)
[22:15] <ovidiu-florin> shadeslayer: I can't find how to set folderview as default
[22:15] <shadeslayer> set folderview as default for what?
[22:15] <shadeslayer> ah
[22:15] <ovidiu-florin> desktop
[22:15] <shadeslayer> right
[22:15] <shadeslayer> it can be done
[22:15] <shadeslayer> I don't remember it off the top of my head
[22:16] <shadeslayer> ovidiu-florin: set it to folderview in your regular desktop and check what config value changes in ~/.kde/share/config
[22:16] <shadeslayer> then you can do appropriate config writes
[22:16] <ovidiu-florin> yeah, I tried that
[22:17] <ovidiu-florin> and Kate is messed up and doesn't show the differences all the times
[22:17] <ovidiu-florin> it just freezes
[22:17] <ovidiu-florin> now it won't open
[22:17] <shadeslayer> just copy ~/.kde to ~/.kde.bak
[22:18] <shadeslayer> then run diff on the config folders
[22:18] <shadeslayer> jussi: pingly
[22:18] <ovidiu-florin> ok
[22:23] <shadeslayer> o_o
[22:26] <Sick_Rimmit> Cool, after a busy day reading through docs, and getting lost in bug reports, I think I am ready to have a crack at fixing my first bug.
[22:26] <Sick_Rimmit> That's enough for today, catch yall tomorrow.. ttfn
[23:03] <ovidiu-florin> for OEM installs can I change the default language for the first boot, when the user has to configure his account?
[23:06] <ovidiu-florin> shadeslayer: I've removed the activities widget from /usr/share/kubuntu-default-settings/kde4-profile/default/share/apps/plasma-desktop/init/00-defaultLayout.js but on the first login on the new user the widget is still there. Is there some other place that adds it?
[23:06] <shadeslayer> yes
[23:06] <shadeslayer> there's a kde specific update script that adds it
[23:07] <shadeslayer> /usr/share/kde4/apps/plasma-desktop/updates/addShowActivitiesManagerPlasmoid.js
[23:09] <ovidiu-florin> where is it called from? I want to disable it
[23:09] <shadeslayer> It's called by plasma code
[23:10] <shadeslayer> the only way to disable it is by patching the source or removing that file
[23:11] <ovidiu-florin> removing the file won't affect it if the user later adds the widget?
[23:12] <shadeslayer> nope
[23:12] <shadeslayer> however the file will probably reappear on a update
[23:12] <shadeslayer> causing the widget to be added on a upgrade
[23:12] <ovidiu-florin> what if I just comment the internals of that if?
[23:12] <shadeslayer> what if?
[23:12] <shadeslayer> upgrade will overwrite file
[23:12] <ovidiu-florin> oh..
[23:12] <shadeslayer> new file will not have comments
[23:13] <shadeslayer> log out -> log in -> new shiny plasmoid
[23:14] <ovidiu-florin> so there is no way to disable it for good
[23:14] <shadeslayer> nope
[23:14] <ovidiu-florin> that thing is very confusing for new users
[23:15] <shadeslayer> heheh
[23:15] <ovidiu-florin> they don't know what it is, and just click their way into it and all of the sudden their desktop is gone
[23:15] <ovidiu-florin> and the I get mad calls from angry users
[23:15] <ovidiu-florin> complaining that Kubuntu is bad
[23:16]  * ovidiu-florin experienced this before
[23:18] <ovidiu-florin> I have an oportunity to put Kubuntu in a kindergarden and I need a way to controll the user interface
[23:19] <shadeslayer> ovidiu-florin: the only way to fix that is to patch the source I'm afraid
[23:20] <ovidiu-florin> can't I make a script that deletes that file before login?
[23:20] <ovidiu-florin> :D
[23:20] <shadeslayer> well
[23:20] <ovidiu-florin> I guess that thing comes from upstream right?
[23:20] <shadeslayer> maybe, if you name it correctly
[23:20] <shadeslayer> it might just work
[23:21] <shadeslayer> I don't recall what I did when I had to remove that file
[23:21] <ovidiu-florin> if I name what correctly?
[23:21] <shadeslayer> ovidiu-florin: the update scripts are called in a sequence according to the name of the script
[23:22] <ovidiu-florin> where are these scripts located?
[23:22] <shadeslayer> "If there is more than one script, they are run sequentially in the alphabetical order of the file names."
[23:22] <shadeslayer> from http://techbase.kde.org/KDE_System_Administration/PlasmaDesktopScripting
[23:22] <shadeslayer> so if you name it so that it is run after the activities script, it'll work
[23:23] <shadeslayer> also remember that the paths are also taken into account
[23:23] <shadeslayer> read that page ^^ :P
[23:23] <shadeslayer> has everything you need
[23:24] <ovidiu-florin> ok, thanks