[00:07] -kubuntu-ci:#kubuntu-devel- Project mgmt_merger build #737: SUCCESS in 7 min 21 sec: http://kci.pangea.pub/job/mgmt_merger/737/
[00:08] <ahoneybun> acheronuk: https://code.launchpad.net/~aaronhoneycutt/kubuntu-packaging/+git/kalzium/+merge/311785
[01:04] <acheronuk> tsimonq2: zesty archive merges cleanly into xenial_backports
[01:11] <acheronuk> santa_: did you copy everything?
[01:13] <santa_> acheronuk: yes
[01:16] <acheronuk> I was wondered about the ppa size, that is all.
[01:16] <acheronuk> may take a while to properly register
[01:17] <santa_> yeah, but there's more than enough space apparently
[01:18] <acheronuk> yeah. and when I think of it, KCI fits all 3 releases into just over 30GB, so my worry was silly
[01:24] <acheronuk> santa_: Aaron got these two error on a xenial upgrade.... http://paste.ubuntu.com/23530141/
[01:24] <acheronuk> I shall investigate in a VM tomorrow I hope
 Yep
[01:27] -kubuntu-ci:#kubuntu-devel- Project yakkety_unstable_kfind build #4: STILL UNSTABLE in 1 hr 19 min: http://kci.pangea.pub/job/yakkety_unstable_kfind/4/
[01:27] -kubuntu-ci:#kubuntu-devel- Project xenial_unstable_libkcompactdisc build #65: STILL UNSTABLE in 1 hr 18 min: http://kci.pangea.pub/job/xenial_unstable_libkcompactdisc/65/
[01:28] -kubuntu-ci:#kubuntu-devel- Project xenial_unstable_pim-sieve-editor build #20: STILL UNSTABLE in 1 hr 19 min: http://kci.pangea.pub/job/xenial_unstable_pim-sieve-editor/20/
[01:28] -kubuntu-ci:#kubuntu-devel- Project xenial_unstable_pim-data-exporter build #13: STILL UNSTABLE in 1 hr 19 min: http://kci.pangea.pub/job/xenial_unstable_pim-data-exporter/13/
[01:28] -kubuntu-ci:#kubuntu-devel- Project zesty_unstable_kfind build #10: STILL UNSTABLE in 1 hr 20 min: http://kci.pangea.pub/job/zesty_unstable_kfind/10/
[01:56] -kubuntu-ci:#kubuntu-devel- Project zesty_unstable_kde-runtime build #69: STILL FAILING in 1 hr 44 min: http://kci.pangea.pub/job/zesty_unstable_kde-runtime/69/
[01:56] -kubuntu-ci:#kubuntu-devel- Project yakkety_unstable_kde-runtime build #292: STILL FAILING in 1 hr 46 min: http://kci.pangea.pub/job/yakkety_unstable_kde-runtime/292/
[01:56] -kubuntu-ci:#kubuntu-devel- Project xenial_unstable_kopete build #120: STILL UNSTABLE in 1 hr 43 min: http://kci.pangea.pub/job/xenial_unstable_kopete/120/
[01:56] -kubuntu-ci:#kubuntu-devel- Project xenial_unstable_kde-runtime build #285: STILL FAILING in 1 hr 44 min: http://kci.pangea.pub/job/xenial_unstable_kde-runtime/285/
[01:56] -kubuntu-ci:#kubuntu-devel- Project xenial_unstable_ktp-common-internals build #229: STILL UNSTABLE in 1 hr 47 min: http://kci.pangea.pub/job/xenial_unstable_ktp-common-internals/229/
[01:56] -kubuntu-ci:#kubuntu-devel- Project xenial_unstable_kalarm build #21: STILL UNSTABLE in 1 hr 47 min: http://kci.pangea.pub/job/xenial_unstable_kalarm/21/
[01:56] -kubuntu-ci:#kubuntu-devel- Project yakkety_unstable_kirigami build #68: STILL UNSTABLE in 1 hr 45 min: http://kci.pangea.pub/job/yakkety_unstable_kirigami/68/
[01:56] -kubuntu-ci:#kubuntu-devel- Project zesty_unstable_kopete build #21: STILL UNSTABLE in 1 hr 47 min: http://kci.pangea.pub/job/zesty_unstable_kopete/21/
[01:56] -kubuntu-ci:#kubuntu-devel- Project xenial_unstable_konqueror build #17: STILL UNSTABLE in 1 hr 48 min: http://kci.pangea.pub/job/xenial_unstable_konqueror/17/
[01:56] -kubuntu-ci:#kubuntu-devel- Project yakkety_unstable_libkipi build #98: STILL UNSTABLE in 1 hr 47 min: http://kci.pangea.pub/job/yakkety_unstable_libkipi/98/
[01:56] -kubuntu-ci:#kubuntu-devel- Project zesty_unstable_krita build #20: STILL UNSTABLE in 1 hr 48 min: http://kci.pangea.pub/job/zesty_unstable_krita/20/
[01:56] -kubuntu-ci:#kubuntu-devel- Project zesty_unstable_kdesdk-kioslaves build #35: STILL UNSTABLE in 1 hr 46 min: http://kci.pangea.pub/job/zesty_unstable_kdesdk-kioslaves/35/
[01:57] -kubuntu-ci:#kubuntu-devel- Project xenial_unstable_print-manager build #204: STILL UNSTABLE in 1 hr 48 min: http://kci.pangea.pub/job/xenial_unstable_print-manager/204/
[01:57] -kubuntu-ci:#kubuntu-devel- Project yakkety_unstable_kopete build #96: STILL UNSTABLE in 1 hr 45 min: http://kci.pangea.pub/job/yakkety_unstable_kopete/96/
[02:29] -kubuntu-ci:#kubuntu-devel- Project xenial_unstable_kalzium build #112: STILL FAILING in 5 min 25 sec: http://kci.pangea.pub/job/xenial_unstable_kalzium/112/
[02:37] -kubuntu-ci:#kubuntu-devel- Project zesty_unstable_kalzium build #25: STILL FAILING in 12 min: http://kci.pangea.pub/job/zesty_unstable_kalzium/25/
[02:38] -kubuntu-ci:#kubuntu-devel- Project zesty_unstable_kde-runtime build #70: STILL FAILING in 37 min: http://kci.pangea.pub/job/zesty_unstable_kde-runtime/70/
[02:38] -kubuntu-ci:#kubuntu-devel- Project yakkety_unstable_kde-runtime build #293: STILL FAILING in 37 min: http://kci.pangea.pub/job/yakkety_unstable_kde-runtime/293/
[02:38] -kubuntu-ci:#kubuntu-devel- Project xenial_unstable_kde-runtime build #286: STILL FAILING in 37 min: http://kci.pangea.pub/job/xenial_unstable_kde-runtime/286/
[02:40] -kubuntu-ci:#kubuntu-devel- Project xenial_unstable_kalzium build #113: STILL FAILING in 5 min 27 sec: http://kci.pangea.pub/job/xenial_unstable_kalzium/113/
[02:41] -kubuntu-ci:#kubuntu-devel- Project yakkety_unstable_kalzium build #55: STILL FAILING in 16 min: http://kci.pangea.pub/job/yakkety_unstable_kalzium/55/
[02:47] -kubuntu-ci:#kubuntu-devel- Project zesty_unstable_kalzium build #26: STILL FAILING in 4 min 35 sec: http://kci.pangea.pub/job/zesty_unstable_kalzium/26/
[02:51] -kubuntu-ci:#kubuntu-devel- Project yakkety_unstable_kalzium build #56: STILL FAILING in 4 min 57 sec: http://kci.pangea.pub/job/yakkety_unstable_kalzium/56/
[02:56] -kubuntu-ci:#kubuntu-devel- Project yakkety_unstable_kitemmodels build #132: STILL UNSTABLE in 31 min: http://kci.pangea.pub/job/yakkety_unstable_kitemmodels/132/
[02:56] -kubuntu-ci:#kubuntu-devel- Project xenial_unstable_kitemmodels build #331: STILL UNSTABLE in 32 min: http://kci.pangea.pub/job/xenial_unstable_kitemmodels/331/
[02:56] -kubuntu-ci:#kubuntu-devel- Project xenial_unstable_kcoreaddons build #311: STILL UNSTABLE in 32 min: http://kci.pangea.pub/job/xenial_unstable_kcoreaddons/311/
[02:57] -kubuntu-ci:#kubuntu-devel- Project yakkety_unstable_kcoreaddons build #138: STILL UNSTABLE in 31 min: http://kci.pangea.pub/job/yakkety_unstable_kcoreaddons/138/
[02:57] -kubuntu-ci:#kubuntu-devel- Project zesty_unstable_kitemmodels build #35: STILL UNSTABLE in 32 min: http://kci.pangea.pub/job/zesty_unstable_kitemmodels/35/
[03:07]  * wxl stretches
 Hey wxl, good timing
[03:07] <wxl> oh?
 Remember that big book bundle you or someone pasted in IRC earlier?
 Mine now :D
[03:08] <wxl> nice
[03:08] <wxl> i decided against it
 Oh?
[03:08] <wxl> i did get a programming bundle which was pretty nice
 (Photo, 720x1280) https://irc-attachments.kde.org/Pq5csrWX/file_1234.jpg
[03:08] <wxl> but most of those things are glorified references
 Niiice
 Yeah I guess
[03:08] <wxl> i'd probably take the the 5 extra ones
[03:08] <wxl> tho i'm not sure i'd use them all that much
 Link to your loot? :D
[03:10] <wxl> um
[03:10] <wxl> can i do that?
 Well just tell me which books then
[03:10] <wxl> hold
 Well just see Telegram
[03:14] <DarinMiller> tsimonq2: Do you already have a bash programming reference?  I have one I found an open guide  the web a couple years ago that's fairly comprehensive....
[03:15] -kubuntu-ci:#kubuntu-devel- Project yakkety_unstable_knotifications build #114: STILL UNSTABLE in 16 min: http://kci.pangea.pub/job/yakkety_unstable_knotifications/114/
[03:15] <DarinMiller> The bash guide is in pdf format...
[03:41] -kubuntu-ci:#kubuntu-devel- Project zesty_unstable_kwallet build #28: STILL UNSTABLE in 15 min: http://kci.pangea.pub/job/zesty_unstable_kwallet/28/
[03:42] -kubuntu-ci:#kubuntu-devel- Project xenial_unstable_kwallet build #329: STILL UNSTABLE in 15 min: http://kci.pangea.pub/job/xenial_unstable_kwallet/329/
[03:54] -kubuntu-ci:#kubuntu-devel- Project yakkety_unstable_kwallet build #168: STILL UNSTABLE in 12 min: http://kci.pangea.pub/job/yakkety_unstable_kwallet/168/
[03:59] <tsimonq2> Hai wxl :D
[04:00] <wxl> hai
[04:00] <wxl> let's do some work huh?
[04:00] <tsimonq2> Sure :)
[04:00] <tsimonq2> So you have something in mind?
[04:00] <wxl> i dunno let's fix some crap
[04:00] <tsimonq2> Pick something you want to fix
[04:01] <wxl> well something that requires a little more effort maybe
[04:01] <tsimonq2> FIne I'll find something
[04:01] <tsimonq2> Gimme a min or two
[04:02] <tsimonq2> wxl: You good with manpages?
[04:02] <wxl> not that i know of :)
[04:02] <tsimonq2> Like writing them
[04:02] <wxl> i mean it doesn't have to be hard
[04:02] <wxl> just fixing a simple thing works
[04:03] <wxl> but more complicated than a merge conflict
[04:05] <tsimonq2> wxl: http://kci.pangea.pub/job/zesty_unstable_kppp/19/parsed_console/
[04:05] <tsimonq2> You know how to look up Lintian errors? XD
[04:06] <wxl> ummm don't think so
[04:06] <tsimonq2> https://lintian.debian.org/tags/STUPID-FREAKING-TAG.html
[04:06] <tsimonq2> :P
[04:07] <wxl> 404
[04:07] <tsimonq2> *facepalm*
[04:07] <tsimonq2> wxl: Go here: https://lintian.debian.org/tags/
[04:07] <wxl> didn't see it
[04:08] <tsimonq2> KCI-W :: W: kppp: debian-news-entry-has-unknown-version 4:4.8.4-3
[04:08] <wxl> i see that error, yes
[04:08] <tsimonq2> So here: https://lintian.debian.org/tags/debian-news-entry-has-unknown-version.html
[04:08] <wxl> OH
[04:08] <wxl> how do i know that's a lintian error?
[04:09] <tsimonq2> Well I know because it's in that format
[04:09] <tsimonq2> But if you wanted to check, go find the build log
[04:09] <tsimonq2> So go to Console Output, scroll down all the way to the bottom, and it should be staring you in the face
[04:10] <tsimonq2> [04:10] <tsimonq2> warning: the authors of lintian do not recommend running it with root privileges!
[04:10] <tsimonq2> E: kppp changes: bad-distribution-in-changes-file zesty
[04:10] <tsimonq2> E: kppp source: debian-revision-should-not-be-zero 4:16.04.3+p17.04+git20161107.1621-0
[04:10] <tsimonq2> W: kppp source: ancient-standards-version 3.9.6 (current is 3.9.8)
[04:10] <tsimonq2> W: kppp: debian-news-entry-has-unknown-version 4:4.8.4-3
[04:10] <tsimonq2> E: kppp: debian-revision-should-not-be-zero 4:16.04.3+p17.04+git20161107.1621-0
[04:10] <tsimonq2> W: kppp: binary-without-manpage usr/bin/kppp
[04:10] <tsimonq2> W: kppp: binary-without-manpage usr/bin/kppplogview
[04:10] <tsimonq2> N: 1 tag overridden (1 warning)
[04:10] <tsimonq2> /usr/share/pkg-kde-tools/qt-kde-team/2/lintian.mk:20: recipe for target 'lintian' failed
[04:10] <tsimonq2> make[1]: [lintian] Error 1 (ignored)
[04:10] <tsimonq2> Ignore debian-revision-should-not-be-zero
[04:10] <tsimonq2> [04:10] <tsimonq2> Ignore running as root
[04:10] <tsimonq2> Poke everyone about ancient-standards-version again :P
[04:11] <tsimonq2> Ignore binary-without-manpage
[04:11] <tsimonq2> That leaves?
[04:11] <wxl> not console output
[04:11] <wxl> you mean the buildlog
[04:11] <tsimonq2> Yes
[04:11] <tsimonq2> That
[04:12] <wxl> well i guess i would ignore those other ones because they're not a given error from the console output
[04:12] <wxl> although that's interesing
[04:13] <tsimonq2> Yeah we need to fix KCI :P
[04:13] <wxl> i suspect the 1 tag overridden (1 warning) is the one that's kept
[04:13] <wxl> let me grab the code
[04:14] <wxl> um
[04:14] <wxl> is the branch just unstable?
[04:15] <tsimonq2> kubuntu_unstable
[04:15] <tsimonq2> BUT
[04:15] <wxl> oh right always kubuntu_
[04:15] <tsimonq2> What do you mean by this? < wxl> i suspect the 1 tag overridden (1 warning) is the one that's kept
[04:15] <wxl> well lintian gives 3 errors and 4 warnings (ignoring the root stuff)
[04:16] <wxl> we know of one error that is yielded in the end
[04:16] <tsimonq2> Ignore that
[04:16] <wxl> and that's a warning
[04:16] <tsimonq2> It's not important
[04:16] <wxl> so there you go. 1 tag was kept. and a warning at that
[04:16] <wxl> it's a maybe
[04:16] <wxl> anywho
[04:16] <tsimonq2> But that's not what we need to focus on here
[04:16] <wxl> nope we sure dont
[04:18] <wxl> um
[04:18] <wxl> so there's no NEWS.Debian
[04:18] <wxl> there's a NEWS and a README.Debian
[04:18] <wxl> both of which have the offending version
[04:18] <tsimonq2> NEWS is what it is
[04:19] <wxl> yes but it's not NEWS.Debian
[04:19] <tsimonq2> Bah
[04:19] <tsimonq2> Doesn't matter
[04:19] <wxl> i need to get through that darn policy manual already
[04:20] <tsimonq2> wxl: So now what's the latest changelog entry?
[04:20] <tsimonq2> What's the latest version?
[04:20] <wxl> well no wait
[04:20] <wxl> the issue is that that version number is not included in the changelog
[04:21] <tsimonq2> Well I'm wondering if the version in the changelog has an epoch
[04:21] <tsimonq2> If so, then figure it out from there
[04:21] <tsimonq2> If not, simple solution
[04:21] <wxl> 4:4.8.4-1 is there
[04:21] <wxl> no instance of 4.8.4 anything without an epoch exists
[04:22] <wxl> so that's just freaking weird
[04:22] <tsimonq2> You are wrong
[04:23] <tsimonq2> And I see the problem dude :)
[04:23] <tsimonq2> Let me explain
[04:23] <tsimonq2> kppp (4:4.8.4-3) unstable; urgency=low
[04:23] <tsimonq2> That's in NEWS
[04:23] <tsimonq2> Right?
[04:23] <wxl> ja
[04:24] <tsimonq2> We only have kdenetwork (4:4.8.4-1) unstable; urgency=low, not kppp (4:4.8.4-3) unstable; urgency=low
[04:24] <wxl> oh hahahahah
[04:25] <tsimonq2> So guess what you get to do? :PP
[04:25] <wxl> so just s/kpp/kdenetwork/
[04:25] <tsimonq2> OH SHOOT
[04:25] <wxl> on {NEWS,README}
[04:25] <tsimonq2> I didn't even see that
[04:25] <tsimonq2> LOL
[04:25] <wxl> :)
[04:25] <tsimonq2> I was looking at the version!
[04:25] <wxl> hahahahah
[04:25] <wxl> still that doesn't fix it because the version number is not there
[04:26] <wxl> so that's only part of the solution
[04:26] <tsimonq2> So now when in doubt, look at Debian
[04:26] <tsimonq2> Then Neon
[04:26] <wxl> and actually for that version that's not a solution
[04:26] <tsimonq2> Debian has: kppp (4:4.8.4-3) unstable; urgency=low in NEWS
[04:27] <wxl> well it should be that actually, tho
[04:27] <tsimonq2> Well no it seems
[04:27] <wxl> 4.8 would have been kdenetwork
[04:27] <wxl> soooooooooooooooooo
[04:27] <wxl> just leave it??
[04:27] <tsimonq2> Lintian page has affected packages: https://lintian.debian.org/tags/debian-news-entry-has-unknown-version.html
[04:27] <tsimonq2> Right?
[04:27] <tsimonq2> So it's affected in Debian
[04:28] <tsimonq2> kdenetwork (4:4.8.4-1) unstable; urgency=low
[04:28] <tsimonq2> Should be that
[04:28] <tsimonq2> Change the NEWS file and let's be done with it
[04:29] <tsimonq2> But let's leave your MP open so that other ninjas can comment
[04:29] <tsimonq2> wxl: Good deal? :)
[04:29] <wxl> wow that's crazy
[04:31] <tsimonq2> wxl: Want me to sick symbols on ya? XD
[04:32] <wxl> yeah i might give it a shot
[04:32] <wxl> let me finish the mp
[04:32] -kubuntu-ci:#kubuntu-devel- Project xenial_unstable_frameworkintegration build #325: FAILURE in 6 min 13 sec: http://kci.pangea.pub/job/xenial_unstable_frameworkintegration/325/
[04:32] <wxl> also i gotta find the loo :)
[04:33] <tsimonq2> wxl: http://kci.pangea.pub/job/yakkety_unstable_akonadi-calendar/35/parsed_console/ have fun, I don't even know much about them yet :P
[04:34] <tsimonq2> wxl: Then try this once you wrap your brain around that: http://kci.pangea.pub/job/yakkety_unstable_audiocd-kio/61/
[04:34] <wxl> well anything i do that's more complex is going to require your help
[04:34] <wxl> so maybe let's not :)
[04:34] <tsimonq2> :P
[04:34] <wxl> what part of kci are you picking these out of btw?
[04:34]  * wxl is listening to Comphonie III by Ultralyd ♫ https://www.last.fm/music/Ultralyd/_/Comphonie+III
[04:34] <tsimonq2> This atm: http://kci.pangea.pub/view/yakkety%20FIX/
[04:35] <wxl> that above is neat stuff btw
[04:35] <wxl> not like you'd like it but hey :)
[04:36] <wxl> target reference path = branch, bno?
[04:37] <tsimonq2> Yes
[04:38] -kubuntu-ci:#kubuntu-devel- Project zesty_unstable_frameworkintegration build #27: FAILURE in 5 min 14 sec: http://kci.pangea.pub/job/zesty_unstable_frameworkintegration/27/
[04:38] <tsimonq2> I think I'm going to lay in bed and read some ebooks
[04:38] <wxl> k
[04:38] <tsimonq2> Nini wxl :)
[04:38] <wxl> i wish there was another ninja on my timezonee :(
[04:39] <wxl> hey wait you don't have school tomorrow
 Yeah but I have work in the afternoon]
 Working from 11:30 AM to 4 PM
 (my time)
[04:39] <wxl> aw jeez
[04:39] <wxl> fine just leave me
[04:39]  * wxl cries
 When will you awake in the morn?
[04:40] <wxl> well kind of doesn't matter cuz i have to work
 Oh
 bah
[04:40] <wxl> and besides not early enough probably
[04:41] <wxl> i mean i often get up at 6 but i'll probably be out the door by 7 or so
 Well we'll have like 3 hours give or take after I come home from work
 Alright yeah
 Go find Santa. XD
[04:41] -kubuntu-ci:#kubuntu-devel- Project xenial_unstable_frameworkintegration build #326: STILL FAILING in 3 min 44 sec: http://kci.pangea.pub/job/xenial_unstable_frameworkintegration/326/
[04:41] <wxl> hahahha
 Ok for real night o/
[04:41] <wxl> nai
[04:48] -kubuntu-ci:#kubuntu-devel- Project zesty_unstable_frameworkintegration build #28: STILL FAILING in 5 min 50 sec: http://kci.pangea.pub/job/zesty_unstable_frameworkintegration/28/
[04:54] -kubuntu-ci:#kubuntu-devel- Project yakkety_unstable_frameworkintegration build #171: FAILURE in 6 min 40 sec: http://kci.pangea.pub/job/yakkety_unstable_frameworkintegration/171/
[04:55] -kubuntu-ci:#kubuntu-devel- Project xenial_unstable_peruse build #21: FAILURE in 7 min 45 sec: http://kci.pangea.pub/job/xenial_unstable_peruse/21/
[04:56] -kubuntu-ci:#kubuntu-devel- Project zesty_unstable_peruse build #7: FAILURE in 4 min 53 sec: http://kci.pangea.pub/job/zesty_unstable_peruse/7/
[05:02] -kubuntu-ci:#kubuntu-devel- Project xenial_unstable_umbrello build #136: STILL UNSTABLE in 22 min: http://kci.pangea.pub/job/xenial_unstable_umbrello/136/
[05:03] -kubuntu-ci:#kubuntu-devel- Project xenial_unstable_kstars build #303: STILL UNSTABLE in 23 min: http://kci.pangea.pub/job/xenial_unstable_kstars/303/
[05:03] -kubuntu-ci:#kubuntu-devel- Project yakkety_unstable_frameworkintegration build #172: STILL FAILING in 3 min 50 sec: http://kci.pangea.pub/job/yakkety_unstable_frameworkintegration/172/
[05:04] -kubuntu-ci:#kubuntu-devel- Project xenial_unstable_peruse build #22: STILL FAILING in 3 min 42 sec: http://kci.pangea.pub/job/xenial_unstable_peruse/22/
[05:05] -kubuntu-ci:#kubuntu-devel- Project zesty_unstable_peruse build #8: STILL FAILING in 3 min 49 sec: http://kci.pangea.pub/job/zesty_unstable_peruse/8/
[05:11] -kubuntu-ci:#kubuntu-devel- Project yakkety_unstable_peruse build #8: FAILURE in 4 min 51 sec: http://kci.pangea.pub/job/yakkety_unstable_peruse/8/
[05:18] <valorie> oh my, working on Thanksgiving
[05:18] <valorie> while I was eating pie
[05:18] <wxl> heheh not too much :)
 Not today for me
[05:18] <IrcsomeBot1> * tsimonq2 rolls over
 zzzZZZzzz
[05:19] <wxl> i'm currently working on a very interesting little problem
[05:19] <wxl> i kind of feel like i opened pandora's box
[05:21] -kubuntu-ci:#kubuntu-devel- Project yakkety_unstable_peruse build #9: STILL FAILING in 5 min 1 sec: http://kci.pangea.pub/job/yakkety_unstable_peruse/9/
[05:24] -kubuntu-ci:#kubuntu-devel- Project xenial_unstable_kirigami build #61: STILL UNSTABLE in 13 min: http://kci.pangea.pub/job/xenial_unstable_kirigami/61/
[05:24] -kubuntu-ci:#kubuntu-devel- Project xenial_unstable_plasma-integration build #44: STILL UNSTABLE in 13 min: http://kci.pangea.pub/job/xenial_unstable_plasma-integration/44/
[05:24] -kubuntu-ci:#kubuntu-devel- Project xenial_unstable_plasma-mediacenter build #215: STILL UNSTABLE in 13 min: http://kci.pangea.pub/job/xenial_unstable_plasma-mediacenter/215/
[05:24] -kubuntu-ci:#kubuntu-devel- Project xenial_unstable_ktp-auth-handler build #217: STILL UNSTABLE in 14 min: http://kci.pangea.pub/job/xenial_unstable_ktp-auth-handler/217/
[05:29] <DarinMiller> !kdenetwork
[05:29] <DarinMiller> !kppp
[05:29] <wxl> oh dude
[05:29] <wxl> that's the pandora's box
[05:30] <DarinMiller> !info kppp
[05:30] <wxl> i'm about to make a merge proposal on that one
[05:30] <wxl> but it's pretty funny
[05:30] <DarinMiller> Oh high wxl
[05:30] <wxl> the proposal is all like:
[05:30] <DarinMiller> ;hi
[05:30] <wxl> "here's a fix, but here's why i think it's wrong and we need to basically do a major overhaul"
[05:30] <wxl> XD
[05:30] <wxl> also hai DarinMiller :)
[05:30] <DarinMiller> I was attemting to follow your troubleshooting path
[05:30] -kubuntu-ci:#kubuntu-devel- Project zesty_unstable_umbrello build #32: STILL UNSTABLE in 20 min: http://kci.pangea.pub/job/zesty_unstable_umbrello/32/
[05:30] <wxl> did you say you were in colorado?
[05:31] <DarinMiller> Meridian, Idaho
[05:31] <wxl> oh interesting
[05:31] <wxl> well that's close enough to oregon that the "high" makes sense
[05:31] <wxl> XD
[05:31] <DarinMiller> LOL
[05:32] <DarinMiller> And you work for a bike shop in Eugene?
[05:32] <wxl> a bike manufacturer yes
[05:32] <DarinMiller> Even better.  Which one?
[05:32] <wxl> Bike Friday
[05:33] <DarinMiller> I am a warm showers host and knew nothing about Bike Friday until a guy on Bike Friday rode through and stayed at the house.
[05:33] <wxl> ah cool
[05:34] <wxl> well this is -offtopic so just to put the final word on this before valorie yells at me, i can get you wholesale pricing if you need it. got a wheel on order for claydoh
[05:35] <valorie> why would I yell?
[05:36] <valorie> I think it's awesome to get more people riding
[05:36] <wxl> valorie: oh i was kidding, but you did ask clay and i to get off -devel with the discussion XD
[05:36] <wxl> DarinMiller: https://code.launchpad.net/~wxl/kubuntu-packaging/+git/kppp/+merge/311791
[05:36] <DarinMiller> Very good.  I am a year around commuter so I was disappointed when I read the kubuntu-devel log a saw the off topic bike conversation.  I don't think the offtopic thread has log. :(
[05:37] <valorie> heh
[05:37] <wxl> well now you know :)
[05:37] <valorie> DarinMiller: it has a telegram bridge though
[05:37] -kubuntu-ci:#kubuntu-devel- Project zesty_unstable_kstars build #32: STILL UNSTABLE in 27 min: http://kci.pangea.pub/job/zesty_unstable_kstars/32/
[05:38] <valorie> on T. it's called Kubuntu Cafe or so
[05:38] <DarinMiller> I need to learn this Telegram thingy.
[05:38] -kubuntu-ci:#kubuntu-devel- Project zesty_unstable_ktp-common-internals build #23: STILL UNSTABLE in 21 min: http://kci.pangea.pub/job/zesty_unstable_ktp-common-internals/23/
[05:38] <wxl> meh telegram
[05:39] <valorie> DarinMiller: it was the killer app of Akademy in A Coruna
[05:39] <wxl> i told simon i'd use the heck out of telegram if i had a bitlbee server running the libpurple version so i told he could get em to chat on it all the time if he set up his own servers. still waiting :)
[05:39] <valorie> and has sort of spread like moss since then
[05:39] <wxl> it was the killer app of akademy???
[05:39] <wxl> i mean it's not ktelegram XD
[05:40] <wxl> hell, it's not even cute ;)
[05:40] <valorie> because wifi was terrible, and IRC just wouldn't work
[05:40] <wxl> oh that makes sense then
[05:40] <valorie> Cutegram doesn't work as well
[05:40] <valorie> we tried
[05:44] -kubuntu-ci:#kubuntu-devel- Project xenial_unstable_plasma-sdk build #263: STILL UNSTABLE in 14 min: http://kci.pangea.pub/job/xenial_unstable_plasma-sdk/263/
[05:45] -kubuntu-ci:#kubuntu-devel- Project yakkety_unstable_kstars build #171: STILL UNSTABLE in 20 min: http://kci.pangea.pub/job/yakkety_unstable_kstars/171/
[05:45] -kubuntu-ci:#kubuntu-devel- Project yakkety_unstable_umbrello build #121: STILL UNSTABLE in 20 min: http://kci.pangea.pub/job/yakkety_unstable_umbrello/121/
[05:48] -kubuntu-ci:#kubuntu-devel- Project xenial_unstable_kolourpaint build #107: FAILURE in 17 min: http://kci.pangea.pub/job/xenial_unstable_kolourpaint/107/
[05:48] -kubuntu-ci:#kubuntu-devel- Project xenial_unstable_cantor build #228: FAILURE in 17 min: http://kci.pangea.pub/job/xenial_unstable_cantor/228/
[05:51] -kubuntu-ci:#kubuntu-devel- Project xenial_unstable_marble build #53: STILL UNSTABLE in 27 min: http://kci.pangea.pub/job/xenial_unstable_marble/53/
[05:51] -kubuntu-ci:#kubuntu-devel- Project zesty_unstable_libkcompactdisc build #26: STILL UNSTABLE in 13 min: http://kci.pangea.pub/job/zesty_unstable_libkcompactdisc/26/
[05:51] -kubuntu-ci:#kubuntu-devel- Project zesty_unstable_print-manager build #19: STILL UNSTABLE in 19 min: http://kci.pangea.pub/job/zesty_unstable_print-manager/19/
[05:51] -kubuntu-ci:#kubuntu-devel- Project zesty_unstable_ktp-auth-handler build #24: STILL UNSTABLE in 13 min: http://kci.pangea.pub/job/zesty_unstable_ktp-auth-handler/24/
[05:51] -kubuntu-ci:#kubuntu-devel- Project zesty_unstable_plasma-integration build #30: STILL UNSTABLE in 19 min: http://kci.pangea.pub/job/zesty_unstable_plasma-integration/30/
[05:52] -kubuntu-ci:#kubuntu-devel- Project yakkety_unstable_ktp-auth-handler build #170: STILL UNSTABLE in 21 min: http://kci.pangea.pub/job/yakkety_unstable_ktp-auth-handler/170/
[05:52] -kubuntu-ci:#kubuntu-devel- Project xenial_unstable_kio-extras build #241: STILL UNSTABLE in 21 min: http://kci.pangea.pub/job/xenial_unstable_kio-extras/241/
[05:52] <DarinMiller> wxl: Nice Description of change for kppp MR (very helpful for me!)   So, the kdenetwork version problem is a debian packaging or developer (upstream?) issue?
 Sorry battery died
 Decided to get in bed
[05:54] <DarinMiller> OK, np.  I can wait until tomorrow...
 Anyways the issue always to exist in Debian from what I can tell
 I should have double checked kde repos but i have to imagine there's no problem there
[05:56] <DarinMiller> So we fix the same issue every 6 months with each new ubuntu release?
 I can only imagine that's the case.
 But I'm not sure either
 This is where I think you just need to cut your teeth on a reasonable solution and see what happens
[05:59] -kubuntu-ci:#kubuntu-devel- Project zesty_unstable_cantor build #28: STILL UNSTABLE in 20 min: http://kci.pangea.pub/job/zesty_unstable_cantor/28/
 When I feel like I can answer things definitively, then I think I'll be more ready for Ninja
[05:59] -kubuntu-ci:#kubuntu-devel- Project zesty_unstable_kio-extras build #24: STILL UNSTABLE in 20 min: http://kci.pangea.pub/job/zesty_unstable_kio-extras/24/
[05:59] -kubuntu-ci:#kubuntu-devel- Project yakkety_unstable_kio-extras build #104: STILL UNSTABLE in 14 min: http://kci.pangea.pub/job/yakkety_unstable_kio-extras/104/
[05:59] -kubuntu-ci:#kubuntu-devel- Project yakkety_unstable_akonadi build #215: STILL UNSTABLE in 29 min: http://kci.pangea.pub/job/yakkety_unstable_akonadi/215/
 @wxl23, 👍
[06:02] <DarinMiller> gn, heading to bed also.
 😪
 K nai
[06:06] -kubuntu-ci:#kubuntu-devel- Yippee, build fixed!
[06:06] -kubuntu-ci:#kubuntu-devel- Project xenial_unstable_kolourpaint build #108: FIXED in 12 min: http://kci.pangea.pub/job/xenial_unstable_kolourpaint/108/
[06:06] -kubuntu-ci:#kubuntu-devel- Project yakkety_unstable_plasma-sdk build #153: STILL UNSTABLE in 14 min: http://kci.pangea.pub/job/yakkety_unstable_plasma-sdk/153/
[06:07] -kubuntu-ci:#kubuntu-devel- Project yakkety_unstable_plasma-integration build #42: STILL UNSTABLE in 15 min: http://kci.pangea.pub/job/yakkety_unstable_plasma-integration/42/
[06:07] -kubuntu-ci:#kubuntu-devel- Project zesty_unstable_marble build #39: STILL UNSTABLE in 34 min: http://kci.pangea.pub/job/zesty_unstable_marble/39/
[06:07] -kubuntu-ci:#kubuntu-devel- Project yakkety_unstable_marble build #55: STILL FAILING in 32 min: http://kci.pangea.pub/job/yakkety_unstable_marble/55/
[06:13] -kubuntu-ci:#kubuntu-devel- Project xenial_unstable_cantor build #229: NOW UNSTABLE in 19 min: http://kci.pangea.pub/job/xenial_unstable_cantor/229/
[06:15] -kubuntu-ci:#kubuntu-devel- Project xenial_unstable_kwin build #62: STILL UNSTABLE in 44 min: http://kci.pangea.pub/job/xenial_unstable_kwin/62/
[06:22] -kubuntu-ci:#kubuntu-devel- Project zesty_unstable_kwin build #37: STILL UNSTABLE in 30 min: http://kci.pangea.pub/job/zesty_unstable_kwin/37/
[06:24] -kubuntu-ci:#kubuntu-devel- Project yakkety_unstable_kaddressbook build #15: STILL FAILING in 5 min 32 sec: http://kci.pangea.pub/job/yakkety_unstable_kaddressbook/15/
[06:24] -kubuntu-ci:#kubuntu-devel- Project yakkety_unstable_plasma-workspace build #62: STILL FAILING in 24 min: http://kci.pangea.pub/job/yakkety_unstable_plasma-workspace/62/
[06:31] -kubuntu-ci:#kubuntu-devel- Project yakkety_unstable_pim-data-exporter build #13: STILL UNSTABLE in 12 min: http://kci.pangea.pub/job/yakkety_unstable_pim-data-exporter/13/
[06:31] -kubuntu-ci:#kubuntu-devel- Project yakkety_unstable_mbox-importer build #19: STILL UNSTABLE in 12 min: http://kci.pangea.pub/job/yakkety_unstable_mbox-importer/19/
[06:31] -kubuntu-ci:#kubuntu-devel- Project zesty_unstable_mbox-importer build #17: STILL UNSTABLE in 12 min: http://kci.pangea.pub/job/zesty_unstable_mbox-importer/17/
[06:31] -kubuntu-ci:#kubuntu-devel- Project yakkety_unstable_kalarm build #20: STILL UNSTABLE in 12 min: http://kci.pangea.pub/job/yakkety_unstable_kalarm/20/
[06:31] -kubuntu-ci:#kubuntu-devel- Project yakkety_unstable_grantlee-editor build #18: STILL UNSTABLE in 12 min: http://kci.pangea.pub/job/yakkety_unstable_grantlee-editor/18/
[06:31] -kubuntu-ci:#kubuntu-devel- Project zesty_unstable_korganizer build #21: STILL UNSTABLE in 12 min: http://kci.pangea.pub/job/zesty_unstable_korganizer/21/
[06:31] -kubuntu-ci:#kubuntu-devel- Project zesty_unstable_pim-data-exporter build #15: STILL UNSTABLE in 12 min: http://kci.pangea.pub/job/zesty_unstable_pim-data-exporter/15/
[06:35] -kubuntu-ci:#kubuntu-devel- Project yakkety_unstable_kaddressbook build #16: STILL FAILING in 5 min 50 sec: http://kci.pangea.pub/job/yakkety_unstable_kaddressbook/16/
[06:39] -kubuntu-ci:#kubuntu-devel- Project zesty_unstable_kalarm build #20: STILL UNSTABLE in 20 min: http://kci.pangea.pub/job/zesty_unstable_kalarm/20/
[06:39] -kubuntu-ci:#kubuntu-devel- Project xenial_unstable_plasma-workspace build #61: STILL FAILING in 24 min: http://kci.pangea.pub/job/xenial_unstable_plasma-workspace/61/
[06:47] -kubuntu-ci:#kubuntu-devel- Project yakkety_unstable_messagelib build #65: STILL FAILING in 22 min: http://kci.pangea.pub/job/yakkety_unstable_messagelib/65/
[06:47] -kubuntu-ci:#kubuntu-devel- Project zesty_unstable_plasma-workspace build #43: FAILURE in 25 min: http://kci.pangea.pub/job/zesty_unstable_plasma-workspace/43/
[06:48] -kubuntu-ci:#kubuntu-devel- Project yakkety_unstable_marble build #56: STILL FAILING in 35 min: http://kci.pangea.pub/job/yakkety_unstable_marble/56/
[06:54] -kubuntu-ci:#kubuntu-devel- Project yakkety_unstable_plasma-workspace build #63: STILL FAILING in 24 min: http://kci.pangea.pub/job/yakkety_unstable_plasma-workspace/63/
[07:07] -kubuntu-ci:#kubuntu-devel- Project xenial_unstable_plasma-workspace build #62: STILL FAILING in 23 min: http://kci.pangea.pub/job/xenial_unstable_plasma-workspace/62/
[07:19] -kubuntu-ci:#kubuntu-devel- Project yakkety_unstable_messagelib build #66: STILL FAILING in 26 min: http://kci.pangea.pub/job/yakkety_unstable_messagelib/66/
[07:27] -kubuntu-ci:#kubuntu-devel- Project zesty_unstable_plasma-workspace build #44: STILL FAILING in 34 min: http://kci.pangea.pub/job/zesty_unstable_plasma-workspace/44/
[07:32] -kubuntu-ci:#kubuntu-devel- Project zesty_unstable_kdepim-addons build #35: STILL UNSTABLE in 24 min: http://kci.pangea.pub/job/zesty_unstable_kdepim-addons/35/
[07:33] -kubuntu-ci:#kubuntu-devel- Project yakkety_unstable_akonadi-calendar-tools build #24: STILL UNSTABLE in 13 min: http://kci.pangea.pub/job/yakkety_unstable_akonadi-calendar-tools/24/
[07:41] -kubuntu-ci:#kubuntu-devel- Project yakkety_unstable_kdepim-addons build #47: STILL UNSTABLE in 22 min: http://kci.pangea.pub/job/yakkety_unstable_kdepim-addons/47/
[12:11] -kubuntu-ci:#kubuntu-devel- Yippee, build fixed!
[12:11] -kubuntu-ci:#kubuntu-devel- Project xenial_unstable_kppp build #25: FIXED in 14 min: http://kci.pangea.pub/job/xenial_unstable_kppp/25/
[12:11] -kubuntu-ci:#kubuntu-devel- Yippee, build fixed!
[12:11] -kubuntu-ci:#kubuntu-devel- Project yakkety_unstable_kppp build #102: FIXED in 15 min: http://kci.pangea.pub/job/yakkety_unstable_kppp/102/
[12:11] -kubuntu-ci:#kubuntu-devel- Yippee, build fixed!
[12:11] -kubuntu-ci:#kubuntu-devel- Project zesty_unstable_kppp build #20: FIXED in 15 min: http://kci.pangea.pub/job/zesty_unstable_kppp/20/
[12:15] <BluesKaj> Hey folks
[12:15] <ahoneybun> acheronuk: seems that did fix that missing .cmake file for kalzium
[12:15] <ahoneybun> and now another one poped up
[12:15] <ahoneybun> heyo BluesKaj
[12:15] <BluesKaj> Hi ahoneybun
[12:16] <ahoneybun> acheronuk: adding backports to a 16.04.1 VM then the staging stuff
[12:37] <doko> hi, could somebody check if the ui for quassel-client comes up when you start it? it doesn't seem to work for me on the unity desktop
[12:42] <BluesKaj> doko, do you have quassel-client installed ? Think you need it on Unity
[12:42] <doko> ??? how would I be able to start it without having it installed?
[12:43] <BluesKaj> in the terminal or the run command
[12:44] <doko> on the command line
[12:45] <BluesKaj> btw this is #kubuntu-devel , not #ubuntu support
[12:46] <mamarley> You might try asking in #quassel.  I remember at least one other person who had a similar problem, but I can't remember what the solution was, sorry.
[12:46] <BluesKaj> doko, you need quassel-client to run it on unity , so install it
[12:47] <doko> BluesKaj, you are not helpful
[12:47] <doko> mamarley, thanks
[12:47] <BluesKaj> doko you're in the wrong chat
[12:48] <BluesKaj> ask in #quassel or #ubuntu
[12:55] <BluesKaj> doko, my aplologies, I misread your question,  no wonder I wasn't helpful to you :-)
[12:56]  * BluesKaj goes for more coffee
[14:20] <acheronuk> ahoneybun: everything for backport upgrades should now be in backports-landing ppa. so can you retest your VM upgrade with only that ppa enabled possible?
[14:22] <acheronuk> I just did on Xenial, and it went smoothly on a apt-get dist-upgrade. some packages get removed, but for me only those which are deliberately intended for removal.
[14:34] -kubuntu-ci:#kubuntu-devel- Project merger_kwin build #1022: FAILURE in 17 sec: http://kci.pangea.pub/job/merger_kwin/1022/
[14:35] -kubuntu-ci:#kubuntu-devel- Project merger_kwin build #1023: STILL FAILING in 18 sec: http://kci.pangea.pub/job/merger_kwin/1023/
[14:36] -kubuntu-ci:#kubuntu-devel- Yippee, build fixed!
[14:36] -kubuntu-ci:#kubuntu-devel- Project merger_kwin build #1024: FIXED in 24 sec: http://kci.pangea.pub/job/merger_kwin/1024/
[14:50] <acheronuk> santa_: incidenceeditor and kdepim im Xenial backports rebuilt and copied over to landing, as they were depending on the old non debianabimanager'd library versions
[15:03] -kubuntu-ci:#kubuntu-devel- Project zesty_unstable_kwin build #38: STILL UNSTABLE in 28 min: http://kci.pangea.pub/job/zesty_unstable_kwin/38/
[15:05] -kubuntu-ci:#kubuntu-devel- Project yakkety_unstable_kwin build #60: STILL FAILING in 30 min: http://kci.pangea.pub/job/yakkety_unstable_kwin/60/
[15:15] -kubuntu-ci:#kubuntu-devel- Project xenial_unstable_kwin build #63: STILL UNSTABLE in 40 min: http://kci.pangea.pub/job/xenial_unstable_kwin/63/
[15:52] -kubuntu-ci:#kubuntu-devel- Project xenial_unstable_kwin build #64: STILL UNSTABLE in 37 min: http://kci.pangea.pub/job/xenial_unstable_kwin/64/
[15:53] -kubuntu-ci:#kubuntu-devel- Project zesty_unstable_kwin build #39: STILL UNSTABLE in 50 min: http://kci.pangea.pub/job/zesty_unstable_kwin/39/
[15:55] -kubuntu-ci:#kubuntu-devel- Project yakkety_unstable_kwin build #61: STILL FAILING in 49 min: http://kci.pangea.pub/job/yakkety_unstable_kwin/61/
[16:36] -kubuntu-ci:#kubuntu-devel- Project yakkety_unstable_kwin build #62: STILL FAILING in 32 min: http://kci.pangea.pub/job/yakkety_unstable_kwin/62/
[17:14] <ejat> sorry to bother ...
[17:15] <ejat> https://forum.kde.org/viewtopic.php?f=215&t=102577
[17:15] <ejat> im having problem with my kmail mailbox ..
[17:15] <ejat> anyone can assist ?
[17:29] <wxl> !info calamares
[17:31]  * wxl stretches
[17:32] <DarinMiller> ejat: Please seek assistance on the #kubuntu channel as this channel is for packaging related issues.  I checked the #kmail channel, but almost nobody is home.
[17:32] <DarinMiller> ejat: I do not use kmail at the moment or I would try to assist myself.
[17:33] <DarinMiller> G'morning wxl!
 Hey D ☺
[17:34] <DarinMiller> I am attempting to fix a akonadi-calendar-tools warning: KCI-W :: W: konsolekalendar: desktop-command-not-in-package usr/share/applications/konsolekalendar.desktop kdialog
[17:36] <DarinMiller> Not sure if am barking up the wrong tree (i.e. attempting to fix the wrong issue).  But I cannot find any reference to konsolekalendar.desktop nor kdialong in the akonadi-calendar-tools package set.
[17:36] <ejat> DarinMiller: okie
[17:36] <ejat> thanks
[17:38] <wxl> gimme a sec, DarinMiller
[17:38] <DarinMiller> ok
[17:38] <wxl> ok first, do you already know about the lintian tags page?
[17:38] <DarinMiller> nope
[17:38] <wxl> oh well that one will help immensely
[17:38] <wxl> here's the directory https://lintian.debian.org/tags/
[17:39] <wxl> it includes files of the form tag.html
[17:39] <wxl> e.g. desktop-command-not-in-package.html
[17:39] <DarinMiller> oh, I lied. I have that bookmarked, but I don't know how to use it.
[17:39] <wxl> so if you do go to the right page
[17:39] <wxl> https://lintian.debian.org/tags/desktop-command-not-in-package.html
[17:39] <wxl> The desktop entry specifies a command that is not available in the package. In most cases, this is a typo or a forgotten update of the desktop file after the install location of the binary was changed. A desktop file for a command should be included in the same package as that command.
[17:40] <wxl> see where you can get with that
[17:40] <wxl> i need to do something at work right quick
[17:40] <DarinMiller> ah yes.
[17:41] <DarinMiller> np, I will try to take it from here...
[17:41] <wxl> btw you might wonder how you know that's a *lintian* issue
[17:42] <wxl> you'll see mention of it in the [17:42] <wxl> and remember build logs != console output
[17:42] <DarinMiller> the dashes int the error descript?
[17:42] <wxl> that's the 'amd64' link
[17:42] <wxl> yep
[17:42] <wxl> i don't remember if there's two or three tho :)
[17:42] <wxl> you could search for lintian, too
[17:45]  * acheronuk lurks
[17:45] <ahoneybun> acheronuk: I added all the ppa for xenial and then a dist-upgrade with no issues about python3.aptdaemon thing
[17:45] <ahoneybun> so everything has been moved to backport-landing acheronuk?
[17:46] <acheronuk> ahoneybun: "all the ppa"?
[17:46] <acheronuk> ahoneybun: yep. should only need that one ppa now
[17:46] <ahoneybun> staging-* and backport-landing
[17:46] <wxl> query: who does iso testing around here?
[17:46] <ahoneybun> so backport-landing has everythhing now?
[17:46] <ahoneybun> !testers
[17:46] <ahoneybun> mm
[17:47] <wxl> oh cool
[17:47] <ahoneybun> sorry about that
[17:47] <acheronuk> ahoneybun: should have, yes
[17:47] <ahoneybun> acheronuk: I think we should ask for testers on the site then, no?
[17:47] <ahoneybun> in news
[17:47] <ahoneybun>   /testers
[17:47] <acheronuk> wxl: I have done iso testing for the last few
[17:48] <wxl> um
[17:48] <wxl> hahahah i cant' remember the animal for zesty XD
[17:48] <wxl> !zesty
[17:48] <ahoneybun> a mouse
[17:48] <wxl> yes i got that much :)
[17:49] <wxl> anyways if you look at the schedule alpha 1 is due 29 December
[17:49] <wxl> so we'll need to have testers ready to go before that week
[17:49] <DarinMiller> I test, there I am.
[17:49] <acheronuk> ahoneybun: I want to do a few more tests in a VM yet. e.g. an upgrade on an install where someone already has the current backports (plasma 5.6.5) installed
[17:49] <wxl> perhaps we could do a BBB on testing training?
[17:49] <wxl> are we ready enough that a current zesty is usable?
[17:50] <ahoneybun> acheronuk: 16.10 you mean?
[17:51] <acheronuk> ahoneybun: no I mean an upgrade on 16.04 where someone already has the backport ppa enabled and so has plasma 5.6.5
[17:51] <DarinMiller> ^therefore
[17:51] -kubuntu-ci:#kubuntu-devel- Yippee, build fixed!
[17:51] -kubuntu-ci:#kubuntu-devel- Project yakkety_unstable_grantlee-editor build #19: FIXED in 14 min: http://kci.pangea.pub/job/yakkety_unstable_grantlee-editor/19/
[17:52] <wxl> ooh i just figured out a neat way to switch between gitconfigs with the GIT_CONFIG environment variable
[17:52] -kubuntu-ci:#kubuntu-devel- Yippee, build fixed!
[17:52] -kubuntu-ci:#kubuntu-devel- Yippee, build fixed!
[17:52] -kubuntu-ci:#kubuntu-devel- Project xenial_unstable_grantlee-editor build #19: FIXED in 15 min: http://kci.pangea.pub/job/xenial_unstable_grantlee-editor/19/
[17:52] -kubuntu-ci:#kubuntu-devel- Project zesty_unstable_grantlee-editor build #17: FIXED in 15 min: http://kci.pangea.pub/job/zesty_unstable_grantlee-editor/17/
[17:52] <DarinMiller> please tell
[17:52] <acheronuk> ahoneybun: i.e. simulate what will happen for them it we dump the contents of backport-landing into backports ppa
[17:53] <wxl> so just set GIT_CONFIG=/path/to/some/.gitconfig and it will automatically use it
[17:53] <ahoneybun> acheronuk: just for 16.10 though?
[17:53] <acheronuk> ahoneybun: nothing to do with 16.10
[17:53] <wxl> i have a config specific to work so i need to be able to override easily without removing/replacing
[17:53] <acheronuk> ahoneybun: I'm talking about 16.04
[17:53] <ahoneybun> oh right
[17:54]  * DarinMiller noted GIT_CONFIG feature...
[17:54] <ahoneybun> backports has 5.6.5 for 16.04
[17:54] <BluesKaj> ahoneybun, what's up for the testers?
[17:54] <acheronuk> ahoneybun: yep. so a lot of people will already have that. so need to check what will happen for them
[17:54] <wxl> BluesKaj: i asked who they were. you gvot pinged. sorry
[17:54] <ahoneybun> BluesKaj: sorry was just showing wxl about that
[17:55] <BluesKaj> np guys
[17:55] <acheronuk> ahoneybun: I will add basic test cases to the trello card
[17:55] <ahoneybun> acheronuk: super cool
[17:55] <ahoneybun> thanks
[17:55] <wxl> can someone change the topic to maybe point out the fact that testing on alpha 1 to begin 27 Dec 2016?
[17:56] <BluesKaj> wxi ok good looking forward to that
[17:56] <wxl> ugh i can't remember the alias in gitconfig
[17:57] <wxl> isn't it [url "git+ssh://etc" ] ????
[17:57] <wxl> nm
[17:57] <wxl> whitespace
[17:57] <wxl> stupid
[17:57] <DarinMiller> cat ~/.gitconfig
[17:57] <wxl> i guess when you git config -l it makes sense tho
[17:57] <ahoneybun> wxl: I'm not sure what to remove to add that
[17:58] <wxl> it ends up being url.yr-url-here.insteadof=kubuntu
[17:58] <wxl> so the whitespace probably confuses it
[17:58] <wxl> url.yr-url-here .insteadof=kubuntu
[17:58] <wxl> ahoneybun: bad use a pronouns. need more context :)
[17:59] <ahoneybun> well poke tsimonq2 about that
[17:59] <ahoneybun> not me
[17:59] <ahoneybun> lol
[17:59] <wxl> ahoneybun: i figured it out
[17:59]  * ahoneybun plays with his new Fire tablet
[18:01] <wxl> ugh
[18:01] <wxl> acheronuk: could you paste your url.<baseurl>.insteadof=<alias> for kubuntu-packaging? i'm doing something wrong somewhere.
[18:03] <DarinMiller> [url<EMAIL_ADDRESS>   insteadof = kp:
[18:03] <DarinMiller> worked for me this morning
[18:03] <wxl> weird
[18:03] <wxl> totally right
[18:03] <DarinMiller> missing slash at the end?
[18:03] <wxl> maybe it needs a new line??
[18:03] <wxl> nope
[18:04] <wxl> it keeps trying to resolve kp as a hostname
[18:05] <DarinMiller> do you have kp defined more than once?  After yesterday's session I had duplicate commands from Rik and Simon...
[18:05] <wxl> no :(
[18:07] <DarinMiller> my current .gitconifg .... https://paste.ubuntu.com/23533408/
[18:08] <mparillo> I saw a call for testers. sudo add-apt-repository ppa:kubuntu-ppa/backports-landing ? To 16.04?
[18:08] <wxl> mparillo: the call for testers was technically a mistake
[18:08] <acheronuk> wxl: http://paste.ubuntu.com/23533417/
[18:09] <wxl> and you git clone kp:repo right? jeez wtf
[18:09] <acheronuk> mparillo: if you are brave. I would like to do a few more tests myself before making that more general call
[18:10] <mparillo> acheronuk: No problem. If I mess it up, I will just boot to ZZ. So, sudo add-apt-repository ppa:kubuntu-ppa/backports-landing to 16.04?
[18:10] <DarinMiller> yes, worked perfectly this morning on a backported 16.10 box.  What package is failing?
[18:11] <wxl> DarinMiller: it's not a package issue. it's the fact that ssh is trying to take the alias (e.g. kp) and resolve it as if it were a hostname
[18:11] <mparillo> Oh, 16.10. Sorry. I missed that. For some reason I get a funny TPM error on 16.10, but not on 16.04 or ZZ on my triple-boot laptop.
[18:12] <acheronuk> mparillo: yes. that ppa on it's own should do for 16.04 or 16.10
[18:12] <DarinMiller> ohhhhh
[18:12] <mparillo> Then I will try 16.04.
[18:15] <DarinMiller> wxl: git config -l shows the correct alias?
[18:16] <wxl><EMAIL_ADDRESS>[18:18] <DarinMiller> git --version?
[18:18] <DarinMiller> 2.9.3 here
[18:21] <mparillo> Downloading now: 494 upgraded, 53 newly installed, 8 to remove and 0 not upgraded.
[18:21] <wxl> um well 1.9.1 so i guess that could be a thing
[18:22] <mparillo> Just above there was a warning AppStream cache update completed, but some metadata was ignored due to errors.
[18:22] <wxl> man page says insteadOf
[18:23] <wxl> still didn't work
[18:24] <acheronuk> mparillo: yep. I had that. appstream data in 16.04 is not great, so I think that is expected
[18:25] <mparillo> I already had the 'regular' backports enabled so I was on Plasma 5.6.5 / FW 5.23.
[18:25] <acheronuk> DarinMiller: gimme a shout when you want to discuss that lintian error
[18:27] <acheronuk> mparillo: cool. I tested that when things were in the staging ppas, but haven't yet tried that case with the single ppa. so your feedback will be great :)
[18:28] <mparillo> Preparing and unpacking. The status hashes show maybe a quarter of the way through.
[18:30] <mparillo> Just out of curiosity: Why backports-landing first before the ZZ archive?
[18:35] <DarinMiller> acheronuk:  OK ready.  I am not sure how https://lintian.debian.org/tags/desktop-command-not-in-package.html applies to akonadi-calendar-tools
[18:36] <DarinMiller> acheronuk: As I said to wxl above, I not sure if I am barking up the right tree (I may be in the wrong forest...)
[18:37] <wxl> weird
[18:38] <DarinMiller> acheronuk: I re-read the start lintian section:  I think I should be looking here: https://lintian.debian.org/tags/bad-distribution-in-changes-file.html
[18:38] <wxl> well i moved away from the whole GIT_CONFIG thing and it behaves better
[18:38]  * wxl shrugs
[18:38] <wxl> DarinMiller: the lintian section gives a lot of errors but the only one you should pay attention to is the one KCI reports
[18:39] <ahoneybun> acheronuk: about kalzium
[18:39] <ahoneybun> one of the packages it is missing is: libqt5opengl5-dev
[18:39] <ahoneybun> but there is a qt4 version in the build
[18:39] <ahoneybun> *control file
[18:39] <mparillo> apt seemed to run cleanly. Re-booting.
[18:40] <wxl> well
[18:40] <wxl> maybe the issue is that there IS no desktop command
[18:40] <acheronuk> DarinMiller: the bad distribution for zesty is just an artefact of not all the build tools knowing about zesty's existence yet. don't worry about that
[18:41] <DarinMiller> acheronuk: so the PC KCI warning says: KCI-W :: W: konsolekalendar: desktop-command-not-in-package usr/share/applications/konsolekalendar.desktop kdialog
[18:41] <acheronuk> ahoneybun: I'll get to that shortly
[18:42] <acheronuk> DarinMiller: yep. that is the issue at hand
[18:43] <wxl> um
[18:43] <wxl> so
[18:43] <DarinMiller> acheronuk: I've poked around in the akonadi-calendar-tools files, but I am still clueless.   Please give a hint without giving away the issue.
[18:43] <ahoneybun> acheronuk: so don't touch it?
[18:43] <wxl> kdialog doesn't seem like it would be a command of konsolekalendar
[18:44] <acheronuk> this is a bit confusing, as you need to know the history. akonadi-calendar-tools used to be part of the huge kdepim source package
[18:44] <wxl> and kdialog wouldn't require a desktop command anyways
[18:44] <wxl> so is the problem that there's a lintian-overrides in there specifing it to ignore something that's not even there anymore/
[18:45] <acheronuk> this was then split into separate git repos by kde, so we now have individual source packages.
[18:46] <acheronuk> this is the old kdepim packaging -> https://git.launchpad.net/~kubuntu-packagers/kubuntu-packaging/+git/kdepim/tree/debian?h=kubuntu_unstable
[18:46] <DarinMiller> so is this a control file issue and I need to sort the depends?
[18:48] <mparillo> I had to sudo poweroff (the kicker > leave shortcuts did not work). I successfully restarted and got the new blinding sddm theme, a different plymouth (I assume), and the new desktop background. Konversation and rekonq still work. My super key now works. kinfocenter reports Plasma 5.8.3, and Frameworks 5.27 and Qt 5.6.1. Dolphin reports Version 16.04.3
[18:50] <acheronuk> DarinMiller: so the old kdepim packaging I linked to produced a konsolekalendar sub package. you can see the konsolekalendar.install file there
[18:52] <wxl> etc/xdg/console.categories needs to be added?
[18:53] <acheronuk> DarinMiller: you can also see that in the old kdepim packaging they had a konsolekalendar.lintian-overrides file
[18:53] <wxl> ..which is the same as the one we have now
[18:53] <acheronuk> containing "konsolekalendar: desktop-command-not-in-package usr/share/applications/konsolekalendar.desktop kdialog"
[18:54] <mparillo> The new Discover looks a lot nicer.
[18:54] <wxl> a LOT
[18:54] <acheronuk> wxl: which is the same as what lintian is complaining about in the new split package. i.e. we somehow lost that override when the package was split
[18:55] <acheronuk> as for the reason it is moaning.......
[18:55] <wxl> yessssss
[18:56] <acheronuk> if you dig into the code, you will see that the konsolekalendar.desktop file contains the line:
[18:56] <acheronuk> Exec=kdialog --sorry "konsolekalendar is a command-line only program.  Please read the handbook at help:/konsolekalendar for more info."
[18:57] <wxl> that code not necessarily being in this repo? or do i need to change to the right branch or what?
[18:57] <acheronuk> in other words, that desktop file is there so should anyone try to run the program via a menu or gui, kiadiog is run to warn you not to do that
[18:58] <acheronuk> wxl: that 'code' is the KDE code we are packaging
[18:58] <wxl> i get that much :)
[18:59] <wxl> but how do i find it?
[18:59] <acheronuk> https://cgit.kde.org/akonadi-calendar-tools.git/tree/konsolekalendar/konsolekalendar.desktop
[18:59] <wxl> right go upstream
[18:59] <wxl> got it :)
[19:00] <acheronuk> wxl: sorry. I'm try to be clear for both you and Darin, so spelling things out
[19:01] <acheronuk> so, it is intended that the kdialog command is in that desktop file. but lintian is not smart enough to know the reason, and sees it as a possible mistake. so warns you
[19:03] <acheronuk> which is why on the previous packaging we had an override in konsolekalendar.lintian-overrides to squish that warning
[19:03] <DarinMiller> digesting...
[19:05] <acheronuk> and is why IMO we can reinstate that override here. as the reasoning still holds
[19:05] <DarinMiller> Still in a fog:  konsolekalendar.lintian-overrides in the akonadi-calendar-tools package set I downloaded this morning has "konsolekalendar: desktop-command-not-in-package usr/share/applications/konsolekalendar.desktop kdialog"
[19:06] <wxl> acheronuk: but that file is already here
[19:07] <acheronuk> is it in the kubuntu_unstable branch?
[19:07] <wxl> oh go
[19:07] <wxl> s/g/h/
[19:07] <acheronuk> you may be looking at master, which is the old master branch from before the 'split'
[19:08] <DarinMiller> oh.. switch now....
[19:08] <wxl> this is where having a schroot setup with kci's code in it would be helpful because kubuntu_unstable is totally without any installs or lintian-overrides and there's a ton in master
[19:08] <DarinMiller> switching...
[19:10] <wxl> it would seem sensible that the konsolekalendar.install would be added
[19:10] <DarinMiller> So just copy the konsolekalendar.lintian-overrides file from master to _unstable?
[19:10] <wxl> from what i can tell the only .desktop in the code for is for konsolekalendar, suggesting the other .installs/lintian-overrides are irrelevant
[19:10] <acheronuk> kubuntu_unstable now packages for this single split part of what used to be a multipackage kdepim
[19:10] <wxl> but doesn't it make sense to also grab the konsolekalendar.install?
[19:11] <acheronuk> single package can do without a .install file
[19:11] <wxl> oh i guess that makes sense
[19:11] <wxl> are there conventions for naming the lintian-overrides when dealing with a single package?
[19:12] <wxl> why am i asking you when i have the debian policy manual?
[19:12] <acheronuk> DarinMiller: not quite. if this is a single package that doesn't use .install files, then the overide just goes in a file called 'lintian-overrides'
[19:12] <wxl> ah there you go
[19:13] <wxl> so there you go, DarinMiller. this one's a home run :)
[19:13] <DarinMiller> Same content as konsolekalendar.lintian-overrides
[19:13] <DarinMiller> ?
[19:13] <acheronuk> you only have to prefix it with a subpackage/install file name if you have the package using multiple of those
[19:13] <acheronuk> DarinMiller: yep
[19:14] <DarinMiller> cool.  fixing now...
[19:16] <acheronuk> I had to go off and do a bit of digging on this one ;)
[19:16]  * DarinMiller Needs to find "magic wand of knowlegde" like Rik's.  Goolge foo is next to impossible when one does not know the question...
[19:16] <acheronuk> Often things are a lot simpler, but sometimes you also have to 'play detective'
[19:16] <wxl> well knowing the information about it being split would have helped
[19:17] <wxl> i kind of discovered that with kppp but that was a little more obvious
[19:17] <wxl> although the info is there
[19:17] <wxl> compare `grep Package debian/control` on the two branches
[19:18] <wxl> that kind of gives it away :)
[19:18] <acheronuk> you will quickly get in the loop. 6 months ago I would have been utterly stumped
[19:18] <wxl> XD
[19:18] <wxl> that's what i was saying last night. i just neeed a little more experience. i think i have a decent understanding of the tools and i'm good with basic logic XD
[19:19] <wxl> although if all you need for ninja is an ability to grok terminology/tools, i could probably get it :)
[19:19] <DarinMiller> wxl: please expand on the grep commands-grep'ing Packages is new to me...
[19:20]  * acheronuk will be back in 5-10 mins
[19:21] <mparillo> IMHO, I think backports-landing is ready for broader testing. I re-booted using the kicker menu. One big glitch: After the update, I needed to sudo poweroff. One minor glitch: I think pressing the super key twice should cause the kicker to disappear again. Otherwise, thanks for the much-anticipated upgrade.
[19:22] <wxl> DarinMiller: the best thing about using git is being able to use standard linux (or for you vrms'ers, GNU) tools. this is why i think git GUI tools are silly. grep is one of your absolute best friends. have you ever used grep at all?
[19:23] <wxl> find, too, is another one you shoudl know btw
[19:23] <DarinMiller> wxl: I have used grep, egrep am familir with some of their options ( -v, -n etc).  but that about it.
[19:24] <wxl> DarinMiller: ok, well if you know the basic use, you can figure out the rest. the part that's probably not clear is why i searched for Packages in control
[19:24] <wxl> DarinMiller: for that, consult the debian policy manual (let me know if you need a link)
[19:25] <wxl> DarinMiller: everything we deal with is a "source package," which is to say that it is used to build a final binary. in some cases, it builds MANY binaries. this is traditionally what we think of when we say "source package"
[19:25] <wxl> DarinMiller: the control file will have a "Package" entry for every binary package that is built
[19:25] <DarinMiller> I have also written scripts using find, awk, and other misc shell commands so though I am not super proficent with many of them, they are familiar.
[19:26] <wxl> DarinMiller: if you look for the Package entries in unstable you find only konsolekalendar. in master, though (the old code), you find 16 entries (i cheated piping that grep into wc)
[19:26] <wxl> DarinMiller: that suggests that something changed, namely that it was split off from a larger source package
[19:30] <DarinMiller> wxl: had to "man wc" ....ah, counts words
[19:30] <wxl> XD
[19:30] <wxl> well counts stuff
[19:31] <wxl> technically i would have wanted to `wc -l` to have it print newline counts
[19:31] <wxl> but the default display is "newline, word, byte" so i just look at the first value
[19:33] <DarinMiller> wxl: oh, when you said `grep Package debian/control`, I thought you were referrencing a remote grep via an URL.  That is what I wanted to see.  But, now I think you mean git checkout each branch and grep from checkout directory. Yes?
[19:34] <wxl> yep
[19:34] <DarinMiller> Dang, I was hoping for something fancy.
[19:34] <wxl> i mean jeez dude if you want to go that route we can come up with something :)
[19:34] <DarinMiller> :)
[19:36] <DarinMiller> I assume I leave konsolekalendar in the lintian-overrides files even though the other packages are no longer included?
[19:39] <wxl> DarinMiller: don't change the content
[19:39] <DarinMiller> And the source directory had a another lintian-overrides file.  <So much to learn>.....
[19:39] <DarinMiller> OK, I just changed the name.
[19:41] <ahoneybun> mparillo: https://goo.gl/forms/jHZBotLS6oZ80kCS2
[19:41] <ahoneybun> if you would fill this out about your experience with the upgrade
[19:41] <ahoneybun> with backport-landing
[19:44] <mparillo> Done. Everything on the checkbox worked (I tested more than that) except I did not test suspend / resume, because I have never done it, so I lack a good frame of reference. As I said, if you warn testers that they may need to sudo poweroff, I think it is ready for broad testing. BTW, I have tested on Manjaro (also plasma 5.8.3), and the second time you hit the super key, the kicker menu disappears.
[19:44] <ahoneybun> thanks mparillo
[19:45] <mparillo> For some reason, with backports-landing, I need to hit escape or click on my desktop to get rid of the kicker menu.
[19:45] <ahoneybun> same here on YY
[19:45] <ahoneybun> odd
[19:45] <ahoneybun> wxl: updated the topic
[19:46] <acheronuk> DarinMiller: yes, it stays as konsolekalendar, as that it the name of the package to be built. even though the source is called akonadi-calendar-tools
[19:46] <wxl> ahoneybun: thank you :)
[19:46] <ahoneybun> I'm sure Simon will find something wrong with my other changes
[19:46] <ahoneybun> np wxl
[19:47] <mparillo> SDDM still lacks the guest session LightDM had, but I suppose that is upstream (closed) https://github.com/sddm/sddm/issues/322
[19:47] <ahoneybun> wxl: they just snapped Unity 8
[19:48] <ahoneybun> I see an option for it in SDDM though
[19:48] <ahoneybun> never used it
[19:50] <mparillo> Hmmm. Maybe I need to look closer. Not a guest user you added, but in LightDM, evertying would mount to /tmp and get cleaned out every time.
[20:12] <acheronuk> ahoneybun: kalzium
[20:12] <acheronuk> nothing qt4 here? https://git.launchpad.net/~kubuntu-packagers/kubuntu-packaging/+git/kalzium/tree/debian/control?h=kubuntu_unstable
[20:13] <acheronuk> kalzium recently ported to KF5, so maybe you were looking on a branch other than kubuntu_unstable?
[20:13] <ahoneybun> nope
[20:13] <ahoneybun> I don't think so
[20:14] <ahoneybun> mm maybe
[20:14] <ahoneybun> yea my bad
[20:14] <acheronuk> easy to do!
[20:14] <ahoneybun> acheronuk: you said not to touch it though
[20:15] <acheronuk> did I?
[20:15] <ahoneybun> well  something like that
[20:16] <ahoneybun> 1] <acheronuk> ahoneybun: I'll get to that shortly
[20:16] <ahoneybun> that I'm guessing
[20:16] <acheronuk> I said I would get to it shortly. i.e. discuss it with you once I had finished taking to Darin/wxl
[20:16] <ahoneybun> ok np
[20:16] <acheronuk> sorry that wasn't clear
[20:16] <ahoneybun> my bad'
[20:17] <wxl> acheronuk: i'm good at this point unless you need something else. afaik DarinMiller was working on the fix.
[20:17] <acheronuk> so you have worked out what dep needs adding?
[20:17] <wxl> ooh well one step at a time i guess XD
[20:18] <acheronuk> wxl: great. I have fixed and tested my end in pbuilder, so I know it works. ;)
[20:19] <wxl> i have no clue about the additional dependency, but haven't tried to rebuild
[20:19] <wxl> i don't have sbuild set up over here at work
[20:19] <acheronuk> sorry wxl, that was @ ahoneybun
[20:19] <wxl> oh hahahah
[20:19] <ahoneybun> mm?
[20:19] <acheronuk> ahoneybun: so you have worked out what dep needs adding?
[20:22] <mparillo> After installing the backports-landing PPA, I like the look of the new Discover, but has anybody noticed it takes a long time to load the sources list?
[20:22] <ahoneybun> acheronuk: the new one yes
[20:22] <ahoneybun> one of the packages it is missing is: libqt5opengl5-dev
[20:23] <acheronuk> yep
[20:26] <acheronuk> DarinMiller: you got my comment?
[20:26] <DarinMiller> sry, I was on another channel... reading now...
[20:29] <DarinMiller> sry, still clueless after reading.. should I be attempting to assist Aaron?
[20:30] <acheronuk> DarinMiller: you remember the bit about changelog entries last night?
[20:30] <ahoneybun> ?
[20:31] <acheronuk> DarinMiller: maybe add something like? http://paste.ubuntu.com/23534086/
[20:32] <acheronuk> ahoneybun: ?
[20:32] <ahoneybun> acheronuk: idk DarinMiller saiud my name
[20:32] <ahoneybun> *said
[20:32] <DarinMiller> acheronuk: I remember to "keep them simple but sufficient to understand the change"
 santa_: incidenceeditor and kdepim im Xenial backports rebuilt and copied over to landing, as they were depending on the old non debianabimanager'd library versions
[20:32] <santa_> got it, ok
[20:33] <acheronuk> santa_: cool. was just a FYI
[20:33] <santa_> acheronuk: I'm going to deal with part of ahoneybun stuff you reported ¿yesterday?
[20:34] <acheronuk> santa_: I tried in a VM earlier, and could not reproduce those errors using just backports-landing
[20:35] <santa_> yes, but that doesn't mean the problems are there of course
[20:35] <acheronuk> but there is at least a file moved issue on one of those errors that others might get
[20:35] <santa_> they are all file moving problems I presume
[20:36] <ahoneybun> I think I should have used dist-upgrade and not upgrade
[20:36] <ahoneybun> as that upgraded everything with no issues
[20:36] <DarinMiller> acheronuk: OK, will do.
[20:38] <acheronuk> santa_: looks like we are both on the same page then :)
[20:39] <santa_> yes
[20:51]  * acheronuk fires up testing VM
[21:01] <DarinMiller> acheronuk:  I ran "git commit --amend", but my git push fails because my current branch is behind.  git pull did not fix... need advice.
[21:09] <clivejo> does anyone happen to know what builds libkpmcore-dev ?
[21:09] <clivejo> I think its KDE Partition Manager
[21:10] <acheronuk> DarinMiller: maybe 'git push --force' but that is not advisable on a public repo
[21:12] <DarinMiller> acheronuk: I was trying to upload to my lp site for the akonadi-calendar-tools mp.
[21:12] <acheronuk> DarinMiller: yep, I realise that
[21:13] <DarinMiller> acheronuk: so just restart from the beginning and delete my current  mp?
[21:15] <acheronuk> I mean it's not advisable to say force a rewrite of an already pushed commit to a public repo, like directly to our packaging, as someone or something may have cloned/pulled the 1st change you pushed. if you then rewrite it and they pull again, they will get a mess up history
[21:16] <acheronuk> might not matter when doing to your personal LP git, but if you want to redo the clone, changes and merger proposal, then that is also good practice
[21:16] <DarinMiller> acheronuk: so what is the correct way to update changelog at this point?
[21:16] <ahoneybun> acheronuk: do I add the backports-landing then remove the staging stuff?
[21:18] <acheronuk> ahoneybun: yep. don't have the staging in there now please. we want to test backports-landing on its own
[21:19] <acheronuk> DarinMiller: at what point? I'm not sure what you are doing? still wanting to amend the commit you pushed? or start from scratch? or do you mean how to actually add the changelog with the dch command?
[21:23] <valorie>  might be best to ask in #git ?
[21:24] <valorie> the experts live in there
[21:24] <ahoneybun> acheronuk: all done on the desktop
[21:24] <wxl> um
[21:25] <wxl> i guess i should have a changelog entry on my commit from last night huh?
[21:25] <ahoneybun> I'm thinking if I grab an SSD today I might do a reinstall of Xenial
[21:25] <ahoneybun> so we can have real HW for that
[21:28] <wxl> acheronuk: should i have had a changelog with https://code.launchpad.net/~wxl/kubuntu-packaging/+git/kppp/+merge/311791?
[21:30] -kubuntu-ci:#kubuntu-devel- Project xenial_unstable_audiocd-kio build #60: STILL FAILING in 37 sec: http://kci.pangea.pub/job/xenial_unstable_audiocd-kio/60/
[21:30] -kubuntu-ci:#kubuntu-devel- Project yakkety_unstable_audiocd-kio build #62: STILL FAILING in 41 sec: http://kci.pangea.pub/job/yakkety_unstable_audiocd-kio/62/
[21:30] -kubuntu-ci:#kubuntu-devel- Project zesty_unstable_audiocd-kio build #9: STILL FAILING in 42 sec: http://kci.pangea.pub/job/zesty_unstable_audiocd-kio/9/
[21:34] <acheronuk> wxl: probably. really trivial changes like fixing a typo you made, or correcting or adding to your last change a little may not need one. the changelog entries are there so someone can get a good idea of what significant or impactful changes have been made without having to dig in the history to look for them. or at least know that a change has been made that they might want to know and look at
[21:36] <acheronuk> ahoneybun: on a real machine would be great :)
[21:36] <valorie> some typos are important!
[21:36] <valorie> I'll try later today to update my XX box too, which is also real hardware
 I'll install it on my Intel NUC once I get an image made
 I need backports and backports-landing right?
[21:37] <wxl> acheronuk: thx for putting my mind at ease :)
[21:38] <acheronuk> valorie: true. personally I look at it in the fashion of, "is there a reason to not add a changelog entry?", rather than "should I add one?"
[21:39] <valorie> documentation ++
[21:42] <wxl> echo $documentation
[21:42] <wxl> 3
[21:44] -kubuntu-ci:#kubuntu-devel- Project yakkety_unstable_audiocd-kio build #63: STILL FAILING in 11 min: http://kci.pangea.pub/job/yakkety_unstable_audiocd-kio/63/
[21:45] -kubuntu-ci:#kubuntu-devel- Project xenial_unstable_audiocd-kio build #61: STILL FAILING in 11 min: http://kci.pangea.pub/job/xenial_unstable_audiocd-kio/61/
[21:45] -kubuntu-ci:#kubuntu-devel- Project zesty_unstable_audiocd-kio build #10: STILL FAILING in 12 min: http://kci.pangea.pub/job/zesty_unstable_audiocd-kio/10/
[21:46] <acheronuk> well, git documents via your commit messages as well. changelog for the packaging itself is something slightly different, and won't always need an entry for every commit
[21:47] <wxl> in reality that would probably be ridiculously annoying
[21:48] <acheronuk> like most things, it's a judgement call. basically I think if I was reading the changelog without access to the git history, would I want to know about this change?
[21:51] <DarinMiller> acheronuk: I deleted and re-added the branch on LP but have not pushed MP as my comment lacks a signature and the formatting is not consistent with yours.  Do you have a fancy way to generate: " -- Rik Mills<EMAIL_ADDRESS>Mon, 21 Nov 2016 15:30:59 +0000"
[21:56] -kubuntu-ci:#kubuntu-devel- Project xenial_unstable_audiocd-kio build #62: STILL FAILING in 4 min 56 sec: http://kci.pangea.pub/job/xenial_unstable_audiocd-kio/62/
[21:56] -kubuntu-ci:#kubuntu-devel- Project yakkety_unstable_audiocd-kio build #64: STILL FAILING in 4 min 57 sec: http://kci.pangea.pub/job/yakkety_unstable_audiocd-kio/64/
[21:56] -kubuntu-ci:#kubuntu-devel- Project zesty_unstable_audiocd-kio build #11: STILL FAILING in 4 min 58 sec: http://kci.pangea.pub/job/zesty_unstable_audiocd-kio/11/
[21:58] <acheronuk> DarinMiller: what I posted is a git diff, so that is already there and is just context to the changes. the actual changes are just the lines beginning with a single +
[22:00] <acheronuk> also I see on your LP branch that you added the comment to your commit message, and not the debian/changelog file. you need to run the command 'dch' to add a debian/changelog message before you git add and git commit
[22:03] <acheronuk> (1) make your changes
[22:03] <acheronuk> (2) run 'dch' to add a changlog entry if you want one
[22:04] <acheronuk> (2) git add whatever files got changed or added
[22:04] <acheronuk> (4) git commit with whatever commit message you want
[22:04] <acheronuk> (5) git push
[22:07] -kubuntu-ci:#kubuntu-devel- Project zesty_unstable_audiocd-kio build #12: STILL FAILING in 5 min 25 sec: http://kci.pangea.pub/job/zesty_unstable_audiocd-kio/12/
[22:07] -kubuntu-ci:#kubuntu-devel- Project xenial_unstable_audiocd-kio build #63: STILL FAILING in 5 min 44 sec: http://kci.pangea.pub/job/xenial_unstable_audiocd-kio/63/
[22:07] -kubuntu-ci:#kubuntu-devel- Project yakkety_unstable_audiocd-kio build #65: STILL FAILING in 5 min 51 sec: http://kci.pangea.pub/job/yakkety_unstable_audiocd-kio/65/
[22:14] -kubuntu-ci:#kubuntu-devel- Project yakkety_unstable_audiocd-kio build #66: STILL FAILING in 3 min 50 sec: http://kci.pangea.pub/job/yakkety_unstable_audiocd-kio/66/
[22:15] -kubuntu-ci:#kubuntu-devel- Project zesty_unstable_audiocd-kio build #13: STILL FAILING in 4 min 50 sec: http://kci.pangea.pub/job/zesty_unstable_audiocd-kio/13/
[22:16] -kubuntu-ci:#kubuntu-devel- Project xenial_unstable_audiocd-kio build #64: STILL FAILING in 6 min 14 sec: http://kci.pangea.pub/job/xenial_unstable_audiocd-kio/64/
[22:18] <DarinMiller> I checked in the debian packaging guidelines for changelog ediquette and auto signing and did not find either.
[22:19] <DarinMiller>  I am confused by the dch behavior as it did not auto add a signature and it did not put my comments at the top.  Should my comments be at the top? Will my signature be auto-added or is that manual?
[22:20] <DarinMiller> this is what dch proposed for my comments: https://paste.ubuntu.com/23534530/
[22:21] -kubuntu-ci:#kubuntu-devel- Project xenial_unstable_audiocd-kio build #65: STILL FAILING in 4 min 44 sec: http://kci.pangea.pub/job/xenial_unstable_audiocd-kio/65/
[22:22] -kubuntu-ci:#kubuntu-devel- Project yakkety_unstable_audiocd-kio build #67: STILL FAILING in 4 min 47 sec: http://kci.pangea.pub/job/yakkety_unstable_audiocd-kio/67/
[22:22] -kubuntu-ci:#kubuntu-devel- Project zesty_unstable_audiocd-kio build #14: STILL FAILING in 5 min 20 sec: http://kci.pangea.pub/job/zesty_unstable_audiocd-kio/14/
[22:25] <acheronuk> DarinMiller: that is what it should do. there is only a whole new changelog entry when we release a new version or make a new unreleased one
[22:26] <acheronuk> the version in kubuntu_unstable shows UNRELEASED, so this is a work in progress toward a new released version
[22:27]  * wxl needs to find a more significant change so he can actually get his name in lights— err, changelog
[22:27] <valorie> :-)
[22:28] <acheronuk> as such, each changelog entry you make with a plain dch command adds your comment in it's own subsection on the current version
[22:29] <acheronuk> and the name and email stays as whoever made the initial change to make that new potential version
[22:31] -kubuntu-ci:#kubuntu-devel- Project xenial_unstable_audiocd-kio build #66: STILL FAILING in 4 min 42 sec: http://kci.pangea.pub/job/xenial_unstable_audiocd-kio/66/
[22:37] <wxl> acheronuk: i see kalarm is also part of the kdepim split, but the fix for http://kci.pangea.pub/job/zesty_unstable_kalarm/20/parsed_console/ is not obvious to me.
[22:39] <wxl> i have the offending file https://cgit.kde.org/kalarm.git/tree/src/kalarm.autostart.desktop
[22:39] <wxl> which calls kalarmautostart which is build from https://cgit.kde.org/kalarm.git/tree/src/autostart/autostart.cpp
[22:39] <wxl> that said it should be an ELF
 Afternoon
[22:40] <wxl> hey stinky
 (Document) https://irc-attachments.kde.org/WI0aehcW/file_1236.mp4
[22:43] <wxl> XD
[22:43] <DarinMiller> acheronuk: Wow. there's an infinite number of ways to do packaging incorrectly and I definitely disovered more than I wanted today.  MP submitted finally with changelog....
 You did a bad, ahoneybun
 Hey Darin :)
[22:44] <DarinMiller> Hi Simon :)
[22:45] <wxl> ahoneybun: let me interpret the simon speak for you: "i appreciate everything you do but i think you made a mistake"
[22:47] <tsimonq2> ahoneybun: AKA https://irc-attachments.kde.org/WI0aehcW/file_1236.mp4
[22:47] <tsimonq2> :P XD
[22:48] <acheronuk> wxl: that lintian warning in kalarm existed in the old kdepim for us and for debian. and has just been left as a warning. AFAIK nothing to be done about it
[22:50] <wxl> acheronuk: maybe we should add a lintian override?
[22:51] <tsimonq2> There, all fixed. :P
[22:58] <bipul> Hi
[22:58] <acheronuk> wxl: maybe add one. it's just that people seem to have consistently not done so for some time, and that makes me wonder if there is a reason not to in this case?
[22:59] <tsimonq2> Hello bipul. :D
[22:59] <tsimonq2> bipul: What brings you here? ;)
[22:59] <wxl> acheronuk: well what's the worst that can happen except that my merge proposal gets denied
[22:59] <bipul> You and contribution for ubuntu
[23:00] <acheronuk> wxl: true :)
[23:00] <bipul> Hi wxl
[23:00] <wxl> hai and welcome bipul
[23:00] <bipul> Hope you doing great.
[23:00] <wxl> wonderful actually
[23:00] <wxl> doing some packaging with this crazy lot
[23:00] <tsimonq2> ^ ;
[23:00] <tsimonq2> *:)
[23:00] <bipul> Great to see you happy
[23:01] <bipul> Wow love to learn from you.
[23:01] <tsimonq2> bipul: Want to learn some packaging? :D
[23:01] <bipul> :)
[23:01] <acheronuk> DarinMiller: yep, lots of ways to do things right and wrong. fun!
[23:01] -kubuntu-ci:#kubuntu-devel- Project yakkety_unstable_audiocd-kio build #68: STILL FAILING in 4 min 48 sec: http://kci.pangea.pub/job/yakkety_unstable_audiocd-kio/68/
[23:01] <tsimonq2> +1 ahoneybun
[23:01] <tsimonq2> whoops
[23:01] <tsimonq2> NEVER lol
[23:02] <tsimonq2> +1 acheronuk
[23:02] -kubuntu-ci:#kubuntu-devel- Project xenial_unstable_audiocd-kio build #67: STILL FAILING in 5 min 10 sec: http://kci.pangea.pub/job/xenial_unstable_audiocd-kio/67/
[23:02] <acheronuk> and I'm still learning a lot as I go
[23:03] -kubuntu-ci:#kubuntu-devel- Project zesty_unstable_audiocd-kio build #15: STILL FAILING in 6 min 48 sec: http://kci.pangea.pub/job/zesty_unstable_audiocd-kio/15/
[23:07] <wxl> acheronuk: do you think i should include the old lintian-overrides? probably not. i think i'll just wait
[23:08] <acheronuk> one step at a time is usually best if you are unsure
[23:09] <wxl> so with the changelog i know how to deal with multiple contributors, but do i change the signature to the most recent?
[23:09] <bipul> I am going to bed , see you all later
[23:09] <bipul> I am feeling very sleepyhead
[23:10] <tsimonq2> o/ bipul
[23:10] <wxl> night bipul
[23:11] -kubuntu-ci:#kubuntu-devel- Project yakkety_unstable_audiocd-kio build #69: STILL FAILING in 4 min 15 sec: http://kci.pangea.pub/job/yakkety_unstable_audiocd-kio/69/
[23:11] <acheronuk> wxl: no, it stays with the original person until a whole new version entry is made
[23:11] <wxl> acheronuk: thx
[23:11] -kubuntu-ci:#kubuntu-devel- Yippee, build fixed!
[23:11] -kubuntu-ci:#kubuntu-devel- Project xenial_unstable_akonadi-calendar-tools build #24: FIXED in 13 min: http://kci.pangea.pub/job/xenial_unstable_akonadi-calendar-tools/24/
[23:11] -kubuntu-ci:#kubuntu-devel- Yippee, build fixed!
[23:11] -kubuntu-ci:#kubuntu-devel- Project yakkety_unstable_akonadi-calendar-tools build #25: FIXED in 13 min: http://kci.pangea.pub/job/yakkety_unstable_akonadi-calendar-tools/25/
[23:11] -kubuntu-ci:#kubuntu-devel- Yippee, build fixed!
[23:11] -kubuntu-ci:#kubuntu-devel- Project zesty_unstable_akonadi-calendar-tools build #16: FIXED in 14 min: http://kci.pangea.pub/job/zesty_unstable_akonadi-calendar-tools/16/
[23:11] <acheronuk> \o/
[23:12] <tsimonq2> O_o
[23:12] -kubuntu-ci:#kubuntu-devel- Project xenial_unstable_audiocd-kio build #68: STILL FAILING in 4 min 44 sec: http://kci.pangea.pub/job/xenial_unstable_audiocd-kio/68/
[23:14] <wxl> acheronuk: how can i properly display in this merge proposal that it's bveen there forever?
[23:14] -kubuntu-ci:#kubuntu-devel- Project zesty_unstable_audiocd-kio build #16: STILL FAILING in 5 min 50 sec: http://kci.pangea.pub/job/zesty_unstable_audiocd-kio/16/
[23:35] <wxl> um so kcoreaddons is complaining about licenses
[23:35] <wxl> http://kci.pangea.pub/job/zesty_unstable_kcoreaddons/26/parsed_console/
[23:36] <wxl> ARTISTIC is not in copyright so that makes sense
[23:36] <wxl> but it's NOT tripping up on QPL_V1.0
[23:37] <wxl> https://cgit.kde.org/kcoreaddons.git/tree/src/lib/licenses btw
[23:37] <wxl> and it's complaining about all the ones that ARE there
[23:39] <wxl> i guess i can ignore the QPL thing
[23:39] <wxl> (for now)
[23:39] <valorie> Riddell is a good one to ask about licensing
[23:39] <wxl> this is not a legal issue, admittedly
[23:40] <valorie> also: check how neon does it, because he knows his stuff
[23:40] <wxl> bizarre
[23:40] <valorie> KDE is picky about licensing
[23:40] <wxl> that was added in june too
[23:40] <valorie> as is Debian
[23:40] <valorie> which is good for all of us
[23:40] <valorie> sort of late in Riddell's day though
[23:40] <wxl> the issue is not pickiness regarding licenses
[23:41] <wxl> it's more the issue that it's complaining that it can't parse all the licenses out of copyright
[23:41] <wxl> they're all in the code itself
[23:42] <tsimonq2> wxl: https://irc-attachments.kde.org/WI0aehcW/file_1236.mp4
[23:42] <tsimonq2> :P
[23:42] <tsimonq2> Well the MP
[23:44] <valorie> wxl: right, but getting them readable is important too


[06:12] <lordievader> Good morning
[08:45] <diogenes_> !dual
[08:45] <diogenes_> !dual boot
[11:18] <BluesKaj> Howdy folks
[13:01] <Alabalistic> Nobody is asking for Help, Because Everityng work so PERFECT
[13:01] <Alabalistic> Kubunto Fanboyyyy
[15:20] <Oderus> hi. wondering if you guys could have a look at an issue I am having exporting a QTCurve theme. there is a thread here and a screenshot. https://www.kubuntuforums.net/showthread.php/75469-QTCurve-Unable-to-Export?p=427551
[19:01] <big_pannard> iop
[19:50] <il> il is here
[19:50] <il> !
[20:49] <blkhawk> lo
[20:53] <blkhawk> anyone else getting weird graphical glitches since yesterdays mesa gfx driver upgrade with an amd gpu? certain accelerated surfaces create garbage for me then cause everything to crash
[20:57] <blkhawk> pretty much all of plasma seems to be affexted - some more than others
[21:02] <tyler82> hi
[21:02] <tyler82> anybody has HMA VPN working on 18.04 LTS?
[21:03] <tyler82> i just can not set it up to work
[21:04] <tyler82> NordVPN works fine but if i want to set up the HMA with the same type of protocol it just does not work.
[21:05] <tyler82> Of course i have subsription of both VPN company. on my phone works well both. i have issue only in Kubuntu. On Ubuntu was working fine both...
[21:09] <blkhawk> reverted the gpu drivers - so if anybody has the same trouble i suggest doin the same


[00:01] <gomiboy> pietro10: check the settings under System Settings -> Application Appearance -> GTK
[00:02] <pietro10> I did; it's font rendering that's wrong, not that the font itself is wrong
[00:03] <pietro10> the best explanation I can give is that the kerning is nonexistent and some characters, like t, are very wide
[00:03] <qdata> try qtcurve as a substitute for oxygen theme to eliminate a possibility of a theme problem; oxygen theme(s) has had problems before
[00:05]  * gomiboy had to check what kerning means :D
[00:06] <qdata> also consider if it isn't a theme problem per se, maybe you have a mix of different versions from different repos of the rendering engines such as freetype2
[00:07]  * qdata has no way of knowing what you've done to your system
[00:08] <pietro10> this is off a fresh install
[00:08] <pietro10> but thanks
[00:08] <qdata> I've also seen Qt cause font render trouble, although very rare - some of these I still see currently and these are Qt bugs
[00:09] <qdata> fresh install fo 13.10 or 14.x?
[00:10] <pietro10> 14.x (have tried asking in +1 though)
[00:10] <pietro10> it was more fun in the past when making ~/.fontconfig would have this effec ton EVERY PROGRAM though :D
[00:10] <pietro10> making .fontconfig at all, even blank
[00:10] <qdata> well, 14.x is alpha code and not surprised something broken
[00:11] <qdata> if you're a user and not a developer or bug tester you're better off with 13,10
[00:11] <pietro10> 13.10 had weird issues fo rme
[00:11] <pietro10> and I am a developer (though not of KDE itself)
[00:12] <qdata> yeah - 13.04 started leaving my file system in an inconsistant state on shutdown and was dismayed to see 13.10 come out and not fix it
[00:13] <qdata> same old story - everybody ego stroking over new features and not focused on producing quality software
[00:33] <djdanielalan> exit
[00:33] <djdanielalan> quit
[00:33] <djdanielalan> close
[02:05] <Blueink> Fuck
[02:25] <HH> YO MAN
[02:25] <HH> IM NEW USER
[02:25] <HH> COULD YOU
[02:25] <HH> EXPLAIN ME
[02:25] <HH> MORE ABOUT
[02:26] <HH> OR YOU SPY ME
[02:26] <HH> OR SOMETHING
[03:35] <zack_> why cant i use my proxy on a irc channal it just says im baned
[03:35] <zack_> hello
[03:35] <tsimpson> don't try and evade bans then
[03:35] <zack_> im not
[03:36] <zack_> i just want to use proxy
[03:36] <zack_> it says cant locate user or somthing
[03:38] <zack_> hello
[03:38] <zack_> @tsimpson_: hello
[03:38] <zack_> oh i mean host not user
[03:40] <tsimpson> if it says it can't locate the host then you're either trying to connect to a host that doesn't exist or your proxy isn't allowing you to resolve DNS entries
[03:40] <valorie> !proxy
[03:41] <zack_> i just feel paranoid
[03:41] <valorie> too paranoid to use Tor?
[03:42] <zack_> how do i use tor
[03:42] <valorie> !tor
[03:42] <zack_> do i have to download
[03:42] <valorie> did you see the factoid ubottu just served up for you above?
[03:43] <valorie> two of them, in fact
[03:43] <zack_> i use foxyproxy
[03:43] <zack_> i dont have anything else
[03:44] <valorie> you can use tor, and/or you can get a cloak
[03:44] <valorie> !cloak
[04:17] <wsr3193> Try backbox linux, it will route you through the tor routers
[11:10] <BluesKaj> HIyas all
[12:37] <dougl> BluesKaj, morning
[12:39] <simion314> hi, i just updated firefox and now it hangs when opening any page, I disabled all my addons but  this did not helped, anyone experienced same issue?
[12:42] <BluesKaj> 'Morning dougl
[13:55] <Boogeyman> anyone familiar with conky?
[13:55] <ikonia> Boogeyman: please don't cross-post questions, you've already asked in #ubuntu
[13:57] <Boogeyman> any specific reason why?
[13:59] <yossarianuk> Boogeyman: what desktop enviornment are you running conky ?
[14:00] <Boogeyman> kde
[14:04] <jargon> how do i import multiple email accounts (3 IMAP, 4 POP3) from thunderbird into kmail?
[14:06] <yossarianuk> Boogeyman: I would ask perhaps in #conky
[14:23] <JoeSomebody> hi, will some app that works on ubuntu work on kubuntu as well, or not necessarily?
[14:23] <Boogeyman> yes
[14:24] <Boogeyman> 99% of the time
[14:24] <JoeSomebody> non repo apps?
[14:24] <Boogeyman> such as?
[14:24] <Boogeyman> i know teamviewer works in both
[14:25] <Boogeyman> as does opera
[14:25] <JoeSomebody> well, hmmm, can you pm me on this for a min? :)
[14:25] <Boogeyman> if i can remember how, lol
[14:26] <JoeSomebody> if you're in xchat like me, right click the nick its right there
[15:25] <LucidGuy> Kubuntu 12.04 - nvidia-331 drivers.  Anyone experience slow response when unlocking lock screen?  The password prompt response quickly, it's once I hit enter the screen goes black and I have a good 10 second delay before desktop appears.
[16:32] <BluesKaj> LucidGuy, do you have alot of apps running at startup like akonadi server for pim and nepomuk for file search and indexing
[16:33] <BluesKaj> ?
[16:38] <LucidGuy> BluesKaj, I do not, I noticed this delay after my most recent troubleshooting of the graphics card.. as you know.
[16:38] <LucidGuy> BluesKaj, thinking of installing nvidia-331-updates
[16:44] <BluesKaj> LucidGuy, it may help your high end gpu since it's listed in the OpenCL part of 331-updates
[16:49] <share> hi
[17:03] <rberg> anyone here running precise as a xen domu?
[17:04] <rberg> I am attempting to boot a precise domu and it gets stuck at "Begin: Running /scripts/init-bottom ... done." I also noticed there was no precise xen-tools target, I used stable and sid
[17:25] <rberg> ok, so anybody know what happens next in boot after "Begin: Running /scripts/init-bottom ... done."
[17:31] <jussi> is there a way to make the vlc mozilla plugin launch the real vlc not the mebedded one ?
[17:36] <shadeslayer> mmmm
[17:36] <shadeslayer> jussi: not that I know of
[17:36] <shadeslayer> protocol handling in FF is currently screwed
[17:36] <shadeslayer> badly
[17:36] <jussi> in chrome :P
[17:36] <shadeslayer> you said mozilla up there
[17:36] <Poisoned_Dragon> I don't even use firefox. So, I pull that plugin outright.
[17:36] <jussi> its a mozilla plugin...
[17:37] <shadeslayer> I see
[17:37] <shadeslayer> jussi: no clue about chrome
[17:37] <shadeslayer> I don't use NSA'ware
[17:37] <shadeslayer> ;)
[17:37] <jussi> !info mozilla-vlc-plugin
[17:37] <jussi> or some such name
[17:37] <Poisoned_Dragon> pfft... nsa-ware
[17:38] <Poisoned_Dragon> nsa doesn't need chrome to spy on you.
[17:40] <howie_> when was the last time you took a dump?
[17:44]  * genii passes around the tinfoil hats
[17:46] <Poisoned_Dragon> !info browser-plugin-vlc
[18:29] <lordievader> Good evening.
[18:29] <Poisoned_Dragon> good afternoon
[18:31] <lordievader> Hey Poisoned_Dragon, how are you?
[18:32] <Poisoned_Dragon> not bad.  Very little docs about how software-properties-gtk verify the codename it's running on.
[18:45] <lordievader> Poisoned_Dragon: Hehe, it's GTK. Qt is pretty well documented. Anyhow this is more a topic for #kubuntu-offtopic.
[18:46] <Poisoned_Dragon> Yeah... I didn't want to get into it too much here. sowwies.
[18:46] <Poisoned_Dragon> I was just happy to finally get how it works.
[20:12] <naftilos76> Hi, i am using kubuntu 13.10 and kmail seems to be having several bugs. The attachment flag is missing. Does anybody else have this issue with kmail 4.11.3 ?
[20:17] <BluesKaj> naftilos76, is this workplace pc ?
[20:18] <naftilos76> It is a laptop for general use. Are you asking something else?
[20:25] <BluesKaj> naftilos76, it's just that kmail can work well on some installs not on others. I've tried to track down the problem over the last couple of yrs, but i haven't concluded what the cause is. I suspect it's hardware related. I gave up on kmail and use thunderbird instead , since I'm a home user.
[20:26] <genii> Apparently Thunderbird is being discontinued.
[20:27] <lordievader> genii: What!!! Since when?
[20:27] <BluesKaj> well, it's still working ok here, genii
[20:28] <naftilos76> I am using thunderbird as well as my email account are all configured over IMAP and it seems nice and stable instead of kmail.  It is really sad. So much  development for nothing? All these people that wrote the code...Unbeleivable...
[20:28] <genii> Let me find the relevant documents
[20:28] <lordievader> genii: http://techcrunch.com/2012/07/06/so-thats-it-for-thunderbird/ Says no more innovation.
[20:29] <BluesKaj> naftilos76, further devel has been dropped for the last 2 yrs
[20:29] <lordievader> And: http://blog.lizardwrangler.com/2012/07/06/thunderbird-stability-and-community-innovation/
[20:30] <genii> lordievader: There was something else out just last week that was referenced in a channel here, but I can't find the link atm
[20:30] <naftilos76> BluesKaj, that is so wrong. Is there an other email client that integrates well with KDE?
[20:30] <lordievader> genii: Hmm, okay. Well too bad I guess.. :(
[20:31] <BluesKaj> naftilos76, it's been left up to the open source community to keep up development
[21:51] <mhall119> valorie: ping
[22:47] <icy05> hi people could some linux guru help me for a sec please, having trouble setting up duel monitors in kubuntu 13.10
[22:51] <icy05> anyone ?
[22:55] <icy05> i removed the old driver then tried to install fglrx drivers,then updated xorg.conf rebooted then tried to login and it keeps boot looping to the lgin screen???
[22:56] <icy05> where did i go wrong people???anyone now :
[23:10] <icy05> hi people could some linux guru help me for a sec please, having trouble setting up duel monitors in kubuntu 13.10
[23:15] <lithiumjake> anyone encountered a problem with adding plasmoids to the desktop or panel, where you can't click the strip that shows with plasmoids?


[00:00] <tsimonq2> balloons: you around?
[06:17] <flocculant> tsimonq2: congrats
[21:22] <tsimonq2> balloons: you around to talk about Walter's task that he gave to me as well as some general API "difficulties"? :)
[21:23] <balloons> tsimonq2, I'm here. I can try to help. However, you likely know more than me if you've been digging into the API :-)
[21:24] <tsimonq2> balloons: just why is it written in PHP?!?!?!?!?
[21:24] <tsimonq2> :P
[21:24] <tsimonq2> balloons: compatibility or preference?
[21:24] <balloons> the api? it's a python api
[21:25] <tsimonq2> balloons: server-end is PHp
[21:25] <tsimonq2> *PHP
[21:25] <balloons> right -- it's drupal you know, the whole thing is php
[21:26] <tsimonq2> balloons: aww so no changing that? :P
[21:26] <teward> drupal is drupal
[21:26] <teward> :P
[21:26] <tsimonq2> alright :P
[21:31] <tsimonq2> balloons: well I guess I can deal...gonna be stuck looking at source code instead of taking random stabs using the python console
[21:31] <balloons> tsimonq2, you're going to have to learn to love php indeed
[21:31] <tsimonq2> balloons: is every function of the API also put into the Python module or does it just forward requests
[21:31]  * tsimonq2 isn't learning PHP, I am just going to look at conceptual stuff :D
[21:31] <tsimonq2> and with by background knowledge on other programming languages it helps
[21:32] <tsimonq2> balloons: because if it's all just in the Python module, that will be MUCH easier to read
[21:33] <balloons> tsimonq2, you've hit the limit of my knowlegde, hah!
[21:34] <balloons> the api is not complete, nor documented as you know
[21:34] <flocculant> you could ask me
[21:34] <balloons> it's a WIP bit of python; it could certainly be added to
[21:34] <flocculant> but it would be even more pointless
[21:34] <flocculant> badum tssh
[21:34] <balloons> as far as what? how? etc, I really have no answers without digging myself
[21:35]  * tsimonq2 will just look into it himself
[21:35] <tsimonq2> I thought you guys would be able to give me some quick answers but I guess I'll have to explore a bit :)
[21:37] <tsimonq2> balloons: when I get done digging after a few weeks I should train you XD


[22:38] <kallisti5[m]> Hi! Is anyone maintaining the sbsigntools repo + mailing list?
[22:38] <kallisti5[m]> https://groups.io/g/sbsigntools/topics
[22:38] <kallisti5[m]> seems like nobody is reviewing pull requests / patches
[22:39] <kallisti5[m]> that's https://git.kernel.org/pub/scm/linux/kernel/git/jejb/sbsigntools.git/
[22:39] <kallisti5[m]> I submitted some patches for riscv32 / riscv64 support, only to find out that someone else did 8 months ago without any responses
[22:50] <kallisti5[m]> ah. Jeremy Kerr hasn't been with Canonical for like 7 years lol. That explains it


[14:19] <slangasek> davmor2: migration-assistant is higher priority (ubuntu amd64)
[14:20] <davmor2> slangasek: no probs I'll hit that after this xubunt 32bit wubi
[14:51] <slangasek> ev: the wubi 'stable' link points to r176, but davmor2 says he's been testing r174 - which am I meant to be publishing?
[14:51] <ev> 176 fixes the UNR is now UNE issue
[14:51] <ev> 174 fixes the crash
[14:52] <ev> I think we can get away with just 174 and telling UNE users to wait until beta 2
[14:52] <slangasek> davmor2: you've been testing 174?
[14:52] <davmor2> slangasek: yeap but I can run une and a couple of other on 176 if you want to release on that one instead?
[14:53] <slangasek> no, let's go with 174
[14:53] <cjwatson> err, is the release meeting in 7 minutes or 67 minutes?  this is Google Calendar Confusion Week
[14:53] <slangasek> 67 minutes
[14:53] <pitti> cjwatson: 67 usually
[14:53] <cjwatson> goodd
[14:54] <davmor2> slangasek: would you like me to test 176 for une to ensure that works?
[14:54] <slangasek> davmor2: it's not pertinent to beta1, though it should certainly be tested at some point
[14:55] <davmor2> slangasek: Well m-a on 64bit ubu is 50% installed now so I can do it after that
[14:56] <slangasek> GrueMaster: bug #541399> loaded from USB?  That seems to defeat the purpose of a netboot image
[14:57] <GrueMaster> slangasek: It's irrelevant how the kernel gets loaded by uboot.  The fact that the kernel wouldn't execute is the issue.
[14:57] <GrueMaster> I don't have a tftpboot server set up at the moment.
[14:58] <GrueMaster> But this is perfectly valid.  We have an img file for babbage that gets loaded from SD card for the same image.
[15:02] <slangasek> GrueMaster: ah, ok
[15:03] <slangasek> davmor2: how long do you expect the m-a test to take to finish?
[15:03] <davmor2> 95% now
[15:03] <davmor2> 98%
[15:03] <slangasek> cool
[15:03] <davmor2> restart
[15:07] <davmor2> slangasek: done
[15:08] <slangasek> sweet
[16:19] <slangasek> smoser: could you update the ec2 webpages, please?  (publicize-build running now)
[16:22] <smoser> slangasek, with --make-public ?
[16:22] <smoser> i will update ec2 pages now.
[16:22] <slangasek> smoser: isn't that implicit in the 'publicize' command?
[16:22] <slangasek> (I'm going by the wiki page...)
[16:23] <smoser> oh. shoot. no, you're right.
[16:23] <slangasek> ok, good :)
[16:23] <smoser> i was thinking you were running 'promote-daily'
[16:23] <smoser> thanks.
[16:30] <smoser> slangasek, pages updated.
[16:32] <slangasek> smoser: thanks!
[17:35] <cjwatson> slangasek: shall I kill queuebot?
[17:35] <slangasek> oh, probably :)
[17:35]  * ScottK imagines cjwatson with a large revolver.
[17:37] <cjwatson> I've got Control and C keys, if those are equivalent
[17:50] <cjwatson> nhandler: I've registered queuebot now
[17:54] <ScottK> slangasek: You may want to look at 538860 and decide if you want to retroactively approve it or get it reverted.
[17:57] <slangasek> ScottK: ah, actually I approved that one from the queue by hand after a review, I just didn't comment the bug :)
[17:58] <ScottK> slangasek: OK.  No problem then.
[18:01] <doko__> please promote python3-defaults and python3.1 (now needed by distribute as b-d). will have to seed python3-all-dbg
[18:24] <nigelb> if an apport hook is added, worth a beta freeze exception?
[18:24] <nigelb> or do I wait till lucid+1?
[18:26] <cjwatson> I don't think that needs a freeze exception
[18:26] <nigelb> ok, I'll get to work on it soon then :)
[18:35] <slangasek> doko__: is there an MIR for this?
[19:09] <doko> slangasek: hmm, no, in the past we never had MIR's for new versions. maybe we could have one for pybsddb3, but this is a new version of something we already have in the python2.6 package as well
[19:09] <doko> let me know what you prefer; I'll write it over the weekend. away now
[19:10] <slangasek> doko: well, python3 is a substantial enough change, and going in parallel, that I would be more comfortable having an MIR for it
[19:10] <doko> ok, will do over the weekend
[19:11] <slangasek> thanks
[19:16] <AnAnt> slangasek: Hello, regarding LP 402874, is there anything else needed other than than upgrade & install logs ?
[19:18] <cjwatson> pitti: I'd like to go ahead with the grub2 SRU in bug 477104; it's definitely the right fix for grub2 itself, even if there are some problems getting the update applied to wubildr
[19:19] <cjwatson> pitti: WDYT?  The latter might be covered by my lupin upload
[19:19] <cjwatson> I could upload that to -proposed if that would help
[19:22] <cjwatson> ... uploaded
[19:23] <cjwatson> pitti: see my most recent comment on the bug
[19:31] <slangasek> AnAnt: yes, the information described on the FreezeExceptionProcess page
[19:31] <slangasek> # A description of the proposed changes, with sufficient detail to estimate their potential impact on the distribution
[19:31] <slangasek> # A rationale for the exception, explaining the benefit of the change
[19:31] <slangasek> # Any additional information which would be helpful in considering the decision
[20:10] <asac> FYI, bug 542141
[20:58] <cjwatson> asac: does the default search change affect other Mozilla products, or just Firefox?
[21:00] <asac> cjwatson: just firefox
[21:01] <asac> cjwatson: mozilla prefers if we name it "Mozilla Firefox"
[21:01] <asac> rather than Firefox
[21:03] <asac> commented that on bug
[21:07] <cjwatson> asac: can we trade it for them not referring to "Ubuntu Linux" on mozilla.org? :-)
[21:14] <asac> haha
[21:14] <asac> where is that?
[21:15] <asac> or you want them to refer to Ubuntu rather than just "Linux"?
[21:25] <pitti> cjwatson: this bug keeps confusing me. A lot of people applied workarounds, but I didn't see any testing of the proposed package yet
[21:26] <pitti> hmm, unapproved queue still not flushed? any particular reason?
[21:42] <cjwatson> asac: google "Ubuntu Linux" site:mozilla.org - various wiki pages and such but some official things too
[21:43] <cjwatson> pitti: I think the lupin package I uploaded to karmic-proposed unapproved should help - it should fix upgrade to work the way it's meant to and rewrite wubildr automatically
[21:44] <cjwatson> the lack of that is probably why we haven't got real testing yet, but both parts are needed
[21:48] <asac> cjwatson: so they should just refer to "Ubuntu"?
[21:49] <asac> or what should i suggest?
[21:59] <cjwatson> I'll follow up
[21:59] <cjwatson> (to the bug)
[22:08] <asac> k
[22:08] <nhandler> cjwatson: Is there a draft of the next beta announcement? I want to s/FreeNode/freenode/g
[22:10] <slangasek> nhandler: feel free to copy https://wiki.ubuntu.com/LucidLynx/Beta1Announcement to https://wiki.ubuntu.com/LucidLynx/Beta2Announcement and tweak
[22:10] <nhandler> slangasek: Will do


[18:07] <flocculant> ochosi: just seen andre's comment in xfce ... if custom actions no longer work then I'll not want to be testing it.
[18:07] <flocculant> use 4 custom actions here :(
[18:08] <flocculant> re dropping thunar into experimental that is
[18:32] <flocculant> apparently I got the wrong end of the stick there ...
[22:48] <ochosi> flocculant: yeah, it's only custom kb shortcuts for custom actions that currently don't work
[22:48] <ochosi> custom actions work just fine, as before
[22:48] <ochosi> (but i guess you already figured that out)