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