[00:03] -kubuntu-ci:#kubuntu-devel- Project artful_stable_ark build #53: STILL UNSTABLE in 30 min: https://kci.pangea.pub/job/artful_stable_ark/53/
[00:07] -kubuntu-ci:#kubuntu-devel- Yippee, build fixed!
[00:07] -kubuntu-ci:#kubuntu-devel- Project xenial_stable_kwin build #82: FIXED in 59 min: https://kci.pangea.pub/job/xenial_stable_kwin/82/
[00:07] -kubuntu-ci:#kubuntu-devel- Project artful_unstable_elisa build #52: STILL UNSTABLE in 32 min: https://kci.pangea.pub/job/artful_unstable_elisa/52/
[00:08] -kubuntu-ci:#kubuntu-devel- Project artful_unstable_umbrello build #38: STILL UNSTABLE in 36 min: https://kci.pangea.pub/job/artful_unstable_umbrello/38/
[00:21] -kubuntu-ci:#kubuntu-devel- Project artful_unstable_ark build #60: STILL UNSTABLE in 25 min: https://kci.pangea.pub/job/artful_unstable_ark/60/
[00:38] -kubuntu-ci:#kubuntu-devel- Project artful_stable_kalzium build #51: STILL UNSTABLE in 37 min: https://kci.pangea.pub/job/artful_stable_kalzium/51/
[00:39] -kubuntu-ci:#kubuntu-devel- Project xenial_unstable_ring-kde build #12: STILL FAILING in 8 min 46 sec: https://kci.pangea.pub/job/xenial_unstable_ring-kde/12/
[00:39] -kubuntu-ci:#kubuntu-devel- Project artful_stable_umbrello build #49: STILL UNSTABLE in 31 min: https://kci.pangea.pub/job/artful_stable_umbrello/49/
[00:42] -kubuntu-ci:#kubuntu-devel- Project xenial_unstable_kile build #58: STILL UNSTABLE in 20 min: https://kci.pangea.pub/job/xenial_unstable_kile/58/
[00:42] -kubuntu-ci:#kubuntu-devel- Project zesty_unstable_kget build #128: STILL UNSTABLE in 26 min: https://kci.pangea.pub/job/zesty_unstable_kget/128/
[00:42] -kubuntu-ci:#kubuntu-devel- Project artful_unstable_kalzium build #56: STILL UNSTABLE in 34 min: https://kci.pangea.pub/job/artful_unstable_kalzium/56/
[00:52] -kubuntu-ci:#kubuntu-devel- Project xenial_stable_cantor build #45: STILL UNSTABLE in 24 min: https://kci.pangea.pub/job/xenial_stable_cantor/45/
[00:52] -kubuntu-ci:#kubuntu-devel- Project xenial_stable_plasma-pa build #55: STILL UNSTABLE in 22 min: https://kci.pangea.pub/job/xenial_stable_plasma-pa/55/
[00:55] -kubuntu-ci:#kubuntu-devel- Project xenial_unstable_elisa build #58: STILL UNSTABLE in 27 min: https://kci.pangea.pub/job/xenial_unstable_elisa/58/
[00:55] -kubuntu-ci:#kubuntu-devel- Project artful_unstable_kstars build #97: STILL UNSTABLE in 34 min: https://kci.pangea.pub/job/artful_unstable_kstars/97/
[01:21] -kubuntu-ci:#kubuntu-devel- Project xenial_unstable_kalzium build #219: STILL UNSTABLE in 40 min: https://kci.pangea.pub/job/xenial_unstable_kalzium/219/
[01:21] -kubuntu-ci:#kubuntu-devel- Project artful_unstable_kmailtransport build #38: STILL FAILING in 25 min: https://kci.pangea.pub/job/artful_unstable_kmailtransport/38/
[01:21] -kubuntu-ci:#kubuntu-devel- Project xenial_unstable_kstars build #524: STILL UNSTABLE in 26 min: https://kci.pangea.pub/job/xenial_unstable_kstars/524/
[01:22] -kubuntu-ci:#kubuntu-devel- Project xenial_unstable_ark build #527: STILL UNSTABLE in 30 min: https://kci.pangea.pub/job/xenial_unstable_ark/527/
[01:25] -kubuntu-ci:#kubuntu-devel- Project zesty_unstable_ring-kde build #13: STILL FAILING in 5 min 51 sec: https://kci.pangea.pub/job/zesty_unstable_ring-kde/13/
[01:31] -kubuntu-ci:#kubuntu-devel- Project artful_unstable_ring-kde build #13: STILL FAILING in 11 min: https://kci.pangea.pub/job/artful_unstable_ring-kde/13/
[01:31] -kubuntu-ci:#kubuntu-devel- Project artful_unstable_ktorrent build #13: STILL FAILING in 9 min 53 sec: https://kci.pangea.pub/job/artful_unstable_ktorrent/13/
[01:33] -kubuntu-ci:#kubuntu-devel- Project zesty_unstable_ark build #210: STILL UNSTABLE in 22 min: https://kci.pangea.pub/job/zesty_unstable_ark/210/
[01:34] -kubuntu-ci:#kubuntu-devel- Project zesty_unstable_kmailtransport build #177: STILL FAILING in 25 min: https://kci.pangea.pub/job/zesty_unstable_kmailtransport/177/
[01:40] -kubuntu-ci:#kubuntu-devel- Project xenial_unstable_kgoldrunner build #140: STILL FAILING in 6 min 24 sec: https://kci.pangea.pub/job/xenial_unstable_kgoldrunner/140/
[01:42] -kubuntu-ci:#kubuntu-devel- Project xenial_unstable_ring-kde build #13: STILL FAILING in 9 min 0 sec: https://kci.pangea.pub/job/xenial_unstable_ring-kde/13/
[01:56] -kubuntu-ci:#kubuntu-devel- Project zesty_unstable_elisa build #59: STILL UNSTABLE in 47 min: https://kci.pangea.pub/job/zesty_unstable_elisa/59/
[01:56] -kubuntu-ci:#kubuntu-devel- Project zesty_unstable_cantor build #166: STILL UNSTABLE in 46 min: https://kci.pangea.pub/job/zesty_unstable_cantor/166/
[01:56] -kubuntu-ci:#kubuntu-devel- Project zesty_unstable_kalzium build #157: STILL UNSTABLE in 38 min: https://kci.pangea.pub/job/zesty_unstable_kalzium/157/
[01:57] -kubuntu-ci:#kubuntu-devel- Project xenial_unstable_kmailtransport build #232: STILL FAILING in 35 min: https://kci.pangea.pub/job/xenial_unstable_kmailtransport/232/
[02:00] -kubuntu-ci:#kubuntu-devel- Project xenial_unstable_kgoldrunner build #141: STILL FAILING in 3 min 47 sec: https://kci.pangea.pub/job/xenial_unstable_kgoldrunner/141/
[02:14] -kubuntu-ci:#kubuntu-devel- Project zesty_unstable_umbrello build #192: STILL UNSTABLE in 55 min: https://kci.pangea.pub/job/zesty_unstable_umbrello/192/
[02:14] -kubuntu-ci:#kubuntu-devel- Project artful_unstable_kile build #50: STILL UNSTABLE in 43 min: https://kci.pangea.pub/job/artful_unstable_kile/50/
[02:15] -kubuntu-ci:#kubuntu-devel- Project artful_unstable_kgoldrunner build #26: STILL FAILING in 41 min: https://kci.pangea.pub/job/artful_unstable_kgoldrunner/26/
[02:15] -kubuntu-ci:#kubuntu-devel- Project zesty_unstable_kile build #61: STILL UNSTABLE in 41 min: https://kci.pangea.pub/job/zesty_unstable_kile/61/
[02:15] -kubuntu-ci:#kubuntu-devel- Project zesty_unstable_kgoldrunner build #85: STILL FAILING in 41 min: https://kci.pangea.pub/job/zesty_unstable_kgoldrunner/85/
[02:15] -kubuntu-ci:#kubuntu-devel- Project artful_unstable_kmailtransport build #39: STILL FAILING in 41 min: https://kci.pangea.pub/job/artful_unstable_kmailtransport/39/
[02:15] -kubuntu-ci:#kubuntu-devel- Project zesty_unstable_kstars build #260: STILL UNSTABLE in 56 min: https://kci.pangea.pub/job/zesty_unstable_kstars/260/
[02:17] -kubuntu-ci:#kubuntu-devel- Yippee, build fixed!
[02:17] -kubuntu-ci:#kubuntu-devel- Project xenial_unstable_kwin build #250: FIXED in 55 min: https://kci.pangea.pub/job/xenial_unstable_kwin/250/
[02:26] -kubuntu-ci:#kubuntu-devel- Project xenial_unstable_ktorrent build #18: STILL FAILING in 8 min 40 sec: https://kci.pangea.pub/job/xenial_unstable_ktorrent/18/
[02:34] -kubuntu-ci:#kubuntu-devel- Project zesty_stable_umbrello build #60: STILL UNSTABLE in 1 hr 25 min: https://kci.pangea.pub/job/zesty_stable_umbrello/60/
[02:36] -kubuntu-ci:#kubuntu-devel- Yippee, build fixed!
[02:36] -kubuntu-ci:#kubuntu-devel- Project xenial_stable_plasma-desktop build #68: FIXED in 1 hr 14 min: https://kci.pangea.pub/job/xenial_stable_plasma-desktop/68/
[02:38] -kubuntu-ci:#kubuntu-devel- Project zesty_unstable_kmailtransport build #178: STILL FAILING in 41 min: https://kci.pangea.pub/job/zesty_unstable_kmailtransport/178/
[02:40] -kubuntu-ci:#kubuntu-devel- Project xenial_unstable_ktorrent build #19: STILL FAILING in 8 min 38 sec: https://kci.pangea.pub/job/xenial_unstable_ktorrent/19/
[02:55] -kubuntu-ci:#kubuntu-devel- Project artful_unstable_kgoldrunner build #27: STILL FAILING in 34 min: https://kci.pangea.pub/job/artful_unstable_kgoldrunner/27/
[02:55] -kubuntu-ci:#kubuntu-devel- Project zesty_unstable_kgoldrunner build #86: STILL FAILING in 34 min: https://kci.pangea.pub/job/zesty_unstable_kgoldrunner/86/
[03:11] -kubuntu-ci:#kubuntu-devel- Project zesty_unstable_kfilemetadata build #172: STILL UNSTABLE in 32 min: https://kci.pangea.pub/job/zesty_unstable_kfilemetadata/172/
[03:11] -kubuntu-ci:#kubuntu-devel- Yippee, build fixed!
[03:11] -kubuntu-ci:#kubuntu-devel- Project xenial_unstable_plasma-desktop build #227: FIXED in 53 min: https://kci.pangea.pub/job/xenial_unstable_plasma-desktop/227/
[03:18] -kubuntu-ci:#kubuntu-devel- Project zesty_unstable_ktorrent build #16: STILL FAILING in 7 min 39 sec: https://kci.pangea.pub/job/zesty_unstable_ktorrent/16/
[03:31] -kubuntu-ci:#kubuntu-devel- Project zesty_unstable_ktorrent build #17: STILL FAILING in 7 min 37 sec: https://kci.pangea.pub/job/zesty_unstable_ktorrent/17/
[03:33] -kubuntu-ci:#kubuntu-devel- Project artful_unstable_kfilemetadata build #43: STILL UNSTABLE in 22 min: https://kci.pangea.pub/job/artful_unstable_kfilemetadata/43/
[03:52] -kubuntu-ci:#kubuntu-devel- Project xenial_unstable_phonon build #40: STILL UNSTABLE in 18 min: https://kci.pangea.pub/job/xenial_unstable_phonon/40/
[03:52] -kubuntu-ci:#kubuntu-devel- Project xenial_unstable_kpackage build #446: FAILURE in 9 min 43 sec: https://kci.pangea.pub/job/xenial_unstable_kpackage/446/
[04:08] -kubuntu-ci:#kubuntu-devel- Project xenial_unstable_kpackage build #447: STILL FAILING in 10 min: https://kci.pangea.pub/job/xenial_unstable_kpackage/447/
[04:16] <ahoneybun> clivejo: acheronuk http://www.omgubuntu.co.uk/2017/06/ubuntu-mate-new-software-boutique
[04:26] -kubuntu-ci:#kubuntu-devel- Project artful_unstable_kpackage build #44: FAILURE in 18 min: https://kci.pangea.pub/job/artful_unstable_kpackage/44/
[04:36] -kubuntu-ci:#kubuntu-devel- Project zesty_unstable_kpackage build #108: FAILURE in 18 min: https://kci.pangea.pub/job/zesty_unstable_kpackage/108/
[04:37] -kubuntu-ci:#kubuntu-devel- Project zesty_unstable_phonon build #33: STILL UNSTABLE in 19 min: https://kci.pangea.pub/job/zesty_unstable_phonon/33/
[04:47] -kubuntu-ci:#kubuntu-devel- Project artful_unstable_kpackage build #45: STILL FAILING in 15 min: https://kci.pangea.pub/job/artful_unstable_kpackage/45/
[04:54] <acheronuk> ahoneybun: discover without the cr**iness?
[04:55] -kubuntu-ci:#kubuntu-devel- Project zesty_unstable_kpackage build #109: STILL FAILING in 13 min: https://kci.pangea.pub/job/zesty_unstable_kpackage/109/
[04:55] -kubuntu-ci:#kubuntu-devel- Project artful_unstable_phonon build #48: STILL UNSTABLE in 18 min: https://kci.pangea.pub/job/artful_unstable_phonon/48/
[05:07] <acheronuk> is anyone able to do the verification on?: https://launchpad.net/bugs/1687444
 crappiness?
 @acheronuk
 yup
[05:21] <acheronuk> I missed the podcast?
 Well if they are removing the branding to allow other distros to use it
 Plus the themeing can be changed
 Yea
[05:21] <acheronuk> :(
[05:21] <acheronuk> was not the 1st Wednesday of the month any more then!
[05:22] <acheronuk> changed to the last?
 Well from Rick and issues with getting together
 A lot of things caused that
[05:23] <acheronuk> Now I don't get G+ notification and invites, it's hard to know :/
 Yea this was a badly timed one
[05:25] <acheronuk> ok. I'll have a look when it's online
 I didn't want to promote it and then it's just me or something
[05:25] <acheronuk> when is the next now then?
 Should be July 5th not sure now
 I'm wondering about expending it a bit more but idk
 Also just audio
[08:46] -kubuntu-ci:#kubuntu-devel- Project mgmt_docker » master build #1610: SUCCESS in 1 min 0 sec: https://kci.pangea.pub/job/mgmt_docker/label=master/1610/
[08:46] -kubuntu-ci:#kubuntu-devel- Project mgmt_docker » linode-01 build #1610: SUCCESS in 1 min 6 sec: https://kci.pangea.pub/job/mgmt_docker/label=linode-01/1610/
[08:49] -kubuntu-ci:#kubuntu-devel- Project mgmt_docker » swy-01 build #1610: SUCCESS in 4 min 0 sec: https://kci.pangea.pub/job/mgmt_docker/label=swy-01/1610/
[08:49] -kubuntu-ci:#kubuntu-devel- Project mgmt_docker » swy-02 build #1610: SUCCESS in 4 min 15 sec: https://kci.pangea.pub/job/mgmt_docker/label=swy-02/1610/
[09:13] <gsilvapt> I can't be of much help because I don't even know what needs to be done there, acheronuk 
[09:16] -kubuntu-ci:#kubuntu-devel- Yippee, build fixed!
[09:16] -kubuntu-ci:#kubuntu-devel- Project zesty_unstable_ktorrent build #18: FIXED in 27 min: https://kci.pangea.pub/job/zesty_unstable_ktorrent/18/
[09:17] -kubuntu-ci:#kubuntu-devel- Yippee, build fixed!
[09:17] -kubuntu-ci:#kubuntu-devel- Project artful_unstable_ktorrent build #14: FIXED in 27 min: https://kci.pangea.pub/job/artful_unstable_ktorrent/14/
[09:17] -kubuntu-ci:#kubuntu-devel- Yippee, build fixed!
[09:17] -kubuntu-ci:#kubuntu-devel- Project xenial_unstable_ktorrent build #20: FIXED in 28 min: https://kci.pangea.pub/job/xenial_unstable_ktorrent/20/
[09:37] -kubuntu-ci:#kubuntu-devel- Yippee, build fixed!
[09:37] -kubuntu-ci:#kubuntu-devel- Project zesty_unstable_kpackage build #110: FIXED in 20 min: https://kci.pangea.pub/job/zesty_unstable_kpackage/110/
[09:37] -kubuntu-ci:#kubuntu-devel- Yippee, build fixed!
[09:37] -kubuntu-ci:#kubuntu-devel- Project xenial_unstable_kpackage build #448: FIXED in 20 min: https://kci.pangea.pub/job/xenial_unstable_kpackage/448/
[09:37] -kubuntu-ci:#kubuntu-devel- Yippee, build fixed!
[09:37] -kubuntu-ci:#kubuntu-devel- Project artful_unstable_kpackage build #46: FIXED in 20 min: https://kci.pangea.pub/job/artful_unstable_kpackage/46/
[09:49] <BluesKaj> Hi folks
[09:50] <acheronuk> gsilvapt: no problem
[10:08]  * clivejo thinks Rik has the patients of a saint
[10:08] <clivejo> and that St Rik has a nice ring to it
[10:09] <acheronuk> Grrrrr..... https://cgit.kde.org/kdav2.git/
[10:13] <gsilvapt> To check if a missing symbol file is an ABI break, I need to find the .h file which defines the all functions, right? Is there a specific region for those or can it be anywhere inside the upstream's src directory?
[10:13] <gsilvapt> If function is public, it can be ABI, if private, is API (and thus the fix is simpler - get the logs, run symbolshelper, remove all #missing entries, push changes)
[10:14] <mparillo_> Hi BluesKaj. No re-spin of AA Alpha 1 so far. I did bump into: https://bugs.launchpad.net/ubuntu/+source/oem-config/+bug/1638473 The only 64-bit test remaining is manual partitioning.
[10:17] <BluesKaj> mparillo_, after installing AlphaI had a couple of crashes discober and system settings , but none after installing the nvidia gpu driver
[10:18] <mparillo_> TY. I assume valorie ^ is taking over as a release manager, and she will want to know all test cases were attempted.
[10:23] -kubuntu-ci:#kubuntu-devel- Project xenial_unstable_discover build #252: FAILURE in 3 min 53 sec: https://kci.pangea.pub/job/xenial_unstable_discover/252/
[10:32] -kubuntu-ci:#kubuntu-devel- Project xenial_unstable_discover build #253: STILL FAILING in 3 min 48 sec: https://kci.pangea.pub/job/xenial_unstable_discover/253/
[10:42] <santa_> ‎<‎gsilvapt‎>‎ If function is public, it can be ABI, if private, is API (and thus the fix is simpler - get the logs, run symbolshelper, remove all #missing entries, push changes)
[10:42] <santa_> this is statement is just wrong
[10:43] <santa_> API is one thing
[10:43] <santa_> ABI is another thing
[10:44] <santa_> whether if an element from the API or ABI is public or not is another thing
[10:45] -kubuntu-ci:#kubuntu-devel- Yippee, build fixed!
[10:45] -kubuntu-ci:#kubuntu-devel- Project zesty_unstable_discover build #261: FIXED in 25 min: https://kci.pangea.pub/job/zesty_unstable_discover/261/
[10:45] -kubuntu-ci:#kubuntu-devel- Yippee, build fixed!
[10:45] -kubuntu-ci:#kubuntu-devel- Project artful_unstable_discover build #72: FIXED in 25 min: https://kci.pangea.pub/job/artful_unstable_discover/72/
[10:47] <santa_> and that being said if an element of the ABI dissappears you can remove it from the symbols file safely
[10:48] <santa_> if it's not, the solution is either using the abi manager or sending a patch to kde restoring the ABI (asuming the ABI breaking was an accident)
[10:52] <santa_> https://phabricator.kde.org/w/kubuntu/packaging/symbols-files/
[10:52] <santa_> ↑ some "must read"
[10:53] <gsilvapt> I already read those, may have understood some concepts wrong
[10:55] <santa_> I encourage you to re-read. don't get demotivated, it's just the most complicated task we have here in the kde packaging land
[10:56] <santa_> also our documentation about it could be improved
[10:57] <gsilvapt> Ok, thanks. I'm trying to follow as I can. I think the hardest part is understanding how I can figure out if it is an ABI or API breakage. It's not clear in the logs we have online, where you explain Darin how this works
[10:59] <santa_> first you have to understand what the API is and what the ABI is
[11:04] <santa_> ‎<‎santa_‎>‎ and that being said if an element of the ABI dissappears you can remove it from the symbols file safely
[11:04] <santa_> ↑ I meant
[11:04] <santa_> and that being said if a PRIVATE element of the ABI dissappears you can remove it from the symbols file safely
[11:06]  * acheronuk did wonder at that remark
[11:09] <gsilvapt> If element is public, I have to use the ABI Manager, right? 
[11:09] <gsilvapt> So that, not only the package will build again, but other dependencies work too.
[11:11] <santa_> once they are rebuilt against the modified package with the bumped library, yes
[11:12] <gsilvapt> Ok, thanks. 
[11:13] <gsilvapt> Last request: Can you check if this simple to-do list is correct? http://paste.ubuntu.com/24980505/
[11:13] <gsilvapt> Check missing symbols is c++filt 
[11:23] <santa_> gsilvapt: I think that should work
[11:24] <santa_> if it doesn't you can simply ask again
[11:53] <gsilvapt> thanks, santa_ :)
[11:55] <acheronuk> no nasty reports from 5.10.3 in bp-landing, so going to copy that to backports proper
[12:00] <acheronuk> kopied
[12:10] <mparillo> acheronuk: Plasma 5.10.3 is only going to backports for ZZ, correct? Kubuntu 16.04 will keep with Plasma 5.8 LTS series?
[12:11] <acheronuk> mparillo: correct
[12:11] <mparillo> Starting up my 17.04 VM.
[12:26] <mparillo> When packages get moved from -landing to the archive, the version changes, so I get a fresh copy. But when they get moved from -landing to backports, is there no version bump? Because I did not get a fresh set of 5.10.3 packages.
[12:41] <acheronuk> mparillo: correct. it's a straight copy of the existing packages. if you already have them from landing, there will be no change
[14:19] <gsilvapt> After making changes to the symbols files, is there a way to test if I did the correct changes, i.e, if it will not cause any regression in other packages?
[14:19] <gsilvapt> Besides, of course, pushing the changes upstream and then break other packages
[14:45] -kubuntu-ci:#kubuntu-devel- Project mgmt_docker » linode-01 build #1611: SUCCESS in 55 sec: https://kci.pangea.pub/job/mgmt_docker/label=linode-01/1611/
[14:46] -kubuntu-ci:#kubuntu-devel- Project mgmt_docker » master build #1611: SUCCESS in 59 sec: https://kci.pangea.pub/job/mgmt_docker/label=master/1611/
[14:48] -kubuntu-ci:#kubuntu-devel- Project mgmt_docker » swy-01 build #1611: SUCCESS in 3 min 47 sec: https://kci.pangea.pub/job/mgmt_docker/label=swy-01/1611/
[14:49] -kubuntu-ci:#kubuntu-devel- Project mgmt_docker » swy-02 build #1611: SUCCESS in 4 min 13 sec: https://kci.pangea.pub/job/mgmt_docker/label=swy-02/1611/
[15:18] <acheronuk> gsilvapt: which package are these symbols on? or are your questions theoretical?
 Theoretical only, acheronuk
[17:09] <clivejo> @gsilvapt still a problem with kgoldrunner
[17:09] <gsilvapt> Something's missing? It was building locally 
[17:10] <clivejo> [17:10] <clivejo> -./etc/xdg/kgoldrunner.knsrc
[17:10] <clivejo> [17:11] <clivejo> and another issue7
[17:11] <clivejo> well few items
[17:12] <gsilvapt> Is that in the log I posted? 
[17:12] <clivejo> better to use KCI parser
[17:12] <clivejo> http://kci.pangea.pub/job/artful_unstable_kgoldrunner/27/parsed_console/
[17:12] <gsilvapt> I can take a look later tonight. It said successful and not tempted, thus I thought I fixed it.
[17:12] <clivejo> E: kgoldrunner source: obsolete-relation-form-in-source in source build-depends: libkf5kdegames-dev (> 4.9.0)
[17:12] <clivejo> E: kgoldrunner source: obsolete-relation-form-in-source in source build-depends: libqt5svg5-dev (> 5.7.0)
[17:12] <clivejo> KCI-E :: E: kgoldrunner source: obsolete-relation-form-in-source in source build-depends: qtdeclarative5-dev (> 5.7.0)
[17:13] <gsilvapt> What does that mean? 
[17:13] <clivejo> W :: Phonon4Qt5Experimental (required version == 4.9.51)
[17:13] <gsilvapt> I have to leave now but I'll be back soon to fix that package
[17:13] <clivejo> lintian is your friend and your enemy
[17:14] <clivejo> https://lintian.debian.org/tags/obsolete-relation-form-in-source.html
[17:14] <clivejo> should be (>= 4.9.0) rather than (> 4.9.0)
[17:14] <clivejo> you are misisng an equals sign
[17:16] <clivejo> think of lintian like a little Simon on your shoulder
[17:16] <clivejo> whispering OCD stuff in your ear
[17:17] <clivejo> "surnames shouldn't be capitalised"
 @acheronuk so I found pandoc that can convert rst to docbook
[17:44] -KubuntuManual:#kubuntu-devel- [kubuntu-manual] ahoneybun pushed 1 new commit to master: https://git.io/vQ8uS
[17:44] -KubuntuManual:#kubuntu-devel- kubuntu-manual/master 28f37d0 Aaron Honeycutt: testing pandoc to convert rst to docbook(db)
 @ahoneybun, please translate that to English. I don't speak 'documentation' :P
 well docbook is what khelpcenter uses
 tho the docs on it say they should use HTML frst
 I know what docbook is. It's the rest tha is gobbledygook
 the manual is written in rst, restructured text
 funny enough all the khelpcenter docs are just docbook no html...
[17:52] <travis-ci> ahoneybun/kubuntu-manual#40 (master - 28f37d0 : Aaron Honeycutt): The build passed.
[17:52] <travis-ci> Change view : https://github.com/ahoneybun/kubuntu-manual/compare/6ded6cf1f669...28f37d05a28f
[17:52] <travis-ci> Build details : https://travis-ci.org/ahoneybun/kubuntu-manual/builds/248468588
 oh right
[19:25] <valorie> ahoneybun: you could work upstream and get khelpcenter fixed and able to read rst?
[19:25] <valorie> folks, is anyone working on 386 test cases?
 valorie that must a job
 *joke
[19:31] <ahoneybun> I say that as I doubt they would help with it
[19:32] <ahoneybun> cyphermox_: any time to look at that MR?
[19:33] <valorie> kde devels are helpful!
[19:33] <ahoneybun> helpful =/ cooparative 
[19:33] <ahoneybun> tsimonq2: I know I spelled that wrong
[19:34] <ahoneybun> I've learned that the hard way
[19:34] <tsimonq2> ahoneybun: AARON WHY YOU SPELL THINGS WRONG URGHHGJHLJKDFSGSHGKJLSHDTJKLHE54KJTH43KQT5KHGHLE5HGHDEKJH
[19:34] <tsimonq2> lol
[19:34] <ahoneybun> the point was made
 @ahoneybun, Maybe that's your problem?
[19:56] <ahoneybun> what Santa?
 The fact that kde developers 'are uncooperative'(sic)?
 How would that be my problem?
 Because kde tends to be a project open to anyone, unlike linux distributions
 Again not sure what that has to do with me
 We are open to anyone if that's what your driving at
 Nope, linux distributions tend to be 'open' only to 'trusted' people. An that includes kubuntu.
 So maybe, if can't get your stuff done inside kde, maybe you aren't pulling the right strings.
 Well you need to be trusted and no project just let's some random people come in and start editing
 Kde does
 Not sure your problem with common methods
 I don't believe that
 I got an svn account in 3 days.
 And I jusr send a mail saying what I was planning to do.
 Well that's not how it works here or in other distros
 For good reason
 @ahoneybun, They are not common. The culture of 'trust' is something which, so far, I have seen only in linux distributions and not in kde
 They are common in most places
 You just don't understand the reasoning behind it
 @ahoneybun, Sure, to keep some people in their thrones.
 Strongly disagree there
 No, they aren't
 No one is in a throne other then sabdfl
 Really?
[20:06] <ahoneybun> yep
 Why Simon got his privileges revoked then?
[20:06] <ahoneybun> cuz he made bad choices
[20:07] <valorie> thrones?
 No, because you decided to revoke his permissions, because *you* think he made bad choices
[20:08] <valorie> I don't understand what is being said here
[20:08] <mparillo> How does one make good decisions? Experience. How does one gain experience? Bad decisions.
[20:08] <valorie> @Santa -- it was a general decision, and Simon agreed with it
[20:08] <valorie> and I think he's a better developer because of it
 Also, why we had to wait like one month to get our packaging into the unstable version?
[20:09] <valorie> in Ubuntu you mean?
 Why I had to send patches over 2 years to get a simple git account?
[20:09] <valorie> here?
[20:09] <valorie> I'm unsure what exactly is being said here
 Why, after that I had to deal with so much unfair questioning of a work which was absolutely neccesary?
[20:10] <mparillo> valorie: Thanks for joining. I think the testing is complete for 64-bit. If you scroll to early this morning, BluesKaj said after installing drivers, his AA install was good, and I am pretty sure he did manual partitioning, which is the test case not marked as attempted from http://iso.qa.ubuntu.com/qatracker/milestones/378/builds/150984/testcases
[20:11] <BluesKaj> mparillo, yes that's what i did
 @valorie, That kde tends to be an open project. Linux distributions are not. So if you don't get your stuff done in kde, you are probably the only one to blame.
[20:12] <mparillo> Thanks BluesKaj. 
 Santa distros are open projects, I've told you this
[20:13] <valorie> @Santa, ok, point taken, although I don't think blame enters into it
 as with any project there is someone to review the change of course
[20:13] <valorie> here in Kubuntu we have had projects that ended up moving upstream to KDE
[20:14] <mparillo> So, I took the liberty of passing http://iso.qa.ubuntu.com/qatracker/milestones/378/builds/150984/testcases/1302/results
[20:14] <valorie> I don't know about other distros, but yes they are in some ways less open than KDE or some other upstreams
[20:15] <valorie> but then some upstreams are very closed
[20:15] <mparillo> Which completes 64-bit. All passed except OEM.
[20:15] <valorie> cool
[20:17] <mparillo> And Arch will drop official support for i686 (https://lists.archlinux.org/pipermail/arch-dev-public/2017-January/028660.html), neon never did support it.
[20:21] <valorie> if we can't get testers for it, I will vote to drop it
[20:21] <valorie> however I think we need at least a bit of discussion about that
[20:36] <valorie> mail sent
[20:51] <mparillo> valorie: Great note. There will inevitably be complainers at release time, so perhaps (assuming the larger ubuntu project is OK with that) we can postpone the final decision.
[20:54] <clivejo> gsilvapt: about?
[20:54] <gsilvapt> sorry? 
[20:54] <clivejo> just regarding MR
[20:54] <gsilvapt> I miss a dot, didn't I? 
[20:54] <clivejo> the install file
[20:54] <clivejo> nope, you need to drop the ./
[20:54] <gsilvapt> hum
[20:55] <gsilvapt> Closing & proposing again
[20:55] <clivejo> the reason the first two have ../ on them is because they are copy a file from within the packaging, into the .deb file
[20:55] <gsilvapt> so I should drop ./ in this case, right? 
[20:56] <clivejo> yes
[20:56] <gsilvapt> Ah, right you wrote that above, sorry.
[20:56] <clivejo> its more a pattern to match, rather than a path
[20:57] <clivejo> etc/ would work just as well
[20:57] <gsilvapt> god dammit
[20:57] <clivejo> like the usr/ alreadly there
[20:57] <clivejo> no what you have is fine
[20:57] <gsilvapt> Ok, this worked in this case. Totally forgot to run wrap-and-sort
[20:57] <clivejo> there is only one new file and that will catch it
[20:58] <gsilvapt> Hum, I see. If just etc/ is cleaner, I can cancel and propose again if needed
[20:58] <clivejo> no no
[20:58] <clivejo> just keep it in mind
[20:59] <gsilvapt> It's hard for me to read all those outputs and logs so I can't really tell when I should use each one. But I'll try to check if the logs says something more about it next time
[20:59] <clivejo> make notes for yourself
[21:00] <clivejo> I have load of .txt files with notes on how to do stuff
[21:00] <clivejo> unfortunately I'm like a gold fish when it comes to commands 
[21:01] <clivejo> just can't remember them
[21:01] <clivejo> would you refresh the symbols on kreport
[21:02] <clivejo> it's not in the archive, so we can't break anything by removing symbols
[21:04] <gsilvapt> I was going to take care of those this evening but wasn't sure if it was okay with just removing symbols. Tried deciphering if  it was an ABI breakage or API but couldn't really figure out.
[21:04] <gsilvapt> In that case, I will proceed with the cleanup and push changes via merge request
[21:04] <clivejo> that package is new
[21:04] <clivejo> hasnt made it into the archive and may never 
[21:05] -kubuntu-ci:#kubuntu-devel- Project xenial_unstable_kgoldrunner build #142: STILL FAILING in 4 min 45 sec: https://kci.pangea.pub/job/xenial_unstable_kgoldrunner/142/
[21:05] <clivejo> unfortunately I don't have the time nor the patients to fight to get it in! 
[21:08] <clivejo> ah, libqt53dquick5 is not in xenial
[21:13] <tsimonq2> clivejo: *patience
[21:13] <tsimonq2> clivejo: Let me know what you need in and I'll make sure it does.
[21:15] <clivejo> not that important in the grand scheme of things
[21:16] <clivejo> hi ronnoc
[21:17] <gsilvapt> I'll be on & off for the rest of the evening, but feel free to ping me 
[21:34] <clivejo> anyone know if VLC can stream to Chromecast?
[21:38] <valorie> that would be cool if so
[21:38] <valorie> ask in #kde-multimedia?
[21:38] <clivejo> according to Joey it's official!
[21:39] <clivejo> It’s Official: VLC 3.0 Will Get Chromecast Support
[21:39] <valorie> nice
[21:39] <valorie> oops, almost made a disparaging remark
[21:39] <clivejo> humm
[21:40]  * valorie goes back to reading GSoC evaluations
[21:40]  * clivejo grabs valorie's tongue
[21:40] <valorie> yikes!
[21:41] <clivejo> and 3.0.0 isn't building :(
[21:45] -kubuntu-ci:#kubuntu-devel- Project artful_unstable_kgoldrunner build #28: NOW UNSTABLE in 44 min: https://kci.pangea.pub/job/artful_unstable_kgoldrunner/28/
[21:45] -kubuntu-ci:#kubuntu-devel- Yippee, build fixed!
[21:45] -kubuntu-ci:#kubuntu-devel- Project artful_unstable_kreport build #47: FIXED in 21 min: https://kci.pangea.pub/job/artful_unstable_kreport/47/
[21:47] <clivejo> gsilvapt: you can't find packages for Phonon4Qt5Experimental?
[21:47] <tsimonq2> clivejo: Got a build log?
[21:47] <tsimonq2> clivejo: <3 vlc
[21:48] <valorie> I began using VLC when I was still a windows user!
[21:48] <clivejo> videolan team on LP
[21:48] <clivejo> master
[21:48] <clivejo> PPA
[21:49]  * clivejo ponders adding vlc to KCI
[21:50] <clivejo> tsimonq2:  https://launchpad.net/~videolan/+archive/ubuntu/master-daily
[21:53] <clivejo> tsimonq2: fix it!
[21:53] <clivejo> now
[21:55] <tsimonq2> clivejo: looking into it
[21:55] <tsimonq2> First step in fixing a build error: reproduce it locally
[21:55] <tsimonq2> If you can't reproduce it, how can you fix it?
[21:57] <clivejo> your magic wand
[21:58] <tsimonq2> My magic wand contains those steps
[21:58] <tsimonq2> :P
 Not really, clivejo. The Photon4Qt5 packages have always been a nightmare
[22:00] <tsimonq2> clivejo: Rather than using this packaging, I'll just take the one from Debian's Git repo...
[22:01] <tsimonq2> Because they have it there!
[22:06] -kubuntu-ci:#kubuntu-devel- Project zesty_unstable_kgoldrunner build #87: NOW UNSTABLE in 1 hr 6 min: https://kci.pangea.pub/job/zesty_unstable_kgoldrunner/87/
[22:08] <clivejo> just make it work :P
[22:19] <clivejo> tsimonq2: you done yet?
[22:22] <tsimonq2> clivejo: Not yet, busy
[22:23]  * clivejo rolls eyes
[23:06] -kubuntu-ci:#kubuntu-devel- Project mgmt_merger build #901: SUCCESS in 6 min 49 sec: https://kci.pangea.pub/job/mgmt_merger/901/
[23:08] <valorie> gosh, just try to remove 32-bit, and out crawl the faithful users
[23:08] <valorie> let's see if they will *test*
[23:09] <valorie> ok, upgrading to artful
[23:15] -kubuntu-ci:#kubuntu-devel- Project zesty_unstable_ring-kde build #14: STILL FAILING in 7 min 51 sec: https://kci.pangea.pub/job/zesty_unstable_ring-kde/14/
[23:17] -kubuntu-ci:#kubuntu-devel- Project xenial_unstable_kdepim-runtime build #235: FAILURE in 9 min 45 sec: https://kci.pangea.pub/job/xenial_unstable_kdepim-runtime/235/
[23:18] -kubuntu-ci:#kubuntu-devel- Project xenial_unstable_ktorrent build #21: FAILURE in 10 min: https://kci.pangea.pub/job/xenial_unstable_ktorrent/21/
[23:19] -kubuntu-ci:#kubuntu-devel- Project xenial_unstable_discover build #254: STILL FAILING in 11 min: https://kci.pangea.pub/job/xenial_unstable_discover/254/
[23:23] -kubuntu-ci:#kubuntu-devel- Project zesty_unstable_kdepim-addons build #252: STILL FAILING in 15 min: https://kci.pangea.pub/job/zesty_unstable_kdepim-addons/252/
[23:29] -kubuntu-ci:#kubuntu-devel- Project artful_unstable_kdb build #54: STILL FAILING in 22 min: https://kci.pangea.pub/job/artful_unstable_kdb/54/
[23:38] <mwhudson> hiya, translate-toolkit is seeded in ubuntu but ftbfs at the moment, would there be anything especially terrifying about updating to the latest upstream release?
[23:38] <mwhudson> (assuming that actually builds :-p)
[23:38] <mwhudson> *seeded in kubuntu
[23:38] <mwhudson> (which it doesn't dammit)
[23:40] <tsimonq2> mwhudson: It should be fine as long as you do it on top of the current packaging in Kubuntu's Git repositories and give us a merge proposal when you're done. :)
[23:40] <tsimonq2> mwhudson: I mean, I'm not currently an active member of the team, but that's how it always has worked.
[23:41] <tsimonq2> mwhudson: Additionally, if it's visible at kci.pangea.pub, keep in mind that it has to be buildable on Xenial and Zesty as well.
[23:41] <mwhudson> tsimonq2: there's not actually any ubuntu delta currently
[23:41]  * mwhudson check debian's git
[23:41] <tsimonq2> mwhudson: Oh well then no problem, it won't be in our system much. I'd say it's safe to JFDI.
[23:41] <tsimonq2> mwhudson: But my answer is unofficial. :P
[23:43] -kubuntu-ci:#kubuntu-devel- Project artful_unstable_kde-cli-tools build #62: FAILURE in 10 sec: https://kci.pangea.pub/job/artful_unstable_kde-cli-tools/62/
[23:44] -kubuntu-ci:#kubuntu-devel- Project artful_stable_krdc build #53: FAILURE in 22 sec: https://kci.pangea.pub/job/artful_stable_krdc/53/
[23:44] -kubuntu-ci:#kubuntu-devel- Project zesty_stable_kdeedu-data build #65: FAILURE in 28 sec: https://kci.pangea.pub/job/zesty_stable_kdeedu-data/65/
[23:45] -kubuntu-ci:#kubuntu-devel- Project zesty_unstable_kasync build #84: FAILURE in 50 sec: https://kci.pangea.pub/job/zesty_unstable_kasync/84/
[23:45] -kubuntu-ci:#kubuntu-devel- Project zesty_stable_signon-kwallet-extension build #73: FAILURE in 50 sec: https://kci.pangea.pub/job/zesty_stable_signon-kwallet-extension/73/
[23:48] <ronnoc> clivejo: 0/
[23:48]  * clivejo waves
[23:49] -kubuntu-ci:#kubuntu-devel- Project artful_unstable_ring-kde build #14: STILL FAILING in 5 min 49 sec: https://kci.pangea.pub/job/artful_unstable_ring-kde/14/
[23:59] -kubuntu-ci:#kubuntu-devel- Yippee, build fixed!
[23:59] -kubuntu-ci:#kubuntu-devel- Project artful_unstable_cantor build #41: FIXED in 32 min: https://kci.pangea.pub/job/artful_unstable_cantor/41/
[23:59] -kubuntu-ci:#kubuntu-devel- Project artful_unstable_umbrello build #39: STILL UNSTABLE in 50 min: https://kci.pangea.pub/job/artful_unstable_umbrello/39/