[00:48] -kubuntu-ci:#kubuntu-devel- Project bionic_stable_kwin build #312: STILL UNSTABLE in 1 hr 39 min: https://kci.pangea.pub/job/bionic_stable_kwin/312/
[04:52] -kubuntu-ci:#kubuntu-devel- Project mgmt_tooling_deploy » master build #153: SUCCESS in 25 sec: https://kci.pangea.pub/job/mgmt_tooling_deploy/label=master/153/
[04:52] -kubuntu-ci:#kubuntu-devel- Project mgmt_tooling_deploy » linode-01 build #153: SUCCESS in 28 sec: https://kci.pangea.pub/job/mgmt_tooling_deploy/label=linode-01/153/
[04:53] -kubuntu-ci:#kubuntu-devel- Project mgmt_tooling_deploy » swy-01 build #153: SUCCESS in 58 sec: https://kci.pangea.pub/job/mgmt_tooling_deploy/label=swy-01/153/
[05:32] -kubuntu-ci:#kubuntu-devel- Project mgmt_docker » linode-01 build #2787: SUCCESS in 1 min 1 sec: https://kci.pangea.pub/job/mgmt_docker/label=linode-01/2787/
[05:32] -kubuntu-ci:#kubuntu-devel- Project mgmt_docker » master build #2787: SUCCESS in 1 min 4 sec: https://kci.pangea.pub/job/mgmt_docker/label=master/2787/
[05:35] -kubuntu-ci:#kubuntu-devel- Project mgmt_docker » swy-01 build #2787: SUCCESS in 4 min 19 sec: https://kci.pangea.pub/job/mgmt_docker/label=swy-01/2787/
[09:45] -kubuntu-ci:#kubuntu-devel- Project mgmt_docker » linode-01 build #2788: SUCCESS in 53 sec: https://kci.pangea.pub/job/mgmt_docker/label=linode-01/2788/
[09:46] -kubuntu-ci:#kubuntu-devel- Project mgmt_docker » master build #2788: SUCCESS in 1 min 4 sec: https://kci.pangea.pub/job/mgmt_docker/label=master/2788/
[09:49] -kubuntu-ci:#kubuntu-devel- Project mgmt_docker » swy-01 build #2788: SUCCESS in 4 min 22 sec: https://kci.pangea.pub/job/mgmt_docker/label=swy-01/2788/
[12:06] <BluesKaj> Hi folks
[15:45] -kubuntu-ci:#kubuntu-devel- Project mgmt_docker » linode-01 build #2789: SUCCESS in 54 sec: https://kci.pangea.pub/job/mgmt_docker/label=linode-01/2789/
[15:46] -kubuntu-ci:#kubuntu-devel- Project mgmt_docker » master build #2789: SUCCESS in 1 min 3 sec: https://kci.pangea.pub/job/mgmt_docker/label=master/2789/
[15:49] -kubuntu-ci:#kubuntu-devel- Project mgmt_docker » swy-01 build #2789: SUCCESS in 4 min 16 sec: https://kci.pangea.pub/job/mgmt_docker/label=swy-01/2789/
 Anything I can do to help to move backports-landing to backports?
 I see 18.04.2 has very few official test reports.  It's a little late, but I now have time to test 18.04.2 if the feedback will serve any purpose.
 @DarinMiller, Yeah, too late for much point now.
 @DarinMiller, I'm conflicted about that. 5.14.1 bugfix is out on Tuesday...
 ?  Do you mean 5.15.1 is out on Tuesday?
 Yes
 No hurry in my opinion.  Landing worked fine for one install.  But I did not know if Simon's patch needed testing.
 The .1 bugfix release seems a sensible time to push to main backports PPA IMO
 Sounds good to me.  I have a 3 day weekend with no exciting plans, so let me know what I can do to help.
 Cheers :)
 At the moment I am just sheperding the last of FW 5.55 through proposed. May do the non pim part of app 18.12.2 tomorow or Mon
 Plasma is not much to do at the moment
 I ddidn't make the same plasma packaging snafus that Neon did (merge related)
 On a recent 18.10 update, apparently grub-install was ran so that my 18.10 partition now controlled by grub menu.  If this upstream or can Kubuntu override this "feature"?
 Neon snafu's?  I did not notice any snafu's on my neon dev unstable upates over the last week or two...
 Not easy to override for us. Really a Ubuntu thing
 @DarinMiller, Some dropped runtime deps, in stable -> user edition
 thought as much.  I kept trying to fix it with grub-update but to no avail.  Had to run grub-install from Disco to restore order.
 @DarinMiller, Not a snafu really, but bad timing that 18.04.2 base files update from Ubuntu overwrote the Neon versioning in about:system
 And for some reason discover is having issues with the update button for many in Neon, whereas I can't replicate it bug in Cosmic with backports
 Prompted this sort of thread on reddit: https://www.reddit.com/r/kde/comments/aqycwp/how_can_we_help_keep_kde_neon_user_edition_from/
 DIscover is improving dramatically, but I always forget to test it as it has had such a history of growing pains, I just automatically use the command line.
 (Document) https://irc-attachments.kde.org/6QuIWwh5/file_13375.mp4
 :)
 Attempting to install kinit-dev on Cosmic with backports.
 kinit-dev : Depends: kinit (= 5.52.0-0ubuntu1~ubuntu18.10~ppa1) but 5.53.0-0ubuntu1~ubuntu18.10~ppa1 is to be installed
 looking at the backport control file, I do not see any reference to 5.53.  What am I missing.... https://git.launchpad.net/~kubuntu-packagers/kubuntu-packaging/+git/kinit/tree/debian/control?h=kubuntu_cosmic_backports
 Ubuntu package search also failed to enlighten: https://packages.ubuntu.com/search?keywords=kinit&searchon=names&suite=cosmic&section=all
 On disco, the kinit-dev installs just fine....
 @DarinMiller, Backports PPA does not have 5.53 for cosmic. You must have maybe installed some 5.53 from a staging/landing PPA at some point?
 Entirely possible, but not that I recall on my desktop.... not a big deal.  I was more interested in understading how to trouble shoot....
 find any 5.53 packages and force downgrade them to 5.52
 but fw is v 5.53 with current backports, yes? So I would have to ppa purge backports?
 also, FWIW, kinit-dev on 18.10 with landing and fw 5.54 installs just fine.  Again, not a big deal and probably self induced via ppa diving.
 @DarinMiller, No, it's all 5.52 in Cosmic backports. Which is why I said you must have got some 5.53 from another testing PPA
 duh..... https://launchpad.net/~kubuntu-ppa/+archive/ubuntu/backports .... I did not even think to check here....
[19:39] <IrcsomeBot1> * acheronuk nods
[19:41] <IrcsomeBot1> * DarinMiller somewhat remebers testing one of Rik's super secret PPA's a while back at Rik's request and thus blames Rik...
 ^^ ENTIRELY KIDDING^^ of course :)
 hahaha
 what the correct way to generate or download ~/.kubuntu-automation.conf ?  It's not part of ka-metadata or ka packages as far as I can tell....