[00:37] <acheronuk> ark done it seems
[00:39] <valorie> \o/
[00:40] <valorie> well done
[00:40] <valorie> and I hope we can do better next time
[00:43] <valorie> gosh, how to I search LP for bugs about ktp or telepathy-morse?
[00:43] <valorie> each search shows no matches
[00:44] <valorie> perhaps it thinks I want only my bugs
[00:44] <valorie> gah
[00:48] <valorie> found a way, but there are no BRs for -morse
[00:48] <valorie> weird
[00:48] <valorie> 16 for ktp, none fixed
[00:48]  * valorie goes off to dinner
[00:53] <clivejo> it doesnt exist in the archive, so there wouldnt be any bugs filed against it
[00:54] <clivejo> There is a bug for telepath not being able to find "morse"
[00:55] <clivejo> LP 1512135
[00:59] <mparillo> Anybody use kteatime? With today's ZZ updates, the icon in the system tray looks more like the old oxygen theme (realistic) than Breeze style (flat).
[01:06] <clivejo> never heard of it!
[01:06] <clivejo> !info kteatime
[01:07] <clivejo> LOL
 That is some people's favorite app!
[01:09] <clivejo> LOL
[01:09] <clivejo> looks up on my system
[01:09] <clivejo> ok
[01:11] <clivejo> could be handy
[01:12] <clivejo> remind me when to stock the fire
[01:12] <clivejo> small log = x mins, medium log = y mins and large log = z mins
[02:15] <tsimonq2> clivejo, acheronuk, valorie and anyone else, CVE-2017-5330 is now fixed.
[02:15] <tsimonq2> Bah.
[02:15] <tsimonq2> bug1655507
[02:15] <tsimonq2> bug 1655507
[03:41] <valorie> thanks, tsimonq2
[03:41] <valorie> thanks for finding that BR, clivejo
[03:45] <valorie> commented
[09:17] <lordievader> Good morning.
[10:41] <BluesKaj> Howdy all
[12:07] -kubuntu-ci:#kubuntu-devel- Project yakkety_unstable_kdav build #1: FAILURE in 4 min 16 sec: http://kci.pangea.pub/job/yakkety_unstable_kdav/1/
[12:08] -kubuntu-ci:#kubuntu-devel- Project xenial_unstable_kdav build #1: FAILURE in 4 min 30 sec: http://kci.pangea.pub/job/xenial_unstable_kdav/1/
[12:09] -kubuntu-ci:#kubuntu-devel- Project zesty_unstable_kdav build #1: FAILURE in 5 min 22 sec: http://kci.pangea.pub/job/zesty_unstable_kdav/1/
[12:18] -kubuntu-ci:#kubuntu-devel- Yippee, build fixed!
[12:18] -kubuntu-ci:#kubuntu-devel- Project yakkety_unstable_kdav build #2: FIXED in 7 min 38 sec: http://kci.pangea.pub/job/yakkety_unstable_kdav/2/
[12:23] -kubuntu-ci:#kubuntu-devel- Yippee, build fixed!
[12:23] -kubuntu-ci:#kubuntu-devel- Project xenial_unstable_kdav build #2: FIXED in 13 min: http://kci.pangea.pub/job/xenial_unstable_kdav/2/
[12:24] -kubuntu-ci:#kubuntu-devel- Yippee, build fixed!
[12:24] -kubuntu-ci:#kubuntu-devel- Project zesty_unstable_kdav build #2: FIXED in 13 min: http://kci.pangea.pub/job/zesty_unstable_kdav/2/
[13:02] -kubuntu-ci:#kubuntu-devel- Project zesty_unstable_kdepim-runtime build #100: STILL FAILING in 19 min: http://kci.pangea.pub/job/zesty_unstable_kdepim-runtime/100/
[13:02] -kubuntu-ci:#kubuntu-devel- Project xenial_unstable_kdepim-runtime build #96: STILL FAILING in 19 min: http://kci.pangea.pub/job/xenial_unstable_kdepim-runtime/96/
[13:02] -kubuntu-ci:#kubuntu-devel- Project yakkety_unstable_kdepim-runtime build #83: STILL FAILING in 19 min: http://kci.pangea.pub/job/yakkety_unstable_kdepim-runtime/83/
[13:15] -kubuntu-ci:#kubuntu-devel- Project zesty_unstable_kdepim-runtime build #101: ABORTED in 8 min 19 sec: http://kci.pangea.pub/job/zesty_unstable_kdepim-runtime/101/
[13:16] -kubuntu-ci:#kubuntu-devel- Project yakkety_unstable_kdepim-runtime build #84: ABORTED in 8 min 21 sec: http://kci.pangea.pub/job/yakkety_unstable_kdepim-runtime/84/
[13:16] -kubuntu-ci:#kubuntu-devel- Project xenial_unstable_kdepim-runtime build #97: ABORTED in 8 min 24 sec: http://kci.pangea.pub/job/xenial_unstable_kdepim-runtime/97/
[13:36] -kubuntu-ci:#kubuntu-devel- Yippee, build fixed!
[13:36] -kubuntu-ci:#kubuntu-devel- Project xenial_unstable_kdepim-runtime build #98: FIXED in 20 min: http://kci.pangea.pub/job/xenial_unstable_kdepim-runtime/98/
[13:36] -kubuntu-ci:#kubuntu-devel- Yippee, build fixed!
[13:36] -kubuntu-ci:#kubuntu-devel- Project yakkety_unstable_kdepim-runtime build #85: FIXED in 20 min: http://kci.pangea.pub/job/yakkety_unstable_kdepim-runtime/85/
[13:41] -kubuntu-ci:#kubuntu-devel- Yippee, build fixed!
[13:41] -kubuntu-ci:#kubuntu-devel- Project zesty_unstable_kdepim-runtime build #102: FIXED in 25 min: http://kci.pangea.pub/job/zesty_unstable_kdepim-runtime/102/
[13:44] <aniketh__> Ping
[13:44] <aniketh__> I wanted to change the ubuntu ppa of 16.10 from 5.28 to 5.30.
[13:44] <aniketh__> I did some googling and found out this
[13:45] <aniketh__> https://www.irccloud.com/pastebin/4flLUcQJ/
[13:45] <aniketh__> will doing this crash/break my system ?
[13:47] <blaze> aniketh__: it's meant only for testing, can eat your kittens
[13:49] <aniketh__> blaze: Haahha..
[13:49] <aniketh__> blaze: Anyways I tried that. But unable to see the results :(
[13:50] <aniketh__> its again saying 5.28.0-0ubuntu1~ubuntu16.10~ppa1
[13:51] <aniketh__> I want that to be 5.30.0-0ubuntu1~ubuntu16.10~ppa1
[14:04] <acheronuk> aniketh__: frameworks 5.30 is yet to be staged anyway. we have been dealing with a transition to Qt 5.7.1 and uploadign some new apps 1st, plus there are a few issues with 5.30 that need to be checked/resolved before it is staged
[14:06] <acheronuk> aniketh__: plus at the moment it is by no means sure that 5.30 will be backported for 16.10
[14:54] <aniketh__> acheronuk: Oh ! Then why does building KDE applications askes lib files from 5.30 ?
[14:55] <acheronuk> aniketh__: building what applications? from what branch?
[14:55] <aniketh__> acheronuk: Like for example, Ktexteditor from it's master branch :)
[14:56] <acheronuk> aniketh__: stable applications 16.12 do not require 5.30
[14:57] <clivejo> Room 1 is working again, after ovidiu-florin broke it!
[14:57] <acheronuk> aniketh__: building the master branch will likely need the latest or even unreleased frameworks
[14:58] <aniketh__> acheronuk: Does the files in the application 16.12 will be having the same files itself. Like will I be getting the patch merges which happends ?
[14:58] <acheronuk> kubuntu stable releases like 16.10 are not bleeding edge dev platforms
[14:58] <aniketh__> acheronuk: Which is the bleeding edge one ?
[15:00] <acheronuk> clivejo: ok :)
[15:01] <acheronuk> aniketh__: Neon de-unstable, our KCI repo if you are quite brave, maybe opensuse with whatever dev kde repos they now have. 
[15:01] <acheronuk> *dev-unstable
[15:09] <aniketh__> okay. thanks acheronuk, will work something out :)
[15:54] -kubuntu-ci:#kubuntu-devel- Project xenial_unstable_telegram-qt build #1: FAILURE in 5 min 30 sec: http://kci.pangea.pub/job/xenial_unstable_telegram-qt/1/
[15:54] -kubuntu-ci:#kubuntu-devel- Project yakkety_unstable_telegram-qt build #1: FAILURE in 5 min 32 sec: http://kci.pangea.pub/job/yakkety_unstable_telegram-qt/1/
[15:54] -kubuntu-ci:#kubuntu-devel- Project zesty_unstable_telegram-qt build #1: FAILURE in 5 min 34 sec: http://kci.pangea.pub/job/zesty_unstable_telegram-qt/1/
[16:03] -kubuntu-ci:#kubuntu-devel- Project yakkety_unstable_telegram-qt build #2: STILL FAILING in 3 min 59 sec: http://kci.pangea.pub/job/yakkety_unstable_telegram-qt/2/
[16:04] -kubuntu-ci:#kubuntu-devel- Project xenial_unstable_telegram-qt build #2: STILL FAILING in 4 min 33 sec: http://kci.pangea.pub/job/xenial_unstable_telegram-qt/2/
[16:05] -kubuntu-ci:#kubuntu-devel- Project zesty_unstable_telegram-qt build #2: STILL FAILING in 6 min 3 sec: http://kci.pangea.pub/job/zesty_unstable_telegram-qt/2/
[16:14] -kubuntu-ci:#kubuntu-devel- Yippee, build fixed!
[16:14] -kubuntu-ci:#kubuntu-devel- Project yakkety_unstable_telegram-qt build #3: FIXED in 11 min: http://kci.pangea.pub/job/yakkety_unstable_telegram-qt/3/
[16:14] -kubuntu-ci:#kubuntu-devel- Yippee, build fixed!
[16:14] -kubuntu-ci:#kubuntu-devel- Project xenial_unstable_telegram-qt build #3: FIXED in 10 min: http://kci.pangea.pub/job/xenial_unstable_telegram-qt/3/
[16:15] -kubuntu-ci:#kubuntu-devel- Yippee, build fixed!
[16:15] -kubuntu-ci:#kubuntu-devel- Project zesty_unstable_telegram-qt build #3: FIXED in 10 min: http://kci.pangea.pub/job/zesty_unstable_telegram-qt/3/
[17:12] <clivejo> !info scratch
[17:12] <clivejo> !info scratch unstable
[17:12] <clivejo> !info nextcloud
[17:13] <clivejo> !info nextcloud unstable
[17:21] <clivejo> !info  scratch-text-editor
[19:05] <mparillo> I saw this:  [Notice] -queuebot to #ubuntu-release- New: accepted okular [amd64] (zesty-proposed) [4:16.12.1-0ubuntu1]
[19:05] <mparillo> Does that mean okular is now KF5?
[19:05] <mparillo> !okular zesty
[19:05] <mparillo> !info okular zesty
[19:06] <mparillo> 16.04.3 still.
[19:08] <acheronuk> !info okular zesty-proposed
[19:08] <acheronuk> you lie ^^^
[19:11] <acheronuk> !info okular proposed
[19:11] <acheronuk> bit seems not to know about zesty proposed
[19:11] <acheronuk> *bot
[19:12] <acheronuk> mparillo: the version in proposed is KF5, even though the bot can't find it
[19:13] <acheronuk> !info marble zesty-proposed
[19:13] <mparillo> acheronuk: TY. Is there an easy way to enable -proposed? The Ubuntu help pages show their app, not Discover.
[19:15] <acheronuk> mparillo: see: https://wiki.ubuntu.com/Testing/EnableProposed
[19:17] <acheronuk> I have proposed enabled here, but with the proposed pocket pinned to to a priority of 400
[19:17] <mparillo> TY, maybe I did not scroll down enough to see I can edit /etc/apt/sources.list:
[19:17] <mparillo> I know I did not see Developer Options in Discover.
[19:18] <acheronuk> so I don't upgrade to the stuff in proposed by default, but I can upgrade stuff selectively
[19:18] <mparillo> Ahh, so I will take that as a hint. It would be like leaving -staging on.
[19:19] <acheronuk> !info okular zesty-proposed
[19:19] <acheronuk> bot still not seeing the new binaries yet. oh well.....
[19:20] <acheronuk> shows here: https://launchpad.net/ubuntu/+source/okular
[22:57]  * acheronuk is in autopgktest hell
[23:07] <clivejo> sounds like fun!
[23:22]  * acheronuk rolls eyes
[23:23] <acheronuk> I'm sorta learning something
[23:27] <mparillo> ovidiuflorin: Thank you for fixing https://bugs.launchpad.net/bugs/1652158 Next will be 16.04.2, but it looks as if it is now in February. https://wiki.ubuntu.com/XenialXerus/ReleaseSchedule
[23:33] <clivejo> hope you making notes so you can teach me!
[23:33] <tsimonq2> ^
[23:34] <clivejo> it would be nice if KCI could integrate autotests
[23:38] <acheronuk> sort of. I'm mostly finding what doesn't work and how rubbish the documentation is!
[23:57] <clivejo> just extremely out of date