[00:01] <tsimonq2> acheronuk and clivejo HEY ping
[00:01] <tsimonq2> bug 1647204
[00:01] <acheronuk> yes?
[00:02] <tsimonq2> acheronuk: Look at the bug
[00:02] <tsimonq2> acheronuk: IT HAS PATCH :D
[00:02] <acheronuk> I know.
[00:03] -kubuntu-ci:#kubuntu-devel- Project zesty_unstable_trojita build #47: STILL UNSTABLE in 47 min: http://kci.pangea.pub/job/zesty_unstable_trojita/47/
[00:03] <acheronuk> tsimonq2: I know, but that won't fix the FTBFS in arm64 and armhf
[00:04] <tsimonq2> acheronuk: Ping barry?
[00:04] <tsimonq2> (it's an IRC nick :P)
[00:05] <acheronuk> https://bugs.launchpad.net/ubuntu/+source/gpgme1.0/+bug/1647204/comments/29
[00:07] -kubuntu-ci:#kubuntu-devel- Project mgmt_merger build #787: SUCCESS in 7 min 30 sec: http://kci.pangea.pub/job/mgmt_merger/787/
[00:07] <clivejo> anyone know whats going on with oxygen-fonts - https://anonscm.debian.org/cgit/pkg-kde/plasma/oxygen-fonts.git/ ?
[00:08] <acheronuk> tsimonq2: and barry's build in his ppa with that patch are still running after 1 hr, so not sure his patch is 100% good, even on amd64 and i386
[00:09] <barry> o/
[00:09] <barry> tsimonq2: hi
[00:09] <tsimonq2> acheronuk: I got barry here
[00:09] <acheronuk> clivejo: not a lot happening from that changelog!
[00:09] <acheronuk> hi barry :)
[00:10] <barry> acheronuk: hi!
[00:10]  * barry is only here until he hears the dinner bell
[00:10] <tsimonq2> acheronuk: What's up with his patch? :P
[00:10] <barry> fwiw, gpgme1.0 is still building in my ppa
[00:10] <acheronuk> tsimonq2: don't know. only glanced at it
[00:10] <tsimonq2> But... acheronuk> tsimonq2: I know, but that won't fix the FTBFS in arm64 and armhf
[00:11] <barry> right, my ppa is only amd64 and i386
[00:11] <barry> has that package ever passed on arm*?
[00:12] <acheronuk> 'ever' as in historically?
[00:12] <barry> acheronuk: yep
[00:12] <tsimonq2> barry: You're Canonical, right? It would be Really Really Great if you could enable ALL architectures then do a rebuild so we can make sure. :)
[00:12] <barry> tsimonq2: i am
[00:13] <tsimonq2> barry: So then you should have access to do that, right?
[00:13] <barry> tsimonq2: yes, everything but powerpc and s390x, but let's ignore them
[00:13] <acheronuk> barry: yes it has, but there are a lot of changes since like the Qt bindings/cmake files + tests
[00:14] <barry> i'll have to upload a new source pkg to trigger the other arch builds in my ppa
[00:14] <barry> acheronuk: ok.  it still might make sense to whitelist those arm failures
[00:14] <acheronuk> + it builds on arm on debian builders
[00:14] <barry> in any case, dinner.  i'll come back online a little later, but i'll trigger a rebuild on the new arches first
[00:15] <acheronuk> barry: well, it's 00:15 here, so I may not be about. tsimonq2 may well be though
[00:15] <barry> cool.  uploaded.  i'll read the scrollback when i return
[00:16] <tsimonq2> barry: Many thanks :)
[00:17] <acheronuk> for kubuntu stuff, I find it a bit hard to care about fails on arm, but am trying to be good and at least try a little
[00:18] -kubuntu-ci:#kubuntu-devel- Project xenial_unstable_trojita build #37: FAILURE in 46 min: http://kci.pangea.pub/job/xenial_unstable_trojita/37/
[00:19] -kubuntu-ci:#kubuntu-devel- Project yakkety_unstable_trojita build #36: FAILURE in 46 min: http://kci.pangea.pub/job/yakkety_unstable_trojita/36/
[00:19] -kubuntu-ci:#kubuntu-devel- Project zesty_unstable_kross-interpreters build #47: FAILURE in 10 min: http://kci.pangea.pub/job/zesty_unstable_kross-interpreters/47/
[00:19] <clivejo> !info  oxygen-fonts
[00:19] <acheronuk> Qtwebengine is borked for arm64 anyway, so KDE PIM we need gpgme for is a no-go for us on that arch even if gpgme built
[00:20] <clivejo> !info fonts-oxygen
[00:20] <acheronuk> and as Phil said earlier, we don't support those arm arches in kubuntu, so.... :P
[00:20] <clivejo> !info fonts-oxygen unstable
[00:22] <acheronuk> clivejo: did not KDE give up on oxygen fonts, in favour of Noto or similar?
[00:22] <valorie> noto does have better international coverage
[00:22] <clivejo> yeah, trying to find out why debian have uploaded a newer version than ours
[00:23] <valorie> but there may be a few people still at work on the oxy. font anyway
[00:23] <clivejo> looks like ximion added a patch for appstream metadata
[00:23] <valorie> KDE software are not the only users
[00:23] <clivejo> so Im wondering what to do about it
[00:23] <acheronuk> clivejo: seems so
[00:24] <clivejo> should I just request a sync to bring us up to 4:5.4.3-3 as well?
[00:24] <acheronuk> what was the ubuntu delta?
[00:25] <clivejo> not sure
[00:25] <acheronuk> if it's nothing important or is droppable, then I would say so.
[00:26] <clivejo> do you know an easy way of getting a delta?
[00:27] <acheronuk> usually I just clone both repos, check out the branches, and use something like kompare to do a GUI diff compare
[00:27] <clivejo> https://merges.ubuntu.com/o/oxygen-fonts/REPORT
[00:28] <acheronuk> may well be an easier way
[00:29] <clivejo> talks about patch file
[00:29] <clivejo> but no idea where that is
[00:29] <clivejo> oh
[00:29] <clivejo> https://merges.ubuntu.com/o/oxygen-fonts/
[00:29] <acheronuk> that would do it
[00:32] <clivejo> what do you make of that?
[00:33] <clivejo> I think this is the diff - https://merges.ubuntu.com/o/oxygen-fonts/oxygen-fonts_4:5.4.3-3.patch
[00:33] <acheronuk> between debian versions, it is
[00:36] <acheronuk> https://merges.ubuntu.com/o/oxygen-fonts/oxygen-fonts_4:5.4.3-0ubuntu1.patch
[00:36] <acheronuk> gives the ubuntu delta on the previous version
[00:37] <acheronuk> which seems to have been just a new version debian did not have yet to make a 0ubuntu1, plus changelog and a bit of wrap-and-sort
[00:37] <acheronuk> so....
[00:38] <clivejo> http://paste.ubuntu.com/23872285/
[00:39] <acheronuk> in a sync, seems we would just lose the 4:5.4.3-0ubuntu1 changelog entry and some inconsequential tidying up
[00:40] <clivejo> LP 1518598
[00:42] <acheronuk> huh? ^^^
[00:43] -kubuntu-ci:#kubuntu-devel- Project xenial_unstable_kproperty build #38: STILL UNSTABLE in 34 min: http://kci.pangea.pub/job/xenial_unstable_kproperty/38/
[00:43] -kubuntu-ci:#kubuntu-devel- Project xenial_unstable_kdb build #40: STILL UNSTABLE in 34 min: http://kci.pangea.pub/job/xenial_unstable_kdb/40/
[00:44] -kubuntu-ci:#kubuntu-devel- Project zesty_unstable_krita build #78: STILL FAILING in 36 min: http://kci.pangea.pub/job/zesty_unstable_krita/78/
[00:46] <acheronuk> clivejo: hmmm. debian did make a fair few changes then. compared to our 4:5.4.3-0ubuntu1
[00:49] <acheronuk> we would lose the transitional package in a sync?
[00:49]  * acheronuk is too tired for this!
[00:49] -kubuntu-ci:#kubuntu-devel- Project yakkety_unstable_krita build #51: STILL FAILING in 41 min: http://kci.pangea.pub/job/yakkety_unstable_krita/51/
[00:50] -kubuntu-ci:#kubuntu-devel- Project xenial_unstable_krita build #53: STILL FAILING in 41 min: http://kci.pangea.pub/job/xenial_unstable_krita/53/
[00:51] <clem_l> acheronuk: use git?
[00:51] <acheronuk> clem_l: for what?
[00:51] <clem_l> i.e. git init one version, commit it, delete everything, add version B, git diff
[00:51] <clem_l> to visualize all the changes
[00:52] <acheronuk> clem_l: I think our packaging for this old package is still in bzr
[00:52] <acheronuk> never got moved to git
[00:52] <acheronuk> debian is in git now, but not ours
[00:52] <clem_l> it doesn't matter, you can git the difference
[00:53] <clem_l> instead of using meld/kompare on the files/directories
[00:53] <acheronuk> true, but I quite like those. especially meld
[00:53] <clem_l> you use git to go from one version to the other and get git to produce the difference
[00:54] <clem_l> yeah, I'm quite fond of meld too :)
[00:54] <acheronuk> you can, and staring at git diff is not my idea of fun
[00:54] <clem_l> gitk and its beautiful widgets
[00:55] -kubuntu-ci:#kubuntu-devel- Project zesty_unstable_trojita build #48: FAILURE in 47 min: http://kci.pangea.pub/job/zesty_unstable_trojita/48/
[00:55] <acheronuk> clem_l: urgh! yes
[00:56] <clem_l> anyway it's very handy to analyze diffs
[00:56] <clem_l> meld is great too, but with git you can branch, checkout files which are irrelevant, etc etc..
[00:56] <acheronuk> must have a play sometime then
[00:59] <clem_l> I use git to reverse engineer KDE sometimes :)
[00:59] <clem_l> pure laziness, instead of reading the specs, when you want to know what variable to set in which file to achieve some configuration change
[00:59] -kubuntu-ci:#kubuntu-devel- Project xenial_unstable_kdiagram build #68: STILL UNSTABLE in 51 min: http://kci.pangea.pub/job/xenial_unstable_kdiagram/68/
[01:00] <clem_l> just git init your .config dir, commit it, change the setting in System Settings and ask git diff what changed
[01:00] <acheronuk> I have enough issue forward engineering it!
[01:00] <clem_l> :))
[01:01] -kubuntu-ci:#kubuntu-devel- Project yakkety_unstable_kdiagram build #41: STILL UNSTABLE in 52 min: http://kci.pangea.pub/job/yakkety_unstable_kdiagram/41/
[01:01] -kubuntu-ci:#kubuntu-devel- Project zesty_unstable_kdb build #37: STILL UNSTABLE in 51 min: http://kci.pangea.pub/job/zesty_unstable_kdb/37/
[01:03] -kubuntu-ci:#kubuntu-devel- Project yakkety_unstable_kwin build #146: STILL FAILING in 54 min: http://kci.pangea.pub/job/yakkety_unstable_kwin/146/
[01:14] -kubuntu-ci:#kubuntu-devel- Project xenial_unstable_libkmahjongg build #222: FAILURE in 13 min: http://kci.pangea.pub/job/xenial_unstable_libkmahjongg/222/
[01:17] -kubuntu-ci:#kubuntu-devel- Project zesty_unstable_kstars build #85: STILL UNSTABLE in 1 hr 8 min: http://kci.pangea.pub/job/zesty_unstable_kstars/85/
[01:17] -kubuntu-ci:#kubuntu-devel- Project zesty_unstable_ktp-common-internals build #82: STILL UNSTABLE in 1 hr 8 min: http://kci.pangea.pub/job/zesty_unstable_ktp-common-internals/82/
[01:17] -kubuntu-ci:#kubuntu-devel- Project zesty_unstable_kproperty build #43: STILL UNSTABLE in 34 min: http://kci.pangea.pub/job/zesty_unstable_kproperty/43/
[01:18] -kubuntu-ci:#kubuntu-devel- Project yakkety_unstable_marble build #138: STILL FAILING in 1 hr 9 min: http://kci.pangea.pub/job/yakkety_unstable_marble/138/
[01:19] <ahoneybun> trojita
[01:19] <clivejo> say it three times and you'll find the secret menu
 trojita
 trojita
 trojita
 WHERE'S MY MENU?!?
[01:20] <ahoneybun> xD
[01:20] <ahoneybun> just found it cool that it was there
[01:23] <clivejo> it is pretty cool
[01:23] <clivejo> very fast
[01:23] <ahoneybun> is it?
[01:23] <ahoneybun> I'
[01:23] <clivejo> it is
[01:23] <ahoneybun> I've just been using web gmail and protonmail
[01:24] <clivejo> grrrr @ protomail
[01:24] <ahoneybun> with Trump I've been moving my email to protonmail more
[01:24] <ahoneybun> all my banks link to it now
[01:24] <clivejo> lot of spammer using it
[01:24] <ahoneybun> I've seen a few emails
[01:25] <clivejo> I've banned the domain on my personal server
[01:25] <ahoneybun> mostly just because they are hitting my @kubuntu ones
[01:25] <ahoneybun> *one
[01:25] <ahoneybun> trojita needs gpg support
[01:25] <clivejo> I emailed them and they basically said tough luck
[01:26] <ahoneybun> the gpg ?
[01:26] <clivejo> protomail
[01:26] <ahoneybun> about the spam?
[01:26] <clivejo> yup
[01:26] <ahoneybun> well that's kinda the point of it
[01:26] <ahoneybun> they can't even touch it
[01:26] <ahoneybun> email wise
[01:26] <clivejo> thousands of email accounts controlled by bots
[01:27] <clivejo> I dont want to touch it, just want the bots prevented from signing up!
[01:27] <ahoneybun> well someone posted online of a bot passing Google's antibot test
[01:28] <ahoneybun> so there might be more of those now
[01:28] <clivejo> well I sent a list of about 500 email accounts I know are bots
[01:28] <ahoneybun> wow
[01:31] <ahoneybun> any testing I can help with?
[01:31] <clivejo> ie xyzpochc is a username used by a bot to spam the hell outta forums
[01:31] <clivejo> they have registered xyzpocha all the way through to z
[01:32] <clivejo> thousands if not millions of spam posts generated by those bots
[01:37] <ahoneybun> darn
[01:38] -kubuntu-ci:#kubuntu-devel- Project zesty_unstable_kopete build #76: STILL UNSTABLE in 1 hr 29 min: http://kci.pangea.pub/job/zesty_unstable_kopete/76/
[01:53] -kubuntu-ci:#kubuntu-devel- Yippee, build fixed!
[01:53] -kubuntu-ci:#kubuntu-devel- Project zesty_unstable_kross-interpreters build #48: FIXED in 35 min: http://kci.pangea.pub/job/zesty_unstable_kross-interpreters/48/
[01:53] -kubuntu-ci:#kubuntu-devel- Project zesty_unstable_kpimtextedit build #84: STILL UNSTABLE in 35 min: http://kci.pangea.pub/job/zesty_unstable_kpimtextedit/84/
[01:53] -kubuntu-ci:#kubuntu-devel- Project xenial_unstable_kopete build #164: STILL UNSTABLE in 53 min: http://kci.pangea.pub/job/xenial_unstable_kopete/164/
[01:53] -kubuntu-ci:#kubuntu-devel- Project xenial_unstable_trojita build #38: NOW UNSTABLE in 35 min: http://kci.pangea.pub/job/xenial_unstable_trojita/38/
[01:53] -kubuntu-ci:#kubuntu-devel- Project zesty_unstable_umbrello build #92: STILL UNSTABLE in 36 min: http://kci.pangea.pub/job/zesty_unstable_umbrello/92/
[01:53] -kubuntu-ci:#kubuntu-devel- Project xenial_unstable_ktp-auth-handler build #271: STILL UNSTABLE in 36 min: http://kci.pangea.pub/job/xenial_unstable_ktp-auth-handler/271/
[01:54] -kubuntu-ci:#kubuntu-devel- Project zesty_unstable_peruse build #63: STILL UNSTABLE in 37 min: http://kci.pangea.pub/job/zesty_unstable_peruse/63/
[01:59] -kubuntu-ci:#kubuntu-devel- Project xenial_unstable_krita build #54: STILL FAILING in 20 min: http://kci.pangea.pub/job/xenial_unstable_krita/54/
[02:01] -kubuntu-ci:#kubuntu-devel- Project zesty_unstable_krita build #79: STILL FAILING in 22 min: http://kci.pangea.pub/job/zesty_unstable_krita/79/
[02:02] -kubuntu-ci:#kubuntu-devel- Project yakkety_unstable_krita build #52: STILL FAILING in 23 min: http://kci.pangea.pub/job/yakkety_unstable_krita/52/
[02:14] -kubuntu-ci:#kubuntu-devel- Project zesty_unstable_kdiagram build #66: STILL UNSTABLE in 56 min: http://kci.pangea.pub/job/zesty_unstable_kdiagram/66/
[02:14] -kubuntu-ci:#kubuntu-devel- Project xenial_unstable_umbrello build #195: STILL UNSTABLE in 56 min: http://kci.pangea.pub/job/xenial_unstable_umbrello/195/
[02:14] -kubuntu-ci:#kubuntu-devel- Project yakkety_unstable_trojita build #37: NOW UNSTABLE in 56 min: http://kci.pangea.pub/job/yakkety_unstable_trojita/37/
[02:14] -kubuntu-ci:#kubuntu-devel- Project xenial_unstable_plasma-sdk build #313: STILL UNSTABLE in 36 min: http://kci.pangea.pub/job/xenial_unstable_plasma-sdk/313/
[02:14] -kubuntu-ci:#kubuntu-devel- Project xenial_unstable_kreport build #41: STILL UNSTABLE in 36 min: http://kci.pangea.pub/job/xenial_unstable_kreport/41/
[02:14] -kubuntu-ci:#kubuntu-devel- Project xenial_unstable_kstars build #354: STILL UNSTABLE in 57 min: http://kci.pangea.pub/job/xenial_unstable_kstars/354/
[02:39] -kubuntu-ci:#kubuntu-devel- Project zesty_unstable_trojita build #49: NOW UNSTABLE in 46 min: http://kci.pangea.pub/job/zesty_unstable_trojita/49/
[02:39] -kubuntu-ci:#kubuntu-devel- Project yakkety_unstable_okular build #197: STILL UNSTABLE in 45 min: http://kci.pangea.pub/job/yakkety_unstable_okular/197/
[02:39] -kubuntu-ci:#kubuntu-devel- Project yakkety_unstable_ktp-auth-handler build #225: STILL UNSTABLE in 45 min: http://kci.pangea.pub/job/yakkety_unstable_ktp-auth-handler/225/
[02:39] -kubuntu-ci:#kubuntu-devel- Project yakkety_unstable_kstars build #220: STILL UNSTABLE in 1 hr 1 min: http://kci.pangea.pub/job/yakkety_unstable_kstars/220/
[02:40] -kubuntu-ci:#kubuntu-devel- Project yakkety_unstable_umbrello build #166: STILL UNSTABLE in 1 hr 1 min: http://kci.pangea.pub/job/yakkety_unstable_umbrello/166/
[02:40] -kubuntu-ci:#kubuntu-devel- Project zesty_unstable_marble build #96: STILL UNSTABLE in 1 hr 22 min: http://kci.pangea.pub/job/zesty_unstable_marble/96/
[02:40] -kubuntu-ci:#kubuntu-devel- Project yakkety_unstable_akonadi build #298: STILL FAILING in 46 min: http://kci.pangea.pub/job/yakkety_unstable_akonadi/298/
[02:40] -kubuntu-ci:#kubuntu-devel- Yippee, build fixed!
[02:40] -kubuntu-ci:#kubuntu-devel- Project yakkety_unstable_kalzium build #105: STILL UNSTABLE in 47 min: http://kci.pangea.pub/job/yakkety_unstable_kalzium/105/
[02:40] -kubuntu-ci:#kubuntu-devel- Project xenial_unstable_libkmahjongg build #223: FIXED in 46 min: http://kci.pangea.pub/job/xenial_unstable_libkmahjongg/223/
[02:41] -kubuntu-ci:#kubuntu-devel- Project xenial_unstable_peruse build #53: STILL UNSTABLE in 26 min: http://kci.pangea.pub/job/xenial_unstable_peruse/53/
[02:49] -kubuntu-ci:#kubuntu-devel- Project zesty_unstable_plasma-sdk build #87: FAILURE in 9 min 44 sec: http://kci.pangea.pub/job/zesty_unstable_plasma-sdk/87/
[02:55] -kubuntu-ci:#kubuntu-devel- Project yakkety_unstable_trojita build #38: STILL UNSTABLE in 40 min: http://kci.pangea.pub/job/yakkety_unstable_trojita/38/
[02:55] -kubuntu-ci:#kubuntu-devel- Project xenial_unstable_kexi build #45: STILL UNSTABLE in 40 min: http://kci.pangea.pub/job/xenial_unstable_kexi/45/
[02:55] -kubuntu-ci:#kubuntu-devel- Project yakkety_unstable_marble build #139: STILL FAILING in 1 hr 0 min: http://kci.pangea.pub/job/yakkety_unstable_marble/139/
[02:55] -kubuntu-ci:#kubuntu-devel- Project xenial_unstable_trojita build #39: STILL UNSTABLE in 41 min: http://kci.pangea.pub/job/xenial_unstable_trojita/39/
[03:00] -kubuntu-ci:#kubuntu-devel- Project yakkety_unstable_kwin build #147: STILL FAILING in 1 hr 6 min: http://kci.pangea.pub/job/yakkety_unstable_kwin/147/
[03:01] -kubuntu-ci:#kubuntu-devel- Project zesty_unstable_plasma-sdk build #88: STILL FAILING in 6 min 52 sec: http://kci.pangea.pub/job/zesty_unstable_plasma-sdk/88/
[03:14] -kubuntu-ci:#kubuntu-devel- Project xenial_unstable_okular build #133: STILL UNSTABLE in 34 min: http://kci.pangea.pub/job/xenial_unstable_okular/133/
[03:14] -kubuntu-ci:#kubuntu-devel- Project xenial_unstable_kalzium build #159: STILL UNSTABLE in 34 min: http://kci.pangea.pub/job/xenial_unstable_kalzium/159/
[03:14] -kubuntu-ci:#kubuntu-devel- Project zesty_unstable_okular build #108: STILL UNSTABLE in 34 min: http://kci.pangea.pub/job/zesty_unstable_okular/108/
[03:14] -kubuntu-ci:#kubuntu-devel- Project zesty_unstable_trojita build #50: STILL UNSTABLE in 34 min: http://kci.pangea.pub/job/zesty_unstable_trojita/50/
[03:21] <sintre> imageMagik (display 16) still won't open on my 16.04 older nvidia lappy
[03:21] <sintre> usjust updated thru backports
[03:27] <sintre> same result on new intel intel 5500 is as nvidia core 2 duo
[03:29] -kubuntu-ci:#kubuntu-devel- Project yakkety_unstable_plasma-workspace build #164: STILL FAILING in 28 min: http://kci.pangea.pub/job/yakkety_unstable_plasma-workspace/164/
[03:29] -kubuntu-ci:#kubuntu-devel- Project zesty_unstable_pim-sieve-editor build #81: STILL UNSTABLE in 34 min: http://kci.pangea.pub/job/zesty_unstable_pim-sieve-editor/81/
[03:29] -kubuntu-ci:#kubuntu-devel- Project yakkety_unstable_akonadi build #299: STILL FAILING in 44 min: http://kci.pangea.pub/job/yakkety_unstable_akonadi/299/
[03:29] -kubuntu-ci:#kubuntu-devel- Project yakkety_unstable_kexi build #49: STILL UNSTABLE in 34 min: http://kci.pangea.pub/job/yakkety_unstable_kexi/49/
[03:30] <valorie> sintre: please file a bug
[03:30] <valorie> imagemagick is not in our packageset
[03:30] <sintre> its comes in the iso
[03:30] <sintre> so how is it not?
[03:30] <sintre> you put it in
[03:31] <valorie> !info imagemagick
[03:31] <valorie> like firefox, we include it because we pretty much have to
[03:31] <tsimonq2> valorie: We need imagemagick out of zesty-proposed anyways.
[03:31] <tsimonq2> Lubuntu bugfix is in there.
[03:31] <valorie> cool
[03:32] <sintre> valorie really why do you talk to me like i'm you kid too
[03:32] <valorie> nevertheless, please file a bug
[03:32] <valorie> what?
[03:32] <sintre> i'm 30's losing my hair now
[03:32] <valorie> this is the procedure
[03:32] <valorie> I file them as well
[03:32] <sintre> yet you'll jjke around in the channel
[03:32] <sintre> but only target me for stern instructions
[03:32] <valorie> !
[03:33] <tsimonq2> sintre: Now treating you like a kid would be saying, "go away, rtfm or I'll kick you from the channel"
[03:33] <tsimonq2> sintre: But she's giving you an intelligent answer. :)
[03:33] <sintre> what go file a bug report?
[03:33] <sintre> thats the second time todday
[03:33] <tsimonq2> sintre: Now, would you like me to link you to the page? It's a little hard to find. :)
[03:33] <sintre> cmon
[03:34] <valorie> and about the fourth time I have asked people to do that
[03:34] <valorie> it is increasingly important
[03:34] <valorie> as we approach the beta
[03:34] <sintre> yes but you will joke around and talk "off-topic" in this channel yet second i do it
[03:34] <sintre> you'll jumpodown my throat
[03:35] <valorie> no
[03:35] <valorie> stop this
[03:35] <tsimonq2> >__> ... <__< ... huh?
[03:35] <valorie> I have no idea why you are unwilling to accept useful advice from me
[03:35] <sintre> make a bug report is not usefull advise
[03:36] <valorie> sintre: pm, please
[03:37] <sintre> last time i did that you told me not to pm you so no thank you
[03:37] <valorie> otherwise, please leave the channel
[03:37] <tsimonq2> sintre: I would say it's *really* on-topic, she just doesn't have the proper resources to deal with it. Saying "please file a bug report" is just saying "I unfortunately don't have control over this or know the people who maintain this, but I know the right people who do. Here, if you file a bug report, I'm really sure they'll see it. If they don't, please let me know and I can help you."
[03:37] <sintre> kick me
[03:37] <tsimonq2> sintre: I would say it's the best response she can give you. :)
[03:40] <valorie> I will ask you again, please file a bug, sintre
[03:40] <valorie> the easiest way is in the commandline: ubuntu-bug imagemagick
[03:52] -kubuntu-ci:#kubuntu-devel- Project xenial_unstable_pim-sieve-editor build #64: STILL UNSTABLE in 38 min: http://kci.pangea.pub/job/xenial_unstable_pim-sieve-editor/64/
[03:53] -kubuntu-ci:#kubuntu-devel- Project xenial_unstable_marble build #107: STILL UNSTABLE in 58 min: http://kci.pangea.pub/job/xenial_unstable_marble/107/
[04:09] -kubuntu-ci:#kubuntu-devel- Project yakkety_unstable_pim-sieve-editor build #52: STILL UNSTABLE in 39 min: http://kci.pangea.pub/job/yakkety_unstable_pim-sieve-editor/52/
[04:09] -kubuntu-ci:#kubuntu-devel- Project yakkety_unstable_korganizer build #55: STILL UNSTABLE in 39 min: http://kci.pangea.pub/job/yakkety_unstable_korganizer/55/
[04:09] -kubuntu-ci:#kubuntu-devel- Project yakkety_unstable_plasma-workspace build #165: STILL FAILING in 35 min: http://kci.pangea.pub/job/yakkety_unstable_plasma-workspace/165/
[04:16] <ahoneybun> tsimonq2: talked to Rick about the documentation
[04:16] <ahoneybun> ?
[04:16] <tsimonq2> ahoneybun: No actually, I haven't.
[04:17] <tsimonq2> ahoneybun: I'll send him a ping tomorrow after releasing Alpha 2, but now is homework.
[04:17] <ahoneybun> right
[04:46] -kubuntu-ci:#kubuntu-devel- Project zesty_unstable_kitemmodels build #88: STILL UNSTABLE in 26 min: http://kci.pangea.pub/job/zesty_unstable_kitemmodels/88/
[04:57] -kubuntu-ci:#kubuntu-devel- Project yakkety_unstable_kitemmodels build #179: STILL UNSTABLE in 11 min: http://kci.pangea.pub/job/yakkety_unstable_kitemmodels/179/
[05:19] -kubuntu-ci:#kubuntu-devel- Project yakkety_unstable_kjobwidgets build #235: STILL UNSTABLE in 6 min 49 sec: http://kci.pangea.pub/job/yakkety_unstable_kjobwidgets/235/
[05:19] -kubuntu-ci:#kubuntu-devel- Project zesty_unstable_kjobwidgets build #81: STILL UNSTABLE in 14 min: http://kci.pangea.pub/job/zesty_unstable_kjobwidgets/81/
[05:19] -kubuntu-ci:#kubuntu-devel- Project zesty_unstable_kconfigwidgets build #51: STILL UNSTABLE in 14 min: http://kci.pangea.pub/job/zesty_unstable_kconfigwidgets/51/
[05:19] -kubuntu-ci:#kubuntu-devel- Project zesty_unstable_kdbusaddons build #84: STILL UNSTABLE in 14 min: http://kci.pangea.pub/job/zesty_unstable_kdbusaddons/84/
[05:19] -kubuntu-ci:#kubuntu-devel- Project zesty_unstable_kitemviews build #78: STILL UNSTABLE in 14 min: http://kci.pangea.pub/job/zesty_unstable_kitemviews/78/
[05:27] -kubuntu-ci:#kubuntu-devel- Project yakkety_unstable_kcompletion build #162: STILL UNSTABLE in 14 min: http://kci.pangea.pub/job/yakkety_unstable_kcompletion/162/
[05:28] -kubuntu-ci:#kubuntu-devel- Project zesty_unstable_kguiaddons build #83: STILL UNSTABLE in 8 min 48 sec: http://kci.pangea.pub/job/zesty_unstable_kguiaddons/83/
[05:28] -kubuntu-ci:#kubuntu-devel- Project zesty_unstable_kcodecs build #78: STILL UNSTABLE in 8 min 56 sec: http://kci.pangea.pub/job/zesty_unstable_kcodecs/78/
[05:35] -kubuntu-ci:#kubuntu-devel- Project yakkety_unstable_kcodecs build #246: STILL UNSTABLE in 7 min 23 sec: http://kci.pangea.pub/job/yakkety_unstable_kcodecs/246/
[05:35] -kubuntu-ci:#kubuntu-devel- Project xenial_unstable_kdbusaddons build #384: STILL UNSTABLE in 15 min: http://kci.pangea.pub/job/xenial_unstable_kdbusaddons/384/
[05:35] -kubuntu-ci:#kubuntu-devel- Project xenial_unstable_kitemviews build #354: STILL UNSTABLE in 15 min: http://kci.pangea.pub/job/xenial_unstable_kitemviews/354/
[05:35] -kubuntu-ci:#kubuntu-devel- Project xenial_unstable_kwidgetsaddons build #375: STILL UNSTABLE in 15 min: http://kci.pangea.pub/job/xenial_unstable_kwidgetsaddons/375/
[05:35] -kubuntu-ci:#kubuntu-devel- Project xenial_unstable_kguiaddons build #358: STILL UNSTABLE in 15 min: http://kci.pangea.pub/job/xenial_unstable_kguiaddons/358/
[05:35] -kubuntu-ci:#kubuntu-devel- Project zesty_unstable_kcoreaddons build #78: STILL UNSTABLE in 16 min: http://kci.pangea.pub/job/zesty_unstable_kcoreaddons/78/
[05:35] -kubuntu-ci:#kubuntu-devel- Project xenial_unstable_kconfig build #395: STILL UNSTABLE in 15 min: http://kci.pangea.pub/job/xenial_unstable_kconfig/395/
[05:35] -kubuntu-ci:#kubuntu-devel- Project xenial_unstable_kcodecs build #361: STILL UNSTABLE in 15 min: http://kci.pangea.pub/job/xenial_unstable_kcodecs/361/
[05:35] -kubuntu-ci:#kubuntu-devel- Project zesty_unstable_kwidgetsaddons build #85: STILL UNSTABLE in 16 min: http://kci.pangea.pub/job/zesty_unstable_kwidgetsaddons/85/
[05:36] -kubuntu-ci:#kubuntu-devel- Project xenial_unstable_ki18n build #381: STILL UNSTABLE in 15 min: http://kci.pangea.pub/job/xenial_unstable_ki18n/381/
[05:36] -kubuntu-ci:#kubuntu-devel- Project yakkety_unstable_kdbusaddons build #249: STILL UNSTABLE in 8 min 43 sec: http://kci.pangea.pub/job/yakkety_unstable_kdbusaddons/249/
[05:36] -kubuntu-ci:#kubuntu-devel- Project yakkety_unstable_kguiaddons build #174: STILL UNSTABLE in 8 min 40 sec: http://kci.pangea.pub/job/yakkety_unstable_kguiaddons/174/
[05:41] -kubuntu-ci:#kubuntu-devel- Project yakkety_unstable_kwidgetsaddons build #247: STILL UNSTABLE in 13 min: http://kci.pangea.pub/job/yakkety_unstable_kwidgetsaddons/247/
[05:42] -kubuntu-ci:#kubuntu-devel- Project zesty_unstable_ki18n build #83: STILL UNSTABLE in 13 min: http://kci.pangea.pub/job/zesty_unstable_ki18n/83/
[05:48] -kubuntu-ci:#kubuntu-devel- Project xenial_unstable_kcoreaddons build #356: STILL UNSTABLE in 13 min: http://kci.pangea.pub/job/xenial_unstable_kcoreaddons/356/
[05:49] -kubuntu-ci:#kubuntu-devel- Project yakkety_unstable_kcoreaddons build #185: STILL UNSTABLE in 12 min: http://kci.pangea.pub/job/yakkety_unstable_kcoreaddons/185/
[05:49] -kubuntu-ci:#kubuntu-devel- Project yakkety_unstable_ki18n build #247: STILL UNSTABLE in 14 min: http://kci.pangea.pub/job/yakkety_unstable_ki18n/247/
[05:49] -kubuntu-ci:#kubuntu-devel- Project xenial_unstable_kcompletion build #392: STILL UNSTABLE in 13 min: http://kci.pangea.pub/job/xenial_unstable_kcompletion/392/
[05:56] -kubuntu-ci:#kubuntu-devel- Project zesty_unstable_kwallet build #78: STILL UNSTABLE in 13 min: http://kci.pangea.pub/job/zesty_unstable_kwallet/78/
[06:02] -kubuntu-ci:#kubuntu-devel- Project xenial_unstable_kconfigwidgets build #350: STILL UNSTABLE in 13 min: http://kci.pangea.pub/job/xenial_unstable_kconfigwidgets/350/
[06:10] -kubuntu-ci:#kubuntu-devel- Project xenial_unstable_kwallet build #378: STILL UNSTABLE in 7 min 43 sec: http://kci.pangea.pub/job/xenial_unstable_kwallet/378/
[06:46] -kubuntu-ci:#kubuntu-devel- Project yakkety_unstable_kconfigwidgets build #213: STILL UNSTABLE in 19 min: http://kci.pangea.pub/job/yakkety_unstable_kconfigwidgets/213/
[08:39] -kubuntu-ci:#kubuntu-devel- Project xenial_unstable_k3b build #18: STILL FAILING in 4 min 24 sec: http://kci.pangea.pub/job/xenial_unstable_k3b/18/
[08:44] -kubuntu-ci:#kubuntu-devel- Project yakkety_unstable_k3b build #19: STILL FAILING in 8 min 50 sec: http://kci.pangea.pub/job/yakkety_unstable_k3b/19/
[08:44] -kubuntu-ci:#kubuntu-devel- Project zesty_unstable_k3b build #18: STILL FAILING in 9 min 25 sec: http://kci.pangea.pub/job/zesty_unstable_k3b/18/
[08:48] -kubuntu-ci:#kubuntu-devel- Project xenial_unstable_k3b build #19: STILL FAILING in 3 min 45 sec: http://kci.pangea.pub/job/xenial_unstable_k3b/19/
[09:01] -kubuntu-ci:#kubuntu-devel- Project yakkety_unstable_k3b build #20: STILL FAILING in 11 min: http://kci.pangea.pub/job/yakkety_unstable_k3b/20/
[09:01] -kubuntu-ci:#kubuntu-devel- Project zesty_unstable_k3b build #19: STILL FAILING in 11 min: http://kci.pangea.pub/job/zesty_unstable_k3b/19/
[09:37] <lordievader> Good morning.
[10:37] <BluesKaj> Hiyas all
[13:09] <mparillo> On ZZ, The following packages have been kept back:   libkf5gapi-data libkf5gapicalendar5 libkf5gapicore5 libkf5gapitasks5
[13:09] <clivejo> mparillo: that plain zesty from the archive, no PPAs?
[13:10] <mparillo> Ahh, let me see if I still have your PPA
[13:10] <clivejo> looks like it :P
[13:10] <mparillo> D'oh: Get:5 http://ppa.launchpad.net/clivejo/zesty/ubuntu zesty InRelease [18.0 kB]
[13:11] <clivejo> Im testing that in my PPA
[13:11] <clivejo> but having issues with symbol helper
[13:12] <mparillo> I had not bothered to remove it, since I was planning on blitzing this laptop with either ZZ Alpha 2 (if it got re-spun) or 16.04.2, which was supposed to be any day now, but got pushed to early Feb, IIRC.
[13:14] <clivejo> acheronuk: pkg-kde-tools from staging has fixed the symbols helper problem for me
[13:31] <acheronuk> clivejo: :)
[14:19]  * blaze loves zesty
[14:19] <blaze> but qtwebengine is crashy :\
[14:19] <clivejo> blaze: how so?
[14:20] <blaze> who knows, i was thinking it's impossible too
[14:20] <clivejo> what is crashing?
[14:21] <blaze> a browser
[14:21] <blaze> qupzilla
[14:22] <blaze> if you wanna reproduce, try to open the source of any page and then search with ctrl+f
[14:22] <clivejo> have you proposed enabled?
[14:22] <blaze> no
[14:22] <clivejo> https://launchpad.net/ubuntu/+source/qupzilla
[14:23] <clivejo> 2.0.2 is stuck in proposed
[14:23] <clivejo> eakk
[14:23] <clivejo> no wonder
[14:24] <clivejo> https://launchpad.net/ubuntu/+source/qupzilla/2.0.2~dfsg1-1
[14:24] <clivejo> !info qupzilla unstable
[14:26] <Riddell> clivejo: what do you have against libkcompactdisc? (besides the obvious I mean)
[14:27] <clivejo> Riddell: ??
[14:27] <Riddell> clivejo: Rik just removed it from k3b packaging
[14:29] <clivejo> Im not sure, havent looked at it in a while
[14:29] <clivejo> we are having problems with dependencies as far as I remember
[14:31] <BluesKaj> K3b hasn't worked on my last 4 Kubuntu OSs , fails everytime so i use wodim in the terminal instead
[14:32] <clivejo> issues with KDE4 stuff and KF5
[14:32] <clivejo> I think he was trying something
[14:32] <Riddell> BluesKaj:  possibly the new maintainer has fixed it, who knows
[14:33] <clivejo> basically we noticed devels porting it to KF5 and wondered how stable it was
[14:33] <clivejo> so added it to KCI
[14:34] <clivejo> in the view of _maybe_ trying to get it into zesty
[14:38] <BluesKaj> just tried k3b on Zesty alpha 2 and it still fails to burn , it does format the disk however 
[14:38] <BluesKaj> Riddell, ^
[14:38] <clivejo> BluesKaj: it hasnt been packaged yet
[14:38] <Riddell> that won't be the new version unless it's from KCI presumably
[14:38] <clivejo> can't test it yet
[14:39] <BluesKaj> ok
[14:40] <BluesKaj> I won't hold my breath tho :-)
[14:40] <clivejo> awww why not?
[14:41] <clivejo> you are very biased towards the history of certain projects
[14:41] <BluesKaj> well it hasn't worked for 2 yrs ..me of little faith 
[14:42] <clivejo> k3b is getting love and attention from devs, so it helps to encourage them, not dis their hard work
[14:44] <BluesKaj> well, my impression was that it was being neglected due it's inability to burn disks, but it's nice to know that it's finally getting some attention by our devoted devs.
[14:45] <tsdgeos> BluesKaj: you really need to get your facts straight sir
[14:47] <tsdgeos> apologies, misread "hasn't worked" for "hasn't been worked"
[14:47] <BluesKaj> Idid say it was my impression tsdgeos , but the fact is in my experience that K3b fails, every time.
[15:09] <BluesKaj> just tried K3b on my Lenovo laptop qith Yakkety and unfortunately it fails to burn on it as well
[15:09] <BluesKaj> with
[15:21] <clivejo> Riddell: can you organise KDE git sync with git hub?
[15:21] <Riddell> clivejo: who? what? me? I know nothing
[15:21] <clivejo> sure you do!  You know everything about everyone
[15:22] <clivejo> https://github.com/TelepathyIM/telepathy-morse/ > https://cgit.kde.org/telepathy-morse.git/
[15:22] <clivejo> the devel seems to be using github as main repo
[15:24] <clivejo> I emailed the devel and he said "TelegramQt is also available on Github ([4]) and I don't have reasons
[15:24] <clivejo> to update kde mirrors"
[15:24] <clivejo> so maybe they can be sync'ed somehow?
[15:26] <Riddell> KDE doesn't run mirrors, if he's not using KDE git then it's not a KDE project any more
[15:27] <clivejo> oh ok
[15:27] <Riddell> goodness knows the correct process to deal with that, probably there isn't one
[15:28] <clivejo> only way is for him to sync it?
[15:29] <Riddell> I've e-mailed kde-community to ask
[15:30] <clivejo> my email is messed up at the moment
[15:31] <clivejo> so I cant reply to him
[15:44] <BluesKaj> clivejo, that's why i have a gmail acct, it can come in handy when a simple communique' is in order
 Valorie: release notes good to go for Alpha 2?
 Actually nix that
 I just noticed that all of the tests aren't completed
 That said, I'm disinclined to release
 Anyone feel otherwise?
 @wxl23, I can do a whole lot of QA quick
 Need me to?
 Or is there another reason why you don't want to release?
 That's the reason mainly
[19:55] <tsimonq2> I can get them done
[19:55] <tsimonq2> Syncing ISOs now.
 I'm a bit concerned about the encryption test not working but my guess is that's ultimately an uncommon concern
 Plus there are ways around that, albeit annoying ones
[20:01] <tsimonq2> @wxl23: Ok, so am I still including Kubuntu in the release announcement? I can still test after I release global, then we can release Kubuntu when I'm done?
[20:02] <valorie> release notes need a look from a devel
[20:02] <valorie> and there are no bug reports unless someone added them
[20:02] <tsimonq2> acheronuk, clivejo: PING PING PING PING PING go look over release notes please?
 I guess if the other tests are ok,  include it. We'll need info on how to solve the encryption thing
[20:05] <tsimonq2> Ok cool.
 The bug reports from the tracker need to be added
[20:05] <acheronuk> link?
[20:07] <tsimonq2> acheronuk: https://wiki.ubuntu.com/ZestyZapus/Alpha2/Kubuntu
[20:10] <valorie> I have a draft announcement for the website as well, once we have an alpha2 release
[20:11] <valorie> I hope ahoneybun can look it over before publishing
[20:12] <tsimonq2> valorie: Well I'm the guy releasing global, I'll let you know when it's passed my QA testing and we can go forward.
[20:12] <valorie> cool
[20:12] <valorie> bleah, why is that damn image broken
[20:12] <valorie> on the release notes
[20:24] -queuebot:#kubuntu-devel- Builds: Kubuntu Desktop amd64 [Zesty Alpha 2] has been marked as ready
[20:24] -queuebot:#kubuntu-devel- Builds: Kubuntu Desktop i386 [Zesty Alpha 2] has been marked as ready
[20:31] <wxl> now that i've looked further, i don't think the encryption bug has an easy work around
[20:34] <wxl> needless to say that bug will definiately need to be in the release notes (it's marked on the qa tracker if you need the bug number)
[20:36] <tsimonq2> wxl: Ok, waiting on slangasek to release.
[20:53] -kubuntu-ci:#kubuntu-devel- Project yakkety_unstable_k3b build #21: NOW UNSTABLE in 23 min: http://kci.pangea.pub/job/yakkety_unstable_k3b/21/
[20:53] -kubuntu-ci:#kubuntu-devel- Project xenial_unstable_k3b build #20: NOW UNSTABLE in 23 min: http://kci.pangea.pub/job/xenial_unstable_k3b/20/
[21:02] -kubuntu-ci:#kubuntu-devel- Project zesty_unstable_k3b build #20: NOW UNSTABLE in 32 min: http://kci.pangea.pub/job/zesty_unstable_k3b/20/
[21:18] <tsimonq2> Fresh Alpha 2 release, hot off the press!
 *KDE Community
 Not Project
[21:20] <valorie> ?
[21:23] <valorie> bleah, no editing on the draft yet
[21:24] <clivejo> acheronuk: do you understand what slangasek is saying?
[21:24] <tsimonq2> clivejo: I do.
[21:24] <tsimonq2> clivejo: You don't?!?
[21:25] <clivejo> tsimonq2: please explain it with examples
[21:25] <clivejo> I need to see the code
[21:27] <acheronuk> dpkg-architecture -e s390x
[21:27] <acheronuk> gives an exit status code 0 if you are on s390x
[21:29] <tsimonq2> clivejo: Give me the package name and I'll write a solution for you.
[21:29] <tsimonq2> Basically we need a filter.
[21:29] <clivejo> I dont want you to write it, I want to write it myself
[21:30] <tsimonq2> But I can't describe it, I need to write it.
[21:31] <clivejo> can you show me an example of it in action?
[21:32] <tsimonq2> Give me the package and I can make that your example... lol
[21:33] <acheronuk> you don't need the package. it's just logic to exit the testsuite with a pass exit code if it's run on s390x
[21:34] <tsimonq2> acheronuk: OR
[21:35] <tsimonq2> 03:27:04 PM <tsimonq2> Best way to disable a debian/tests test for only one arch?
[21:35] <tsimonq2> 03:27:18 PM <tsimonq2> I can't find it, if you could link, I can RTFM :)
[21:35] <tsimonq2> 03:28:06 PM <slangasek> dpkg --print-architecture
[21:35] <tsimonq2> 03:28:15 PM <slangasek> check the value, filter on it, exit 0
[21:35] <tsimonq2> Never said I couldn't ask him directly. :P
[21:35] <tsimonq2> 03:28:18 PM <slangasek> in your test script
[21:35] <tsimonq2> 03:28:30 PM <tsimonq2> kthx
[21:35] <clivejo> thanks so much
[21:36] <clivejo> ever considered being a parrot?
[21:36] <acheronuk> which is what I was saying. and could be applied to any testsuite and any package
[21:39] <tsimonq2> acheronuk: Good idea
[21:53] <clivejo> tsimonq2: waiting....
[21:58] <tsimonq2> clivejo: What?
[21:58] <clivejo> write a generic filter to exit if the arch is s390x
[21:59] <tsimonq2> 03:29:54 PM < clivejo> I dont want you to write it, I want to write it myself
[22:00]  * clivejo face palms
[22:00]  * clivejo mutters about ashtrays on motorbikes
[22:06] <tsimonq2> Going to nap, be back in a few hours.
[23:09] <soee> Plasma 5.9 next week \o/
[23:10] <soee> Kubuntu 16.04 will stick to 5.8 LTS though?
[23:14] <valorie> soee: I believe that is the plan, yes
[23:14] <soee> +1
[23:20] <clivejo> so on first run of k3b, Im getting "Unable to find cdrskin executable
[23:20] <clivejo> K3b uses cdrskin in place of cdrecord.
[23:20] <clivejo> Solution: Install the libburn package which contains cdrskin"
[23:20] <clivejo> looks like we need a runtime dep on that
[23:20] <acheronuk> makes sense
[23:21] <clivejo> !info cdrskin
[23:22] <clivejo> yup, installing cdrskin solves it
[23:35] <acheronuk> does it work?
[23:37] <clivejo> will I try burning a disc?
[23:44] <acheronuk> clivejo: https://autopkgtest.ubuntu.com/packages/kdeconnect/zesty/s390x
[23:50] -kubuntu-ci:#kubuntu-devel- Project xenial_unstable_k3b build #21: STILL UNSTABLE in 21 min: http://kci.pangea.pub/job/xenial_unstable_k3b/21/
[23:50]  * clivejo high-fives acheronuk
[23:51] -kubuntu-ci:#kubuntu-devel- Project yakkety_unstable_k3b build #22: STILL UNSTABLE in 22 min: http://kci.pangea.pub/job/yakkety_unstable_k3b/22/
[23:51] <acheronuk> must work out how to do that for several architectures in one go, in case we need that in the future
[23:59] -kubuntu-ci:#kubuntu-devel- Project zesty_unstable_k3b build #21: STILL UNSTABLE in 30 min: http://kci.pangea.pub/job/zesty_unstable_k3b/21/