[01:18] <mamarley> So it looks like the latest build of kde-spectacle from staging-kdeapplications depends on all of Telepathy (transitively through libkf5purpose).
[02:14] <ahoneybun> well that's new
[02:14] <ahoneybun> the panel is up top but off the screen
[02:17] <ahoneybun> anyone notice the new system tray option in making a new panel?
[04:24] <tsimonq2> Fixing the merges
[04:25] <valorie> that's lovely tsimonq2
[04:26] <tsimonq2> valorie: :)
[04:27] <tsimonq2> valorie: I have a magical Git setup that likes to fix about half the merges that fail in KCI automatically XD
[04:27] <tsimonq2> s/automatically/on it's own/
[04:40] <tsimonq2> hehe I literally had to do nothing for that one ^
[04:54] <tsimonq2> that was me
[04:54] <valorie> awesome
[04:55] <tsimonq2> (talking about the ABORTED)
[04:55] <tsimonq2> but the rest of the recent green was mine :)
[04:55] <tsimonq2> me as well
[04:58] <valorie> \o/
[04:58] <tsimonq2> I did it \o/
[04:58] <tsimonq2> all merges are fixed!
[04:58] <valorie> that is wonderful
[05:00] <tsimonq2> I'm just a >< little nervous about marble, so I aborted those because they've had a history of green, they were started by the nightly, there weren't any recent code changes, and I only wanted to wait on the direct upstreams of marble
[05:00] <tsimonq2> I'm maybe a little impatient but what I did wasn't bad ;)
[05:01] <valorie> marble is one of those monsters
[05:01] <tsimonq2> it is, which is why I got a little nervous when my merge merged *45* commits
[05:01] <tsimonq2> I double checked everything...
[05:02] <valorie> as I recall, they package a bunch of their own libs
[05:02] <tsimonq2> idk tbh
[05:03] <valorie> there has been talk of moving them to frameworks, but not so far
[05:16] <tsimonq2> I'm gonna see if I can fix kanagram in apps staging
[05:17] <tsimonq2> I'll get it working in my PPA then once I'm absolutely 100% sure it works, I'll copy it over to staging-kdeapplications
[05:36] <tsimonq2> couldn't figure that out, gonna find something to fix
[05:36] <valorie> fix PIM!
[05:36] <tsimonq2> I take requests... :P
[05:37] <tsimonq2> working on kdepim now
[05:37] <valorie> oh nice!
[06:37] <tsimonq2> kdepim is building in staging-kdeapplications now
[06:41]  * valorie crosses fingers
[06:41] <valorie> the neon team was saying it took like 20 hours to build
[06:41] <tsimonq2> s/hours/minutes/
[06:42] <tsimonq2> that's more accurate
[06:42] <tsimonq2> I built it in another PPA first and then copied it over
[06:42]  * tsimonq2 takes the time and updates https://wiki.ubuntu.com/tsimonq2
[06:42] <acheronuk> tsimonq2: you aware that most of the errors, lintian etc, only show with the amd64 builds on that QA page?
[06:42] <tsimonq2> oh HAI acheronuk :D
[06:43] <tsimonq2> I'm aware
[06:43] <acheronuk> HAI?
[06:43] <tsimonq2> I've been looking at both
[06:43] <tsimonq2> acheronuk: HAI = HI
[06:43] <acheronuk> just double checking. it's easy to click the i386 and miss a lot
[06:44]  * tsimonq2 nods
[06:44] <acheronuk> oh, and Hi :)
[06:45] <tsimonq2> Sunday morning for you?
[06:45] <tsimonq2> I should sleep but I'm not :P
[06:45] <acheronuk> 07:45 am (urgghhh)
[06:45] <tsimonq2> I'm 6 hours behind you
[06:45]  * acheronuk slurps more coffee
[06:46] <tsimonq2> wow if I continue to keep track of *everything* and put it *all* on my wiki page, it's going to get HUGE
[06:46] <tsimonq2> XD
[06:47] <acheronuk> I keep wondering how verbose to be on mine
[06:48] <tsimonq2> I link to everything
[06:48] <tsimonq2> if I ever need to refer to anything, there's my reference sheet XD
[06:48] <valorie> you don't need to put what is already on your LP
[06:49] <tsimonq2> but it's not *just* on LP, there's also my UWN contributions etc.
[06:49] <acheronuk> well depends, mine will be a quick ref for an eventual application (perhaps) so probably need more detail
[06:50] <tsimonq2> well that's what I mean
[06:51] <tsimonq2> I keep mine *so* up-to-date I can apply for anything I'm eligible for and it's a nice overview of my work
[06:51] <valorie> it's good to remember, for sure
[06:51] <valorie> I keep forgetting
[06:52] <acheronuk> valorie: whole PIM stack may take 2hrs on their build machine
[06:52] <acheronuk> *20hrs
[06:53] <valorie> sooner started, sooner done
[06:53] <acheronuk> the single kdepim package itself, without the preceding parts, take about 30mins on LP though I think?
[06:53] <valorie> I'm happy we can have PIM this time out
[06:53] <valorie> and have Trojita as an alternative now
[06:55] <acheronuk> apps and PIM 16.08 is out now! don't think they are going in YY..
[06:55] <acheronuk> without a FFE anyway
[07:00] <valorie> really?
[07:00] <valorie> then we should get the FFEs going, shouldn't we?
[07:01] <tsimonq2> FF isn't in effect yet
[07:01] <tsimonq2> it's on the 18th
[07:16] <acheronuk> I know, but it's also v close in terms of getting 16.08 done
[07:23] <tsimonq2> hey acheronuk, I had a typo in an MP that you approved when I was still a Yellow Belt, it was an obvious and glaring one too :P
[07:24] <acheronuk> was probably getting mailbombed with MPs at the time :P
[07:24] <tsimonq2> oh, who would do such a thing? :P XD
[07:40] <acheronuk> yofel: clivejo for thing like in kdepim W: kalarm: executable-not-elf-or-script etc/xdg/autostart/kalarm.autostart.desktop
[07:41] <acheronuk> does that just needs it's path correctly in KA lintian-ignore.json so the QA page doesn't orange on it, or still needs a real override, or both, or neither?
[07:42] <acheronuk> *need it's path correcting
[07:48] <tsimonq2> yofel, clivejo, acheronuk: loop me in on this too? I'm curious as well :)
[08:11] <tsimonq2> I need sleep o/
[08:12] <valorie> sleep!
[08:24] <acheronuk> tsimonq2: you uploaded a changed build of kdepim, but I see no corresponding change in kubuntu_yakkety_archive git?
[08:31] <acheronuk> yofel: https://launchpad.net/ubuntu/+source/kdepim-addons/16.04.3-1
[08:32] <acheronuk> so should our version be a -1ubuntu or a -0ubuntu in light of that?
[08:36] <acheronuk> ditto with https://launchpad.net/ubuntu/+source/libkf5grantleetheme/16.04.3-1
[08:38] <acheronuk> after synced with debian I mean
[08:50] <santa_> good morning everyone
[09:07] <acheronuk> morning santa :)
[09:09] <mamarley> So it looks like the latest build of kde-spectacle from staging-kdeapplications depends on all of Telepathy (transitively through libkf5purpose).
[09:10] <santa_> and that's a bad thing?
[09:10] <santa_> (sorry, no clue about spectacle)
[09:11] <mamarley> Yeah, I don't particularly want to have to install all of Telepathy (which I don't use).
[09:22] <acheronuk> mamarley: libkf5purpose-dev was an optional build dep on that, so quite possibly ok to leave out again
[09:22] <mamarley> acheronuk: That would be my preference, if it matters. :)
[09:25] <acheronuk> mamarley: If I can evict telepathy from my system, and keep spectacle at the same time, that would be my pref as well. Now that I see the consequence of that.
[09:27] <mamarley> acheronuk: Thanks!  I'm not trying to complain or be a pest, and I really do appreciate all the work that you guys do. :)
[09:38] <acheronuk> mamarley: not at all. hugely better for that to be pointed out now :D
[09:38] <mamarley> :)
[10:50] <acheronuk> clivejo: NoWorries o_O
[11:02] <santa_> acheronuk: reagrding the desktop files not executable I would put an override. but I can't say that adding the thing to the .json ignore is wrong
[11:03] <santa_> tsimonq2: ↑
[11:05] <santa_> acheronuk: btw the lintian warnings about symbols files injecting dependencies on -bin packages were already overriden by yofel. as I said, that was the correct solution for that
[11:05] <santa_> https://www.youtube.com/watch?v=4g8RqFnHz4Q
[11:15] <soee> i have 2 more drafts for B&B widget
[11:24] <soee> http://wstaw.org/m/2016/08/14/layout-all.png
[11:24] <soee> what do you think ?
[11:33] <santa_> soee: my favourite one is the 3rd because it seems the most complete and nice looking one. but it's just my opinion
[11:36] <soee> santa_: yes but all 3 are one widget
[11:36] <soee> thy show content of each tab
[11:38] <santa_> ah, I see, nevermind
[11:39] <santa_> soee: looks good to me, in what version of plasma do you expect to provide it?
[11:40] <soee> not me, kai wants to change it in 5.8 i think
[11:40] <soee> together with Media widget
[11:40] <santa_> aha
[11:41] <soee> 5.8 LTS should be cool release :)
[11:52]  * ahoneybun wakes up to bug comment about a different product on kdenlive...
[12:01] <ahoneybun> clivejo: think I should not release that blog post about yakkety?
[12:27] <BluesKaj> Hi folks
[12:32] <ahoneybun> heyo
[14:19] <ahoneybun> going to beat soee to it: https://www.kde.org/announcements/kde-frameworks-5.25.0.php
[14:19] <ahoneybun> lol
[14:20] <soee> hihi :D
[14:21] <soee> i'm doing some design changes atm. so  im using http://i.imgur.com/Lkuy0Ql.png
[14:23] <soee> working on a ultra wide screen is so cool: http://i.imgur.com/isaqwCy.png :)
[14:25] <ahoneybun> they built it already?
[14:25] <soee> build what>
[14:25] <ahoneybun> FW 5.25
[14:26] <soee> today was some  bigger update but this is dev-unstable
[14:26] <soee> version, so a lot of updates all the time
[14:26] <ahoneybun> mm
[14:26] <ahoneybun> stupid packagekit
[14:27] <soee> :)
[14:27] <ahoneybun> I have broken packages
[14:27] <soee> :o
[14:27] <soee> on what > YY ?
[14:27] <ahoneybun> yea
[14:27] <ahoneybun> http://pastebin.ubuntu.com/23055695/
[14:30] <soee> uhm some version problems
[14:34] <ahoneybun> mm
[14:34]  * ahoneybun installs libastro1
[14:35] <ahoneybun> that did not work
[14:36] <soee> i am nood when it comes to all this dependencies :)
[14:36] <soee> you need to ask some ninja
[15:33] <soee> someone up ?
[15:33] <soee> need some opinion :D
[15:33] <blaze> bout what?
[15:37] <soee> final battery widget redesing
[15:37] <soee> one moment
[15:40] <soee> http://wstaw.org/m/2016/08/14/layout-all_4.png
[15:41] <soee> from a home user point of view, anyone would add something here ?
[15:45] <ahoneybun> what gens the Power messages? 
[15:47] <soee> i'm not sure, system somehow generates them
[15:47] <soee> here is just dummy text except the first one
[15:48] <ahoneybun> darn can't install any software with my system like this
[15:49] <ahoneybun> clivejo: can I remove packagekit?
[16:16] <ahoneybun> valorie: heyo
[16:25] <blaze> soee: looks good
[16:25] <blaze> I'd rather improve task manager
[16:26] <blaze> it's extremely inconvinient for me
[16:30] <soee> what is wrong with it ?
[16:49] <ahoneybun> !info packaging-dev
[17:01] <ahoneybun> tsimonq2: added some stuff https://github.com/ahoneybun/kubuntu-manual/blob/master/README.md
[17:35] <ahoneybun> http://www.aelog.org/kio-gdrive-is-still-alive
[17:46] <tsimonq2> acheronuk: I *knew* I was missing something...
[17:56] <acheronuk> tsimonq2: what?
[17:57] <tsimonq2> acheronuk: re: kdepim and yakkety_archive
[17:57] <acheronuk> oh right
[17:59] <acheronuk> I figured that was just an accidental omission
[18:05] <soee> what is the package name for system language ?
[18:06] <soee> http://i.imgur.com/gk5z5WA.png
[19:02] <soee> !info update-apt-xapian-index xenial
[19:13] <clivejo> ahoneybun: install the packagekit from proposed
[19:13] <clivejo> that should work
[19:16] <clivejo> done nothing but sit around and eat, I’m knackered!!
[19:19] <tsimonq2> let's say there's a native Debian package with version 4
[19:19] <tsimonq2> I want to make an Ubuntu revision
[19:19] <tsimonq2> would the correct action be to make the version 4ubuntu1 or 4-1ubuntu1 ?
[19:19] <clivejo> simon_1.0.0-4 ?
[19:20] <tsimonq2> !info lxqt-core
[19:20] <tsimonq2> that ^
[19:20] <clivejo> simon_1.0.0-4ubuntu1
[19:20] <tsimonq2> not lxqt-core-4ubuntu1 ?
[19:21] <tsimonq2> clivejo: I don't know what you're sayinh
[19:21] <tsimonq2> *saying
[19:21] <clivejo> this - https://launchpad.net/ubuntu/+source/lxqt-metapackages/4 ?
[19:22] <clivejo> thats weird
[19:22] <clivejo> lxqt-metapackages (4) unstable; urgency=medium
[19:24] <tsimonq2> yeah
[19:24] <tsimonq2> it is weird
[19:24] <clivejo> santa_: do you know?
[19:26] <tsimonq2> I don't like Launchpad, it's so slow...
[19:26] <tsimonq2> that, and why wouldn't the build logs dynamically update like Jenkins?
[19:26] <tsimonq2> stupid...
[19:28] <santa_> tsimonq2: I would say it would be 4ubuntu1
[19:28] <tsimonq2> great, then I win XD
[19:28] <santa_> but be careful with my advices about ubuntesque stuff
[19:28] <tsimonq2> alright :P
[19:29] <tsimonq2> clivejo: I think we have to ask the question... WWYD?
[19:29] <clivejo> I have no idea!
[19:29] <clivejo> hes AFK 
[19:29] <tsimonq2> yofel: WWYD? ^
[19:30] <santa_> I mean I'm familiar with the packaging tech, but not so much about the ubuntesque bureaucracy, workflows, etc
[19:30] <santa_> what's WWYD?
[19:30] <tsimonq2> santa_: What Would Yofel Do?
[19:30] <santa_> ah
[19:31] <clivejo> that seems to be named that way in Debian
[19:31] <tsimonq2> yeah wth?
[19:32] <clivejo> I thought debian had strict standards!
[19:32] <tsimonq2> I guess maybe they get away with it because it's a native package
[19:32] <tsimonq2> santa_: thoughts? ^
[19:33] <ahoneybun> clivejo: that remove the apt fix
[19:33] <clivejo> huh?
[19:34] <ahoneybun> http://pastebin.ubuntu.com/23056393/
[19:34] <clivejo> is that the proposed packagekit?
[19:35] <santa_> tsimonq2: sorry, I'm a bit confused, which package are you working on?
[19:35] <ahoneybun> idk I just have staging
[19:35] <tsimonq2> !info lxqt-core
[19:35] <tsimonq2> santa_: ^
[19:35] <clivejo> https://launchpad.net/ubuntu/+source/lxqt-metapackages/4
[19:35] <clivejo> ahoneybun: there is a ton of stuff stuck in proposed
[19:36] <clivejo> and our stuff in PPA's is built using it
[19:37] <ahoneybun> mm
[19:37] <santa_> tsimonq2: and what's the problem if you use the version 4ubuntu1?
[19:38] <clivejo> I wouldnt enabled it directly cause if could kill kittens
[19:38] <clivejo> santa_: we just trying to figure out the correct version for ubuntu
[19:38] <tsimonq2> ^
[19:38] <clivejo> but Ive never seen a package with just an integer version !
[19:39] <santa_> I would say "4ubuntu1" if you plan to fix something in the package and upload it to ubuntu
[19:39] <tsimonq2> me neither
[19:39] <tsimonq2> ok cool santa_ 
[19:39] <santa_> well, it's a native package
[19:39] <clivejo> if I was a betting man Id go with santa
[19:39] <santa_> samke as "our" meta-kde but without the epoch
[19:40] <santa_> I'm betting here too
[19:40] <santa_> I wish I can get some time to read about this kind of stuff
[19:43] <tsimonq2> hmm
[19:43] <tsimonq2> https://bugs.launchpad.net/lubuntu-next/+bug/1387237
[19:44] <tsimonq2> so there's two ways to solve this
[19:45] <tsimonq2> work around it by implementing all the code that is in lxqt-common in lubuntu-qt-default-settings (which idk if that's against Debian policy or not) or fix the actual bug at hand
[19:45] <tsimonq2> anyone have any ideas?
[19:48] <tsimonq2> I wonder if it would be possible to split lxqt-common into two packages. that way, lxqt-core can still pick up on lxqt-common, and lubuntu-qt-default-settings can conflict on the other package
[19:49] <tsimonq2> I think that's entirely possible, right?
[19:53] <tsimonq2> let's see how that works
[21:46] <yofel> tsimonq2, clivejo, santa_: 4ubuntu1 would be my best bet. native packages are always a bit annoying in that regard
[21:47] <tsimonq2> yofel: what about the solution I presented above?
[21:47] <tsimonq2> have an opinion?
[21:53] <yofel> forking code would not go against the policy, though patching the original one sounds easier. And yes, what you said is certainly possible, but I don't know enough about the package contents to give proper advice about that
[21:53]  * yofel tried to install lubuntu-qt-desktop earlier and is not quite sure why apt insists on installing sddm-theme-breeze
[21:54] <tsimonq2> because sddm depends on it 
[21:54] <tsimonq2> or at least recommends it
[21:54] <tsimonq2> but we have our own sddm theme
[21:57] <santa_> yofel: btw are yu aware that they are at least a couple of syncs from debian in proposed? https://irclogs.ubuntu.com/2016/08/14/%23kubuntu-devel.html#t08:24
[21:58] <yofel> yes, and providing an alternative for sddm-theme *should* make apt be happy, but it's not :/
[21:58] <yofel> santa_: yes I am, needs working out when we upload apps
[22:04] <santa_> yofel: ok, but do you have a plan or you wll figure it out later?
[22:24] <yofel> santa_: you can see on the PPA details page on launchpad which packages have a higher version in the archive already. So for all apps packages where that's the case someone has to do a merge
[22:24] <tsimonq2> yofel: well to make this more clear, lxqt-common stores some files in /etc/xdg and so does lubuntu-qt-default-settings (not uploaded yet, so currently, lubuntu-default-settings). The bug makes it so the default LXQt files are used for certain things before lubuntu-qt-default-settings. I wanted to split out the /etc/xdg files from lxqt-common and make that package a conflict of lubuntu-qt-default-se
[22:24] <tsimonq2> ttings, so lubuntu-qt-default-settings' settings are the only one installed when using lubuntu-qt-desktop. It's a temporary workaround until the path bug is fixed
[22:24] <tsimonq2> make sense?
[22:26] <yofel> makes sense as a workaround
[22:27] <santa_> yofel: you mean a git merge from master I guess
[22:37] <yofel> santa_: that would be easiest
[22:47] <yofel> hm, our konsole packaging is buggy. konsole-kpart should be enough to run yakuake, but there's kpart pieces in 'konsole'
[22:48] <tsimonq2> yofel: when you have a min, could you please help me debug muon installed via lubutnu-qt-desktop?
[22:49] <tsimonq2> s/lubutnu-qt-desktop/lubuntu-qt-desktop/
[22:49] <tsimonq2> it seems like it's missing something...
[22:50] <clivejo> the muon package manager?
[22:51] <tsimonq2> well we have muon and muon-discover
[22:53] <tsimonq2> clivejo: I'd get you the error, but I'm doing a reinstall of that VM
[22:54] <yofel> just got it running on my netbook, so might as well
[22:54] <tsimonq2> lubuntu-qt-desktop? :O
[22:54] <tsimonq2> so try and launch it and you'll hopefully see my error :)
[22:54] <yofel> using mini.iso and aptitude :P
[22:55] <tsimonq2> EEEEWWWWW aptitude...
[22:56] <yofel> well, that allowed me to install lubuntu-qt-desktop without sddm-theme-breeze, as that explodes on plasma.desktop
[22:56] <tsimonq2> oh
[22:56] <valorie> tsimonq2: why are you still calling it muon-discover?
[22:56] <valorie> it is now plasma discover
[22:56] <tsimonq2> valorie: because that's the package name...
[22:56] <tsimonq2> bah
[22:56] <valorie> that's ooooold
[22:56] <tsimonq2> yofel: can we take this to #lubuntu-devel ?
[23:00] <clivejo> muon-discover is no more
[23:01] <tsimonq2> ok
[23:01] <clivejo> the muon package manage is standalone now
[23:02] <tsimonq2> yeah we depend on muon and muon-discover, I'm poking Julien (dev lead) now
[23:02] <clivejo> but surely you should be able the share the same packaging?
[23:02] <clivejo> do you guys have a seed?
[23:03]  * tsimonq2 throws http://bazaar.launchpad.net/~lubuntu-dev/ubuntu-seeds/lubuntu.yakkety/view/head:/desktop-qt at clivejo 
[23:04] <clivejo> that be why
[23:04] <tsimonq2> hm?
[23:04] <tsimonq2> clivejo: what needs to be corrected?
[23:04] <clivejo> muon-discover needs to become plasma-discover to pull in the new version
[23:04] <tsimonq2> ok, I'll try that in my VM
[23:05] <tsimonq2> meanwhile, I've given Julien a poke
[23:05] <clivejo> yeah try it out
[23:05] <clivejo> its built into the plasma desktop so might want to pull in half of kubuntu!
[23:05] <tsimonq2> awwwwwwww
[23:05] <tsimonq2> come on...
[23:06] <clivejo> try it
[23:07] <tsimonq2> clivejo: can we move this conversation to #lubuntu-devel ?
[23:07] <clivejo> I dont know anything about lubuntu :/
[23:07] <tsimonq2> well this is Lubuntu-related... :P
[23:07] <clivejo> but I was involved in getting Muon into xenial
[23:10] <yofel> clivejo: more like you're missing half the conversation