[00:01] -kubuntu-ci:#kubuntu-devel- Project zesty_unstable_kpat build #58: FAILURE in 23 min: https://kci.pangea.pub/job/zesty_unstable_kpat/58/
[00:01] -kubuntu-ci:#kubuntu-devel- Project xenial_unstable_plasma-pa build #398: STILL UNSTABLE in 12 min: https://kci.pangea.pub/job/xenial_unstable_plasma-pa/398/
[00:01] -kubuntu-ci:#kubuntu-devel- Project xenial_unstable_ktp-common-internals build #297: STILL UNSTABLE in 23 min: https://kci.pangea.pub/job/xenial_unstable_ktp-common-internals/297/
[00:01] -kubuntu-ci:#kubuntu-devel- Project xenial_unstable_kio-extras build #357: STILL FAILING in 24 min: https://kci.pangea.pub/job/xenial_unstable_kio-extras/357/
[00:01] -kubuntu-ci:#kubuntu-devel- Yippee, build fixed!
[00:01] -kubuntu-ci:#kubuntu-devel- Project xenial_unstable_babe build #19: FIXED in 24 min: https://kci.pangea.pub/job/xenial_unstable_babe/19/
[00:01] -kubuntu-ci:#kubuntu-devel- Project xenial_unstable_kpat build #269: FAILURE in 23 min: https://kci.pangea.pub/job/xenial_unstable_kpat/269/
[00:05] <chatter29> hey guys
[00:05] <chatter29> allah is doing
[00:05] <chatter29> sun is not doing allah is doing
[00:05] <chatter29> to accept Islam say that i bear witness that there is no deity worthy of worship except Allah and Muhammad peace be upon him is his slave and messenger
[00:07] <krytarik> Bye.
[00:10] -kubuntu-ci:#kubuntu-devel- Project zesty_unstable_kalzium build #107: STILL UNSTABLE in 23 min: https://kci.pangea.pub/job/zesty_unstable_kalzium/107/
[00:10] -kubuntu-ci:#kubuntu-devel- Project xenial_unstable_kdb build #103: STILL UNSTABLE in 21 min: https://kci.pangea.pub/job/xenial_unstable_kdb/103/
[00:11] -kubuntu-ci:#kubuntu-devel- Project xenial_unstable_kproperty build #103: STILL UNSTABLE in 20 min: https://kci.pangea.pub/job/xenial_unstable_kproperty/103/
[00:15] <tsimonq2> UGH. 100% CPU usage by plasmashell...
[00:15]  * tsimonq2 purges KDE Plasma and installs a different DE for now...
[00:19] -kubuntu-ci:#kubuntu-devel- Project xenial_unstable_kube build #11: STILL FAILING in 8 min 52 sec: https://kci.pangea.pub/job/xenial_unstable_kube/11/
[00:20] -kubuntu-ci:#kubuntu-devel- Project zesty_unstable_kube build #18: STILL FAILING in 9 min 13 sec: https://kci.pangea.pub/job/zesty_unstable_kube/18/
[00:20] -kubuntu-ci:#kubuntu-devel- Project xenial_stable_krita build #23: STILL UNSTABLE in 1 hr 12 min: https://kci.pangea.pub/job/xenial_stable_krita/23/
[00:27] -kubuntu-ci:#kubuntu-devel- Project xenial_unstable_sink build #32: STILL FAILING in 4 min 56 sec: https://kci.pangea.pub/job/xenial_unstable_sink/32/
[00:30] -kubuntu-ci:#kubuntu-devel- Project zesty_stable_kpat build #6: STILL FAILING in 18 min: https://kci.pangea.pub/job/zesty_stable_kpat/6/
[00:31] -kubuntu-ci:#kubuntu-devel- Project xenial_unstable_kube build #12: STILL FAILING in 6 min 43 sec: https://kci.pangea.pub/job/xenial_unstable_kube/12/
[00:32] -kubuntu-ci:#kubuntu-devel- Project zesty_unstable_sink build #38: STILL FAILING in 9 min 25 sec: https://kci.pangea.pub/job/zesty_unstable_sink/38/
[00:32] -kubuntu-ci:#kubuntu-devel- Project zesty_unstable_kio-extras build #159: STILL FAILING in 21 min: https://kci.pangea.pub/job/zesty_unstable_kio-extras/159/
[00:33] -kubuntu-ci:#kubuntu-devel- Project xenial_unstable_kdeconnect-kde build #227: STILL UNSTABLE in 22 min: https://kci.pangea.pub/job/xenial_unstable_kdeconnect-kde/227/
[00:33] -kubuntu-ci:#kubuntu-devel- Project zesty_unstable_kdeconnect-kde build #133: STILL UNSTABLE in 31 min: https://kci.pangea.pub/job/zesty_unstable_kdeconnect-kde/133/
[00:33] -kubuntu-ci:#kubuntu-devel- Project zesty_unstable_ark build #154: STILL UNSTABLE in 31 min: https://kci.pangea.pub/job/zesty_unstable_ark/154/
[00:33] -kubuntu-ci:#kubuntu-devel- Project xenial_unstable_ark build #470: STILL UNSTABLE in 22 min: https://kci.pangea.pub/job/xenial_unstable_ark/470/
[00:33] -kubuntu-ci:#kubuntu-devel- Project xenial_unstable_kdiagram build #126: STILL UNSTABLE in 22 min: https://kci.pangea.pub/job/xenial_unstable_kdiagram/126/
[00:33] -kubuntu-ci:#kubuntu-devel- Project zesty_unstable_cantor build #134: STILL UNSTABLE in 34 min: https://kci.pangea.pub/job/zesty_unstable_cantor/134/
[00:38] -kubuntu-ci:#kubuntu-devel- Project xenial_unstable_sink build #33: STILL FAILING in 5 min 33 sec: https://kci.pangea.pub/job/xenial_unstable_sink/33/
[00:39] -kubuntu-ci:#kubuntu-devel- Project xenial_stable_kpat build #5: STILL FAILING in 17 min: https://kci.pangea.pub/job/xenial_stable_kpat/5/
[00:41] -kubuntu-ci:#kubuntu-devel- Project zesty_unstable_sink build #39: STILL FAILING in 3 min 34 sec: https://kci.pangea.pub/job/zesty_unstable_sink/39/
[00:42] -kubuntu-ci:#kubuntu-devel- Project xenial_unstable_akonadi-import-wizard build #125: STILL UNSTABLE in 21 min: https://kci.pangea.pub/job/xenial_unstable_akonadi-import-wizard/125/
[00:42] -kubuntu-ci:#kubuntu-devel- Project xenial_unstable_ktp-auth-handler build #332: STILL UNSTABLE in 19 min: https://kci.pangea.pub/job/xenial_unstable_ktp-auth-handler/332/
[00:42] -kubuntu-ci:#kubuntu-devel- Project xenial_unstable_kio-extras build #358: STILL FAILING in 19 min: https://kci.pangea.pub/job/xenial_unstable_kio-extras/358/
[00:43] -kubuntu-ci:#kubuntu-devel- Project zesty_unstable_kpat build #59: STILL FAILING in 20 min: https://kci.pangea.pub/job/zesty_unstable_kpat/59/
[00:54] -kubuntu-ci:#kubuntu-devel- Project zesty_unstable_akonadi-import-wizard build #117: STILL UNSTABLE in 32 min: https://kci.pangea.pub/job/zesty_unstable_akonadi-import-wizard/117/
[00:55] -kubuntu-ci:#kubuntu-devel- Project xenial_unstable_kpat build #270: STILL FAILING in 32 min: https://kci.pangea.pub/job/xenial_unstable_kpat/270/
[01:04] <mparillo> ahoneybun_: Only if your machine is slow enough (my little netbook sometimes or a VM on a heavily-loaded host) you will get the try / install option from the live ISO. I never cared for it anyway, as I frequently use a live ISO for things like online banking, and it is just one more useless click to use live, and the same number of clicks to install.
[01:08] -kubuntu-ci:#kubuntu-devel- Project zesty_unstable_kdiagram build #130: STILL UNSTABLE in 25 min: https://kci.pangea.pub/job/zesty_unstable_kdiagram/130/
[01:20] -kubuntu-ci:#kubuntu-devel- Project zesty_unstable_krita build #146: STILL UNSTABLE in 1 hr 19 min: https://kci.pangea.pub/job/zesty_unstable_krita/146/
[01:30] -kubuntu-ci:#kubuntu-devel- Project xenial_unstable_kscreenlocker build #340: STILL UNSTABLE in 21 min: https://kci.pangea.pub/job/xenial_unstable_kscreenlocker/340/
[01:40] -kubuntu-ci:#kubuntu-devel- Project xenial_unstable_krita build #120: STILL UNSTABLE in 1 hr 38 min: https://kci.pangea.pub/job/xenial_unstable_krita/120/
[01:47] -kubuntu-ci:#kubuntu-devel- Project zesty_unstable_ktexteditor build #124: STILL FAILING in 16 min: https://kci.pangea.pub/job/zesty_unstable_ktexteditor/124/
[02:04] <ahoneybun_> https://bugs.kde.org/show_bug.cgi?id=379022
[02:04] <ahoneybun_> \o/
[02:05] <ahoneybun_> please do confirm if you cn
[02:05] <ahoneybun_> *can
[02:13] -kubuntu-ci:#kubuntu-devel- Project xenial_unstable_ktexteditor build #303: STILL FAILING in 18 min: https://kci.pangea.pub/job/xenial_unstable_ktexteditor/303/
[02:14] -kubuntu-ci:#kubuntu-devel- Project zesty_unstable_ktexteditor build #125: STILL FAILING in 21 min: https://kci.pangea.pub/job/zesty_unstable_ktexteditor/125/
[02:17] <ahoneybun_> anyone know where systemsettings git is hosted?
[02:18] -kubuntu-ci:#kubuntu-devel- Project xenial_stable_kwin build #23: UNSTABLE in 3 hr 10 min: https://kci.pangea.pub/job/xenial_stable_kwin/23/
[02:40] -kubuntu-ci:#kubuntu-devel- Project xenial_stable_messagelib build #33: STILL UNSTABLE in 28 min: https://kci.pangea.pub/job/xenial_stable_messagelib/33/
[02:42] -kubuntu-ci:#kubuntu-devel- Project xenial_unstable_ktexteditor build #304: STILL FAILING in 23 min: https://kci.pangea.pub/job/xenial_unstable_ktexteditor/304/
[02:53] -kubuntu-ci:#kubuntu-devel- Project zesty_unstable_kitemviews build #146: STILL UNSTABLE in 23 min: https://kci.pangea.pub/job/zesty_unstable_kitemviews/146/
[02:53] -kubuntu-ci:#kubuntu-devel- Project zesty_unstable_kwidgetsaddons build #156: STILL UNSTABLE in 24 min: https://kci.pangea.pub/job/zesty_unstable_kwidgetsaddons/156/
[03:07] -kubuntu-ci:#kubuntu-devel- Project zesty_unstable_kcoreaddons build #127: STILL UNSTABLE in 14 min: https://kci.pangea.pub/job/zesty_unstable_kcoreaddons/127/
[03:07] -kubuntu-ci:#kubuntu-devel- Project zesty_unstable_kcompletion build #96: STILL UNSTABLE in 14 min: https://kci.pangea.pub/job/zesty_unstable_kcompletion/96/
[03:07] -kubuntu-ci:#kubuntu-devel- Project zesty_unstable_ki18n build #104: STILL UNSTABLE in 14 min: https://kci.pangea.pub/job/zesty_unstable_ki18n/104/
[03:07] -kubuntu-ci:#kubuntu-devel- Project zesty_unstable_kdbusaddons build #153: STILL UNSTABLE in 14 min: https://kci.pangea.pub/job/zesty_unstable_kdbusaddons/153/
[03:14] <ahoneybun_> thanks for the comment DarinMiller_
[03:20] -kubuntu-ci:#kubuntu-devel- Project zesty_unstable_kconfigwidgets build #110: STILL UNSTABLE in 12 min: https://kci.pangea.pub/job/zesty_unstable_kconfigwidgets/110/
[03:20] -kubuntu-ci:#kubuntu-devel- Project zesty_unstable_kjobwidgets build #147: STILL UNSTABLE in 12 min: https://kci.pangea.pub/job/zesty_unstable_kjobwidgets/147/
[03:49] -kubuntu-ci:#kubuntu-devel- Project xenial_unstable_kguiaddons build #422: STILL UNSTABLE in 7 min 49 sec: https://kci.pangea.pub/job/xenial_unstable_kguiaddons/422/
[03:49] -kubuntu-ci:#kubuntu-devel- Project xenial_unstable_kcodecs build #425: STILL UNSTABLE in 7 min 52 sec: https://kci.pangea.pub/job/xenial_unstable_kcodecs/425/
[03:49] -kubuntu-ci:#kubuntu-devel- Project xenial_unstable_kitemviews build #416: STILL UNSTABLE in 7 min 57 sec: https://kci.pangea.pub/job/xenial_unstable_kitemviews/416/
[03:55] -kubuntu-ci:#kubuntu-devel- Project xenial_unstable_kwidgetsaddons build #417: STILL UNSTABLE in 14 min: https://kci.pangea.pub/job/xenial_unstable_kwidgetsaddons/417/
[04:09] -kubuntu-ci:#kubuntu-devel- Project zesty_unstable_messagelib build #206: STILL UNSTABLE in 20 min: https://kci.pangea.pub/job/zesty_unstable_messagelib/206/
[04:09] -kubuntu-ci:#kubuntu-devel- Project xenial_unstable_kcompletion build #426: STILL UNSTABLE in 13 min: https://kci.pangea.pub/job/xenial_unstable_kcompletion/426/
[04:40] -kubuntu-ci:#kubuntu-devel- Project xenial_unstable_kconfig build #460: STILL UNSTABLE in 14 min: https://kci.pangea.pub/job/xenial_unstable_kconfig/460/
[04:40] -kubuntu-ci:#kubuntu-devel- Project xenial_unstable_ki18n build #444: STILL UNSTABLE in 14 min: https://kci.pangea.pub/job/xenial_unstable_ki18n/444/
[04:41] -kubuntu-ci:#kubuntu-devel- Project xenial_unstable_kdbusaddons build #449: STILL UNSTABLE in 15 min: https://kci.pangea.pub/job/xenial_unstable_kdbusaddons/449/
[05:57] -kubuntu-ci:#kubuntu-devel- Project xenial_unstable_kcoreaddons build #417: STILL UNSTABLE in 12 min: https://kci.pangea.pub/job/xenial_unstable_kcoreaddons/417/
[07:57] -kubuntu-ci:#kubuntu-devel- Project xenial_unstable_messagelib build #207: STILL UNSTABLE in 25 min: https://kci.pangea.pub/job/xenial_unstable_messagelib/207/
[08:14] <yofel> acheronUK: you *almost* got it right :P
[08:14] <yofel> you have to delete that failing line. # With sorting - tests the first and last key, it's now validating the "first" against 2 different releases, which will fail
[08:41] <acheronUK> yofel: ok. thanks. gotta run so can't 'fix' at the moment
[08:45] -kubuntu-ci:#kubuntu-devel- Project mgmt_docker » master build #1464: SUCCESS in 50 sec: https://kci.pangea.pub/job/mgmt_docker/label=master/1464/
[08:45] -kubuntu-ci:#kubuntu-devel- Project mgmt_docker » linode-01 build #1464: SUCCESS in 58 sec: https://kci.pangea.pub/job/mgmt_docker/label=linode-01/1464/
[08:47] -kubuntu-ci:#kubuntu-devel- Project mgmt_docker » swy-01 build #1464: SUCCESS in 2 min 41 sec: https://kci.pangea.pub/job/mgmt_docker/label=swy-01/1464/
[08:47] -kubuntu-ci:#kubuntu-devel- Project mgmt_docker » swy-02 build #1464: SUCCESS in 2 min 51 sec: https://kci.pangea.pub/job/mgmt_docker/label=swy-02/1464/
[11:02] <BluesKaj> Howdy folks
[11:11] <clivejo> my internet is so unstable today again
[11:11] <clivejo> only for the BNC I'd be like a yoyo in here
[11:15] <clivejo> I give up
[11:16] <clivejo> can't even keep open an SSH, dput or wget connection
[11:17] <yofel> o.O
[11:18] <clivejo> apparently Jon was able to get flatbuffers to build - https://packaging.neon.kde.org/neon-packaging/flatbuffers.git/log/?h=Neon/unstable
[11:18] <clivejo> I tried 1.3.0 and failed
[11:19] <clivejo> and trying 1.6 but can't even manage to grab the source without timeouts
[11:21]  * clivejo locks computer and storms off
[12:17] <acheronUK> clivejo: yes, coincidently I was looking at the arch flatbuffers pkgbuild last night for v 1.6, and that suggested to me that it might now build. I may have a look if I have the time
[14:45] -kubuntu-ci:#kubuntu-devel- Project mgmt_docker » master build #1465: SUCCESS in 50 sec: https://kci.pangea.pub/job/mgmt_docker/label=master/1465/
[14:46] -kubuntu-ci:#kubuntu-devel- Project mgmt_docker » linode-01 build #1465: SUCCESS in 59 sec: https://kci.pangea.pub/job/mgmt_docker/label=linode-01/1465/
[14:47] -kubuntu-ci:#kubuntu-devel- Project mgmt_docker » swy-01 build #1465: SUCCESS in 2 min 30 sec: https://kci.pangea.pub/job/mgmt_docker/label=swy-01/1465/
[14:47] -kubuntu-ci:#kubuntu-devel- Project mgmt_docker » swy-02 build #1465: SUCCESS in 2 min 48 sec: https://kci.pangea.pub/job/mgmt_docker/label=swy-02/1465/
 I think I have a working packaged KA
 I could use it to do a test rebuild
 So we can update the weegie stuff tomorrow
[17:51] <pedahzur> Quick question: Will 16.12.3 be packaged for packaged for Xenial (16.04)?
 @pedahzur, Yes.
 Wait.
 Maybe?
 @acheronuk?
 @Santa, Mind if I peer-review?
 Sure, please check the conversation I had with yofel @ kubuntu-devel
 OK.
 The thread about op fir tree
 You have there links to the work in progress
 Santa: A solution to make sure it breaks very little or not at all is to implement some automated testing.
 Python has a module for unit testing that's very useful.
 Most important things in ka cannot be unit tested properly
 But I think that if you spend the time to work on that, it will DRASTICALLY reduce the amount of problems
[18:01] <pedahzur> tsimonq2: OK. I saw the announcement about the "oops, packages got in too late" on https://www.kubuntu.org/news/kde-pim-update-for-zesty-available-for-testers/ Just wondered if those packages were coming for Xenial too.
[18:01]  * pedahzur is hoping for some KMail/Akonadi fixes. :)
 @Santa, Example?
 @tsimonq2, How do you fake a new kde release?
[18:02] <pedahzur> tsimonq2: Left left, run right.
 To test that everything works when doing new releases
 + how do you unit test kubuntu-retry-builds?
 Or the iron hand?
[18:03] <clivejo> Santa, I know you are against using master branch for dev, but I don't understand your reasoning, would you mind explaining?
 @clivejo, This is not related to KA, correct?
[18:04] <clivejo> well yes and no
 You mean using master instead of kubuntu_xx_archive. Right?
[18:05] <clivejo> basically the reason our workflow never made use of the master branch was due to us sharing packaging with Debian
[18:06] <pedahzur> tsimonq2: *look left. :(
[18:06] <clivejo> as we no longer share the repo, logically it makes sense to use master for -dev
 "logically"
 @Santa, Setting up a mock server and generating files that look exactly like what you would find in a KDE release. Easy as pie.
[18:06] <clivejo> yes, and the archive branch would then always be in sync with what is in the archive
 @Santa, You generate a fake PPA, "upload" some packages to it, then use that to retry the builds. A little bit tricky but you can do it.
[18:08] <clivejo> well, in Debian the master branch is WIP branch, also in KDE
 @Santa, What's iron hand?
 @tsimonq2, It's more complicated that that
 @Santa, How?
 Sure there's a lot of semantics but it seems doable to me.
[18:09] <clivejo> @tsimonq2 https://phabricator.kde.org/w/kubuntu/black-operations/
 Ok let me go to the laptop cause you are firing so many questions
[18:10] <santa_> ok, good evening everyone
[18:10]  * clivejo tips hat
 You do iron hand by generating a PPA with packages showcasing the different functions of the tool.
 Also doable. Also tricky. :P
[18:11]  * mamarley attempts to tip hat, but isn't wearing a hat.
[18:11]  * mamarley throws a NullPointerException.
 So santa_, it's certainly doable.
[18:13] <santa_> if you have the time to do all the hackish things needed go ahead once we get the op fir tree finished
[18:13] <santa_> because when we are done if you need to change something you will be able to do it safely in the master branch without the risk of interrupting packaging work
[18:14] <santa_> in any case unit testing is not the solution to all the problems of the world
[18:15] <santa_> sometimes it helps you to solve a problem, sometimes doing the unit testing is a problem by itself
[18:15] <clivejo> I propose alcohol as the solution
 Well what I'm saying is, once we have automated QA, we only have to have one branch, because we know it always works.
[18:16] <santa_> I don't think so
 I absolutely think so. The tests will tell us that it works at all times.
[18:16] <santa_> NOPE. but in case you are wondering any patch providing unit tests is welcomed
[18:17] <santa_> actually any patch is welcomed
 I can do that, maybe once you've determined which files we are still using.
[18:18] <santa_> anything not in attic/
 But I strongly believe that unit tests can be written and we can ensure it's working at all times.
 And I'm happy to prove you wrong if you want me to...
[18:21] <santa_> in a world of unicorns butterflies and rainbows unit testing makes sure that everything is working perfectly all times
[18:21] <santa_> in the real world it helps you to reduce a bit the number of problems
 Sure it does. So let's implement it.
[18:24] <santa_> feel free
[18:24] <santa_> clivejo: so going back to the master branch issue
[18:25] <clivejo> santa_: its not an issue, just trying to understand your objection to us using it in LP
[18:25] <santa_> so lets start from the begining
[18:26] <santa_> first of all: do we all understand that merging a branch A into a branch B doesn't mean that A and B have the same content?
[18:28] <santa_> do we?
[18:29] <santa_> clivejo: ↑
[18:29] <clivejo> sorry, yes
[18:30] <santa_> ok
[18:31] <santa_> now, the second thing, you would like to get kubuntu_xx_archive allways tracking the contents of the archive, and a different branch for devel. is that correct?
[18:32] <clivejo> santa_: yes, and maybe even a tool checking that is the case
[18:33] <santa_> we already have a tool to check the contents of the archive, but allright, you have a point
[18:33] <santa_> so lets say we want a different branch for development
[18:34] <clivejo> santa_: I was thinking more at KCI level, when it does the mergers
[18:34] <clivejo> but that is a wishlist thing
[18:34] <santa_> ok, ok
[18:35] <santa_> that's interesting. ayway. let's say we start to use a different branch
[18:35] <santa_> to start, we need to have the same content in it than, in this case, kubuntu_zesty_archive, right?
[18:36] <clivejo> yes, at the beginning of last cycle I asked Simon to look into making master == yakkety_archive
[18:37] <clivejo> unfortunately, despite me saying not to actually run anything, he did
[18:37] <santa_> np, shit happens
[18:37] <wxl> !language | @santa_
[18:37] <wxl> :)
[18:37] <clivejo> so the whole task was put on hold
[18:38] <santa_> correct
[18:38] <clivejo> but I could never understand your objections to it
[18:39] <clivejo> and you're are smart guy, you obviously have your reasons, I just wondered what they are
[18:39] <santa_> ... so the most important problem is having in the devel branch the same contents of _archive
[18:39] <clivejo> well initially yes
[18:39] <santa_> therefore doing a merge into master of _archive is just plainly wrong
[18:39] <clivejo> then all of our staging WIP would happen in master
[18:41] <santa_> so we need something realiable to have the same contents in both branches whenever we start to use that possible workflow
[18:41] <clivejo> I know, that's why I was so upset when Simon did it
[18:42] <clivejo> the task was purely theoretical
[18:42] <santa_> nah, not a big deal even if wrong, things can be changed/fixed
[18:42] <santa_> so given that merging is a no-go...
[18:43] <clivejo> so its not the idea of using master for dev that you have issue with, more how master is setup initially?
[18:43] <santa_> yes and no, let me go on
[18:43] <santa_> here's the 100% reliable way to make sure that 2 branches have exactly the same contents:
[18:44] <santa_> making sure they both point at the same commit!
[18:44] <clivejo> I actually have never taken the time since to look into it
[18:44] <clivejo> so I'm very interested in learning
[18:45] <santa_> ok
[18:46] <santa_> so the obvious thing to do, in my opinion, is creating a new branch for that
[18:46] <santa_> because this way, you can create the branch on top of kubuntu_xx_archive
[18:47] <santa_> and everything is fun & games, no headaches wondering if the branch has the proper contents or not
[18:49] <santa_> so that's my 1st and most important objection regarding using master for development. my point is having an easier and better solution, why we should go for the complicated path?
[18:50] <clivejo> I guess it's like tradition that master tends to be the main development branch
[18:51] <clivejo> then having the archive branches sprouting off that in a "visual" context
[18:53] <santa_> I think the price to pay for the eye-candy of using master is too high
[18:54] <santa_> the 2nd and not so important objection is that using the same branch names than debian makes everything more confusing and counter intuitive
[18:54] <clivejo> and when you do a git clone the default is master
[18:54] <clivejo> at the moment we might as well not even have a master branch
[18:55] <santa_> it's true we can access the branch names trough name_of_the_origin/name_of_the_branch
[18:56] <clivejo> its just a thing that if we intend to do it, needs to be done now, before AA development starts
[18:56] <clivejo> in my head this is the ideal time to make sure master == zesty_archive
[18:58] <santa_> still you need a way to make sure the contents are the same
[18:58] <santa_> I'm open to ideas from other people in that regard btw
[18:58] <santa_> and we have other question
[18:59] <clivejo> yes, that was the question was raised last time
[18:59] <santa_> well, actually I have
[18:59] <santa_> what about the _backports branches?
[19:00] <clivejo> but we need everyone onboard and have people working on different areas as KCI, KA and other tools will nned updating to reflect the changes
[19:01] <clivejo> and set aside a period of time that everyone knows whats happening, when and how
[19:01] <santa_> KA is not going to be a problem
[19:01] <clivejo> you mentioned before about your tooling to do debian merges
[19:01] <clivejo> would it have issues?
[19:02] <santa_> no
[19:02] <santa_> it's using origin/master
[19:02] <clivejo> BTW what do you mean about the _backports branch?
[19:02] <santa_> but that tricked me when I was writing the tooling
[19:03] <santa_> which by the way it's still a bit unmature so I will need to re-check and fix it a bit before we use it for artful
 @santa_, Yofel said to create kubuntu_stage branches
[19:03] <santa_> ↑ THIS
[19:03] <santa_> regarding the _backports branches
[19:04] <santa_> what they would be suposed to track
[19:04] <clivejo> talking about Debian merge tool, would it be possible to also do Neon?
[19:04] <santa_> yes
 Trying to use master was discarded afair
[19:05] <clivejo> well it was discarded for two reasons 1) mainly because Simon went ahead and committed everything and then 2) santa strongly objected to the idea so it was dropped
[19:06] <santa_> the thing was on hold actually
[19:06] <clivejo> but from talking about it now, its not the idea, its the implementation that is the problem
[19:06] <clivejo> which was the task Simon was to research
[19:07] <clivejo> how to make sure master == _zesty_archive
[19:07] <santa_> the idea itself of having a devel branch different than the _archive branch isn't bad
 3) as we can create whatver branches we like, trying to make master do the job semed pointless
[19:10] <santa_> ack
[19:10] <clivejo> santa_: would a physicial file cp work?
[19:11] <santa_> what about file removals?
[19:11] <clivejo> ie cp the folder out to ../ change the branch, wipe the folder and cp the contents back from ../ ?
[19:12] <BluesKaj> .0
[19:13] <clivejo> there is bound to be a git command that does this, no?
[19:13] <santa_> maybe, but we will break things like git blame
[19:14] <santa_> inspecting the history, if we have to, would be pain I think
[19:16] <santa_> anyway
[19:17] <santa_> I still have a gap in my understading of what you want
[19:17] <santa_> which is
[19:17] <santa_> for instance kubuntu_xenial_backports, what would be suposed to track?
[19:19] <santa_> xenial staging?
[19:19] <santa_> something else?
[19:20] <santa_> I'm asking because an alternative approach could be using kubuntu_xx_staging branches
[19:21] <santa_> so if we just use master....
[19:21] <clivejo> it was to track what we have released to backports
[19:22] <santa_> so what if we have something in backports staging ppa?
[19:22] <santa_> which branch we would use for that?
[19:24] <clivejo> staging
[19:24] <clivejo> sorry _backports branch
[19:24] <clivejo> so now zesty been released
[19:24] <clivejo> the archive version of PIM is 16.04
[19:25] <clivejo> but we intend to release 16.12 to backports
[19:25] -kubuntu-ci:#kubuntu-devel- Project zesty_unstable_sink build #40: STILL FAILING in 4 min 35 sec: https://kci.pangea.pub/job/zesty_unstable_sink/40/
[19:25] <clivejo> so need _backports branch for those
[19:25] -kubuntu-ci:#kubuntu-devel- Project xenial_unstable_sink build #34: STILL FAILING in 4 min 41 sec: https://kci.pangea.pub/job/xenial_unstable_sink/34/
[19:25] <santa_> yes
[19:27] <clivejo> in theory if it took a while to get the new devel name, we could still continue to work if we have a devel branch
[19:27] <blaze> https://youtu.be/Bo8Wr3W2vA0
[19:28] <santa_> clivejo: back in the days to solve that we would be using the _backports branch
[19:29] <clivejo> but we need to consider KCI as well
[19:29] <clivejo> and its merges
[19:29] <santa_> clivejo: for instance if we wanted to keep working on frameworks packaging we would be using the kubuntu_zesty_backports branch
[19:30] <santa_> (which does't exist yet, but we would create it on top of _zesty_archive)
[19:30] <santa_> what's the deal with the KCI in this case
[19:30] <santa_> does it need any adjustment?
[19:30] <clivejo> KCI doesnt like the new name
[19:30] <clivejo> need to look at that
[19:31] <santa_> artful
[19:31] <clivejo> yes, it doesnt see that as the next in the series!
[19:31] <clivejo> acheronUK: did you get anywhere with that?
[19:31] <acheronUK> clivejo: read Phil's comments from this morning
[19:32] <santa_> using _zesty_backports wouldn't be a problem, or am I missing something?
[19:32] <clivejo> I don't have any comments :(
[19:32] <santa_> (it's just a heorical question, just curiuous)
[19:32] <santa_> * curious
[19:32] <clivejo> let me pull up -devel channel log
[19:32] <acheronUK> [09:14] <yofel> acheronUK: you *almost* got it right :P
[19:32] <acheronUK> [09:14] <yofel> you have to delete that failing line. # With sorting - tests the first and last key, it's now validating the "first" against 2 different releases, which will fail
[19:33] <acheronUK> clivejo: just seeing if that works!
[19:34] -kubuntu-ci:#kubuntu-devel- Project mgmt_tooling build #116: STILL UNSTABLE in 5 min 15 sec: https://kci.pangea.pub/job/mgmt_tooling/116/
[19:34] -kubuntu-ci:#kubuntu-devel- Rik Mills: add artful series - try 2
[19:34] <clivejo> LOL
[19:34] <clivejo> I appear to be missing huge chucks of today from my backlog :(
[19:34] -kubuntu-ci:#kubuntu-devel- Project mgmt_tooling_deploy » master build #44: SUCCESS in 24 sec: https://kci.pangea.pub/job/mgmt_tooling_deploy/label=master/44/
[19:34] <clivejo> stupid internet connection
[19:34] -kubuntu-ci:#kubuntu-devel- Project mgmt_tooling_deploy » linode-01 build #44: SUCCESS in 25 sec: https://kci.pangea.pub/job/mgmt_tooling_deploy/label=linode-01/44/
[19:34] <acheronUK> in amazing timing, I had just pushed that
[19:35] -kubuntu-ci:#kubuntu-devel- Project mgmt_tooling_deploy » swy-01 build #44: SUCCESS in 52 sec: https://kci.pangea.pub/job/mgmt_tooling_deploy/label=swy-01/44/
[19:35] -kubuntu-ci:#kubuntu-devel- Project mgmt_tooling_deploy » swy-02 build #44: SUCCESS in 1 min 0 sec: https://kci.pangea.pub/job/mgmt_tooling_deploy/label=swy-02/44/
[19:36] <clivejo> santa_: this was suggested on the last cycle and from recall there was a concern about doing that
[19:36] <clivejo> but I can't remember what the concern was :/
[19:37] <clivejo> I wonder does it trip up KCI merge cascade?
[19:39] <clivejo> acheronUK: do you remember ^
[19:39] <acheronUK> nope.
[19:39] -kubuntu-ci:#kubuntu-devel- Project mgmt_docker » master build #1466: SUCCESS in 4 min 13 sec: https://kci.pangea.pub/job/mgmt_docker/label=master/1466/
[19:40] <clivejo> oooo
[19:40] -kubuntu-ci:#kubuntu-devel- Project mgmt_docker » linode-01 build #1466: SUCCESS in 5 min 18 sec: https://kci.pangea.pub/job/mgmt_docker/label=linode-01/1466/
[19:41] <clivejo> artful is a go :)
[19:41] <clivejo> need to upload a key package to the PPA's
[19:41] <clivejo> ecm or something like that
[19:42] <acheronUK> I copied over the zesty one, plus a few others
[19:42] <clivejo> you have such a good memory!
[19:43] <acheronUK> only sometimes
[19:44] <clivejo> did you write this down from last time?
[19:44] <acheronUK> no
[19:45] <acheronUK> just doing what makes sense
[19:45] <santa_> btw
[19:46] <santa_> in case you aren't around tomorow,,,
[19:46] <clivejo> I probably won't be around :(
[19:46] <clivejo> although if it rains that could change
[19:46] -kubuntu-ci:#kubuntu-devel- Project mgmt_docker » swy-01 build #1466: SUCCESS in 11 min: https://kci.pangea.pub/job/mgmt_docker/label=swy-01/1466/
[19:47] <santa_> I would like to create a "Kubuntu Developers" ppa
[19:47] <santa_> put there kdt, ka and ka-deps packages
[19:47] <santa_> make some adjustments on weegie
[19:48] -kubuntu-ci:#kubuntu-devel- Project mgmt_docker » swy-02 build #1466: SUCCESS in 12 min: https://kci.pangea.pub/job/mgmt_docker/label=swy-02/1466/
[19:48] <santa_> and merge this into KA git master
[19:48] <santa_> https://code.launchpad.net/~panfaust/ka/+git/ka/+ref/fir-tree
[19:48] <clivejo> could they go in ninja's?
[19:48] <acheronUK> honestly can't say if I will make it or not
[19:49] <santa_> the reason why I didn't merge those KA changes is that it would break weegie's ppa-build-status setup
[19:49] <santa_> hence why I want to make adjustments in weegie
[19:49] <santa_> clivejo: what ppa?
[19:50] <clivejo> santa_: https://launchpad.net/~kubuntu-ninjas
[19:51] -kubuntu-ci:#kubuntu-devel- Project xenial_unstable_sink build #35: STILL FAILING in 3 min 37 sec: https://kci.pangea.pub/job/xenial_unstable_sink/35/
[19:51] <clivejo> would be nice to get some more ninjas trained up
[19:52] <santa_> you mean adding the new KA packaging ppa there? (not sure what you mean)
[19:54] <clivejo> yeah ninja will be the ones using the tools?
[19:54] <santa_> ok, but I don't have permissions to create ppas there either
[19:55] <clivejo> acheronUK: what do you think?
[19:55] <santa_> I would need someone else to create the ppa
[19:55] <santa_> I guess "Development Tools" would be a good name
[19:56] <clivejo> appears I dont either
[19:56] <clivejo> must be only KC
[19:56] <clivejo> thats a bit odd
[19:58] <acheronUK> historical I expect. Harold and JR are admins, so I guess it never mattered before
[19:58] <clivejo> where would you put them?
[19:59] <acheronUK> not sure there is much value in hiding them away
[19:59] <acheronUK> in fact somewhere easy for new people to get set up
[19:59] <ahoneybun_> what KC?
[20:01] <clivejo> aren't ninjas more -devel decisions?
[20:01] <ahoneybun_> yea I believe so
[20:01] <ahoneybun_> devs would know how far ninjas are and what they can do
[20:01] <clivejo> ahoneybun_:  https://launchpad.net/~kubuntu-ninjas
[20:01] <clivejo> Owner is KC
[20:02] <ahoneybun_> who do we want to have ownership>?
[20:03] <clivejo> I dunno, thought something like https://launchpad.net/~kubuntu-dev would be more suitable?
[20:04] <ahoneybun_> done
[20:07] <clivejo> santa_: https://launchpad.net/~kubuntu-ninjas/+archive/ubuntu/dev-tools
[20:08] <santa_> thank you very much!
[20:08] <clivejo> did I heard Phil talking about putting the tools in the archive?
[20:10] <santa_> he mentioned merging KA and KDT
[20:10] <santa_> which is something we could do at some point
[20:10] <santa_> but not tomorrow, that's sure
[20:11] -kubuntu-ci:#kubuntu-devel- Project zesty_unstable_sink build #41: STILL FAILING in 23 min: https://kci.pangea.pub/job/zesty_unstable_sink/41/
[20:13] <clivejo> santa_: where does KA gbp-ppa pick up the dist?
[20:14] <clivejo> I'm trying to run gbp-ppa -d artful
[20:14] <santa_> I think the branch
[20:14] <santa_> you have it installed from git I presume?
[20:15] <santa_> or are you testing the package?
[20:15] <clivejo> I'm testing a package from Neon
[20:15] <clivejo> flatbuffers
[20:15] <santa_> I mean KA
[20:15] <santa_> you have it from git/master?
[20:15] <clivejo> yes, using gbp-ppa from git master
[20:16] <santa_> ah, ok
[20:16] <clivejo> https://paste.ubuntu.com/24428931/
[20:17] <santa_> lib/ubuntu_info.py must be updated
[20:17] <santa_> one of the things I wanted to do tomorrow
[20:18] <santa_> clivejo: feel free to edit that file and push to master I will merge that into the package
[20:22] <clivejo> pushed
[20:25] -kubuntu-ci:#kubuntu-devel- Project xenial_unstable_sink build #36: STILL FAILING in 4 min 1 sec: https://kci.pangea.pub/job/xenial_unstable_sink/36/
[20:25] <clivejo> oooo ecm for artful is building
[20:26] <clivejo> exciting!
[20:27] <clivejo> https://kci.pangea.pub/view/artful%20FIX/
[20:27] <clivejo> that is such a nice sight to see
[20:30] -kubuntu-ci:#kubuntu-devel- Project artful_unstable_sink build #1: FAILURE in 3 min 55 sec: https://kci.pangea.pub/job/artful_unstable_sink/1/
[20:30] <clivejo> santa_: are there any other places in KA that needs to be updated for artful?
[20:34] <acheronUK> still using 17.04 for the package version
[20:35] <acheronUK> but I guess that will fix when the artful base files etc get out of proposed
[20:35] -kubuntu-ci:#kubuntu-devel- Project xenial_unstable_sink build #37: STILL FAILING in 4 min 58 sec: https://kci.pangea.pub/job/xenial_unstable_sink/37/
[20:35] <acheronUK> as seems to use OS::VERSION_ID to decide that on an artful docker container?
[20:39] -kubuntu-ci:#kubuntu-devel- Project artful_unstable_sink build #2: STILL FAILING in 3 min 44 sec: https://kci.pangea.pub/job/artful_unstable_sink/2/
[20:51] -kubuntu-ci:#kubuntu-devel- Project artful_unstable_kguiaddons build #1: UNSTABLE in 11 min: https://kci.pangea.pub/job/artful_unstable_kguiaddons/1/
[20:51] -kubuntu-ci:#kubuntu-devel- Yippee, build fixed!
[20:52] -kubuntu-ci:#kubuntu-devel- Project zesty_unstable_sink build #42: FIXED in 30 min: https://kci.pangea.pub/job/zesty_unstable_sink/42/
[20:52] -kubuntu-ci:#kubuntu-devel- Project artful_unstable_kdbusaddons build #1: UNSTABLE in 12 min: https://kci.pangea.pub/job/artful_unstable_kdbusaddons/1/
[20:52] -kubuntu-ci:#kubuntu-devel- Project artful_unstable_ki18n build #1: UNSTABLE in 12 min: https://kci.pangea.pub/job/artful_unstable_ki18n/1/
[20:57] -kubuntu-ci:#kubuntu-devel- Project artful_unstable_kitemmodels build #1: UNSTABLE in 16 min: https://kci.pangea.pub/job/artful_unstable_kitemmodels/1/
[20:57] -kubuntu-ci:#kubuntu-devel- Project artful_unstable_kcoreaddons build #1: UNSTABLE in 18 min: https://kci.pangea.pub/job/artful_unstable_kcoreaddons/1/
[21:01] -kubuntu-ci:#kubuntu-devel- Project artful_unstable_kcodecs build #1: UNSTABLE in 11 min: https://kci.pangea.pub/job/artful_unstable_kcodecs/1/
[21:01] -kubuntu-ci:#kubuntu-devel- Project artful_unstable_kconfig build #1: UNSTABLE in 11 min: https://kci.pangea.pub/job/artful_unstable_kconfig/1/
[21:07] -kubuntu-ci:#kubuntu-devel- Project artful_unstable_kitemviews build #1: UNSTABLE in 14 min: https://kci.pangea.pub/job/artful_unstable_kitemviews/1/
[21:16] -kubuntu-ci:#kubuntu-devel- Project artful_unstable_kwidgetsaddons build #1: UNSTABLE in 25 min: https://kci.pangea.pub/job/artful_unstable_kwidgetsaddons/1/
[21:16] -kubuntu-ci:#kubuntu-devel- Project artful_unstable_kauth build #1: UNSTABLE in 18 min: https://kci.pangea.pub/job/artful_unstable_kauth/1/
[21:17] -kubuntu-ci:#kubuntu-devel- Project xenial_unstable_sink build #38: STILL FAILING in 4 min 33 sec: https://kci.pangea.pub/job/xenial_unstable_sink/38/
[21:18] -kubuntu-ci:#kubuntu-devel- Project artful_unstable_sink build #3: STILL FAILING in 5 min 42 sec: https://kci.pangea.pub/job/artful_unstable_sink/3/
[21:18] -kubuntu-ci:#kubuntu-devel- Project zesty_unstable_sink build #43: FAILURE in 5 min 44 sec: https://kci.pangea.pub/job/zesty_unstable_sink/43/
[21:28] <santa_> clivejo: iirc the default branch name but if we don't have kubuntu_artful_archive yet we shouldn't change it yet
[21:28] <santa_> imho
[21:29] <santa_> is there any other issue you are having?
[21:29] <clivejo> not that I can think of
[21:30] <clivejo> I'm currently trying to get kube to build
[21:30] <clivejo> https://paste.ubuntu.com/24429220/
[21:30] <clivejo> santa_: where would you put those /usr/bin files?
[21:32] <santa_> clivejo: do you have a link to the control file?
[21:32] <clivejo> https://git.launchpad.net/~kubuntu-packagers/kubuntu-packaging/+git/sink/tree/debian/control?h=kubuntu_unstable
[21:32] <clivejo> santa_: still working on it
[21:33] <clivejo> only just got flatbuffers working
[21:34] <clivejo> acheronUK: did you add the built on columc?
[21:35] <santa_> clivejo: libsink-bin; since the name won't change along with the SONAME
[21:35] <santa_> and in the symbols file, inject the dependency on the -bin
[21:35] <clivejo> should it be libsink0 ?
[21:36] <acheronUK> clivejo: no. it just seems to be a new default when creating a view
[21:36] <clivejo> ah, Ive copied them in the past
[21:36] -kubuntu-ci:#kubuntu-devel- Project artful_unstable_kwallet build #1: FAILURE in 6 min 50 sec: https://kci.pangea.pub/job/artful_unstable_kwallet/1/
[21:37] -kubuntu-ci:#kubuntu-devel- Project artful_unstable_ktextwidgets build #1: FAILURE in 5 min 12 sec: https://kci.pangea.pub/job/artful_unstable_ktextwidgets/1/
[21:37] <santa_> should it be libsink0 ? probably
[21:38] <santa_> clivejo: I would put the plugins in -bin too
[21:39] <santa_> + this one
[21:39] <santa_> ./usr/lib/x86_64-linux-gnu/liblibhawd.so
[21:39] <santa_> ↑ but this file name is a bit weird
[21:45] -kubuntu-ci:#kubuntu-devel- Project artful_unstable_sink build #5: STILL FAILING in 2 min 40 sec: https://kci.pangea.pub/job/artful_unstable_sink/5/
[21:46] -kubuntu-ci:#kubuntu-devel- Project artful_unstable_ktextwidgets build #2: STILL FAILING in 4 min 41 sec: https://kci.pangea.pub/job/artful_unstable_ktextwidgets/2/
[21:47] -kubuntu-ci:#kubuntu-devel- Project xenial_unstable_sink build #40: STILL FAILING in 4 min 29 sec: https://kci.pangea.pub/job/xenial_unstable_sink/40/
[21:47] -kubuntu-ci:#kubuntu-devel- Project artful_unstable_kwallet build #2: STILL FAILING in 6 min 4 sec: https://kci.pangea.pub/job/artful_unstable_kwallet/2/
[21:48] -kubuntu-ci:#kubuntu-devel- Project xenial_unstable_kube build #13: STILL FAILING in 2 min 38 sec: https://kci.pangea.pub/job/xenial_unstable_kube/13/
[21:49] -kubuntu-ci:#kubuntu-devel- Project zesty_unstable_kube build #19: STILL FAILING in 3 min 35 sec: https://kci.pangea.pub/job/zesty_unstable_kube/19/
[21:50] -kubuntu-ci:#kubuntu-devel- Yippee, build fixed!
[21:50] -kubuntu-ci:#kubuntu-devel- Project zesty_unstable_sink build #44: FIXED in 26 min: https://kci.pangea.pub/job/zesty_unstable_sink/44/
[21:54] -kubuntu-ci:#kubuntu-devel- Project artful_unstable_sink build #6: STILL FAILING in 4 min 7 sec: https://kci.pangea.pub/job/artful_unstable_sink/6/
[21:56] -kubuntu-ci:#kubuntu-devel- Project xenial_unstable_kube build #14: STILL FAILING in 3 min 29 sec: https://kci.pangea.pub/job/xenial_unstable_kube/14/
[21:56] -kubuntu-ci:#kubuntu-devel- Project zesty_unstable_kube build #20: STILL FAILING in 4 min 34 sec: https://kci.pangea.pub/job/zesty_unstable_kube/20/
[21:57] -kubuntu-ci:#kubuntu-devel- Project xenial_unstable_sink build #41: STILL FAILING in 4 min 39 sec: https://kci.pangea.pub/job/xenial_unstable_sink/41/
[21:58] <clivejo> santa_: would you know why this is failing - https://launchpadlibrarian.net/316507476/buildlog_ubuntu-xenial-amd64.sink_0.1.0+p16.04+git20170421.2143-0_BUILDING.txt.gz
[21:58] -kubuntu-ci:#kubuntu-devel- Project artful_unstable_kconfigwidgets build #1: UNSTABLE in 10 min: https://kci.pangea.pub/job/artful_unstable_kconfigwidgets/1/
[21:58] <clivejo> it fails on xenial, but builds ok on zesty :/
[21:59] <clivejo> /<<BUILDDIR>>/sink-0.1.0+p16.04+git20170421.2143/common/notifier.cpp: In lambda function:
[21:59] <clivejo> /<<BUILDDIR>>/sink-0.1.0+p16.04+git20170421.2143/common/notifier.cpp:43:40: error: use of ‘handler’ before deduction of ‘auto’
[21:59] <clivejo>              for (const auto &handler : handler) {
[21:59] <clivejo>                                         ^
[22:00] <santa_> I guess it must be an issue with the older versions of GCC
[22:01] <santa_> I would need to inspect the c++ code with time, because I don't understand right now that line
[22:01] -kubuntu-ci:#kubuntu-devel- Project artful_unstable_kiconthemes build #1: FAILURE in 3 min 42 sec: https://kci.pangea.pub/job/artful_unstable_kiconthemes/1/
[22:02] <clivejo> santa_: https://cgit.kde.org/sink.git/tree/common/notifier.cpp#n43
[22:17] -kubuntu-ci:#kubuntu-devel- Yippee, build fixed!
[22:17] -kubuntu-ci:#kubuntu-devel- Project artful_unstable_kiconthemes build #2: FIXED in 10 min: https://kci.pangea.pub/job/artful_unstable_kiconthemes/2/
[22:19] <santa_> clivejo: hmm, I don't know I never used that connect style in my c++ code (which is new in Qt 5)
[22:19] <santa_> feel free to ask in #kde-devel
[22:20] <clivejo> Jon seems to be on the case, so Ill leave it to him
[22:20] <clivejo> getting too tired now myself
[22:22] -kubuntu-ci:#kubuntu-devel- Project artful_unstable_kxmlgui build #1: FAILURE in 4 min 46 sec: https://kci.pangea.pub/job/artful_unstable_kxmlgui/1/
[22:22]  * acheronUK wonders whether to just click 'build everything"
[22:22] <acheronUK> and deal with the mess in the morning :P
[22:31] -kubuntu-ci:#kubuntu-devel- Yippee, build fixed!
[22:31] -kubuntu-ci:#kubuntu-devel- Project artful_unstable_kwallet build #3: FIXED in 12 min: https://kci.pangea.pub/job/artful_unstable_kwallet/3/
[22:32] -kubuntu-ci:#kubuntu-devel- Project artful_unstable_konquest build #1: FAILURE in 7 min 1 sec: https://kci.pangea.pub/job/artful_unstable_konquest/1/
[22:34] -kubuntu-ci:#kubuntu-devel- Project artful_unstable_telepathy-morse build #1: FAILURE in 8 min 25 sec: https://kci.pangea.pub/job/artful_unstable_telepathy-morse/1/
[22:35] -kubuntu-ci:#kubuntu-devel- Project artful_unstable_kxmlgui build #2: STILL FAILING in 7 min 37 sec: https://kci.pangea.pub/job/artful_unstable_kxmlgui/2/
[22:35] <tsimonq2> acheronUK: Do it :P
[22:35] <acheronUK> tsimonq2: I did!
[22:36] <clivejo> oi!
[22:36] <clivejo> stop trying to kill it
[22:37] <tsimonq2> acheronUK: :D :D :D
[22:37]  * tsimonq2 joins acheronUK in stabbing KCI
[22:37] -kubuntu-ci:#kubuntu-devel- Project artful_unstable_kajongg build #1: FAILURE in 11 min: https://kci.pangea.pub/job/artful_unstable_kajongg/1/
[22:37] <clivejo> don't make me raise my voice!
[22:38]  * tsimonq2 continues :P
[22:39] -kubuntu-ci:#kubuntu-devel- Project artful_unstable_kigo build #1: FAILURE in 13 min: https://kci.pangea.pub/job/artful_unstable_kigo/1/
[22:41] -kubuntu-ci:#kubuntu-devel- Project artful_unstable_libkolabxml build #1: FAILURE in 15 min: https://kci.pangea.pub/job/artful_unstable_libkolabxml/1/
[22:42] -kubuntu-ci:#kubuntu-devel- Project artful_stable_libkolabxml build #1: FAILURE in 41 sec: https://kci.pangea.pub/job/artful_stable_libkolabxml/1/
[22:42] -kubuntu-ci:#kubuntu-devel- Project artful_unstable_kjobwidgets build #1: UNSTABLE in 16 min: https://kci.pangea.pub/job/artful_unstable_kjobwidgets/1/
[22:42] -kubuntu-ci:#kubuntu-devel- Project artful_stable_kajongg build #1: FAILURE in 5 min 48 sec: https://kci.pangea.pub/job/artful_stable_kajongg/1/
[22:45] -kubuntu-ci:#kubuntu-devel- Project artful_unstable_telepathy-morse build #2: STILL FAILING in 3 min 52 sec: https://kci.pangea.pub/job/artful_unstable_telepathy-morse/2/
[22:46] -kubuntu-ci:#kubuntu-devel- Project artful_unstable_kbookmarks build #1: FAILURE in 4 min 45 sec: https://kci.pangea.pub/job/artful_unstable_kbookmarks/1/
[22:46] -kubuntu-ci:#kubuntu-devel- Project artful_unstable_konquest build #2: STILL FAILING in 4 min 53 sec: https://kci.pangea.pub/job/artful_unstable_konquest/2/
[22:47] -kubuntu-ci:#kubuntu-devel- Project artful_stable_libkolabxml build #2: STILL FAILING in 31 sec: https://kci.pangea.pub/job/artful_stable_libkolabxml/2/
[22:47] -kubuntu-ci:#kubuntu-devel- Project artful_unstable_kitemmodels build #2: STILL UNSTABLE in 22 min: https://kci.pangea.pub/job/artful_unstable_kitemmodels/2/
[22:47] -kubuntu-ci:#kubuntu-devel- Project artful_unstable_kajongg build #2: STILL FAILING in 5 min 38 sec: https://kci.pangea.pub/job/artful_unstable_kajongg/2/
[22:48] -kubuntu-ci:#kubuntu-devel- Project artful_unstable_kproperty build #1: UNSTABLE in 22 min: https://kci.pangea.pub/job/artful_unstable_kproperty/1/
[22:48] -kubuntu-ci:#kubuntu-devel- Project artful_unstable_kdb build #1: UNSTABLE in 22 min: https://kci.pangea.pub/job/artful_unstable_kdb/1/
[22:50] -kubuntu-ci:#kubuntu-devel- Project artful_unstable_kigo build #2: STILL FAILING in 5 min 43 sec: https://kci.pangea.pub/job/artful_unstable_kigo/2/
[22:53] -kubuntu-ci:#kubuntu-devel- Project artful_stable_kajongg build #2: STILL FAILING in 5 min 40 sec: https://kci.pangea.pub/job/artful_stable_kajongg/2/
[22:54] -kubuntu-ci:#kubuntu-devel- Project artful_unstable_libkolabxml build #2: STILL FAILING in 7 min 42 sec: https://kci.pangea.pub/job/artful_unstable_libkolabxml/2/
[22:54] -kubuntu-ci:#kubuntu-devel- Project artful_unstable_kdiagram build #1: UNSTABLE in 28 min: https://kci.pangea.pub/job/artful_unstable_kdiagram/1/
[22:57] -kubuntu-ci:#kubuntu-devel- Project artful_unstable_kbookmarks build #2: STILL FAILING in 5 min 46 sec: https://kci.pangea.pub/job/artful_unstable_kbookmarks/2/
[23:00] -kubuntu-ci:#kubuntu-devel- Project artful_stable_kopete build #1: UNSTABLE in 27 min: https://kci.pangea.pub/job/artful_stable_kopete/1/
[23:01] -kubuntu-ci:#kubuntu-devel- Project artful_unstable_kopete build #1: UNSTABLE in 35 min: https://kci.pangea.pub/job/artful_unstable_kopete/1/
[23:02] -kubuntu-ci:#kubuntu-devel- Project artful_unstable_kio build #1: FAILURE in 5 min 24 sec: https://kci.pangea.pub/job/artful_unstable_kio/1/
[23:07] -kubuntu-ci:#kubuntu-devel- Project artful_unstable_telepathy-qt build #1: FAILURE in 21 min: https://kci.pangea.pub/job/artful_unstable_telepathy-qt/1/
[23:14] -kubuntu-ci:#kubuntu-devel- Project artful_unstable_kio build #2: STILL FAILING in 6 min 33 sec: https://kci.pangea.pub/job/artful_unstable_kio/2/
[23:20] -kubuntu-ci:#kubuntu-devel- Project artful_unstable_kxmlrpcclient build #1: FAILURE in 6 min 29 sec: https://kci.pangea.pub/job/artful_unstable_kxmlrpcclient/1/
[23:21] -kubuntu-ci:#kubuntu-devel- Project artful_unstable_syndication build #1: FAILURE in 7 min 28 sec: https://kci.pangea.pub/job/artful_unstable_syndication/1/
[23:21] -kubuntu-ci:#kubuntu-devel- Project artful_unstable_kinit build #1: FAILURE in 7 min 30 sec: https://kci.pangea.pub/job/artful_unstable_kinit/1/
[23:21] -kubuntu-ci:#kubuntu-devel- Project artful_unstable_kdav build #1: FAILURE in 7 min 36 sec: https://kci.pangea.pub/job/artful_unstable_kdav/1/
[23:22] -kubuntu-ci:#kubuntu-devel- Project artful_unstable_knotifyconfig build #1: FAILURE in 8 min 50 sec: https://kci.pangea.pub/job/artful_unstable_knotifyconfig/1/
[23:23] -kubuntu-ci:#kubuntu-devel- Project artful_unstable_kdeclarative build #1: FAILURE in 9 min 46 sec: https://kci.pangea.pub/job/artful_unstable_kdeclarative/1/
[23:24] -kubuntu-ci:#kubuntu-devel- Project artful_unstable_knewstuff build #1: FAILURE in 10 min: https://kci.pangea.pub/job/artful_unstable_knewstuff/1/
[23:25] -kubuntu-ci:#kubuntu-devel- Project artful_unstable_kwave build #1: FAILURE in 11 min: https://kci.pangea.pub/job/artful_unstable_kwave/1/
[23:26] -kubuntu-ci:#kubuntu-devel- Project artful_unstable_baloo build #1: FAILURE in 12 min: https://kci.pangea.pub/job/artful_unstable_baloo/1/
[23:26] -kubuntu-ci:#kubuntu-devel- Project artful_unstable_kparts build #1: FAILURE in 12 min: https://kci.pangea.pub/job/artful_unstable_kparts/1/
[23:27] -kubuntu-ci:#kubuntu-devel- Project artful_stable_syndication build #1: FAILURE in 13 min: https://kci.pangea.pub/job/artful_stable_syndication/1/
[23:27] -kubuntu-ci:#kubuntu-devel- Project artful_stable_kdav build #1: FAILURE in 13 min: https://kci.pangea.pub/job/artful_stable_kdav/1/
[23:29] -kubuntu-ci:#kubuntu-devel- Project artful_unstable_telepathy-qt build #2: STILL FAILING in 16 min: https://kci.pangea.pub/job/artful_unstable_telepathy-qt/2/
[23:31] -kubuntu-ci:#kubuntu-devel- Project artful_unstable_syndication build #2: STILL FAILING in 4 min 35 sec: https://kci.pangea.pub/job/artful_unstable_syndication/2/
[23:31] -kubuntu-ci:#kubuntu-devel- Project artful_unstable_kdav build #2: STILL FAILING in 4 min 35 sec: https://kci.pangea.pub/job/artful_unstable_kdav/2/
[23:32] -kubuntu-ci:#kubuntu-devel- Project artful_unstable_knotifyconfig build #2: STILL FAILING in 4 min 14 sec: https://kci.pangea.pub/job/artful_unstable_knotifyconfig/2/
[23:32] -kubuntu-ci:#kubuntu-devel- Project artful_unstable_kxmlrpcclient build #2: STILL FAILING in 6 min 35 sec: https://kci.pangea.pub/job/artful_unstable_kxmlrpcclient/2/
[23:33] -kubuntu-ci:#kubuntu-devel- Project artful_unstable_knewstuff build #2: STILL FAILING in 3 min 39 sec: https://kci.pangea.pub/job/artful_unstable_knewstuff/2/
[23:33] -kubuntu-ci:#kubuntu-devel- Project artful_unstable_kinit build #2: STILL FAILING in 6 min 40 sec: https://kci.pangea.pub/job/artful_unstable_kinit/2/
[23:34] -kubuntu-ci:#kubuntu-devel- Project artful_unstable_kdeclarative build #2: STILL FAILING in 5 min 35 sec: https://kci.pangea.pub/job/artful_unstable_kdeclarative/2/
[23:36] -kubuntu-ci:#kubuntu-devel- Project artful_unstable_kparts build #2: STILL FAILING in 4 min 39 sec: https://kci.pangea.pub/job/artful_unstable_kparts/2/
[23:36] -kubuntu-ci:#kubuntu-devel- Project artful_stable_syndication build #2: STILL FAILING in 3 min 40 sec: https://kci.pangea.pub/job/artful_stable_syndication/2/
[23:37] -kubuntu-ci:#kubuntu-devel- Project artful_stable_grantleetheme build #1: FAILURE in 4 min 43 sec: https://kci.pangea.pub/job/artful_stable_grantleetheme/1/
[23:37] -kubuntu-ci:#kubuntu-devel- Project artful_unstable_grantleetheme build #1: FAILURE in 4 min 43 sec: https://kci.pangea.pub/job/artful_unstable_grantleetheme/1/
[23:38] -kubuntu-ci:#kubuntu-devel- Project artful_unstable_baloo build #2: STILL FAILING in 6 min 38 sec: https://kci.pangea.pub/job/artful_unstable_baloo/2/
[23:38] -kubuntu-ci:#kubuntu-devel- Project artful_stable_kdav build #2: STILL FAILING in 5 min 40 sec: https://kci.pangea.pub/job/artful_stable_kdav/2/
[23:38] -kubuntu-ci:#kubuntu-devel- Project artful_unstable_kwave build #2: STILL FAILING in 7 min 55 sec: https://kci.pangea.pub/job/artful_unstable_kwave/2/
[23:39] -kubuntu-ci:#kubuntu-devel- Project artful_unstable_kcmutils build #1: FAILURE in 4 min 54 sec: https://kci.pangea.pub/job/artful_unstable_kcmutils/1/
[23:39] -kubuntu-ci:#kubuntu-devel- Project artful_unstable_frameworkintegration build #1: FAILURE in 6 min 48 sec: https://kci.pangea.pub/job/artful_unstable_frameworkintegration/1/
[23:40] -kubuntu-ci:#kubuntu-devel- Project artful_unstable_kded build #1: FAILURE in 6 min 48 sec: https://kci.pangea.pub/job/artful_unstable_kded/1/
[23:41] -kubuntu-ci:#kubuntu-devel- Project artful_unstable_kmediaplayer build #1: FAILURE in 5 min 17 sec: https://kci.pangea.pub/job/artful_unstable_kmediaplayer/1/
[23:41] -kubuntu-ci:#kubuntu-devel- Project artful_stable_kontactinterface build #1: FAILURE in 5 min 18 sec: https://kci.pangea.pub/job/artful_stable_kontactinterface/1/
[23:42] -kubuntu-ci:#kubuntu-devel- Project artful_unstable_kdewebkit build #1: FAILURE in 6 min 19 sec: https://kci.pangea.pub/job/artful_unstable_kdewebkit/1/
[23:42] -kubuntu-ci:#kubuntu-devel- Project artful_unstable_ktexteditor build #1: FAILURE in 6 min 19 sec: https://kci.pangea.pub/job/artful_unstable_ktexteditor/1/
[23:42] -kubuntu-ci:#kubuntu-devel- Project artful_unstable_khtml build #1: FAILURE in 6 min 23 sec: https://kci.pangea.pub/job/artful_unstable_khtml/1/
[23:43] -kubuntu-ci:#kubuntu-devel- Project artful_unstable_kross build #1: FAILURE in 7 min 24 sec: https://kci.pangea.pub/job/artful_unstable_kross/1/
[23:43] -kubuntu-ci:#kubuntu-devel- Project artful_unstable_kontactinterface build #1: FAILURE in 7 min 24 sec: https://kci.pangea.pub/job/artful_unstable_kontactinterface/1/
[23:46] -kubuntu-ci:#kubuntu-devel- Project artful_unstable_grantleetheme build #2: STILL FAILING in 3 min 35 sec: https://kci.pangea.pub/job/artful_unstable_grantleetheme/2/
[23:46] -kubuntu-ci:#kubuntu-devel- Project artful_stable_grantleetheme build #2: STILL FAILING in 3 min 35 sec: https://kci.pangea.pub/job/artful_stable_grantleetheme/2/
[23:48] -kubuntu-ci:#kubuntu-devel- Project artful_unstable_kcmutils build #2: STILL FAILING in 3 min 34 sec: https://kci.pangea.pub/job/artful_unstable_kcmutils/2/
[23:49] -kubuntu-ci:#kubuntu-devel- Project artful_unstable_frameworkintegration build #2: STILL FAILING in 4 min 35 sec: https://kci.pangea.pub/job/artful_unstable_frameworkintegration/2/
[23:50] -kubuntu-ci:#kubuntu-devel- Project artful_unstable_kmediaplayer build #2: STILL FAILING in 3 min 34 sec: https://kci.pangea.pub/job/artful_unstable_kmediaplayer/2/
[23:50] -kubuntu-ci:#kubuntu-devel- Project artful_unstable_kded build #2: STILL FAILING in 5 min 41 sec: https://kci.pangea.pub/job/artful_unstable_kded/2/
[23:51] -kubuntu-ci:#kubuntu-devel- Project artful_stable_kontactinterface build #2: STILL FAILING in 4 min 35 sec: https://kci.pangea.pub/job/artful_stable_kontactinterface/2/
[23:51] -kubuntu-ci:#kubuntu-devel- Project artful_unstable_khtml build #2: STILL FAILING in 3 min 42 sec: https://kci.pangea.pub/job/artful_unstable_khtml/2/
[23:51] -kubuntu-ci:#kubuntu-devel- Project artful_unstable_kdewebkit build #2: STILL FAILING in 3 min 42 sec: https://kci.pangea.pub/job/artful_unstable_kdewebkit/2/
[23:53] -kubuntu-ci:#kubuntu-devel- Project artful_unstable_kactivities build #1: FAILURE in 5 min 8 sec: https://kci.pangea.pub/job/artful_unstable_kactivities/1/
[23:53] -kubuntu-ci:#kubuntu-devel- Project artful_unstable_kontactinterface build #2: STILL FAILING in 4 min 41 sec: https://kci.pangea.pub/job/artful_unstable_kontactinterface/2/
[23:53] -kubuntu-ci:#kubuntu-devel- Project artful_unstable_ktexteditor build #2: STILL FAILING in 5 min 42 sec: https://kci.pangea.pub/job/artful_unstable_ktexteditor/2/
[23:54] -kubuntu-ci:#kubuntu-devel- Project artful_unstable_kross build #2: STILL FAILING in 5 min 38 sec: https://kci.pangea.pub/job/artful_unstable_kross/2/
[23:54] -kubuntu-ci:#kubuntu-devel- Project artful_unstable_kstars build #1: FAILURE in 1 min 23 sec: https://kci.pangea.pub/job/artful_unstable_kstars/1/
[23:56] -kubuntu-ci:#kubuntu-devel- Project artful_unstable_syndication build #3: STILL FAILING in 4 min 45 sec: https://kci.pangea.pub/job/artful_unstable_syndication/3/
[23:56] -kubuntu-ci:#kubuntu-devel- Project artful_unstable_kxmlrpcclient build #3: STILL FAILING in 4 min 56 sec: https://kci.pangea.pub/job/artful_unstable_kxmlrpcclient/3/
[23:57] -kubuntu-ci:#kubuntu-devel- Project artful_unstable_kdesignerplugin build #1: FAILURE in 5 min 51 sec: https://kci.pangea.pub/job/artful_unstable_kdesignerplugin/1/
[23:57] -kubuntu-ci:#kubuntu-devel- Project artful_unstable_frameworkintegration build #3: STILL FAILING in 6 min 46 sec: https://kci.pangea.pub/job/artful_unstable_frameworkintegration/3/
[23:57] -kubuntu-ci:#kubuntu-devel- Project artful_stable_syndication build #3: STILL FAILING in 6 min 43 sec: https://kci.pangea.pub/job/artful_stable_syndication/3/
[23:58] -kubuntu-ci:#kubuntu-devel- Project artful_unstable_kded build #3: STILL FAILING in 5 min 36 sec: https://kci.pangea.pub/job/artful_unstable_kded/3/
[23:58] -kubuntu-ci:#kubuntu-devel- Project artful_stable_kajongg build #3: STILL FAILING in 6 min 37 sec: https://kci.pangea.pub/job/artful_stable_kajongg/3/
[23:59] -kubuntu-ci:#kubuntu-devel- Project artful_stable_kdev-php build #1: FAILURE in 5 min 51 sec: https://kci.pangea.pub/job/artful_stable_kdev-php/1/


[14:57] <frybye> Hi - I am using mainline newest kernel 3.15 - how can I use the automated bug reporting?
[14:57] <frybye> manual bug reporting is way way beyond me - I don't have the background knowledge to do that stuff..
[17:35] <belkinsa_> Hello, is the Remote Deskstop via Ubuntu SSO still possible?  If not, there is a bug in the desktop docs that I will report.