[00:06] -kubuntu-ci:#kubuntu-devel- Project mgmt_merger build #747: SUCCESS in 6 min 37 sec: http://kci.pangea.pub/job/mgmt_merger/747/
[00:30] -kubuntu-ci:#kubuntu-devel- Project yakkety_unstable_khelpcenter build #98: FAILURE in 21 min: http://kci.pangea.pub/job/yakkety_unstable_khelpcenter/98/
[00:39] -kubuntu-ci:#kubuntu-devel- Project yakkety_unstable_umbrello build #128: STILL FAILING in 32 min: http://kci.pangea.pub/job/yakkety_unstable_umbrello/128/
[00:42] -kubuntu-ci:#kubuntu-devel- Project yakkety_unstable_print-manager build #73: STILL UNSTABLE in 33 min: http://kci.pangea.pub/job/yakkety_unstable_print-manager/73/
[00:42] -kubuntu-ci:#kubuntu-devel- Project yakkety_unstable_kfind build #10: STILL UNSTABLE in 34 min: http://kci.pangea.pub/job/yakkety_unstable_kfind/10/
[00:45] -kubuntu-ci:#kubuntu-devel- Project xenial_unstable_umbrello build #143: STILL FAILING in 37 min: http://kci.pangea.pub/job/xenial_unstable_umbrello/143/
[00:51] -kubuntu-ci:#kubuntu-devel- Project xenial_unstable_konqueror build #24: STILL UNSTABLE in 44 min: http://kci.pangea.pub/job/xenial_unstable_konqueror/24/
[00:52] -kubuntu-ci:#kubuntu-devel- Project xenial_unstable_libkcompactdisc build #71: STILL UNSTABLE in 44 min: http://kci.pangea.pub/job/xenial_unstable_libkcompactdisc/71/
[00:52] -kubuntu-ci:#kubuntu-devel- Project zesty_unstable_trojita build #7: STILL UNSTABLE in 44 min: http://kci.pangea.pub/job/zesty_unstable_trojita/7/
[00:52] -kubuntu-ci:#kubuntu-devel- Project xenial_unstable_trojita build #6: STILL UNSTABLE in 45 min: http://kci.pangea.pub/job/xenial_unstable_trojita/6/
[00:52] -kubuntu-ci:#kubuntu-devel- Project yakkety_unstable_libkipi build #103: STILL UNSTABLE in 42 min: http://kci.pangea.pub/job/yakkety_unstable_libkipi/103/
[00:52] -kubuntu-ci:#kubuntu-devel- Project xenial_unstable_print-manager build #209: STILL UNSTABLE in 42 min: http://kci.pangea.pub/job/xenial_unstable_print-manager/209/
[01:00] -kubuntu-ci:#kubuntu-devel- Project zesty_unstable_kopete build #28: STILL UNSTABLE in 52 min: http://kci.pangea.pub/job/zesty_unstable_kopete/28/
[01:07] -kubuntu-ci:#kubuntu-devel- Project xenial_unstable_kopete build #127: STILL UNSTABLE in 55 min: http://kci.pangea.pub/job/xenial_unstable_kopete/127/
[01:09] -kubuntu-ci:#kubuntu-devel- Project yakkety_unstable_kwin build #76: STILL FAILING in 1 hr 1 min: http://kci.pangea.pub/job/yakkety_unstable_kwin/76/
[01:43] -kubuntu-ci:#kubuntu-devel- Project xenial_unstable_kitemmodels build #337: STILL UNSTABLE in 26 min: http://kci.pangea.pub/job/xenial_unstable_kitemmodels/337/
[01:43] -kubuntu-ci:#kubuntu-devel- Project zesty_unstable_krita build #25: STILL UNSTABLE in 1 hr 35 min: http://kci.pangea.pub/job/zesty_unstable_krita/25/
[01:49] -kubuntu-ci:#kubuntu-devel- Project xenial_unstable_kdiagram build #28: FAILURE in 32 min: http://kci.pangea.pub/job/xenial_unstable_kdiagram/28/
[02:05] -kubuntu-ci:#kubuntu-devel- Project xenial_unstable_kdiagram build #29: STILL FAILING in 10 min: http://kci.pangea.pub/job/xenial_unstable_kdiagram/29/
[02:17] -kubuntu-ci:#kubuntu-devel- Project yakkety_unstable_kitemmodels build #137: STILL UNSTABLE in 41 min: http://kci.pangea.pub/job/yakkety_unstable_kitemmodels/137/
[02:28] <DarinMiller> ahoneybun: Is your Kicker search fixed?
 No
[02:51] <tsimonq2> wxl, DarinMiller, ahoneybun, valorie: Who wants to do some packaging work? I'll walk you through it... :) (first come first serve :P)
[02:52] -kubuntu-ci:#kubuntu-devel- Project zesty_unstable_kitemmodels build #41: STILL UNSTABLE in 35 min: http://kci.pangea.pub/job/zesty_unstable_kitemmodels/41/
[02:54] <valorie> tsimonq2: too much wine tonight, sorry
[02:54] <valorie> actual wine, not WINE
[02:55] <DarinMiller> I call shotgun....
[02:55] <DarinMiller> wxl: What shall we package 1st?
[02:56] <tsimonq2> DarinMiller: \o/ :)
[02:56] <valorie> (peruse)
[02:56] <DarinMiller> ahoneybun: Plasma 5.8.3 or 5.8.4.  I had the kicker issue on 5.83, but staging ppa's with 5.8.4 fixed it.
[02:56] <tsimonq2> No this is a special request. :P
[02:57] <tsimonq2> !info kdevelop
[02:57] <tsimonq2> EEK!
[02:57] <DarinMiller> wow, thought this channel was dead....
[02:58] <tsimonq2> DarinMiller: Hm?!?
[02:58] <DarinMiller> cool. I like kdevelop.  I use it at work.
[02:58] <tsimonq2> :D
[02:58] <tsimonq2> Our job is to get 5.0.3 packaged and in a PPA.
[02:58] <valorie> ovidiuflorin will be so happy if there is an up-to-date one in the archive!
[02:58] <DarinMiller> Lots of silence this evening.... (I thought everyone must have gone to bed...)
[02:58] <tsimonq2> valorie: Yep, in Zesty. :)
[02:58] <DarinMiller> cool.
[02:59] <DarinMiller> jumping on jenkins now....
[03:00] <tsimonq2> DarinMiller: Not a KCI thing. We grab it from the PPA and package like normal. :)
[03:01] <tsimonq2> DarinMiller: So, you know how to get started, or shall I lead the way? :)
[03:01] <tsimonq2> !info kdevelop zesty
[03:02] <DarinMiller> Clive showed me how to that once, but I cannot find my link to the PPA list.
[03:02] <DarinMiller> to do^
[03:02] <tsimonq2> Huzzah: https://launchpad.net/~kdevelop/+archive/ubuntu/release/
[03:03] <DarinMiller> oh, an lp link. I was thinking it was elsewhere....
[03:05] <tsimonq2> DarinMiller: Do you have access to my linode container?
[03:06] <DarinMiller> Uhh, I don't know where or what that is....
[03:07] <tsimonq2> Ok, so the ninjas are each given their own container that they get to use for development purposes at dev.kubuntu.co.uk.
[03:07] <tsimonq2> Where's your SSH key?
[03:08] <DarinMiller> I have it  here: https://launchpad.net/~darinsmiller
[03:09] <DarinMiller> https://launchpad.net/~darinsmiller/+sshkeys
[03:09] <tsimonq2> Ok, now, ssh -p 2202 ubuntu@dev.kubuntu.co.uk
[03:10] <DarinMiller> command line IRC, way cool!
[03:11] <DarinMiller> local working directory?
[03:11] <tsimonq2> So I'll type comments in the workspace and we can do that. :)
[03:11] <tsimonq2> Well it's just a fancy term for "the dir we're putting everything in." :P
[03:12] <DarinMiller> Ok, I see the ~/workspace/kdevelop directory...
[03:12] <tsimonq2> I've been told I type fast so please stop me if I'm going too fast. :P
[03:13] <tsimonq2> RIght now I'd like to see if Clive put anything in Git or just uploaded to the PPA.
[03:14] <tsimonq2> So now that it looks like he actually committed things to Git (yay!) it's much easier to work off of now.
[03:14] <DarinMiller> Yep. Clive cool!
[03:14] <DarinMiller> is cool!
[03:15] <tsimonq2> So let's see what the last commit contained. He seems to have done a new upstream release, and while there's tooling for this, I want to look at the diff and show you everything that goes into this. :)
[03:15] <tsimonq2> Heh, so, yeah, that's pretty much it... :P
[03:15] <DarinMiller> very good.
[03:16] <tsimonq2> So now we just need a new changelog entry there. We can do this by entering the "dch" command.
[03:16] <DarinMiller> ah yes... I have used that once.
[03:16] <tsimonq2> It's a nice tool that you should read the manpage for. ;)
[03:17] <tsimonq2> Want your name in the changelog or mine? :)
[03:17] <DarinMiller> Your's fine since you doing all the work. ..
[03:18] <tsimonq2> Ok. :)
[03:18] <tsimonq2> SO let's commit that to Git and push it...
[03:18] <DarinMiller> I find it strange that comments between major changes are inserted at the bottom..
[03:19] <DarinMiller> What is the -a?
[03:19] <tsimonq2> All
[03:19] <DarinMiller> Why not -A
[03:19] <tsimonq2> Because... that's how they designed it? XD
[03:19] <tsimonq2> ¯\_(ツ)_/¯
[03:20] <tsimonq2> So if you look at that script, DarinMiller, I use that to check out KCI things
[03:21] <DarinMiller> I wasn'
[03:21] <DarinMiller> t done reading it all but OK.
[03:21] <tsimonq2> Oh I'm sorry. What did you not get yet?
[03:22] <DarinMiller> How does it know what tarball to dl?  In one of the config files I presume?
[03:22] <tsimonq2> Yep. :)
[03:22] <tsimonq2> One of santa_'s things, blame him. XDD
[03:22] <tsimonq2> (kidding)
[03:22] <DarinMiller> santa_'s cool too. ;)
[03:22] <tsimonq2> So now I have a script that just builds it for me. Let's pop this open...
[03:23] <tsimonq2> I don't know about you but I'd rather not type that long sbuild command over and over again. XD
[03:23] <DarinMiller> oh, the magic sbuild enviro.  I finally got mine working but have not tested it yet....
[03:24] <tsimonq2> You got the gist of what that script does? :)
[03:24] <DarinMiller> is this in the kdevelop toolbox?
[03:24] <tsimonq2> Nope, my own way of not typing out things over and over.
[03:24] <DarinMiller> I like it.
[03:24] <tsimonq2> XD
[03:25] <tsimonq2> Oh do I hate this error with a burning passion...
[03:26] <tsimonq2> "Version number suggests Ubuntu changes, but Maintainer: does not have Ubuntu address"
[03:26] <DarinMiller> hold on, reading error....
[03:27] <DarinMiller> How to fix?
[03:27] <DarinMiller> That's the error I was fighting 1.5 weeks ago...
[03:27] <tsimonq2> Ah, I see, hold on, let me find some docs...
[03:29] <tsimonq2> So we need to change Maintainer to this:
[03:29] <tsimonq2> Maintainer: Ubuntu Developers <ubuntu-devel-discuss@lists.ubuntu.com>
[03:29] <tsimonq2> Then use XSBC-Original-Maintainer:
[03:29] <tsimonq2> Let me demonstrate...
[03:30] <tsimonq2> That should do the trick.
[03:30] <tsimonq2> See what I did there?
[03:30] <DarinMiller> Yes, replaced the Mainter line....
[03:31] <DarinMiller> Maintainer...
[03:31] <tsimonq2> That's literally what the problem is... :P
[03:31] <tsimonq2> And oh shoot, we're not packaging for KCI, are we? I need to replace the KCI tarball and show you uscan!
[03:31] <DarinMiller> I assume they build just fine on LP? No? So why does it break locally?  wrong envior settings?
[03:32] <tsimonq2> Hm, not sure. Maybe gbp-ppa does something...
[03:33] <tsimonq2> Great, I'm smart...
[03:33]  * DarinMiller <shakes head while chuckling>
[03:34] <tsimonq2> DarinMiller: You know about uscan yet?
[03:34] <DarinMiller> tsimonq2: nope
[03:34] <tsimonq2> DarinMiller: Awesome time saving tool for fetching source tarballs. That's what debian/watch is for. :)
[03:35] <DarinMiller> stop
[03:35] <tsimonq2> Yep, I planned on it. :)
[03:35] <DarinMiller> pwd please
[03:36] <DarinMiller> nm  I see your prompt...
[03:36] <DarinMiller> wt... 3 levels of kdevelop....
[03:36] <tsimonq2> So you see what I did?
[03:36] <tsimonq2> lol ik XD
[03:37] <tsimonq2> Bueno?
[03:37] <DarinMiller> you uscan'd --down-cur-ver very deep in the tree
[03:38] <tsimonq2> Yup, see?
[03:38] <DarinMiller> yes
[03:39] <tsimonq2> Ok, cool.
[03:39] <tsimonq2> Let's build it! :D
[03:39] <DarinMiller> does the script auto use -jx? where x is the # of cores?
 Mmmm not sure
[03:41] <DarinMiller> or maybe it was number of threads.  I played around a little bit with that and it makes a big difference!
[03:43] <tsimonq2> Screen loading time is slow, watch my irssi clock. :P
[03:43] <DarinMiller> your irssi clock?
[03:43] <DarinMiller> oh i see ti.
[03:45] <DarinMiller> Why did we have to grab kdevelop manually from LP?  Do we not have a script to batch process the kde packages?
[03:45] <tsimonq2> Eh I felt lazy, I'm sure there's a script somewhere... :P
[03:46] <tsimonq2> Oh noes!
[03:46] <DarinMiller> I need this experience.  But, manually grabbing all plasma, frameworks and applications would be a bit tedious.
[03:46] <DarinMiller> crash and burn
[03:47] <DarinMiller> oh, secret build script
 KCI has a different Qt than the archive
 Bah, it's just my KCI script except different values for the PPAs. :)
[03:48] <DarinMiller> I assume sbuild could have been configured to match kci, yes?
[03:49] <DarinMiller> but wait, this is not using sbuild....
[03:49] <DarinMiller> you killed it.
[03:50] <DarinMiller> dpkg-build died
[03:50] <tsimonq2> Yup, let's see. :)
[03:52] <tsimonq2> Ohhhh I know why...
[03:53] <tsimonq2> So it needs a newer package, right?
[03:53] <tsimonq2> Clive had all the needed deps in that PPA...
[03:53] <tsimonq2> I;m smart... :P
[03:56] <DarinMiller> yakkety?
[03:56] <tsimonq2> He doesn't have Zesty builds, it'll do.
[03:58] <DarinMiller> I like your work envir.  Any reason to not add ~/bin to your path to reduce typing?
 ...it is there
[03:58] <DarinMiller> hopefully this is like a cat and has several lives :)
 Oh sorry, gotta attend to UWN stuff
[03:59] <DarinMiller> Ok, np
[04:01] <tsimonq2> Let's continue this tomorrow, I have UWN to do then bed, and this requires a lot more work...
[04:01] <tsimonq2> (than I thought)
[04:01] <DarinMiller> Sounds good, I will play with what you showed me for now....
[04:01] <tsimonq2> Ok, let me know if you have questions. :)
[04:01] <tsimonq2> Now get off my container! :D
[04:02] <DarinMiller> how? just close my terminal?
[04:02] <tsimonq2> Ctrl + A, D, Ctrl + D
[04:02] <DarinMiller> I think you locked it.... not typing accepted....
[04:03] <tsimonq2>   
[04:03] <tsimonq2> You locked it up! :P
[04:03] <DarinMiller> ok, i just killed my terminal.....
[04:03] <tsimonq2> :)
[04:04] <DarinMiller> tsimonq2: Mind pastebin'ing link your sbuild script?
[04:05] <tsimonq2> Sure. :)
[04:06] <tsimonq2> This is KCI: http://paste.ubuntu.com/23586636/
[04:07] <DarinMiller> Merci
[04:37] -kubuntu-ci:#kubuntu-devel- Project yakkety_unstable_frameworkintegration build #184: STILL UNSTABLE in 16 min: http://kci.pangea.pub/job/yakkety_unstable_frameworkintegration/184/
[04:45] -kubuntu-ci:#kubuntu-devel- Project zesty_unstable_frameworkintegration build #36: STILL UNSTABLE in 15 min: http://kci.pangea.pub/job/zesty_unstable_frameworkintegration/36/
[05:11] -kubuntu-ci:#kubuntu-devel- Project yakkety_unstable_kirigami build #73: STILL UNSTABLE in 17 min: http://kci.pangea.pub/job/yakkety_unstable_kirigami/73/
[05:14] -kubuntu-ci:#kubuntu-devel- Project xenial_unstable_umbrello build #144: STILL FAILING in 13 min: http://kci.pangea.pub/job/xenial_unstable_umbrello/144/
[05:28] -kubuntu-ci:#kubuntu-devel- Project yakkety_unstable_marble build #65: STILL FAILING in 33 min: http://kci.pangea.pub/job/yakkety_unstable_marble/65/
[05:28] -kubuntu-ci:#kubuntu-devel- Project xenial_unstable_kstars build #309: STILL UNSTABLE in 27 min: http://kci.pangea.pub/job/xenial_unstable_kstars/309/
[05:29] -kubuntu-ci:#kubuntu-devel- Project yakkety_unstable_umbrello build #129: STILL FAILING in 18 min: http://kci.pangea.pub/job/yakkety_unstable_umbrello/129/
[05:35] -kubuntu-ci:#kubuntu-devel- Project zesty_unstable_peruse build #15: STILL UNSTABLE in 14 min: http://kci.pangea.pub/job/zesty_unstable_peruse/15/
[05:36] -kubuntu-ci:#kubuntu-devel- Project zesty_unstable_print-manager build #25: STILL UNSTABLE in 14 min: http://kci.pangea.pub/job/zesty_unstable_print-manager/25/
[05:36] -kubuntu-ci:#kubuntu-devel- Project yakkety_unstable_ktp-auth-handler build #175: STILL UNSTABLE in 25 min: http://kci.pangea.pub/job/yakkety_unstable_ktp-auth-handler/175/
[05:46] -kubuntu-ci:#kubuntu-devel- Project zesty_unstable_kstars build #37: STILL UNSTABLE in 35 min: http://kci.pangea.pub/job/zesty_unstable_kstars/37/
[05:46] -kubuntu-ci:#kubuntu-devel- Project yakkety_unstable_kstars build #176: STILL UNSTABLE in 35 min: http://kci.pangea.pub/job/yakkety_unstable_kstars/176/
[05:46] -kubuntu-ci:#kubuntu-devel- Project zesty_unstable_libkcompactdisc build #31: STILL UNSTABLE in 18 min: http://kci.pangea.pub/job/zesty_unstable_libkcompactdisc/31/
[05:46] -kubuntu-ci:#kubuntu-devel- Project zesty_unstable_ktp-common-internals build #28: STILL UNSTABLE in 25 min: http://kci.pangea.pub/job/zesty_unstable_ktp-common-internals/28/
[05:46] -kubuntu-ci:#kubuntu-devel- Project yakkety_unstable_akonadi build #220: STILL UNSTABLE in 36 min: http://kci.pangea.pub/job/yakkety_unstable_akonadi/220/
[05:51] -kubuntu-ci:#kubuntu-devel- Project yakkety_unstable_katomic build #178: FAILURE in 4 min 44 sec: http://kci.pangea.pub/job/yakkety_unstable_katomic/178/
[05:51] -kubuntu-ci:#kubuntu-devel- Project yakkety_unstable_bomber build #137: FAILURE in 4 min 44 sec: http://kci.pangea.pub/job/yakkety_unstable_bomber/137/
[05:51] -kubuntu-ci:#kubuntu-devel- Project yakkety_unstable_akonadi-mime build #121: FAILURE in 4 min 13 sec: http://kci.pangea.pub/job/yakkety_unstable_akonadi-mime/121/
[05:51] -kubuntu-ci:#kubuntu-devel- Project yakkety_unstable_plasma-sdk build #161: FAILURE in 4 min 44 sec: http://kci.pangea.pub/job/yakkety_unstable_plasma-sdk/161/
[05:51] -kubuntu-ci:#kubuntu-devel- Project yakkety_unstable_kmines build #103: FAILURE in 4 min 44 sec: http://kci.pangea.pub/job/yakkety_unstable_kmines/103/
[05:58] -kubuntu-ci:#kubuntu-devel- Project xenial_unstable_ktp-common-internals build #235: STILL UNSTABLE in 31 min: http://kci.pangea.pub/job/xenial_unstable_ktp-common-internals/235/
[05:58] -kubuntu-ci:#kubuntu-devel- Project zesty_unstable_marble build #44: STILL UNSTABLE in 37 min: http://kci.pangea.pub/job/zesty_unstable_marble/44/
[05:58] -kubuntu-ci:#kubuntu-devel- Project zesty_unstable_konqueror build #24: STILL UNSTABLE in 31 min: http://kci.pangea.pub/job/zesty_unstable_konqueror/24/
[05:58] -kubuntu-ci:#kubuntu-devel- Project zesty_unstable_cantor build #33: STILL UNSTABLE in 31 min: http://kci.pangea.pub/job/zesty_unstable_cantor/33/
[05:58] -kubuntu-ci:#kubuntu-devel- Project xenial_unstable_plasma-integration build #49: STILL UNSTABLE in 29 min: http://kci.pangea.pub/job/xenial_unstable_plasma-integration/49/
[05:58] -kubuntu-ci:#kubuntu-devel- Project xenial_unstable_kirigami build #66: STILL UNSTABLE in 29 min: http://kci.pangea.pub/job/xenial_unstable_kirigami/66/
[06:09] -kubuntu-ci:#kubuntu-devel- Project zesty_unstable_kfind build #16: STILL UNSTABLE in 23 min: http://kci.pangea.pub/job/zesty_unstable_kfind/16/
[06:09] -kubuntu-ci:#kubuntu-devel- Yippee, build fixed!
[06:09] -kubuntu-ci:#kubuntu-devel- Project yakkety_unstable_khelpcenter build #99: FIXED in 23 min: http://kci.pangea.pub/job/yakkety_unstable_khelpcenter/99/
[06:09] -kubuntu-ci:#kubuntu-devel- Project yakkety_unstable_marble build #66: STILL FAILING in 36 min: http://kci.pangea.pub/job/yakkety_unstable_marble/66/
[06:09] -kubuntu-ci:#kubuntu-devel- Project zesty_unstable_ktp-auth-handler build #29: STILL UNSTABLE in 23 min: http://kci.pangea.pub/job/zesty_unstable_ktp-auth-handler/29/
[06:18] -kubuntu-ci:#kubuntu-devel- Yippee, build fixed!
[06:18] -kubuntu-ci:#kubuntu-devel- Project yakkety_unstable_katomic build #179: FIXED in 21 min: http://kci.pangea.pub/job/yakkety_unstable_katomic/179/
[06:18] -kubuntu-ci:#kubuntu-devel- Project xenial_unstable_marble build #58: STILL UNSTABLE in 31 min: http://kci.pangea.pub/job/xenial_unstable_marble/58/
[06:18] -kubuntu-ci:#kubuntu-devel- Yippee, build fixed!
[06:18] -kubuntu-ci:#kubuntu-devel- Project yakkety_unstable_bomber build #138: FIXED in 22 min: http://kci.pangea.pub/job/yakkety_unstable_bomber/138/
[06:18] -kubuntu-ci:#kubuntu-devel- Yippee, build fixed!
[06:18] -kubuntu-ci:#kubuntu-devel- Project yakkety_unstable_akonadi-mime build #122: FIXED in 22 min: http://kci.pangea.pub/job/yakkety_unstable_akonadi-mime/122/
[06:18] -kubuntu-ci:#kubuntu-devel- Yippee, build fixed!
[06:18] -kubuntu-ci:#kubuntu-devel- Project yakkety_unstable_kmines build #104: FIXED in 22 min: http://kci.pangea.pub/job/yakkety_unstable_kmines/104/
[06:18] -kubuntu-ci:#kubuntu-devel- Project zesty_unstable_plasma-sdk build #36: STILL UNSTABLE in 19 min: http://kci.pangea.pub/job/zesty_unstable_plasma-sdk/36/
[06:18] -kubuntu-ci:#kubuntu-devel- Project xenial_unstable_ktp-auth-handler build #223: STILL UNSTABLE in 20 min: http://kci.pangea.pub/job/xenial_unstable_ktp-auth-handler/223/
[06:18] -kubuntu-ci:#kubuntu-devel- Project yakkety_unstable_cantor build #129: STILL UNSTABLE in 32 min: http://kci.pangea.pub/job/yakkety_unstable_cantor/129/
[06:18] -kubuntu-ci:#kubuntu-devel- Project yakkety_unstable_plasma-sdk build #162: NOW UNSTABLE in 22 min: http://kci.pangea.pub/job/yakkety_unstable_plasma-sdk/162/
[06:19] -kubuntu-ci:#kubuntu-devel- Project zesty_unstable_plasma-integration build #37: STILL UNSTABLE in 32 min: http://kci.pangea.pub/job/zesty_unstable_plasma-integration/37/
[06:19] -kubuntu-ci:#kubuntu-devel- Project yakkety_unstable_kalzium build #67: STILL UNSTABLE in 32 min: http://kci.pangea.pub/job/yakkety_unstable_kalzium/67/
[06:19] -kubuntu-ci:#kubuntu-devel- Project yakkety_unstable_konqueror build #19: STILL UNSTABLE in 32 min: http://kci.pangea.pub/job/yakkety_unstable_konqueror/19/
[06:27] -kubuntu-ci:#kubuntu-devel- Project yakkety_unstable_kwin build #77: STILL FAILING in 41 min: http://kci.pangea.pub/job/yakkety_unstable_kwin/77/
[06:31] -kubuntu-ci:#kubuntu-devel- Project xenial_unstable_discover build #77: STILL UNSTABLE in 21 min: http://kci.pangea.pub/job/xenial_unstable_discover/77/
[06:31] -kubuntu-ci:#kubuntu-devel- Project xenial_unstable_kalzium build #124: STILL UNSTABLE in 21 min: http://kci.pangea.pub/job/xenial_unstable_kalzium/124/
[06:31] -kubuntu-ci:#kubuntu-devel- Project xenial_unstable_plasma-sdk build #269: STILL UNSTABLE in 22 min: http://kci.pangea.pub/job/xenial_unstable_plasma-sdk/269/
[06:38] -kubuntu-ci:#kubuntu-devel- Project xenial_unstable_cantor build #235: STILL UNSTABLE in 28 min: http://kci.pangea.pub/job/xenial_unstable_cantor/235/
[06:58] -kubuntu-ci:#kubuntu-devel- Project yakkety_unstable_plasma-workspace build #73: STILL FAILING in 30 min: http://kci.pangea.pub/job/yakkety_unstable_plasma-workspace/73/
[07:03] -kubuntu-ci:#kubuntu-devel- Project yakkety_unstable_messagelib build #75: STILL FAILING in 25 min: http://kci.pangea.pub/job/yakkety_unstable_messagelib/75/
[07:20] -kubuntu-ci:#kubuntu-devel- Project yakkety_unstable_messagelib build #76: STILL FAILING in 11 min: http://kci.pangea.pub/job/yakkety_unstable_messagelib/76/
[07:30] -kubuntu-ci:#kubuntu-devel- Project yakkety_unstable_plasma-workspace build #74: STILL FAILING in 27 min: http://kci.pangea.pub/job/yakkety_unstable_plasma-workspace/74/
[07:38] -kubuntu-ci:#kubuntu-devel- Project yakkety_unstable_korganizer build #22: STILL UNSTABLE in 17 min: http://kci.pangea.pub/job/yakkety_unstable_korganizer/22/
[07:50] -kubuntu-ci:#kubuntu-devel- Project xenial_unstable_messagelib build #63: FAILURE in 13 min: http://kci.pangea.pub/job/xenial_unstable_messagelib/63/
[07:53] -kubuntu-ci:#kubuntu-devel- Project zesty_unstable_korganizer build #26: STILL UNSTABLE in 29 min: http://kci.pangea.pub/job/zesty_unstable_korganizer/26/
[08:11] <lordievader> Good morning.
[08:20] -kubuntu-ci:#kubuntu-devel- Project xenial_unstable_messagelib build #64: STILL FAILING in 24 min: http://kci.pangea.pub/job/xenial_unstable_messagelib/64/
[08:20] <yofel> valorie: sorry, no. As I'm not particulary aware of what the guys have been up to with the packaging, sponsoring would involve reviewing every single package which would take several hours that I'm not willing to invest.
[08:26] -kubuntu-ci:#kubuntu-devel- Project xenial_unstable_akregator build #36: FAILURE in 6 min 20 sec: http://kci.pangea.pub/job/xenial_unstable_akregator/36/
[08:36] -kubuntu-ci:#kubuntu-devel- Project xenial_unstable_akregator build #37: STILL FAILING in 4 min 51 sec: http://kci.pangea.pub/job/xenial_unstable_akregator/37/
[08:37] -kubuntu-ci:#kubuntu-devel- Project xenial_unstable_korganizer build #30: STILL UNSTABLE in 17 min: http://kci.pangea.pub/job/xenial_unstable_korganizer/30/
[09:05] <acheronuk> why why why
[09:05] <acheronuk> Architecture 	Builders 	Queue
[09:05] <acheronuk> amd64 	88 	35911 jobs (39 hours) 
[09:06] <acheronuk> just my luck to have archive test rebuilds going on when we upload frameworks! 
[09:24] -kubuntu-ci:#kubuntu-devel- Project yakkety_unstable_messagelib build #77: STILL FAILING in 21 min: http://kci.pangea.pub/job/yakkety_unstable_messagelib/77/
[09:25] <yofel> acheronuk: the test rebuilds should have the lowest possible build score though, so you should't have to care about them
[09:27] <acheronuk> yofel: yeah, I noticed now :)
[09:28] <acheronuk> now sure if they slow down autopackagetests, but guess even they have higher priorities while they do share the same builders
[09:28] -kubuntu-ci:#kubuntu-devel- Yippee, build fixed!
[09:28] -kubuntu-ci:#kubuntu-devel- Project xenial_unstable_messagelib build #65: FIXED in 26 min: http://kci.pangea.pub/job/xenial_unstable_messagelib/65/
[09:28] <yofel> do they? I thought autopackagetests run on a different infrastructure
[09:29] <yofel> might share the machines though
[09:36] <acheronuk> ah, maybe...
[09:36] <acheronuk> [21:51]  <cjwatson> those don't affect LP builders
[09:36] <acheronuk> [21:51]  <cjwatson> they run on the same cloud but there are quotas
[09:42] <acheronuk> patience is required then for all the "tests in progress"
[09:57] -kubuntu-ci:#kubuntu-devel- Project yakkety_unstable_messagelib build #78: STILL FAILING in 27 min: http://kci.pangea.pub/job/yakkety_unstable_messagelib/78/
[10:17] -kubuntu-ci:#kubuntu-devel- Yippee, build fixed!
[10:17] -kubuntu-ci:#kubuntu-devel- Project xenial_unstable_akregator build #38: FIXED in 16 min: http://kci.pangea.pub/job/xenial_unstable_akregator/38/
[10:17] -kubuntu-ci:#kubuntu-devel- Project xenial_unstable_korganizer build #31: STILL UNSTABLE in 16 min: http://kci.pangea.pub/job/xenial_unstable_korganizer/31/
[10:17] -kubuntu-ci:#kubuntu-devel- Project zesty_unstable_korganizer build #27: STILL UNSTABLE in 16 min: http://kci.pangea.pub/job/zesty_unstable_korganizer/27/
[12:00] <acheronuk> yofel tsimonq2 santa_ et al: could you please review (and add to if needed) the list of packages that we needs adding to our packageset please?
[12:01] <acheronuk> trello card is here: https://trello.com/c/NsNY1KVq/237-packages-to-add-to-kubuntu-packageset
[12:01] <BluesKaj> Howdy all
[12:33] <ahoneybun> ?
[13:02] <acheronuk> ahoneybun: ? what?
 Mm why was I added to that card?
 I have no idea about package set
[13:05] <acheronuk> no problem
 Oh
[14:11] <clivejo> @tsimonq2 how did you get on with kdevelop?
 Not good so far, clivejo
 Working on it
 ALSO
[14:24] <IrcsomeBot1> * tsimonq2 rings large bell
 Backports Landing is broken, read the kubuntu-ppa ML
 You know, the Launchpad ML
[14:25] <clivejo> need help with anything?
[14:25] -kubuntu-ci:#kubuntu-devel- Project zesty_unstable_umbrello build #40: STILL FAILING in 17 min: http://kci.pangea.pub/job/zesty_unstable_umbrello/40/
[14:43] -kubuntu-ci:#kubuntu-devel- Project zesty_unstable_umbrello build #41: STILL FAILING in 13 min: http://kci.pangea.pub/job/zesty_unstable_umbrello/41/
[15:14] <yofel> huh, why does kubuntu-ppa have a ML now o.O?
 Why is -landing broken?
[15:16] <clivejo> why am I so cold?
 Yea why does it have a ML
 It should be on -devel
[15:33] <clivejo> looking at the archives its had one for quite a while
[15:36] <acheronuk> I can replicate the kde-l10-nl breakage and am trying a fix in my ppa
[15:36] <acheronuk> not sure if I'm going about it the right way.....
[16:10] <yofel> hm, guess I was just irritated by the moderation notice
[16:45] <santa_> acheronuk: ack, I have added kjots, also there's another trello card to make an script to check the packageset for frameworks/plasma/applications
[16:46] <acheronuk> santa_: ok. will have a look at that later. thanks
[16:46] <santa_> acheronuk: another topic: there's a lot of changes in KA, have you seen them?
[16:46] <santa_> to sum up
[16:47] <acheronuk> santa_: yes, I've seem some of them. not sure I've 100% absorbed it all yet
[16:47] <santa_> 1. I moved most of the package metadata (i.e. data which may change on each new upstream release) to the package-metadata directory
[16:49] <santa_> 2. I changed the way the configuration is handled, now we won't have json files under conf/ we have now a conf/defaultrc having the default configuration and you can configure KA editing ~/.kubuntu-automation.conf
[16:51] <santa_> 3. now you can configure the signing, so you won't have to type '-- -us -uc' each and everytime you execute gbp-whatever
[16:51] <santa_> 4. lintian is disabled automatically when doing 'do-all gbp-whatever', this feature can be disabled in the user configuration
[16:53] <santa_> if 4. works ok I would like to do something similar for git merge, to add '--no-edit' automagically
[16:53] <santa_> acheronuk: any doubts, questions or suggestions?
[16:54] <acheronuk> not 100% sure what the point of 4. is, but it'll probably be fairly obvious when I take a close look.
[16:56] <santa_> from the README.ng
[16:56] <santa_>         NOTE: don't miss the '--no-edit' option for 'git merge', otherwise the editor may pop up
[16:56] <santa_>               for any and all of the dozens of packages you are working on
[17:02] <santa_> hmm, sorry
[17:02] <santa_> acheronuk: you meant the lintian auto disabling? what's the point of auto disabling it?
[17:02] <acheronuk> yes
[17:04] <santa_> the point is getting a "do-all gbp-whatever" done faster
[17:04] <santa_> for instance when we package a new version of frameworks we would be executing lintian twice
[17:04] <santa_> (at least)
[17:05] <santa_> one when we do "do-all gbp-newrelease" and another one when the packages are being built in the ppa
[17:05] <santa_> the first one is pointless because:
[17:06] <santa_> 1. it's done against a source build, therefore the list of issues is going to be incomplete
[17:06] <santa_> 2. we will already have a complete list of lintian issues in the status page
[17:08] <santa_> for the record a "do-all gbp-ppa" against frameworks takes ~ 10 mins here without lintian
[17:08] <santa_> ~ 15 mins with lintian
[17:09] <santa_> acheronuk: got it?
[17:11] <acheronuk> yes, got it
[17:12] <santa_> k, thanks for your attention :)
[17:16] <acheronuk> santa_: the retry script is seeing the kio-dev package in the archive as available, but the dev package is actually not installable as it's held up with a new binary for approval by the release team
 I'm against stopping Lintian.
[17:17] <santa_> tsimonq2: have you read the complete thing?
[17:17] <acheronuk>  New binary: kio [amd64] (zesty-proposed/universe) [5.28.0-0ubuntu1] (kubuntu)
 We can't catch *all* things reported by Lintian because it's a source package, but not the obvious stuff. We all make mistakes.
[17:19] <santa_> tsimonq2: let me insist. did you read the complete thing?
[17:25] <acheronuk> santa_:  if it's not possible to detect held binaries, maybe the retry script can cache it's last output to compare and warn you that it's not managing to do anything new, so you should investigat?
[17:26] <acheronuk> or that a dev package that should be available actually wasn't?
[17:30] <santa_> acheronuk: we just have to check that the version is actually correct, I'm going to work on this now, who is executing the script, clive?
[17:30] <acheronuk> santa_: yep
[17:30] <santa_> clivejo: ping?
[17:33] <acheronuk> what version?
[17:34] <santa_> the version of the source package
[17:39] <clivejo> yes?
[17:43] <santa_> clivejo: I'm working on a patch to solve the issue you are pointing out with kio wating in the new queue, I need you to test it because I won't have permissions to do that. are you using KA from latest master?
[17:43] <clivejo> yes, latest as of about 13:00 today
[17:44] <santa_> allright, I will give you a diff of the intended patch as soon as I have it, ok?
[17:45] <clivejo> Im off for food very shortlyt
[17:51] <santa_> no problem, there's no rush
[18:01] <marco-parillo> acheronuk: I saw your answer to a Plasma 5.8 query in the #kubuntu channel. When you you think inviting them to help test will be helpful?
[18:04] <acheronuk> marco-parillo: pretty soon for people who can afford to break their boxes. just today I had someone who took a chance at the landing ppa and found an issue with language packs upgrade, that I then fixed
[18:05] <acheronuk> marco-parillo: I would just like to discuss when where and who to include in any "calls for testing"
[18:05] <acheronuk> I really want to get that in backports before Xmas :)
[18:06] <acheronuk> but only if it's going to be a good experience for users. half baked is not good enough
[18:07] <marco-parillo> Understood. I always wonder when people complain, how willing they are to just try something.
[18:09] <acheronuk> yes, have had people want to try something new and untested because they just 'want it', then call you every name under the sun when it's not perfect. thus are people
[19:40] <santa_> acheronuk, clivejo: I have just pushed a few fixes to kubuntu-retry-builds, now it should deal better with missing build dependencies. see the commit log for details
[19:41] <santa_> acheronuk: so I didn't check the version actually, using the info from launchpad directly seems better
[19:42] <sick_rimmit> Hi there
[19:42] <santa_> right now if you execute it against the archive it will rebuild nothing because of kio
[20:02] <clivejo> ImportError: No module named jsmin
[20:06] <clivejo> Rebuild candidates: Total: 486, Skipped: 346, Valid: 140, Actually rebuilt: 0
[20:10] <santa_> clivejo: about jsmin, the needed package should be installed by the ka-deps package
[20:10] <santa_> clivejo: see the section 2.3 from README.ng
[20:20] <sick_rimmit> Hey there
[20:20] <sick_rimmit> We're in BBB holding a pre-show
[20:20] <sick_rimmit> be great if you guys have any news to share with us
 Kubuntu Podcast #19 is now LIVE! Join us in http://www.youtube.com/c/KubuntuPodcast/live
[21:16] <valorie> hi folks, I don't see peruse on that trello card -- should I add it?
[21:20] <valorie> oh, duh, if I login it helps
[21:20] <valorie> !info minuet
[21:20] <valorie> !info minuet zesty
[21:20] <ahoneybun> it's not in there
[21:21] <valorie> just checking before I added it
[21:27] <wxl> monr kids
[21:27] <acheronuk> evening :)
[21:36] <santa_> wxl: hey if you have some spare time would you like to try to update konversation for zesty?
[21:36] <wxl> santa_: i got into work late but i can work on that in a bit.
[21:37] <santa_> wxl: ok, I will be very glad to review, once we get it we could sru it for yakkety
[21:39] <wxl> santa_: is there a reason it's not in zety fix?
[21:41] <santa_> wxl: because it doesn't fail I guess, we have 1.6.1, a fellow kde devel requested the latest 1.6.2 version
[21:42] <santa_> 1.6.1 crashes when editing a server, just checked
 editing servers apparently crashes 1.6.1
[21:42] <wxl> is there a bug report?
[21:43] <acheronuk> not sure if a bug, but the the fix commit or one of them is: https://cgit.kde.org/konversation.git/commit/?h=1.6&id=4fa92f7e55dea6354a7dbeae1ddf62c4357912e2
[21:44] <wxl> http://kci.pangea.pub/view/All/search/?q=konversation
[21:44] <wxl> ???
[21:45] <santa_> so it's not on the kci
[21:45] <valorie> konversation crashes for me now when I quit it
[21:45] <valorie> which is weird
[21:45] <wxl> okie dokie
[21:45] <santa_> wxl: but you don't need get it on the kci to package the new version
[21:45] <wxl> sure, got it
[21:47] <wxl> so dumb question but basically i just need to grab upstream, the packaging for 1.6.1, edit the latter as needed to reflect the new version, build it and call it good, yes?
[21:50] <santa_> wxl: more or less, you also need to sync the packaging in git first, see https://launchpad.net/ubuntu/+source/konversation
[21:50] <santa_> vs https://code.launchpad.net/~kubuntu-packagers/kubuntu-packaging/+git/konversation/+ref/kubuntu_yakkety_archive
[21:51] <wxl> oh!
[21:53] <santa_> wxl: so before anything just sync the kubuntu_yakkety_archive branch to the ubuntu2 version, then you can create the kubuntu_zesty_archive branch on top of kubuntu_yakkety_archive, and then update to 1.6.2 on the kubuntu_zesty_archive branch
[21:53] <wxl> ok i think i got it
[21:56] <wxl> santa_: to be clear, which is the best file to grab that from? the debian.tar.xz no?
[21:58] <santa_> wxl: yes, you could - alternatively dget the dsc link, then dkg-source -x whatever.dsc then copy all debian/* files
[21:58] <wxl> santa_: do you prefer one over the other?
[21:58] <santa_> not really, as long as the result is good
[21:58] <wxl> XD
[21:58] <santa_> just sayin
[22:02] <wxl> does README.source need to be thre?
[22:03] <wxl> i'll just leave i guess
[22:12] <clivejo> is konversation in LP git?
[22:12] <wxl> yes
[22:13] <clivejo> can you post the URL pls?
 Hey guys. I'm thinking about writing a blog post about Kubuntu. I want to cover three points: …  1. Backports is coming, hold your horses.  …  2. Extra bodies always help, here's how to join.  …  3. We want testers, come find us.  … Y'all for or against me doing that?
 backports might be touchy
 I might explain our workflow as well.
 but an update is nice
[22:14] <wxl> santa_: merge proposed
 *would be nice
 @ahoneybun, I can be careful. :)
 Yeah, I want to go a little into why, not gonna name names or anything...
 Just a little, glossing over it
 well that might not be a great idea
 though everything in here is logged and public so
 If you want, I can run it by you guys before I post it?
 that would be cool
 Won't hurt I think. :)
 @tsimonq2, Oh, and don't we need an artist?
 nope couldn't hurt
 well wel have andres around sometimes
 I've been doing somethings here and there
 But I mean do we want someone in addition? A dedicated artwork guy that's around most of the time?
 Not saying Andres doesn't do ANYTHING...
 well we mostly ship KDE artwork
 he does
 he did the website cover picture
 Well OK
 I guess I'm just asking if we need one
 we don't need much
 Or if Andres is enough
 testers are needed more then anything I think
[22:20] <wxl> this is the 1.6.2 version of konversation, right? https://cgit.kde.org/konversation.git/commit/?id=bd0add0e9f59eb3fc750d745364f65a06abdbb67
[22:20] <Sho_> yes
 @tsimonq2 if you want I can post it on the website unless you just need it on your own blog
 @ahoneybun, Let's see once I write it. I may put a personal touch on it and it may look weird there.
 mm k
[22:26] <valorie> tsimonq2: I'm always willing to look over writing, whether blog posts or news on the site
 I think I'm going to submit it to the KC for modifications.
[22:35] <wxl> is there anything in the KA packaging that would allow me to quickly grab a particular version of a release tarball?
[22:36] <wxl> (upstream)
[22:36] <santa_> wxl: you can do it with uscan --rename --force-download then put it into the build area
[22:37] <clivejo> uscan not quick enough?
[22:37] <wxl> ah lovely
[22:38] <santa_> wxl: but anyway if you build it with gbp-ppa that should get you the tarball, doesn't it
[22:38] <santa_> ?
[22:39] <wxl> let me see
[22:39] <wxl> there are so many choices, i just want to make sure i'm doing the right thing!
[22:39] <wxl> or rather the *best* thing
[22:41] <valorie> always good to have choices, even if it's confusing
[22:41] <valorie> imo
 Bah, debuild doesn't look I  build-area. Too complicated for me. :P
 *in
[22:54] <wxl> aww hell
[22:54] <wxl> there's no trusty in ka-deps
[22:57] <mparillo> tsimonq2: My instinct is when we get questions (and especially complaints) about backports, is to ask if they have sacrificial machines, partitions, or VMs for testing. acheronuk replied to me that he would be cautious about a blanket invitation to help test at this point.
[23:03] <clivejo> valorie: have you still KCI enabled on your travel laptop?
[23:04] <valorie> nope
[23:04] <valorie> I don't think I ppa-purged though
[23:04] <clivejo> no no, dont want you to
[23:04] <valorie> I can get it out and check if you like
[23:04] <clivejo> want you to test something :P
[23:05] <valorie> have just been listening to the podcast but all of a sudden there is silence
[23:05] <valorie> ok, getting it
[23:05] <wxl> sigh.
[23:05] <wxl> is there a spare contianer i could use to do development on?
[23:08] <wxl> santa_: how can i get ka-deps for trusty?
[23:08] <santa_> wxl: well I could backport it but I would recommend you to use something newer for development
[23:09] <valorie> clivejo: started it up, what would you like me to test?
[23:09] <wxl> santa_: well back to that other idea then. got a spare container? XD
[23:11] <clivejo> valorie: waiting on LP to publish
[23:11] <valorie> ok
[23:12] <santa_> wxl: I could give you a xenial shell. why are you using trusty anyway?
[23:19] <wxl> santa_: oh well it's just what we have going on at work. say no more or else we'll have to listen to simon whine for hours on end
[23:20] <valorie> Kubuntu at work is better than Windows at work!
[23:20] <valorie> even if old
[23:26] -kubuntu-ci:#kubuntu-devel- Project merger_audiocd-kio build #187: FAILURE in 14 sec: http://kci.pangea.pub/job/merger_audiocd-kio/187/
[23:27] <wxl> you mean especially if it's old
[23:29] <wxl> really my biggest concern is that both my work machine and my laptop need a major rebuilding
[23:29]  * wxl sighs
[23:29] -kubuntu-ci:#kubuntu-devel- Yippee, build fixed!
[23:29] -kubuntu-ci:#kubuntu-devel- Project merger_audiocd-kio build #188: FIXED in 18 sec: http://kci.pangea.pub/job/merger_audiocd-kio/188/
[23:30] <clivejo> wxl: can you come on BBB?
[23:30] <wxl> sure but i'm not sure my mic is going to behave all that well
[23:30] <clivejo> no prob
[23:30] <wxl> 1s
[23:31] <wxl> ugh i forgot the pw
[23:31] <clivejo> welcome
[23:31] <wxl> i knew it was something stupid like that XD
[23:34] <clivejo> valorie: can you do a apt update and install konversation
[23:34] <valorie> ok
[23:35] <valorie> actually, it looks like I did do a ppa-purge
[23:35] <valorie> therefore I'll re-add and update
[23:40] <valorie> errors were encountered while processing: kde-runtime, jovie, kio-audiocd, kmouth, kdemultimedia-kio-plugins
[23:40] <valorie> E: Sub-process /usr/bin/dpkg returned error code (1)
[23:42] <valorie> https://paste.kde.org/pata7ivmb
[23:45] <clivejo> did you do an apt update?
[23:45] <clivejo> I deleted the kde-runtime packages from it
[23:48] <clivejo> are you sure you did a ppa-purge?
[23:49] <clivejo> somehow you still have that package that I deleted from the PPA
[23:49] <valorie> I'll ppa-purge again
[23:50] <valorie> probably didn't apt update after doing that
[23:52] <valorie> now I remember
[23:52] <valorie> it gave me a huge number of things to be done, so I didn't do it
[23:52] <valorie> now ppa-purging
[23:52] <acheronuk> 'apt-cache policy kde-runtime' should only show the version from the main archive or staging ppas, if purged ok