[00:03] -kubuntu-ci:#kubuntu-devel- Project xenial_unstable_umbrello build #84: STILL FAILING in 5 min 46 sec: http://kci.pangea.pub/job/xenial_unstable_umbrello/84/
[00:07] -kubuntu-ci:#kubuntu-devel- Project yakkety_unstable_umbrello build #72: STILL FAILING in 7 min 34 sec: http://kci.pangea.pub/job/yakkety_unstable_umbrello/72/
[00:10] -kubuntu-ci:#kubuntu-devel- Project mgmt_merger build #683: FAILURE in 9 min 59 sec: http://kci.pangea.pub/job/mgmt_merger/683/
[00:10] -kubuntu-ci:#kubuntu-devel- Project mgmt_progenitor build #664: STILL UNSTABLE in 10 min: http://kci.pangea.pub/job/mgmt_progenitor/664/
 Kernel 4.8 released
[00:31] <tsimonq2> I saw
[00:48] -kubuntu-ci:#kubuntu-devel- Project xenial_unstable_breeze-icons build #283: STILL FAILING in 22 min: http://kci.pangea.pub/job/xenial_unstable_breeze-icons/283/
[00:58] -kubuntu-ci:#kubuntu-devel- Project yakkety_unstable_breeze-icons build #167: STILL FAILING in 24 min: http://kci.pangea.pub/job/yakkety_unstable_breeze-icons/167/
[01:06] -kubuntu-ci:#kubuntu-devel- Project xenial_unstable_kauth build #277: STILL UNSTABLE in 42 min: http://kci.pangea.pub/job/xenial_unstable_kauth/277/
[01:19] <tsimonq2> omg KCI load speeds are VERY VERY slow
[01:25] <tsimonq2> http://img.ctrlv.in/img/16/10/03/57f1b37409361.png
[01:25] <tsimonq2> argh!
[01:25] <tsimonq2> come on!
[01:25] -kubuntu-ci:#kubuntu-devel- Project yakkety_unstable_kcoreaddons build #103: STILL UNSTABLE in 51 min: http://kci.pangea.pub/job/yakkety_unstable_kcoreaddons/103/
[01:26] -kubuntu-ci:#kubuntu-devel- Project yakkety_unstable_kidletime build #77: STILL UNSTABLE in 55 min: http://kci.pangea.pub/job/yakkety_unstable_kidletime/77/
[01:26] -kubuntu-ci:#kubuntu-devel- Project yakkety_unstable_kde-runtime build #187: STILL FAILING in 56 min: http://kci.pangea.pub/job/yakkety_unstable_kde-runtime/187/
[01:26] -kubuntu-ci:#kubuntu-devel- Project xenial_unstable_kdesdk-kioslaves build #73: STILL UNSTABLE in 28 min: http://kci.pangea.pub/job/xenial_unstable_kdesdk-kioslaves/73/
[01:26] -kubuntu-ci:#kubuntu-devel- Project xenial_unstable_kde-runtime build #181: STILL FAILING in 57 min: http://kci.pangea.pub/job/xenial_unstable_kde-runtime/181/
[01:38] <tsimonq2> COME ON
[01:38] <tsimonq2> I need to access KCI
[01:38] <tsimonq2> valorie: who owns KCI?
[01:38] <tsimonq2> valorie: as in, who runs it?
[02:11] <tsimonq2> ahoneybun: thanks
[02:12] <ahoneybun> thanks for the kickstart on that
[02:15] <tsimonq2> no problem, although Clive has already told me he doesn't even want to THINK about Z until 16.10 is out the door. :P
[02:20] <ahoneybun> yea but we need to fix the current issues
[02:20] <tsimonq2> I agree
[02:20] <tsimonq2> pita
[02:26] <tsimonq2> !info libkeduvocdocument-dev
[03:59] <valorie> tsimonq2: afaik, the KDs own KCI
[03:59] <valorie> but maybe ask Phil and/or Scarlett or sitter?
[04:12] <tsimonq2> yofel, sgclark, sitter: KCI's loading times are terrible atm, and in general loading times suck. Could we see a speed improvement in the near future?
 +1 thing to do is get memberships out the door
[04:12] <tsimonq2> hm?
 Well after 16.10 is
 We have clivejo and Santa have membership meetings
 *well
[04:13] <tsimonq2> not clivejo's membership meeting, developer meeting
[04:13] <tsimonq2> he's already a member
[04:53] <ahoneybun> developer membership
[04:53] <ahoneybun> I know he is I was ther
[04:53] <ahoneybun> *there
[07:47] <acheronuk> santa_: libkexiv2 seems to be missing from the applications upload? and lack of it is blocking things on build-deps
[07:48] <acheronuk> crucial rejects I think... 
[07:49] <acheronuk> (1) kmbox http://launchpadlibrarian.net/287497599/kmbox_15.12.3-0ubuntu1_16.04.3-0ubuntu1.diff.gz 
[07:49] <acheronuk> (2) kidentitymanagement http://launchpadlibrarian.net/287497435/kidentitymanagement_15.12.3-0ubuntu1_16.04.3-0ubuntu1.diff.gz
[07:51] <acheronuk> (3) kpimtextedit http://launchpadlibrarian.net/287497728/kpimtextedit_15.12.3-0ubuntu1_16.04.3-0ubuntu1.diff.gz
[07:52] <acheronuk> (4) libkeduvocdocument http://launchpadlibrarian.net/287497993/libkeduvocdocument_4%3A15.12.3-0ubuntu1_4%3A16.04.3-0ubuntu1.diff.gz
[07:53] <acheronuk> for starters at least, those having been rejected are causing big build dep waits that are not going to get resolved until those are sorted
[07:55] <acheronuk> I don't have the reject emails, but looks like many of those are going to be due to removed symbols and slightly odd soversion bumps/changes in install files?
[07:56] <lordievader> Good morning.
[07:58] <acheronuk> possibly
[07:58] <acheronuk> lol
[08:31] <acheronuk> shadeslayer: may I ask if/when you are likely to be available this week for any fix uploads? sorry to prod :(, but we a a bit short on time
[08:32] <acheronuk> back later....
[08:43] <acheronuk> santa_: just checked & libkexiv2 was not in the .7z you gave to Rohan, and seems the git has not been bumped or tagged for 16.04.3 release either.
[10:04] <acheronuk> [10:31]  <slangasek> acheronuk: and I've just rejected okteta because it appears to have regressed its symbols files... the previous ones that had been checked against multiple archs were replaced with ones only checked against x86, and as a result some symbols marked as ppc64el-specific were removed from the list completely
[10:04] <acheronuk> [10:26]  <slangasek> acheronuk: btw, the strigi packages, according to the Debian maintainers, are obsolete and have all been dropped from Debian unstable; since none of them had actual content updates for 16.04.3, you might want to check if we can do the same
[10:05] <acheronuk> [09:39]  <acheronuk> are some of these rejects because there is not apparent source change?
[10:05] <acheronuk> [09:41]  <slangasek> acheronuk: yes
[10:06] <acheronuk> [09:57]  <acheronuk> slangasek: so are you saying ultimately they can't be accepted, and we have to leave the old versions? or just not now?
[10:06] <acheronuk> [09:58]  <slangasek> acheronuk: if the kubuntu team wants the new version numbers, they can upload later; final freeze is just not a good time for that kind of upload
[10:25] <santa_> good morning
[10:25] <santa_> lets get back to work
[10:26] <santa_> acheronuk: regarding libkexiv, yes I realized, I'm going to fix the thing in KA and prepare a package to be uploaded to the archive
[10:26] <santa_> give me some minutes to do that and we will handle the rest of the things
[10:27] <acheronuk> santa_: no problem. I have to go for an hr or 2 in 10 mins time, which is one reason why I splurged all those messages up right now
[10:28] <santa_> ok, I'll read up and try to handle the stuff with the release team
[10:28] <santa_> shadeslayer, sgclark: are any of you available to sponsor uploads today?
[10:30] <shadeslayer> acheronuk: I'm going to forward you all of the emails from archive@ubuntu.com 
[10:30] <shadeslayer> acheronuk: that way you can sort through them
[10:31] <acheronuk> santa_: valorie sent an email, with some release team comment. others are on their logs
[10:31] <acheronuk> shadeslayer: to santa_ as well? 
[10:32] <shadeslayer> sure
[10:32] <acheronuk> shadeslayer: just he is getting working on things, and I am off for a few hrs
[10:34] <santa_> shadeslayer: if you can sponsor some uploads that would be awesome
[10:34] <shadeslayer> maye
[10:34] <shadeslayer> *maybe
[10:34] <santa_> we missed at least libkexiv2 and drumstick
[10:34] <shadeslayer> if you send me a link, I'll try
 Just got an email saying that Debian might stick to Plasma 5.8.1, but it seems to be up to Maxy.
 And by "stick to" I mean wait
[10:38] <acheronuk> tsimonq2: yes, I saw that email
 Cosas buenas
[10:46] <acheronuk> with the rapid releases at the start of the Fibonacci (ish) sequence, it makes sense to wait for the 1st or 2nd stable updates
[10:46] <tsimonq2> ok makes sense
[10:48] <santa_> shadeslayer: libkexiv2 http://gpul.grupos.udc.es/sponsor/applications/
[10:49] <tsimonq2> shadeslayer: did you ever get a chance to look at hardinfo? if not, I can go hunt down another MOTU :)
[10:49] <shadeslayer> best to
[10:49] <tsimonq2> shadeslayer: talking to me?
[10:49] <shadeslayer> tsimonq2: yes
[10:49] <tsimonq2> ok
[11:00]  * acheronuk looks at watch. eek
 Time of day or distance to release?
[11:02] <acheronuk> I have stuff to go and do, and I should have gone already!
 Then bai o/
[11:10] <santa_> acheronuk: hmm, how do you get all archs build logs in ubuntu? apparently getbuildlog from devscripts doesn't work
 @santa_, manually from the launchpad page for the version yopu want, if no automated tool works I presume
[11:14] <santa_> ugh
 I know
 santa_ QA page has direct links I think?
[11:19] <tsimonq2> y'all get my email last night about queuebot?
 oh. just for failures :/
[11:21] <tsimonq2> and y'all get the email about the meeting?
 if we are subbed to the lists, we got them
[11:27] <tsimonq2> :P
[11:29] <tsimonq2> ok, I'm going afk for school a bit early today
[11:29] <tsimonq2> o/
[11:46] <shadeslayer> tsimonq2: santa_ ignore those emails I just sent
 Ok
[11:47] <santa_> I think I didn't get any yet
[11:48] <santa_> ah, ok
[11:48] <santa_> these 3
[11:48] <santa_> ack
 shadeslayer: if you still have them, could you please forward me the rejection emails from apps?
[11:49] <shadeslayer> yes I'm working on that
[11:49] <shadeslayer> because gmail is shit
 I agree lol
 Thanks
 (<3 Thunderbird)
[12:06] <santa_> a fixed marble is being built on the ppa to test the changes, we would need an upload of this one to get it built on some archs
[12:12] <shadeslayer> santa_: tsimonq2 Emails going out
 Thanks
[12:14] <shadeslayer> might land in spam :P
 Nope
[12:15] <santa_> nope, I got them, thank you very much
[12:15] <shadeslayer> yw
[12:15] <shadeslayer> I /think/ I got all of them
[12:15] <shadeslayer> atleast my search string looks correct gmail.inbox.emails(gm: 'archive@ubuntu.com subject:Rejected newer_than:3d')
 no emails here
[12:16] <shadeslayer> acheronuk: email addy plz
[12:16] <shadeslayer> ah rik
[12:16] <shadeslayer> acheronuk: sending to you too :)
[12:18] <shadeslayer> acheronuk: you should have started getting them
 @shadeslayer, coming through now. thank you :)
[12:19] <santa_> shadeslayer: so ... now that we get the mails we will work on the issues, could you upload libkexiv2? that's one blocking other builds
[12:19] <shadeslayer> yeah sure
[12:20] <santa_> I also have some other pending fixes either discussed with the release team or fixing somewhat trivial ftbfs'es
[12:21] <santa_> so far it's kio, plasma-desktop, plasma-discover, plasma-sdk
[12:22] <shadeslayer> santa_: uploaded
[12:22] <shadeslayer> plz poke someone in release team to approve
[12:24] <santa_> ok, if you can please go ahead with the rest, they are ready here as well http://gpul.grupos.udc.es/sponsor/
[12:24] <santa_> thank you very much for uploading that
[12:29] <shadeslayer> santa_: plasma-desktop has no .diff
[12:29] <shadeslayer> kio uploaded
[12:32] <shadeslayer> santa_: discover and sdk uploaded
[12:32] <shadeslayer> if you could provide a diff for desktop, I'll upload it
[12:33] <santa_> shadeslayer: done, just refresh the page
[12:33] <shadeslayer> uploaded
[12:33] <shadeslayer> thanks :)
 why is a diff needed for those?
[12:34] <santa_> so he can check what we changed and see if it looks sane
 @santa_, erm..... of course.
[12:36] <santa_> :)
[12:36] <shadeslayer> ^^
 was wondering if there was some other requiremnt for uploads at this stage that I didn't know about, and did not see the blinding obvious reason :P
 * acheron goes for more coffee *
[13:00] <BluesKaj> Howdy all
[13:12] <BluesKaj> well, losing sudo and root-system-bin was the last straw on Yakkety ...between the broken graphics with X and the loss of sudo and root access was enough for me to dump the OS from it's partitions.
[13:12] <BluesKaj> I'll stick with Xenial for a while
[13:32] <mamarley> I have been running Yakkety for months without any severe problems.  Perhaps you should try a clean install.
[13:36] <BluesKaj> doh!
 have -release accepted those uploads?
[14:33] <acheronuk> to answer my own question ^^^^, no they have not :/
[15:30] -kubuntu-ci:#kubuntu-devel- Yippee, build fixed!
[15:30] -kubuntu-ci:#kubuntu-devel- Project yakkety_unstable_breeze-icons build #168: FIXED in 19 min: http://kci.pangea.pub/job/yakkety_unstable_breeze-icons/168/
[15:50] -kubuntu-ci:#kubuntu-devel- Yippee, build fixed!
[15:50] -kubuntu-ci:#kubuntu-devel- Project xenial_unstable_breeze-icons build #284: FIXED in 18 min: http://kci.pangea.pub/job/xenial_unstable_breeze-icons/284/
[17:27] -kubuntu-ci:#kubuntu-devel- Project yakkety_unstable_kauth build #146: STILL UNSTABLE in 19 min: http://kci.pangea.pub/job/yakkety_unstable_kauth/146/
[17:27] -kubuntu-ci:#kubuntu-devel- Project xenial_unstable_kcoreaddons build #260: STILL UNSTABLE in 19 min: http://kci.pangea.pub/job/xenial_unstable_kcoreaddons/260/
[17:28] <clivejo> who fixed breeze icons?
[17:30] <acheronuk> why?
 @CliffordTheBigRedDoggie so your meeting is today?
[17:31] <clivejo> heard a discussion somewhere on what to do about it
[17:33] <clivejo> it might be
[17:33] <clivejo> or it might not
[17:33] <acheronuk> clivejo: I did *some* fixing, and also emailed the KDE dev working on them to point out the duplicates he had which where causing sitter's new dupes test to fail
[17:33] <clivejo> ah, looks like poking upstream did the trick
[17:34] <clivejo> but probably too late for 5.8 release
[17:34] <acheronuk> and them did a rebuild of ECM to catch the new version of that
[17:34] <clivejo> are they respinning the tars on depot?
[17:34] <acheronuk> so a comnination of all that nay have done the trick
[17:34] <acheronuk> *combination
[17:36] <acheronuk> breeze icons are frameworks, if you mean those...
[17:36] <clivejo> doh
[17:38] <acheronuk> 'breeze' is a bit fragmented, so easily done
[17:42] -kubuntu-ci:#kubuntu-devel- Project xenial_unstable_kde-runtime build #182: STILL FAILING in 30 min: http://kci.pangea.pub/job/xenial_unstable_kde-runtime/182/
[17:51] -kubuntu-ci:#kubuntu-devel- Project merger_marble build #467: FAILURE in 58 sec: http://kci.pangea.pub/job/merger_marble/467/
[17:55] <tsimonq2> WHO BROKE MARBLE's MERGE
[17:55]  * tsimonq2 chases them with a stick
[17:55] <tsimonq2> (lol kidding)
[17:55] -kubuntu-ci:#kubuntu-devel- Project xenial_unstable_kidletime build #269: STILL UNSTABLE in 31 min: http://kci.pangea.pub/job/xenial_unstable_kidletime/269/
[17:55] -kubuntu-ci:#kubuntu-devel- Project merger_marble build #468: STILL FAILING in 59 sec: http://kci.pangea.pub/job/merger_marble/468/
[17:56] -kubuntu-ci:#kubuntu-devel- Project mgmt_merger build #684: NOW UNSTABLE in 17 hr: http://kci.pangea.pub/job/mgmt_merger/684/
[17:56] -kubuntu-ci:#kubuntu-devel- Project yakkety_unstable_kppp build #76: STILL UNSTABLE in 16 min: http://kci.pangea.pub/job/yakkety_unstable_kppp/76/
[17:56] -kubuntu-ci:#kubuntu-devel- Project yakkety_unstable_kde-runtime build #188: STILL FAILING in 44 min: http://kci.pangea.pub/job/yakkety_unstable_kde-runtime/188/
[18:11] -kubuntu-ci:#kubuntu-devel- Project yakkety_unstable_kpty build #123: STILL UNSTABLE in 29 min: http://kci.pangea.pub/job/yakkety_unstable_kpty/123/
[18:12] -kubuntu-ci:#kubuntu-devel- Project xenial_unstable_kpty build #272: STILL UNSTABLE in 30 min: http://kci.pangea.pub/job/xenial_unstable_kpty/272/
[18:12] -kubuntu-ci:#kubuntu-devel- Project yakkety_unstable_kopete build #53: STILL UNSTABLE in 37 min: http://kci.pangea.pub/job/yakkety_unstable_kopete/53/
[18:12] -kubuntu-ci:#kubuntu-devel- Project xenial_unstable_palapeli build #26: STILL FAILING in 20 min: http://kci.pangea.pub/job/xenial_unstable_palapeli/26/
[18:12] -kubuntu-ci:#kubuntu-devel- Project xenial_unstable_kopete build #76: STILL UNSTABLE in 37 min: http://kci.pangea.pub/job/xenial_unstable_kopete/76/
[18:12] -kubuntu-ci:#kubuntu-devel- Project yakkety_unstable_palapeli build #31: STILL FAILING in 20 min: http://kci.pangea.pub/job/yakkety_unstable_palapeli/31/
[18:13] -kubuntu-ci:#kubuntu-devel- Project xenial_unstable_kdevelop-pg-qt build #37: STILL UNSTABLE in 18 min: http://kci.pangea.pub/job/xenial_unstable_kdevelop-pg-qt/37/
[18:24] -kubuntu-ci:#kubuntu-devel- Project yakkety_unstable_okular build #87: STILL UNSTABLE in 32 min: http://kci.pangea.pub/job/yakkety_unstable_okular/87/
[18:24] -kubuntu-ci:#kubuntu-devel- Project yakkety_unstable_kdevelop-pg-qt build #10: STILL UNSTABLE in 29 min: http://kci.pangea.pub/job/yakkety_unstable_kdevelop-pg-qt/10/
[18:32] -kubuntu-ci:#kubuntu-devel- Project xenial_unstable_palapeli build #27: STILL FAILING in 14 min: http://kci.pangea.pub/job/xenial_unstable_palapeli/27/
[18:32] -kubuntu-ci:#kubuntu-devel- Project yakkety_unstable_palapeli build #32: STILL FAILING in 14 min: http://kci.pangea.pub/job/yakkety_unstable_palapeli/32/
[18:33] -kubuntu-ci:#kubuntu-devel- Project xenial_unstable_kcrash build #268: STILL UNSTABLE in 21 min: http://kci.pangea.pub/job/xenial_unstable_kcrash/268/
[18:33] -kubuntu-ci:#kubuntu-devel- Project yakkety_unstable_kcrash build #144: STILL UNSTABLE in 21 min: http://kci.pangea.pub/job/yakkety_unstable_kcrash/144/
[18:33] -kubuntu-ci:#kubuntu-devel- Project xenial_unstable_kdevelop-pg-qt build #38: STILL UNSTABLE in 20 min: http://kci.pangea.pub/job/xenial_unstable_kdevelop-pg-qt/38/
[18:38] -kubuntu-ci:#kubuntu-devel- Project xenial_unstable_kwrited build #251: FAILURE in 4 min 58 sec: http://kci.pangea.pub/job/xenial_unstable_kwrited/251/
[18:38] -kubuntu-ci:#kubuntu-devel- Project yakkety_unstable_kwrited build #134: STILL FAILING in 5 min 53 sec: http://kci.pangea.pub/job/yakkety_unstable_kwrited/134/
[18:39] -kubuntu-ci:#kubuntu-devel- Project merger_kio build #798: FAILURE in 16 sec: http://kci.pangea.pub/job/merger_kio/798/
[18:45] -kubuntu-ci:#kubuntu-devel- Project yakkety_unstable_kdevelop-pg-qt build #11: STILL UNSTABLE in 21 min: http://kci.pangea.pub/job/yakkety_unstable_kdevelop-pg-qt/11/
[18:47] -kubuntu-ci:#kubuntu-devel- Project xenial_unstable_kwrited build #252: STILL FAILING in 3 min 43 sec: http://kci.pangea.pub/job/xenial_unstable_kwrited/252/
[18:50] -kubuntu-ci:#kubuntu-devel- Project yakkety_unstable_kwrited build #135: STILL FAILING in 6 min 49 sec: http://kci.pangea.pub/job/yakkety_unstable_kwrited/135/
[19:02] <santa_> shadeslayer: fix for marble ftbfs in some archs: http://gpul.grupos.udc.es/sponsor/
[19:04] <acheronuk> santa_: evening :) have you had a chance to consider the 3 packages that are alleged ABI breaks?
[19:06] <santa_> acheronuk: I'm going to dig into that now
[19:07] <acheronuk> santa_: oh, and if enough devs turn up, clive has his dev meeting in < 1hr time. you probably saw the email on that though
[19:08] <santa_> ok
[19:10] <acheronuk> great on the ABI stuff. that still hurts my head somewhat. I think it's a bit like a physics/maths problem. sometimes you just don't have confidence until you see enough worked examples
[19:19] <santa_> if someone has some free time and skills, according to steve kde-runtime is failing its autopkgtests, see #-release for details
[19:25] <santa_> oh, jesus christ
[19:25] <santa_> looking @ kmbox
[19:25] <acheronuk> santa_: if I'm looking at the right thing, the 1st few I checked are complaining that the dependencies to run the tests are unsatisfiable
[19:27] <acheronuk> ummm.... yes. I'm not expert yet , but something looks horribly wrong on kmbox and kidentitymanagement
[19:41] <acheronuk> santa_: is this why debian don't have problems with those tests? :P https://anonscm.debian.org/cgit/pkg-kde/applications/kde-runtime.git/commit/?id=bac71802bceec4c301df4695ccffab4bfc45db3a
[19:43] <santa_> with a couple of iron balls. and sorry for the language
[19:43] <santa_> well, I will see what we can do with that
[19:43] <santa_> I'm trying to find out a reasonable explanation to ignore the pim abi breaks
[19:44] <acheronuk> what reason did debian have?
[19:44] <acheronuk> if any....
[19:44] <santa_> reason for what?
[19:44] <santa_> to drop the testsuite?
[19:44] <acheronuk> the ABI
[19:45] <acheronuk> actually, probably both
[19:46] <santa_> ah, the ABI, maybe it can be ignored. but to be honest you just have to see what happened with kio
[19:46] <acheronuk> yes, that wasn't very good
[19:47] <santa_> it illustrates pretty well how much you can trust debian's kde git to get the right thing when packaging libraries
[19:48] <acheronuk> yes, I still have in that back of my mind the notion "if debian has done that, it must be ok"
[19:48] <acheronuk> that I'm becoming aware is is a tad mistaken sometimes
[19:50] <santa_> I actually prefer, "we must merge things from debian because it's technically convenient and many times it may fix our issues, but never blind trust"
[19:51] <acheronuk> ^^^^ very true
[20:00] <clivejo> Mon  3 Oct 20:00:07 UTC 2016
[20:00] <clivejo> can any Kubuntu Dev's in the room say meep
[20:01] <sitter> my clock is off by 2 minutes
[20:01] <sitter> wtf
[20:01] <clivejo> you forget to wind it?
[20:01] <valorie> Mon Oct  3 20:01:16 UTC 2016 here
[20:02] <clivejo> do we have enough devs to do this?  or too short notice?
[20:02] <sitter> well, I am myself. so I have quorum
 am I a Dev?
[20:02] <sitter> no
 oh...
 I'm just the guy that complains a lot
 😉
[20:03] <acheronuk> ScottK was saying on OFTC earlier that he was 'under the weather'
[20:03] <clivejo> the devs on my doodle were ScottK, sitter, sgclark and yofel
[20:03] <sitter> sgclark, yofel ping
[20:03] <clivejo> sitter: we need at least 4?
[20:04] <sitter> 3 I think
[20:04] <sgclark> present
[20:04] <valorie> shadeslayer is also a devel
[20:04] <sitter> shadeslayer: u round?
[20:04] <ScottK> I'm sort of around
[20:04] <clivejo> hi ScottK
[20:04] <acheronuk> "get accepted by a majority of existing developers and at least 3 existing developers."
[20:04] <sgclark> though I am not a good question asker. not enough notice. will leave that to the others
[20:04] <clivejo> whats up if I may ask?
[20:05] <clivejo> man flu?
[20:05] <sitter> ScottK: heya, do you feel up to conducting a grilling or shall we look for a replacement?
[20:05] <sgclark> woman flu here
[20:05]  * clivejo does mind easy grilling
[20:05] <clivejo> doesnt
[20:06] <ScottK> sitter: let's do it.
[20:06] <sitter> ok. quorum present
[20:07] <ScottK> Wiki page link?
[20:07] <sitter> clivejo: let's start with an intro from you and links to wiki page etc. for review
[20:07] <clivejo> Dev App - https://wiki.ubuntu.com/clivejo/DeveloperApplication
[20:07]  * ScottK reads.
[20:08] <clivejo> Well Im Clive Johnston, hence the nick clivejo
[20:08] <clivejo> been using Ubuntu/Kubuntu for quite some time but only lurked about
[20:09] <clivejo> I came here a year and a bit ago looking for help with a plasma issue I was having and Jon convinved me to do some packaging
[20:09] <clivejo> I was launching kate with sudo :O
[20:10] <clivejo> which is a no no :P
[20:11] <sitter> clivejo: how would you rate your abilities between 1 and 10? 1 being not knowing anything and 10 being me
[20:12] <clivejo> My regular profile is here - https://wiki.ubuntu.com/~clivejo
[20:12] <clivejo> honestly Im a 2, you are a packaging god!
[20:12] <sitter> flattery doesn't give extra points!
[20:13] <sgclark> hah I thought I was hard on myself
[20:13] <clivejo> I know I have a long way to go, a lot to learn, but I realise someone has got to step up
[20:13] <valorie> clivejo: then why were you advised to apply?
[20:13] <ScottK> clivejo: it seems to me like Kubuntu has more to do than it has people to do it.  Do you agree and if so, what work is lower priority and should maybe not get done right now?
[20:13] <clivejo> well Im willing to learn
[20:14] <clivejo> ScottK: that is a fair assessment, in my opinion our issue is uploaders
[20:15] <ScottK> Right and potentially adding you helps.  Is that enough?
[20:16] <clivejo> no, but what Im hoping is that I can be available to teach others who are willing to help
[20:16]  * acheronuk is willing
[20:16] <sitter> clivejo: What language are debian/rules files written in? What does %: in that language?
[20:16] <clivejo> at the moment all the stress is being loaded onto a few very hard working person
[20:17] <clivejo> thats not fair, nor is it sustainable 
[20:19] <clivejo> I believe its written in CMake, as the header is using /usr/bin/make
[20:22] <clivejo> Im kind of guess it means all
[20:23] <clivejo> am I still connected?
[20:23] <tsimonq2> yep
[20:23] <sitter> FTR debian/rules are written in make. cmake is a higher level software on top
[20:24] <clivejo> seem to have lag
[20:24] <sitter> % specifically is a wildcard like *. so %: is a wildcard target, it basically acts on any command you throw at the rules file
[20:24] <clivejo> in my mind its like *
[20:24] <clivejo> but I dont know why its %
[20:25] <sitter> because the people who made the langauge thought % was cool :P
[20:25] <sitter> clivejo: What’s the difference between --with kf5 and --with kde in debian/rules’ dh call?
[20:26]  * tsimonq2 always thouught it was chosen because the debian/rules file allows you to specify many things, and that is the leftover, the remainder, the modulous
[20:26] <tsimonq2> but I'm sorry, /me hides again
[20:27] <wxl> s/ous/us/
[20:27] <clivejo> from what Ive seen kf5 is the frameworks version 5
[20:27] <clivejo> and kde would be version 4 stuff?
[20:27] <clivejo> pre KF5
[20:28] <sitter> tsimonq2: entirely conceivable, with target such as %.c: that makes less sense to me though. entirely possible that that is why they chose it though
[20:28] <sitter> clivejo: is that a question or an answer? :P
[20:28] <clivejo> well I have very little experience with pre-kf5 packages
[20:28] <sitter> fair enough. so for new packages you would use --with kf5?
[20:29] <clivejo> if they been ported to kf5
[20:29] <sitter> ay. sounds good
[20:29] <clivejo> there are a few that havent yet
[20:29] <sitter> clivejo: what are symbols files and what are they used for?
[20:29] <sgclark> clivejo: what is an SRU and describe the steps to achieve one.
[20:29] <clivejo> they are torture method
[20:29] <sitter> besides that :P
[20:29] <wxl> sgclark: Stable Release Update
[20:30] <wxl> !sru | sgclark 
[20:30] <ahoneybun> wxl: she asked clivejo
[20:30] <sitter> wxl: we are interviewing clivejo, please don't answer his questions
[20:30] <wxl> oh
[20:30] <wxl> SORRY
[20:30] <sgclark> wxl: thannks but we are grilling clivejo for his dev app
[20:30]  * wxl cries
[20:30] <sitter> wxl: no worries
[20:30] <clivejo> they are a tool to help use detect ABI breakage
[20:30]  * wxl was wondering why sgclark was asking that XD
[20:30] <sgclark> hehe
[20:31] <sitter> clivejo: is that all they are used for?
[20:31] <clivejo> to track symbols
[20:31] <sitter> what does that mean specifically?
[20:31] <clivejo> if they suddenly go missing we have to do some investigation as to why they have gone missing
[20:32] <sitter> clivejo: do symbols files end up in the final deb?
[20:33] <clivejo> not the main binary, but they are included in the debugging package which can be installed 
[20:33] <clivejo> although Ive seen some packages not named .deb
[20:33] <sitter> oh my
[20:33] <sitter> you just built yourself a trap
[20:33] <sitter> clivejo: what's a udeb? 
[20:34] <sitter> sgclark: I hope you don't mind ;)
[20:34] <sgclark> my question was debunked. go ahead
[20:34] <sgclark> thinking of new one
[20:34] <clivejo> a mini debian package
[20:34] <sitter> sgclark: still worthwhile to get an answer I should think
[20:34] <sgclark> ok
[20:34] <sitter> clivejo: what's the point of that? why aren't all packages mini?
[20:34] <clivejo> with all the not needed stuff stripped out
[20:35] <sitter> why do we need that?
[20:35] <clivejo> because we need to keep the licence and docs and that kind of stuff
[20:35] <sitter> clivejo: we need them in a mini package?
[20:36] <clivejo> for installation, to make it quiicker
[20:36] <sitter> clivejo: so do we have documentation in a udeb or not?
[20:36] <clivejo> no, that would be stripped out to make it mini me
[20:36] <sitter> ay
[20:37] <sitter> clivejo: sgclark  asked a lovely question about SRUs. please walk us through the process
[20:37] <clivejo> sitter: may I ask you a question?
[20:37] <sitter> clivejo: if it needs an answer now. sure
[20:37] <clivejo> I got the impression I answered wrong regarding symbols in debugging package?
[20:38] <clivejo> I have seen .ddeb are these not debugging packages?
[20:38] <sitter> they were for a brief moment. since then they were changed to -dbgsym.deb
[20:39] <sitter> they do not have anything to do with symbols though.
[20:39] <sitter> the symbosl file primarily gets *actually* put into the final deb of the library. the point of this is so that dpkg-* can automatically generate the binary dependencies of a deb you build against that library
[20:40] <sitter> to achieve that it would check the symbols the application uses and try to find them in a lib package, thus making the lib package a dependency of the app package
[20:40] <clivejo> the debugging file isnt a map of symbols to real function names?
[20:41] <sitter> as a side effect of that, maintaining the version in symbols files allows more accurate depednency versioniong. if an app only needs kf5.12 it will only require 5.12 since we maintain perisstent symbol files
[20:41] <sitter> clivejo: it is, that's independent of the symbols file though
[20:41] <sitter> if you have more questions we can discuss this later. for now let's move ahead with SRU
[20:42] <clivejo> ok, what was the question again ?
[20:42] <clivejo> Scottish Rugby Union?
[20:43] <sitter> sgclark: you into rugby at all?
[20:43] <sgclark> lol
[20:43] <valorie> lol
[20:43] <sgclark> ‎[13:29] ‎<‎sgclark‎>‎ clivejo: what is an SRU and describe the steps to achieve one.
[20:44] <clivejo> oh an SRU
[20:44] <clivejo> not the!
[20:44] <clivejo> Its a process we have to follow to get updates into a released version of Kubuntu
[20:45] <clivejo> usually to fix a bug
[20:45] <tsimonq2> clivejo: what is a CVE, where is it announced, why is it announced, how do you fix it, where does it go, and do you get it in the development release or current stable/LTS releases first?
[20:45]  * tsimonq2 runs
[20:46] <clivejo> because the update will be going into the archive it will be installed on many many users machines
[20:47] <clivejo> because of this its very important that the actual fix works as intended, is tested and there are no consequences to this update
[20:47] <sgclark> I am looking for the reasons a package would be considered an SRU, because You cant SRU any random package just becasue you want new stuff
[20:48] <clivejo> sgclark: usually to fix a LP bug
[20:48] <sgclark> a launchpad bug?
[20:48] <tsimonq2> clivejo: when is it appropriate to remove a symbol and what tools do you usually use to update symbols? also, why use symbols at all?
[20:48] <clivejo> a serious one
[20:49] <sgclark> define serious?
[20:49] <sgclark> examples please
[20:50] <sgclark> an exaple of what I am looking for is: a security fix.
[20:50] <clivejo> CVE (security related), data lost, something that needs a recent update
[20:50] <sgclark> err s/exaple/example/
[20:51] <sgclark> clivejo: answer accepted. thanks
[20:51] <sitter> clivejo: do CVEs and SRUs use the same process to get landed?
[20:51] <clivejo> I believe CVE need to be processed by the security team directly by adding them on LP
[20:51] <sgclark> and I still need the steps involved in processing an SRU
[20:52] <tsimonq2> clivejo: what does release day look like? who does what? what testing is needed for an image to be released? where are the release notes stored? where do you go if things go awol?
[20:52]  * tsimonq2 stops with questions for now
[20:53] <clivejo> well at the moment I dont have upload rights so I would have to find a sponsor and fill out a LP bug
[20:53] <clivejo> Id need to explain what and why I need this 
[20:54] <clivejo> a test case detailing how to rep the bug
[20:54] <clivejo> attach a patch or deb diff of how I propose to fix it
[20:55] <sgclark> ok, I am satisfied
[20:55] <clivejo> and carry out tests on the actual package with patch applied
[20:55] <sitter> clivejo: <tsimonq2> clivejo: what is a CVE, where is it announced, why is it announced, how do you fix it, where does it go, and do you get it in the development release or current stable/LTS releases first?
[20:55] <clivejo> Id also try and get other people to test the package and add their notes to the bug report
[20:56] <sgclark> excellent
[20:56] <sitter> that is a fairly long question. I think we'll be satsified if you can outline the difference between a stable release update and a security update
[20:56] <clivejo> a CVE means Common Vulnerabilities and Exposures
[20:57] <clivejo> they come from multiple sources
[20:57] <clivejo> KDE are announced here - https://www.kde.org/info/security/
[20:58] <tsimonq2> clivejo: what about Ubuntu's?
[20:59] <clivejo> at this moment in time I dont know enough about Ubuntu core system to go about dealing with CVE's there
[20:59] <tsimonq2> I see ok
[20:59] <clivejo> the problem with CVE's is that you can fix one thing and break several others
[21:00] <sitter> well. that is a problem of all updates I should think
[21:00] <valorie> all updates, ever, anywhere
[21:00] <tsimonq2> ^
[21:02] <sitter> clivejo: do you have anythin more to say on the topic of CVE?
[21:02] <clivejo> very true, and maybe in time when Im more competent, I will engage more in Ubuntu CVE's
[21:03] <sitter> clivejo: is there documentation on how to do a security update?
[21:03] <clivejo> in what context?
[21:03] <sitter> KDE publishes a CVE. What do you do?
[21:04] <sitter> (I am not looking for process specifics)
[21:04] <clivejo> Id check if it is relevant to our supported releases 
[21:05] <sitter> clivejo: do you know off the top of your head all steps involved in landing the security update? (assuming it is needed for us etc.)
[21:05] <clivejo> if it is, and for a released (not dev) Id open a LP bug and request an SRU
[21:05] <sitter> mh. thank you
[21:06] <sitter> I really need to stress that security updates are not regular SRU and need to have the security update documentatin on the wiki followed.
[21:06] <sitter> In particular depending on where the security udpate was announced keeping it under wraps until a specific date is necessary.
[21:06] <sitter> Let's move this along.
[21:07] <sitter> clivejo: tsimonq2 had some questions about symbols. I'll try to repack them a bit
[21:07] <sitter> clivejo: is it ever appropriate to remove a symbol from the symbols file?
[21:08] <clivejo> yes, sometimes they do have to be removed
[21:08] <sitter> do you have a simple example for when?
[21:09] <clivejo> when a lib is bumped
[21:09] <sitter> (you'd regenerate the entire symbols in that case I should think)
[21:09] <sitter> clivejo: any other cases?
[21:09] <clivejo> sometimes private symbols are dropped too
[21:10] <sitter> clivejo: what do you do if a symbol disappeared that should not have disappeared?
[21:10] <clivejo> investigate why is disappeared by going upstream
[21:10] <sitter> clivejo: what's the name of the tool we use to update symbols files?
[21:10] <clivejo> reading commits or asking the dev directly
[21:11] <clivejo> well I use pkgkde-symbolshelper
[21:12] <sitter> clivejo: what do you do if problems with a candidate ISO for release appear?
[21:12] <clivejo> depends what the problem is
[21:12] <sitter> ScottK, sgclark: any more question you'd like answered?
[21:13] <sitter> clivejo: how so?
[21:13] <clivejo> Id start to panic and try and find out what the problem is
[21:13] <sitter> is that really the first thing you should do?
[21:14] <clivejo> I think Im misunderstanding the question
[21:14] <clivejo> you mean if Id downloaded the ISO and something is wrong?
[21:14] <clivejo> or its not building the ISO?
[21:14] <sitter> clivejo: you noticed something really bad with the candidate ISO that is about to be released as 16.10. what do you do
[21:15] <sitter> there's a nude of angela merkel set as the wallpaper or whatever
[21:15] <sgclark> clivejo: what is a virtual package?
[21:15] <valorie> omg sitter
[21:15] <sgclark> sitter first 
[21:15] <valorie> you sick, sick person!
[21:15] <acheronuk> that is the product of a warped mind!
[21:15]  * acheronuk shuts up
[21:15] <clivejo> Id speak to the release team, figure out how it got there
[21:15] <sitter> :((
[21:16] <sitter> clivejo: ok. I am satsified
[21:16] <clivejo> and get it fixed
[21:16] <clivejo> there are far nicer people Id like to see naked
[21:16] <tsimonq2> ^ lol
[21:16] <sitter> (personally I would leave it as it is for the press of it)
[21:16] <ScottK> clivejo: if you're about to upload a package and you have doubts, what should you do?
[21:17] <clivejo> doubts?
[21:17] <tsimonq2> La pregunta es buy bien
[21:17] <ScottK> You aren't sure if something is correct.
[21:18] <clivejo> sgclark: a virtual package is one that doesnt actually contain anything but pulls in other packages
[21:19] <clivejo> it can sometimes contain logic to ask the user what to install or download the installer
[21:19] <sgclark> ok, but why would you use a virtual package, just to randomly pulls stuff in together?
[21:19] <clivejo> to install kubuntu
[21:20] <clivejo> to pull in a certain set of packages to install the kubuntu desktop
[21:20] <sitter> that's not actually a virtual package. that's a meta package
[21:20] <sgclark> ok I will accept that
[21:20] <sgclark> hah nevermind
[21:20] <sgclark> he is right
[21:22] <sitter> also virtual packages never have content
[21:22] <sgclark> looking for something a bit different than meta. Virtual package brings in a group of packages that provide ____
[21:22] <sitter> they are literaelly just a tag on physical package that it *provides* a virtual package by some name
[21:23] <sgclark> ok I messed up that question. my bad, next
[21:23] <clivejo> so kubuntu desktop isnt a virtual package?
[21:23] <sitter> no
[21:24] <sgclark> clivejo: what is a deb and what files does it contain?
[21:24] <clivejo> ScottK: sorry, if Im not sure, I dont upload it until I am sure
[21:25] <ScottK> How do you get sure?
[21:25] <clivejo> sgclark: its a specially formatted archived file
[21:25] <sgclark> what kind of archive?
[21:25] <clivejo> ar I believe
[21:26] <sgclark> correct
[21:26]  * sitter thinks someone's been digging in my question drawer :P
[21:26]  * sgclark giggles
[21:27] <clivejo> contains 3 files
[21:27] <valorie> ooo, hey Quintasan
[21:27] <Quintasan> Hi.
[21:27] <sgclark> howdy
[21:27] <valorie> are you here to turn up the fire?
[21:28] <Quintasan> I fell ill and fell asleep.
[21:28] <Quintasan> I guess.
[21:28] <sitter> Quintasan: good morning
[21:28] <valorie> sorry hear you're not feeling well
[21:28] <valorie> I think it's going around
[21:28] <sgclark> indeed
[21:29] <valorie> anyway, we're here in the midst of clivejo's grilling
[21:29] <sitter> clivejo: what does ubuntu usually mean when we talk about a "merge"? have you ever done one?
[21:29] <acheronuk> grilling? more like boiling oil and flaming tar
[21:29]  * sitter would like to conclude the griling soon
[21:29] <clivejo> you mean a debian merge?
[21:30] <sitter> that sounds like something we would mean, yes ;)
[21:30]  * sgclark is still waiting for the 3 files that are in a deb
[21:30]  * ahoneybun thanks acheronuk will be better now at his meeting
[21:30] <clivejo> yes, I have done a couple debian merges
[21:30] <tsimonq2> clivejo: what does being a Kubuntu Developer mean? what permissions do you have, what permissions do you not have? here's two scenarios:
[21:30] <tsimonq2> Hey Clive, could you please upload kubuntu-desktop for me? I fixed a problem with X.
[21:30] <tsimonq2> Hey Clive, could you please upload vrms for me? I fixed a problem that kubuntu-desktop caused.
[21:31] <tsimonq2> How would you respond to these?
[21:31] <sgclark> acheronuk: haha I had 5 devs throwing questions at once and in ubuntu-meeting
[21:31] <Quintasan> clivejo: I'd like to follow up on the symbols question: suppose upstream removes some symbols and does not bump the soname, how would you proceed?
[21:31] <clivejo> sgclark: theres a text file and two more archived files
[21:31] <clivejo> control and data
[21:31] <sgclark> maybe even more than 5 now that I think of it
[21:32]  * acheronuk thinks ahoneybun will have to wait a while to see that!
[21:32] <clivejo> sorry, Im getting confused now
[21:32] <clivejo> because tsimonq2 isnt a dev Im purposefully ignoring him
[21:32] <clivejo> Quintasan: Id use the Debian ABI manager to bump it
[21:32] <tsimonq2> sitter: can you repeat my questions pls? :)
[21:34]  * sitter finds ignoring a bit rude :(
[21:34] <clivejo> am I still here?
[21:34] <sitter> clivejo: yes
[21:34] <tsimonq2> clivejo: yup, answer questions pls? ;)
[21:34] <clivejo> sitter: its harmless batter
[21:35] <sitter> clivejo: also I should point out taht before going the ABI manager route you should undertake every possible effort to get upstream to solve this properly
[21:35] <Quintasan> ^
[21:35] <Quintasan> I was about to point that out.
[21:35]  * ScottK hands clivejo an 'n'.
[21:35] <sitter> there rarely is a case where you as package should take control of the abi
[21:35] <sitter> clivejo: as kubuntu-dev, can you upload Qt?
[21:36] <tsimonq2> ^^^^ oooooh
[21:37] <clivejo> sorry, I read that as "doesnt not bump" meaning that they refused to do so
[21:37] <clivejo> for what ever reason
[21:39] <clivejo> sitter: no, Id have to get a sponsor such as Mirv
[21:40] <sitter> pretty sure you can
[21:40] <sitter> clivejo: you'd go through Mirv all the same?
[21:41] <ScottK> If you would want to is a different question.
[21:41] <clivejo> yes, I dont know enough about Qt at this time
[21:43] <clivejo> I think Im lagging big time
[21:43] <sitter> doesn't seem too bad. alas, who knows
[21:43] <valorie> !lag
[21:44] <acheronuk> Ireland just generally lags.....
[21:44] <sitter> clivejo: A week before final release a super important bug fix is submitted for kcoreaddons. It supposedly fixes a bug that makes every KDE application eat all the data in /. No upstream developer is able to review. No other Kubuntu dev is able to help. You have no idea if it is the best patch ever or the worst patch ever. What do you do?
[21:44] <clivejo> sitter: Id have to check if the package is one I could upload, but I wouldnt 
[21:44] <sitter> Quintasan, sgclark, ScottK: final call for questions
[21:45] <ScottK> clivejo: who are your recent sponsors?
[21:45] <sgclark> I am done
[21:45] <clivejo> Id test the bejaysus out of it
[21:45] <tsimonq2> yeah I'll stop grilling now, I'll grill later :P
[21:46] <Quintasan> I'm not really in my top shape so I'll back off.
[21:46] <ScottK> clivejo: still waiting on one last answer ...
[21:47] <clivejo> if I was 100% satisfied that it was tested, the patch came from upstream and the patch was being applied correctly then Id consider uploading it
[21:47] <clivejo> otherwise no
[21:47] <clivejo> ScottK: I dont know :(
[21:48] <sitter> clivejo: who has uploaded packages for you until now?
[21:48] <clivejo> Phillip
[21:48] <sitter> no one else?
[21:48]  * sgclark whistles
[21:48] <clivejo> JR, Scarlett
[21:49] <clivejo> by sponsors I thought you meant on my dev app
[21:49] <sitter> clivejo: I see you only have gotten endorsement on your wiki page from Scarlett. did you ask the other two?
[21:49] <clivejo> sitter: yes I did :(
[21:50]  * sitter wags finger at yofel and Riddell 
[21:50] <sitter> ScottK, sgclark, Quintasan: let's vote. and someone other than me needs to start plz :P
[21:50] <sgclark> start what?
[21:51] <Quintasan> Voting
[21:51] <sgclark> dunno how that works is it private?
[21:52] <Quintasan> sgclark: It's public IIRC, been a long time since we had some grilling.
[21:52] <sitter> +1/+0/-1 with comment if you wish
[21:52] <sitter> public
[21:52] <Quintasan> sec
[21:52] <sgclark> ok.. starting +1 from me.
[21:52] <sitter> unless you want private :P
[21:55]  * sgclark wonders where everyone went
[21:55] <ahoneybun> +1 even if my vote does not matter 
[21:55] <ScottK> Still here.
[21:55] <ScottK> I'll +1.
[21:56] <ScottK> sitter, Quintasan?
[21:57] <tsimonq2> +1 even though my vote doesn't matter
[21:58] <Quintasan> clivejo: +1 from me, I think you have the skills but I can't exactly say that I'm convinced that you know where your responsibilities start and end. What managed to convince me was that you were quick to say you don't have the knowledge necessary to make the right call and you'd ask someone else.
[21:58] <sitter> +0 This was one of the least technical grillings I have done because there are some rather sizable holes in your technical experience here, so I held back. You have a general gaps on symbols but the underlying details seem to be not known yet. Equally it looks with the inner workings of debian/rules as well as overall package metadata. Even so you display a very solid understanding of responsibility towards upstream, peers within Ubuntu, and 
[21:58] <sitter> the users. The ultimate requirement for becoming a dev. I can’t really overlook the technical shortcomings as this vote is not on trust but technical merit. In another 3 to 6 months more experience I could probably give a +1, right now I can’t unfortunately.
[21:59] <sitter> with that I think everyone present voted. 3 in favor, 1 abstain. which is a majority of present and at least 3. meaning clivejo is accepted as developer
[21:59] <sitter> clivejo: congratulations!
[22:00] <sgclark> clivejo: congrats :)
[22:00] <clivejo> thanks sitter
[22:00] <tsimonq2> clivejo: CONGRATS! :D
[22:00] <wxl> congrats clivejo :)
[22:00] <acheronuk> clivejo: Congratulations :)
[22:00] <valorie> woooooo, /me releases the balloons
[22:01] <tsimonq2> clivejo: 🎈🎈🎈🎈🎈🎈🎈🎈🎈🎈🎈🎈🎈🎈🎈🎈🎈🎈🎈🎈🎈🎈🎈🎈🎈🎈🎈🎈🎈🎈🎈🎈
[22:01] <wxl> balloons? i was hoping for hounds.
[22:01] <tsimonq2> LOL
[22:01] <santa_> clivejo: congrats, and when the congrats round is over we have some packages to upload :P
[22:01] <tsimonq2> yup, santa_ is right :P
[22:01] <acheronuk> sitter: be assured we will all do our utmost to help clivejo find his feet in thsi role, technically and otherwise.
[22:01] <Quintasan> clivejo: Congratulations. Please do exercise caution when exerting your powers and do not hestitate to bugger us with questions if you are not sure.
[22:01] <valorie> lol
[22:01] <clivejo> one question I have, is there someone willing to mentor ?
[22:01] <ahoneybun> GOOD STUFF clivejo
[22:02] <sgclark> please do continue to ask any of us when you are unsure of anything clivejo
[22:02] <tsimonq2> GOOOOOOOOOOD STUFF!
[22:02] <sitter> acheronuk: glad to hear. that's what a team is for :)
[22:02] <tsimonq2> +1 ahoneybun 
[22:02] <tsimonq2> *acheronuk
[22:02] <ahoneybun> thanks Quintasan sitter sgclark ScottK for the words of wisdom
[22:02] <tsimonq2> and Aaron too :P
[22:03] <tsimonq2> you'll see me in three months lol
[22:03] <tsimonq2> (kidding, may be more like six)
[22:03] <tsimonq2> (if I don't get MOTU first :P)
[22:03] <Quintasan> tsimonq2: I recommend going the MOTU way first.
[22:04] <Quintasan> You'll have to work with very many different packages.
[22:04] -kubuntu-ci:#kubuntu-devel- Project xenial_unstable_ktp-common-internals build #201: STILL UNSTABLE in 49 min: http://kci.pangea.pub/job/xenial_unstable_ktp-common-internals/201/
[22:04] <tsimonq2> Quintasan: but then I won't need Kubuntu Dev...
[22:04] <Quintasan> You will
[22:04] <tsimonq2> ...?
[22:04] -kubuntu-ci:#kubuntu-devel- Project xenial_unstable_umbrello build #85: NOW UNSTABLE in 49 min: http://kci.pangea.pub/job/xenial_unstable_umbrello/85/
[22:04] <acheronuk> tsimonq2: with fingers already in the pie of a few projects, that might not be a bad idea!
[22:04] <Quintasan> Masters Of The Universe, as the name implies, can't uplod to main
[22:04] -kubuntu-ci:#kubuntu-devel- Project xenial_unstable_kstars build #250: STILL UNSTABLE in 50 min: http://kci.pangea.pub/job/xenial_unstable_kstars/250/
[22:05] <sitter> tsimonq2: Qt is main for example
[22:05] <tsimonq2> Quintasan: does Kubuntu have packages in Main?
[22:05] <sitter> that said motu covers most of kubuntu these days
[22:05] -kubuntu-ci:#kubuntu-devel- Yippee, build fixed!
[22:05] -kubuntu-ci:#kubuntu-devel- Project xenial_unstable_kactivities build #225: FIXED in 51 min: http://kci.pangea.pub/job/xenial_unstable_kactivities/225/
[22:05] <acheronuk> tsimonq2: if you aim is to work for Canonical, as you state.... then...
[22:06] <Quintasan> Fair enough I guess.
[22:06] -kubuntu-ci:#kubuntu-devel- Project xenial_unstable_kdelibs4support build #191: STILL FAILING in 1 min 33 sec: http://kci.pangea.pub/job/xenial_unstable_kdelibs4support/191/
[22:06]  * acheronuk think Simon will try to do all at the same time!
[22:06] <tsimonq2> acheronuk: hopefully I"ll have upload access to the whole archive before I'm legally qualified to apply
[22:06] <tsimonq2> oh you know me so well :P
[22:07] <tsimonq2> I think I have to be 18 to work at Canonical
[22:07] <wxl> move to a country without child labor laws
[22:07] <tsimonq2> lol
[22:10] <sitter> clivejo: I've just added you to the team. As the esteemed founder would say: "remember, with great power.... comes potential for great mischief". try to not break qt though, that will cause tears ;)
[22:11] <mparillo> I would love to change the topic to recognize clivejo, but the topic is crammed full of good info already. 
[22:11] <clivejo> thank you sitter
[22:12] -kubuntu-ci:#kubuntu-devel- Project xenial_unstable_kdelibs4support build #192: STILL FAILING in 41 sec: http://kci.pangea.pub/job/xenial_unstable_kdelibs4support/192/
[22:13] <santa_> sitter: so is he able to upload packages now?
[22:13] <tsimonq2> yes siree!
[22:14] <clivejo> Id rather not upload anything just yet
[22:14] <tsimonq2> soon his name will appear here: http://people.canonical.com/~ubuntu-archive/packagesets/yakkety/kubuntu
[22:15] <wxl> holy unicode issues
[22:15] <wxl> poor Quintasan 
[22:16] <wxl> on the other hand, the unicode ain't looking so hot in his irc real name
[22:16] <wxl> oh and i see poor yofel is messed up too
[22:17] <tsimonq2> Michał Zając - that uses funny chars...
[22:18] <wxl> s/funny/unicode/ 
[22:18] <wxl> certainly not funny for his locale
[22:18] <wxl> you would think that, given that this page is from a canonical resource, and that ubuntu is an international project, that they'd have something so simple as unicode figured out
[22:19] <sitter> unicode is not simple...
[22:19] <wxl> oh and actually they do have that figured at
[22:19] <wxl> my bad
[22:19] <tsimonq2> sitter: you CCed Mark? ;D
[22:19] <wxl> it's just the stupid default chrome font can't handle it ugh
[22:20] <sitter> tsimonq2: he always gets CCd on developer additions
[22:21] <tsimonq2> ooh good stuff
[22:22] -kubuntu-ci:#kubuntu-devel- Project xenial_unstable_ktp-auth-handler build #175: STILL UNSTABLE in 18 min: http://kci.pangea.pub/job/xenial_unstable_ktp-auth-handler/175/
[22:40] <valorie> thank you to all the devels who pitched in today to make clive's life temporarily a living hell
[22:40] <valorie> :-)
[22:41] <acheronuk> lol
[22:41] -kubuntu-ci:#kubuntu-devel- Project yakkety_unstable_umbrello build #73: NOW UNSTABLE in 36 min: http://kci.pangea.pub/job/yakkety_unstable_umbrello/73/
[22:41] <tsimonq2> fun stuff XD
[22:41] <tsimonq2> I MEAN...
[22:41] <acheronuk> tsimonq2: you were
[22:41] <tsimonq2> lol
[22:41] <acheronuk> :P
[22:41] <valorie> now you've upgraded our team, so thank you again
[22:42] <valorie> hopefully you didn't scare acheronuk 10 shades whiter
[22:42] -kubuntu-ci:#kubuntu-devel- Project yakkety_unstable_kdelibs4support build #83: STILL FAILING in 1 min 30 sec: http://kci.pangea.pub/job/yakkety_unstable_kdelibs4support/83/
[22:42] <acheronuk> I've had far worse. just not via IRC
[22:42] <tsimonq2> I'm 100 shades brigher
[22:42] <tsimonq2> lol acheronuk 
[22:43] <tsimonq2> *brighter
[22:43] <acheronuk> face to face is nasty for a grilling
[22:44] <acheronuk> can't have 'lag' either
[22:44] <tsimonq2> you all need to freaking SCORCH me
[22:44] <acheronuk> you scare me
[22:45] <tsimonq2> oh?
[22:46]  * valorie suspects some latent masochism
[22:46] <acheronuk> latent?
[22:47] <valorie> ha!
[22:47] <acheronuk> anyway, that clarified a few thing I need to read up on!
[22:48] -kubuntu-ci:#kubuntu-devel- Project yakkety_unstable_kdelibs4support build #84: STILL FAILING in 48 sec: http://kci.pangea.pub/job/yakkety_unstable_kdelibs4support/84/
[22:48]  * acheronuk bookmarks IRC log
[23:05] -kubuntu-ci:#kubuntu-devel- Project yakkety_unstable_okular build #88: STILL UNSTABLE in 33 min: http://kci.pangea.pub/job/yakkety_unstable_okular/88/
[23:05] -kubuntu-ci:#kubuntu-devel- Project yakkety_unstable_kstars build #120: STILL UNSTABLE in 1 hr 1 min: http://kci.pangea.pub/job/yakkety_unstable_kstars/120/
[23:06] -kubuntu-ci:#kubuntu-devel- Project xenial_unstable_akonadi build #260: STILL FAILING in 1 hr 1 min: http://kci.pangea.pub/job/xenial_unstable_akonadi/260/
[23:06] -kubuntu-ci:#kubuntu-devel- Project yakkety_unstable_kppp build #77: STILL UNSTABLE in 40 min: http://kci.pangea.pub/job/yakkety_unstable_kppp/77/
[23:25] -kubuntu-ci:#kubuntu-devel- Project xenial_unstable_umbrello build #86: STILL UNSTABLE in 49 min: http://kci.pangea.pub/job/xenial_unstable_umbrello/86/
[23:26] -kubuntu-ci:#kubuntu-devel- Project xenial_unstable_kirigami build #28: STILL UNSTABLE in 44 min: http://kci.pangea.pub/job/xenial_unstable_kirigami/28/
[23:26] -kubuntu-ci:#kubuntu-devel- Project yakkety_unstable_kpimtextedit build #90: STILL FAILING in 39 min: http://kci.pangea.pub/job/yakkety_unstable_kpimtextedit/90/
[23:26] -kubuntu-ci:#kubuntu-devel- Project yakkety_unstable_ktp-common-internals build #128: STILL UNSTABLE in 46 min: http://kci.pangea.pub/job/yakkety_unstable_ktp-common-internals/128/
[23:27] -kubuntu-ci:#kubuntu-devel- Project xenial_unstable_kpimtextedit build #177: STILL FAILING in 40 min: http://kci.pangea.pub/job/xenial_unstable_kpimtextedit/177/
[23:27] -kubuntu-ci:#kubuntu-devel- Project xenial_unstable_ktp-common-internals build #202: STILL UNSTABLE in 46 min: http://kci.pangea.pub/job/xenial_unstable_ktp-common-internals/202/
[23:39] -kubuntu-ci:#kubuntu-devel- Project xenial_unstable_kopete build #77: STILL UNSTABLE in 36 min: http://kci.pangea.pub/job/xenial_unstable_kopete/77/
[23:40] -kubuntu-ci:#kubuntu-devel- Project yakkety_unstable_akonadi build #180: STILL FAILING in 58 min: http://kci.pangea.pub/job/yakkety_unstable_akonadi/180/
[23:40] -kubuntu-ci:#kubuntu-devel- Project yakkety_unstable_kopete build #54: STILL UNSTABLE in 37 min: http://kci.pangea.pub/job/yakkety_unstable_kopete/54/
[23:41] -kubuntu-ci:#kubuntu-devel- Project xenial_unstable_kdesdk-kioslaves build #74: STILL UNSTABLE in 16 min: http://kci.pangea.pub/job/xenial_unstable_kdesdk-kioslaves/74/
[23:51] -kubuntu-ci:#kubuntu-devel- Project yakkety_unstable_libkleo build #53: STILL FAILING in 25 min: http://kci.pangea.pub/job/yakkety_unstable_libkleo/53/
[23:52] -kubuntu-ci:#kubuntu-devel- Project yakkety_unstable_plasma-pa build #99: STILL FAILING in 23 min: http://kci.pangea.pub/job/yakkety_unstable_plasma-pa/99/
[23:52] -kubuntu-ci:#kubuntu-devel- Project xenial_unstable_kde-runtime build #183: STILL FAILING in 31 min: http://kci.pangea.pub/job/xenial_unstable_kde-runtime/183/
[23:52] -kubuntu-ci:#kubuntu-devel- Project yakkety_unstable_kde-runtime build #189: STILL FAILING in 31 min: http://kci.pangea.pub/job/yakkety_unstable_kde-runtime/189/
[23:52] -kubuntu-ci:#kubuntu-devel- Project yakkety_unstable_kirigami build #32: STILL UNSTABLE in 23 min: http://kci.pangea.pub/job/yakkety_unstable_kirigami/32/
[23:52] -kubuntu-ci:#kubuntu-devel- Project yakkety_unstable_ktp-auth-handler build #129: STILL UNSTABLE in 24 min: http://kci.pangea.pub/job/yakkety_unstable_ktp-auth-handler/129/
[23:59] -kubuntu-ci:#kubuntu-devel- Project xenial_unstable_discover build #57: STILL FAILING in 7 min 45 sec: http://kci.pangea.pub/job/xenial_unstable_discover/57/