[02:03] <tsimonq2> !info plasma-look-and-feel-org-kde-breezedark-desktop
[02:03] <tsimonq2> longest package name I've ever seen ^
[02:07] <ahoneybun> lol
[02:07] <tsimonq2> like seriously :P
[02:08] <ahoneybun> it is a long name
[02:08] <ahoneybun> I guess it would be hard to know what it was otherwise
[02:09] <tsimonq2> yofel: ...why can't it be simpler? :P ^
[02:57] <ahoneybun> tsimonq2: I found a wordpress theme called Buntu lol
[03:00] <tsimonq2> heh
[04:17]  * ahoneybun has removed python3-aptdaemon.pkcompat and doing an upgrade
[04:17] <ahoneybun> over 700 updates lol
 Here we go, did I break it? Lol
 Well what do you know Plasma remembered my settings for the panel and wallpapers
[05:15] <valorie> ahoneybun: has Plasma ever forgotten your settings?
[05:18] <ahoneybun> everytime
[05:18] <ahoneybun> it switchs the panel and wallpaper
[05:18] <valorie> hmmm
[05:18] <ahoneybun> puts them on the wrong screen
[05:18] <tsimonq2> o/ valorie 
[05:18] <valorie> hi tsimonq2
[05:19]  * ahoneybun wonders if he broke his system removing that package
[05:20] <ahoneybun> anyone know anything about how Plasma handles tray icons?
[05:30] <valorie> tsimonq2: did all your merge requests get taken care of?
[05:30] <valorie> sometimes I see the request, and no answer
[05:31] <valorie> then I wonder
[05:44] <tsimonq2> valorie: huh?
[05:45] <tsimonq2> valorie: I haven't submitted an MP since I was a yellow belt :P
[05:45] <tsimonq2> and all have been approved
[06:03] <valorie> ok
[06:04] <valorie> I was still working through my older email
[06:04] <valorie> gonna get even futher behind until I get back from Germany.....
[06:08] <tsimonq2> off to bed for me o/
[06:09] <valorie> niters
[08:48] <acheronuk> Morning :)
[10:14] <blaze> acheronuk: have you used apt on yakkety?
[10:21] <acheronuk> blaze: used, yes. but how do you mean?
[10:22] <blaze> is it buggy?
[10:23] <blaze> I always see some error messages everytime i run it
[10:23] <acheronuk> blaze: no more than normal that I've noticed
[10:23] <acheronuk> what errors
[10:26] <blaze> assertion failed
[10:27] <acheronuk> not seen anything like that, and I do a fair bit via apt/apt-get rather than a package manager
[10:31] <mparillo> blaze: Are you running Synaptic? Or apt in the command line?
[10:32] <blaze> acheronuk: mparillo: that's what I got http://wstaw.org/m/2016/08/21/x01_21_08_2016_13_28_43.png
[10:38] <acheronuk> blaze: from that appstream-0.9.8, I would guess you have the version of appstream from yakkety-proposed installed?
[10:39] <acheronuk> 0.9.7-1 is the release pocket version
[10:40] <acheronuk> possible that could be the reason. maybe
[10:42] <blaze> oh
[10:42]  * blaze is downgrading
[10:43] <acheronuk> blaze: if not that, then I'm not sure
[10:50] <blaze> yep, libappstream3 0.9.8-2 that's what it was
[10:57] <acheronuk> blaze: great :)
[10:58] <acheronuk> that you fixed it, that is
[10:58] <blaze> :)
[11:44] <BluesKaj> 'Morning folks
[11:47] <acheronuk> BluesKaj: afternoon
[11:47] <BluesKaj> Hi acheronuk
[11:51] <BluesKaj> interesting, system monitor process table didn't show update-apt-xapian index at all on yakkety, mind you there were over 400 upgrades yesterday
[12:12] <mparillo> BluesKaj: 400 upgrades on YY yesterday? Do you still have the three -staging repositories enabled?
[12:13] <BluesKaj> mparillo, no 
[12:13] <mparillo> TY, logging off XX to check YY.
[12:20] <mparillo> Thanks BluesKaj. 364 packages can be upgraded.
[12:21] <mparillo> To be removed: libkwineffects7 libtaskmanager5 plasma-discover-private plasma-discover-updater 
[12:40] <mparillo> Thanks BluesKaj: Looks like many of those YY updates for me were Plasma 5.7.2 and KDE Frameworks 5.24.
[12:41] <BluesKaj> mparillo, yeah, same here
[13:25] <pursuivant> muon (master) v5.6.0-8-ge0123c8 * Carlo Vanini: src/DetailsTabs/MainTab.cpp
[13:25] <pursuivant> hide purge button when marked for change
[13:25] <pursuivant> When a package with residual config was marked for purge, the purge
[13:25] <pursuivant> button was still shown. Hide it, like the other buttons.
[13:25] <pursuivant> http://commits.kde.org/muon/e0123c8fc8b8982cb03792aaa6e4408b3462976d
[15:14] <santa_> valorie: the mails from my merge requests for getting frameworks building with gcc 6 reached the kubuntu-devel mailing list, see:
[15:15] <santa_> https://lists.ubuntu.com/archives/kubuntu-devel/2016-August/010661.html
[15:15] <santa_> https://lists.ubuntu.com/archives/kubuntu-devel/2016-August/010662.html
[15:15] <santa_> https://lists.ubuntu.com/archives/kubuntu-devel/2016-August/010663.html
[15:15] <santa_> https://lists.ubuntu.com/archives/kubuntu-devel/2016-August/010676.html
[15:15] <santa_> https://lists.ubuntu.com/archives/kubuntu-devel/2016-August/010664.html
[15:15] <santa_> but the problem here is not acheronuk not getting the mails from that
[15:16] <santa_> the problem here is that after more than 2 years after sending my first patch I still don't have git permissions
[15:16] <santa_> not even to push the smallest and most obvious fixes
[15:17] <santa_> see the kjsembed patch for instance https://code.launchpad.net/~panfaust/kubuntu-packaging/+git/kjsembed/+merge/302705
[15:18] <santa_> besides the changelog entry, it just changes *one* line. and it was discussed previously that it was the correct solution. and it fixes a build failure
[15:18] <santa_> god help me when I have to change something less important or more complex
[15:19] <santa_> also note that I mentioned the gcc 6 build failures for frameworks several times:
[15:20] <santa_> Mention #1: https://irclogs.ubuntu.com/2016/08/10/%23kubuntu-devel.html#t12:34
[15:20] <santa_> Mention #2: https://irclogs.ubuntu.com/2016/08/11/%23kubuntu-devel.html#t17:14
[15:20] <santa_> Mention #3: https://irclogs.ubuntu.com/2016/08/11/%23kubuntu-devel.html#t21:50
[15:20] <santa_> Mention #4: https://irclogs.ubuntu.com/2016/08/11/%23kubuntu-devel.html#t22:19
[15:20] <santa_> Mention #5: https://irclogs.ubuntu.com/2016/08/19/%23kubuntu-devel.html#t18:4
[15:20] <santa_> Mention #6: https://irclogs.ubuntu.com/2016/08/20/%23kubuntu-devel.html#t13:12
[15:22] <santa_> valorie: so you asked me in the mailing list for a "sustained contribution"
[15:24] <santa_> it's perfectly fine and legit that you asked for that, but please consider that I have been working here for a long time without the slightes warranty that I'm not wasting my time
[15:24] <santa_> slightest
[15:28] <santa_> also besides that unpleasant uncertainty: each time I work on a patch or something ....
[15:29] <santa_> are you aware that many many times I have to spend more time humoring someone to include my patches than writing the patches in question?
[15:30] <santa_> and that being said, do you think this kind of things help me towards keeping a sustained contribution?
[15:32] <santa_> I was told I would be getting git permissions after passing the membership process
[15:33] <santa_> so that would be the end of these kind of problems
[15:37] <santa_> but please think a bit about what you (you=kubuntu) can do to be a nice place to work
[15:37] <santa_> it's really sad that after 2 years I *still* have to work like this
[15:39] <santa_> and sorry for the wall of text, I don't mean to offend, just pointing out some things, which, in my opinion, must be improved
 santa  everywhere has a similar policy about pushing code
[17:20] <santa_> ahoneybun: well, I'm also a KDE developer, after sending *3* patches to the mailing list I got SVN permissions
[17:23] <santa_> ahoneybun: also, note that this in KDE you get permissions to push code to *any* KDE software, however that's not used as an excuse to not give you the permissions you need to do a proper job
[17:23] <santa_> for instance I don't consider myself to be technically capable enough to make decisions about a patch for plasma for example
[17:24] <santa_> because I never worked on plasma
[17:25] <santa_> so if I happen to have a fix for plasma, instead of pushing it directly (I could do that because in KDE when you get SVN/git permissions you get puhs access to everything), I would use the reviewboard
[17:38] <santa_> ahoneybun: now compare it to what we have here: I have been sending patches for 2 years, and when I ask for git permissions I just got called "incompetent" in my face https://irclogs.ubuntu.com/2016/08/02/%23kubuntu-devel.html#t20:11
[17:40] <santa_> ahoneybun: and that's kind of fun because in case you haven't noticed I have been packaging KDE sfotware for ~ 7 years meaning I probably have more experience than many people who already got access, including yofel
[17:41] <santa_> so please reconsider a bit the way you are dealing with "new" contributors
[17:42] <santa_> it would be nice if they way you deal with new people would be more oriented to help people getting in, rather than keeping them out
[17:44] <santa_> * the way
[17:44] <shepster52> Caution! newbie present!  Greetings,  I have Ubuntu running the KDE window manager/desktop.  Question:  What is the difference between what I am running and an install of Kubuntu?
[17:47] <acheronuk> shepster52: You are welcome :), but this is a development channel, so that Q would probably be better on #kubuntu
[17:48] <santa_> hi shepster52, maybe this question would be more appropiate for #kubuntu, anyway I don't think you will find much difference if you installed the kubuntu-desktop metapackage
[17:48] <santa_> oops
[17:49] <acheronuk> shepster52: but not much difference, except you will have kubuntu in addition to whatever DE you had before
[17:49] <acheronuk> snap * 2
[17:50] <santa_> haha
[18:09] <tsimonq2> santa_: do all the GCC6 fixes look similar to kjsembed ?
[18:10] <santa_> tsimonq2: well there are some which change like 3 lines of the symbols files instead of one if that's the question
[18:10] <tsimonq2> ok
[18:11] <tsimonq2> here's what I'm willing to do, if you give me the heads up that kjsembed works exactly as intended in KCI, I'll go through and approve all your MPs
[18:11] <tsimonq2> I'm figuring out how to approve it now :P
[18:12] <tsimonq2> santa_: and I'm really sorry you're feeling this way. By the way, to get Git access, you'd be looking to get Ninja, not Membership ;)
[18:13] <santa_> tsimonq2: it was Ninja what I asked, see yofel's reply above
[18:15] <santa_> tsimonq2: regarding the gcc6 patches they are targeted to the _archive branch, but once you get them there you could merge them to _unstable
[18:16] <tsimonq2> santa_: so with the fixes you presented, would you like those to go into a specific archive or just in KCI for now?
[18:16] <santa_> tsimonq2: the way I see is the following
[18:17] <santa_> they are right now in yakkety 5 frameworks which are failing to build, that's a fact
[18:17] <acheronuk> tsimonq2: I tested an equivalent KCI change for kjsembed I think....
[18:18] <tsimonq2> santa_: 5 is ambiguous, you mean the PPA or in the archive?
[18:18] <acheronuk> tsimonq2: https://git.launchpad.net/~kubuntu-packagers/kubuntu-packaging/+git/kjsembed/commit/?id=7be5a25a261be957a80dcc1f4e5b8c2a42c740ec
[18:18] <santa_> tsimonq2: any. both archive and staging have 5.24
[18:19] <santa_> so now you could release yakkety with fw 5.24 or 5.25
[18:20] <santa_> now lets say you go for 5.24 -> my patches should be included otherwise you would release yakkety with packages which fail to build from source
[18:20] <tsimonq2> I'm not comfortable merging into kubuntu_yakkety_archive quite yet. that's yofel's job.
[18:20] <santa_> now let's say you go for 5.25 -> my patches should be included, and then you can pacakge 5.25 on top of that
[18:21] <tsimonq2> yeah
[18:22] <santa_> ] <tsimonq2> I'm not comfortable merging into kubuntu_yakkety_archive quite yet. that's yofel's job.
[18:22] <tsimonq2> but I'm not! :P
[18:23] <santa_> note that my criticism (I hope you understand it as constructive criticism) is not about rushing my patches but about how kubuntu deals with new, upcoming contributors
[18:23] <tsimonq2> I understand fully :)
[18:23] <tsimonq2> I'm new here too
[18:23] <tsimonq2> well, you aren't
[18:24] <tsimonq2> but I think it's about the trust of the people involved, otherwise you won't get anywhere
[18:24] <santa_> well, actually I should say "third class citizens"
[18:24] <tsimonq2> I got ninja in a week and a half because I worked hard. who says it shouldn't be the same for you?
[18:25] <santa_> I have been sending patches here for about a couple of years
[18:26] <tsimonq2> that being said, Philip seems to have some reservations. I'd be good to work with him and find out what exactly he would like to see. :)
[18:26] <santa_> and I disagree you got it because you worked hard. don't get me wrong, I'm pretty sure you worked hard
[18:27] <santa_> you got ninja because someone decided to make you ninja
[18:27] <tsimonq2> because afair with him being I *think* the only active developer, his vote of yes or no determines it
[18:28] <santa_> which exactly the problem
[18:29] <tsimonq2> the problem there is we lack developers :)
[18:30] <santa_> yeah, well, you won't get more developers this way
[18:33] <tsimonq2> we have clivejo and acheronuk and myself who eventually (if not already) will be candidates for being a developer, so you're wrong there :)
[18:33] <tsimonq2> but, you're a special case
[18:33] <tsimonq2> again, I had a nice turnaround time on my MPs
[18:33] <tsimonq2> but for some reason not yours
 The issue is your past actions santa
[18:34] <santa_> ahoneybun: what past actions?
 You disappeared before for one
 I've been around for a solid 2 1/2 year and have only seen you around a little
[18:39] <santa_> ahoneybun: too bad you weren't paying attention, because I sent a lot of patches https://code.launchpad.net/~panfaust/+merges
[18:40] <santa_> ahoneybun: and I could afford to be more active if didn't have to spend more time humoring someone else to include my patches than writing the patches in question
[18:40] <tsimonq2> santa_: hey now, in that patch, there was something I found that wasn't right
[18:41] <tsimonq2> you wanted to merge into kubuntu_yakkety_archive
[18:41] <santa_> ahoneybun: also note that the link doesn't include the patches I sent when the packaging was in debian's git
[18:41] <tsimonq2> yet you had it as UNRELEASED
[18:41] <santa_> ahoneybun: so you may find more in the kubuntu-devel mailing list
[18:42] <santa_> tsimonq2: that's not wrong, that's intended
[18:42] <tsimonq2> yofel: asking on behalf of the release team (me and Set are doing the flavor-side) is Kubuntu participating in Beta 1?
[18:42] <tsimonq2> santa_: that's wrong, you never do that
[18:42] <acheronuk> tsimonq2: even YY archive stays as unreleased in the changelog, until it actually is.
[18:42] <tsimonq2> acheronuk: but I mean as a top entry?
[18:43] <tsimonq2> am I wrong here?
[18:43] <santa_> tsimonq2: no, it's not. the packages are failing to build in yakkety
[18:43] <santa_> so this way they can be used to upload an update to yakkety
[18:44] <tsimonq2> santa_, acheronuk: so we have to ask ourselves, WWYD?
[18:44] <tsimonq2> :D
[18:44] <acheronuk> tsimonq2: yes, as once released you increment the version on the next change, and as that has not been released it should be UNRELEASED
[18:44] <tsimonq2> acheronuk: but don't those changes go directly into the archive then?
[18:45] <acheronuk> tsimonq2: not until yofel does it and changes it to released when he does
[18:45] <tsimonq2> santa_: so on those MPs you submitted, that's great, thank you, but I'm not good enough at this to merge into kubuntu_yakkety_archive. If you fix something in KCI and want to merge into kubuntu_unstable, I'll be happy to approve if it seems reasonable. :)
[18:45] <tsimonq2> acheronuk: ahhh gotcha
[18:46] <tsimonq2> santa_: after all, we have a LOT of different errors in KCI ;)
[18:46] <shepster52> thanks all
[19:10] <valorie> santa_: just got to my keyboard
[19:10] <valorie> I'll read up before responding
[19:15] <tsimonq2> o/ valorie 
[19:16] <acheronuk> evening valorie :)
[19:17] <tsimonq2> acheronuk: so did we ship apps 16.04.3 or is that still a WIP?
[19:18] <valorie> it's just past noon!
[19:18] <tsimonq2> ik it's just past 2 PM for me!
[19:18] <acheronuk> tsimonq2: WIP to become a FFE I think
[19:18] <valorie> timezones are fun
[19:19] <santa_> tsimonq2: it's not in the archive yet if that's the question
[19:19] <santa_> I also have some important pending reviews for it
[19:19] <santa_> (no pun intended)
[19:20] <tsimonq2> acheronuk: what are we waiting on?!?
[19:21] <valorie> that was my question yesterday. It's not just santa_ that has had merges and changes and stuff published on the list that have had no answers on the list
[19:21] <valorie> but I don't know who needs to do approvals etc.
[19:22] <valorie> having only on Kubuntu Developer right now is a holdup, as is having no MOTU 
[19:22] <tsimonq2> well if I'm getting this right, unless we're uploading fixes to packages in a staging PPA, yofel does kubuntu_yakkety_archive (clivejo too?), and the rest of us all could probably do kubuntu_unstable
[19:23] <tsimonq2> yeah ik :/
[19:23] <valorie> santa_: I do not think you are wasting your time
[19:23] <valorie> I think we all share your frustration, because everyone is working hard
[19:23] <tsimonq2> agreed
[19:23] <valorie> and it seems to take forever to get changes made
[19:24] <tsimonq2> well except for the ninjas which have access but even then, I have no clue why we're waiting on apps 16.04.3
[19:24] <valorie> on the other hand, things are moving in a good direction, and much more quickly than they were last cycle for instance
[19:24] <tsimonq2> I garee
[19:24] <tsimonq2> *agree
[19:25] <valorie> I thought we were all gonna have heart attacks by the time of 16.04 release
[19:25] <tsimonq2> well that sucks, 'cause over at Lubuntu land I was twiddling my thumbs :P
[19:27] <tsimonq2> santa_: we appreciate your efforts, I'd just be able to do more if you proposed fixes against kubuntu_unstable :)
[19:29] <valorie> tsimonq2: much of the frustration is that riddell used to be able to take our tested stuff and get it into the archive
[19:29] <valorie> now we are constantly waiting on them
[19:30] <valorie> clogs all of our processes us to wait for work we did weeks or even months ago just languish
[19:30] <tsimonq2> we need a MOTU don't we?
[19:30] <valorie> that too
[19:30] <tsimonq2> argh I wish I could do more
[19:31] <valorie> one thing at a time
[19:31] <tsimonq2> I know :|
[19:31] <valorie> we've been fixing our tooling, and that is working better, right?
[19:31] <valorie> our packages seem to be in pretty good shape
[19:31] <mparillo> It seems to me that having the larger project control Qt hurts. In an emergency (and we are not there yet, right?) didn't Scott offer to help out?
[19:32] <valorie> yes, waiting on Ubuntu for Qt does hurt
[19:32] <valorie> I don't know a way around that
[19:32] <tsimonq2> well that's just how transitions work :P
[19:33] <valorie> mparillo: ScottK can help with some Debian stuff, yes
[19:33] <valorie> but I believe he's stepped down from all of his former Ubuntu jobs
[19:34] <blaze> that's because some kde man have made Mark nervous and the Riddel was second
[19:34] <blaze> saw it with my eyes
[19:37] <valorie> not sure what you mean, blaze?
[19:39] <blaze> the reason behind all that commotion
[19:39] <blaze> with kubuntu council etc
[19:42] <valorie> blaze: "some kde man"?
[19:43] <valorie> I was there, on the Council, and I don't know what you are talking about
[19:48] <valorie> anyway, ScottK still loves us, and so do shadeslayer, and riddell, and sitter
[19:48] <valorie> but they aren't working with us as a matter of course
[19:50] <blaze> btw, I'm not familiar with the official version of what happened
[19:51] <mparillo> And I thought some of those remain MOTU and were willing to upload in an emergency.
[19:53] <valorie> shadeslayer is a MOTU and will upload in an emergency
[19:53] <valorie> and has done so
[20:53] <acheronuk> clivejo: can you change config on KCI? prison has done away with frameworks branch and merged it to master, so I think KCI needs to pull from there?
[23:10]  * acheronuk wonders how to update the KCI version of prison when it has been 'debianabimanagered'
[23:17] <acheronuk> tsimonq2: what happened with all the merge markers here? https://git.launchpad.net/~kubuntu-packagers/kubuntu-packaging/+git/messagelib/commit/?h=kubuntu_unstable&id=4c8509f665aba222136ca27250d696fecbc3ba29
[23:22] <acheronuk> yofel, if you should be around, would updating the prison packaging in the way Neon have here: http://packaging.neon.kde.org/cgit/frameworks/prison.git/commit/?h=Neon/unstable&id=d7962eb1ec3a8fb2e9b79fc5f106cd7a31577718
[23:23] <acheronuk> need any modification for the debianabimanager?