[00:05] lol [00:05] oops [00:05] Kinfocenter reports Plasma 5.4.3 [00:05] No obvious breakage. [00:06] wxl: Do you have corrections for the wire post? [00:07] mparillo: change the kubuntu-ppa link from bugs.launchpad.net to launchpad.net :) [00:08] Good catch, thanks. [00:08] np. thank YOU :) [00:13] wxl: But the link refers to reporting bugs in the packaging. [00:34] mparillo: released 5.4.3 to backports if you can write up on wire and whatnot, when you can of course. [00:35] TY. I am still confused on my link to bugs, because that is where we want to report them if they are packaging? [00:35] soooo sgclark what do I do? [00:35] mparillo: wily that is. [00:36] ahoneybun: I will look when I can. doing a million things. [00:36] no no [00:36] mparillo: I think pehaps make it more clear that that is a link for bug reporting and not the repository. [00:36] if 5.4.3 is in backports what do I do with the staging [00:37] instructions are on my site. basically you want to ppa-purge after testing. [00:37] add backports if it is not already. [00:43] done, thanks sgclark [00:43] sgclark: what is our timezone diff? [00:43] 3 hours [00:44] tomorrow I'm off [00:44] if we could work on KApps 15.08.3 [00:44] sgclark: btw plasma-workspace needs some fixing [00:44] sgclark: http://dci.pangea.pub/job/plasma/job/plasma-workspace_binary_unstable/arch=amd64/116/console [00:44] in case you can work on it, if not, I can get to it tomorrow [00:44] ahoneybun: running apps now. [00:45] oh [00:45] ( FWIW I think KCI is not being on worked on thes days actively ) [00:45] shadeslayer: I am trying but so much is borked at this point. [00:45] sgclark: that failiure is from ksld being split [00:45] sgclark: right, would recommend just looking at DCI [00:45] for core stuff [00:45] shadeslayer: ok thank you [00:45] a little less borked than KCI since I've been trying to not let the red count go up [00:46] excellent [00:46] it won't catch QA things, but lets get things building first [00:46] lol yes, that is a good start [00:46] thank you very much sgclark and shadeslayer [00:49] np [01:01] mm and the monitor works now [01:01] odd === claydoh_ is now known as claydoh [01:18] sgclark: re your blog announcement, shouldn't the title say "kubuntu-backports" instead of "wily-backports"? I only say this from past experience in what people read and see, lol! [01:19] claydoh: ahh ok, I just wanted to make sure folks know it is only Wily. Kubuntu is in the title. [01:20] I can add kubuntu I guess [01:20] I know, but some will see it as the wily-backports lol, there is probably n o good way to say it [01:21] KDE 5.4.3 Bugfix release Available now for Wily in Kubuntu Backports. ok? claydoh [01:22] perfect ;) thank you for the awseomeness you bring ;) [01:23] * claydoh was very recently describing all the different ppas and official component [01:23] * claydoh is sure it was confusing to them [01:23] confuses me haha [02:55] very cool that you are going to Munich, sgclark [02:56] Riddell: perhaps the KC can ask you to be "treasurer" or something? [02:56] thanks [02:56] so you have a Title or so [02:56] will be a very busy weekend [02:56] :-) [02:56] indeed [03:04] valorie: ubuntu community funding request submitted [03:06] excellent! [03:06] thanks to all who are making this event happen [09:06] valorie: that's a good idea [09:08] sgclark: seems you angered the merger? :P [09:49] Good morning. [09:53] * nluxton waves [10:44] yofel, sgclark: http://kci.pangea.pub/view/xenial/ [10:44] please tell me if or when you want vivid to be nuked [10:44] currently it would CI all three series [10:47] sitter: nice one :) [10:53] sitter: unless sgclark vetoes, now. I don't care about vivid anymore [11:12] PPA exceeded its size limit (19531.00 of 16384.00 MiB). Ask a question in https://answers.launchpad.net/soyuz/ if you need more space. [11:12] guess I'll be wiping it now :P [11:12] sitter: Which PPA? :) [11:13] wgrant: kubuntu-ci/unstable AND kubuntu-ci/unstable-daily AND kubuntu-ci/unstable-weekly [11:13] Good lord! [11:13] ah, they got Qt5.5 landed [11:13] I guess that would push them over [11:14] sitter: All fixed so you don't have to wait a few hours for them to clear. [11:14] wgrant: thank you <3 [11:14] yofel: I think we should drop the weekly PPAs btw [11:15] seeing as they involve(d) human QA they never got a lot of updates and were always outdated for all but one version [11:18] I'll leave that up to you guys, I never used any of the -daily/weekly archives. Daily is useful with the bit of QA it has, weekly probably not, right [11:18] daily is out of date as well since kdepim decides to not fix ABI breaks btw [11:19] meh [11:19] core requirement is that all jobs at least aren't red, which they all are thanks to ABI breakage :/ [11:36] sgclark: thanks for 5.4.3 release [11:39] ok looking good [11:50] * yofel needs to start making notes for the CI to talk about in munich.. [11:56] Hi saw this review: http://www.hecticgeek.com/2015/11/ubuntu-15-10-flavors-comparison/ [12:08] Ridgewing: I wonder is that with the bluz bug? [12:12] 52.6 seems a bit long? [12:13] I also noted that, from the GRUB menu, Kubuntu 15.10 took about 20-22 seconds before it started to run the display-manage [12:26] accoring to the hardware specs he mentioned, the bluez thing shouldn't affect him [12:28] since systemd ubuntu starts slower [12:28] blame mr. poettering [12:30] https://en.wikipedia.org/wiki/Correlation_does_not_imply_causation [12:34] well - the long bluez timeout of the network manager was independant of having BT hardware. Already patched upstring, now running BT detection async. [12:42] jmux: patched in wily-updates as well since yesterday. [12:43] but IIRC it only affected users without or disabled BT interfaces [12:44] regarding startup speed with systemd: Yes, it's slower, but the difference is so small that it really isn't that much of a problem [12:45] Well - we'll be switching from 12.04 to 14.04 next year - systemd problems won't hit us before 2018... [12:47] consider yourself happy === rdieter_work is now known as rdieter [13:33] clivejo, Which one is the bluz bug ? https://launchpad.net/+search?field.text=bluz === bruno-RDD is now known as Wiz-TDD [13:39] Ridgewing: https://bugs.kde.org/show_bug.cgi?id=354230 [13:39] KDE bug 354230 in general "Blocking calls from PlasmaNM to BlueZ for 30s" [Normal,Resolved: fixed] [13:40] Good discussion on KFN, real answers start around here: https://www.kubuntuforums.net/showthread.php?69153-Plasma-long-loading-after-login&p=380979&viewfull=1#post380979 [13:40] Note that things have been much better for me, but I am mostly on the daily build now. [13:42] mparillo: It says that it's closed. Is this is case of 'closed' but not forgotten ? [13:43] It means it is fixed upstream. So, the distros need to package the fix. [13:43] hi everyone [13:44] I believe Kubuntu has (not because I know the Launchpad bug off-hand), but because my boot times have greatly improved. [13:45] gootta go .. don't believe it santa. === rdieter is now known as rdieter_work [13:57] people wouldn't need to believe if they would read the bug comments ^^ [14:01] yofel: Sorry, now I scrolled to the bottom of the BKO, I see: https://bugs.launchpad.net/ubuntu/+source/plasma-nm/+bug/1509334 [14:01] Launchpad bug 1509334 in plasma-nm "[sru] plasma-nm blocks temporarily on startup w/o bluetooth device – KDE/Plasma very slow to launch (Kubuntu 15.10)" [Medium,Fix released] [14:10] Hiyas all [14:22] good morning [14:23] 'Morning sg [14:23] sgclark, :-) [14:24] yeah I did a booboo sitter. unfortunately it was late too. Here to fix now though. Please nuke Vivid. === Tm_Tr is now known as Guest15900 [14:38] Does someone know where the Feedback column on Trello came from and what it's used for? [14:40] no clue === mck182___ is now known as mck182|brb [14:42] hi everyone.. short question: regaridng this message here: http://wire.kubuntu.org/?p=424 [14:43] why does a "bugfix" release not come to the normal stable repositories? [14:43] because our scripts are missing the required functionality right now. Will follow in a week or two [14:44] ahh ok .. so ill get 5.4.3 also without adding backports? [14:44] yes, but you might have to wait... a while [14:45] yofel: thx i was just interested in the procedure :) [14:45] better wait some time than having too many bugs ;) [14:51] sitter: is kubotu lying around somewhere or did the code get deleted (or something)? [15:04] Quintasan: should https://trello.com/c/1zKvQUph/17-package-and-get-ksuperkey-available-by-default still be assigned to you? Any update on it from your side? [15:09] yofel: I don't appear to have access to ubottu.com anymore [15:10] aah, drat [15:10] or maybe I am just doing it wrong xd [15:10] doesn't like me [15:10] perhaps that server imploded at some point? [15:10] would also epxlain why kubotu is not here considering I setup a cron to bring it up on startup === mck182|brb is now known as mck182 [15:16] yofel: the feedback was from Kubuntu Promo for the website [15:37] Mamarok: ping! [15:41] ahoneybun: does that still need it's own column? If it's just untriaged todo items then put them into the backlog [15:42] it was for feedback that people left about the website during its dev [15:44] riiight, can't that just be tagged as "website, feedback" or so? [15:45] we have the backlog column for stuff where we don't know if it makes sense or whether we really want to do it, so the extra column feels out of place to me [15:45] But if you consider it important then leave it [15:45] I think we can just use tags [15:46] to keep it a bit more clean [15:47] sgclark: hey, have a min for a quick PM? [15:47] jose: sure thing === clivejo_ is now known as clivejo [16:55] yofel: what's going on with debian merges? [16:56] santa_: just the regular we-started-a-new-release-cycle-and-need-to-sync-with-debian merge [16:56] santa_: https://trello.com/c/TCAk2U9J/71-debian-merges [16:59] santa_: do you have a place where you track TODO's for the automation stuff? [17:00] yofel: nope, but right now I think it already has the minimal functionality to work decently [17:02] ftr I have just used it for siduction/plasma5.4.3 and works [17:03] ok, then we can maybe try to generate the wily SRU packages using that [17:03] hmm, not sure it will work out of the box for that but I could tweak whatever has to be changed [17:04] I think right now it could be used for xenial + staging, but it's untested [17:04] not sure as I haven't checked how scarlett generated the first set. But at least the versions and changelog need fixing for that [17:05] xenial wasn't done either, but that's stuck on a broken packageset for now [17:05] I just used the old scripts hacked to use backports branch. [17:06] have not touched xenial due to we need to do merges [17:06] aah ok [17:06] so if wily_archive wasn't touched this should be fairly easy [17:06] nope was not touched [17:06] perfect [17:07] ok, may I work with clivejo on xenial? [17:07] well sure, but nobody will be able to upload it [17:07] ? [17:07] work with what? [17:08] getting plasma 5.4.3 and apps .3 on xenial [17:08] though I HAVE to work with my KDE hat on a bit today, that to do list is mounting. [17:08] a lot of packages are missing from our packageset, so nobody here currently has full upload permissions for plasma [17:08] and fixing that is non-trivial because of germinate [17:08] I was under the impression we were going to work on the beta releases there... [17:08] what is the point of doing a point release on xenial? [17:08] yes, but for the .3 SRU to be uploaded to wily it first has to be in xenial [17:09] ahh [17:09] that's policy [17:09] I see [17:09] hmm, let me check the current versions then [17:09] nm santa_ seems I have some policy reading to do. 5.4.3 on xenial it is [17:10] https://wiki.ubuntu.com/StableReleaseUpdates#Procedure point 1 [17:10] thanks yofel [17:11] it's simple: never upload something to -updates that has a higher version than the one in the dev release [17:12] ok, so what to do now? [17:12] but also note: never upload something to -updates that contains changes meant for the dev release (which is why the packages currently in backports only qualify for backports) [17:12] although, you might not have done that [17:13] one thing we could do is merging the current kubuntu_wily_backports branches into kubuntu_xenial_archive and work from there [17:15] *sigh* didn't someone want to get new hardware for moszumanska? :/ [17:15] I can help patching broken merges if that's needed, and I have the impression that clive is also available to do that [17:16] would be an idea, I hope to have the packageset fixed until the weekend [17:17] you will have to merge stuff as there are already xenail changes in the repo [17:18] no prob, I will try to have a look soon [17:19] yofel: afaik I did not upload anythinng meant for dev release. [17:20] ok, I just assumed so because that's what "backports" usually means [17:20] workflow chaos XD [17:20] yes [17:21] sorry. I really have much to learn. [17:22] well, that's normal. I think the last time we did proper SRUs was trusty, and you weren't around much back then [17:22] (hence why staging-upload has a huge commented-out code block that nobody ever bothered to finish) [17:23] the complicated part is that the SRU team doesn't like no-change rebuilds, and a large part of that code is the detection for that [17:25] ahh [17:25] that makes sense. think debian is the same in that [17:25] and yeah trusty is when I first started on this adventure [17:26] so really xenial will be my first LTS [17:26] fun fun [17:34] oooooh, scarlett for CC. voted :D [17:34] lol the secret is out. That is reason I could not KC === genii is now known as fishbot === fishbot is now known as genii === rudydog is now known as monkeyjuice [21:07] sgclark: how is the apps building going ? [21:08] ready to test! soee [21:08] aleady ? :) [21:08] lol just hit the publish on blog post [21:08] yep, bugfix releases usually do not have tons of major changes [21:09] my kmail works once again. woot [21:09] in the backport or staging? [21:10] sgclark: [21:10] staging, needs testing first [21:10] !testers [21:10] testers is Help is needed in #kubuntu-devel. Please ping Riddell, yofel, soee, Tm_T, shadeslayer, BluesKaj, James147, Quintasan, lordievader, shrini, tester56, parad1se, mamarley, alket, SourBlues, sgclark, neo31, vip, mparillo for information [21:10] sgclark: installing [21:11] unless staging disabled for me I dont have them yet [21:11] or the chance to upgrade [21:11] ppa:kubuntu-ppa/staging-kdeapplications [21:11] ohh [21:11] right [21:11] I have the plasma one [21:12] yeah it is best practice to add and remove those ppas as needed or things can explode [21:12] opps [21:12] of course I love exploding desktops [21:12] KDE Apps in staging for Wily? [21:12] learn lots getting it functional again lol [21:12] I don't lol [21:12] mparillo: correct [21:13] * ahoneybun removes staging plasma [21:13] I dont really either haha [21:13] makes it difficult to work [21:13] I don't like rebuilding tomuch [21:13] upgrading [21:14] ahoneybun, is this for 15.10? [21:14] after release we shoudl mentioned to teh users taht they can install extra package with plasma wallpapers [21:14] sgclark: download/upgrade fine, rebooting [21:16] sgclark: back, all seems to be fine [21:17] cool, now go use some of the apps you normally use and make sure they do not go boom! lol [21:17] the wallpapers sounds like something for a kubuntu docs section [21:17] like for instance I am finding ktp is not liking google application passwords [21:17] oh, you have that asking for a password all the time too? [21:19] it will not even let me change it. I am rather confused, it used to work [21:19] yes BluesKaj [21:20] telegram account adding barfs too [21:20] I'm more annoyed that ktp-auth-handler is asking me for a password for an account that doesn't exist [21:20] probably some old config file still has the account and there's like no "normal" way to delete it [21:20] I think I am missing something [21:21] sounds likely yofel [21:21] sgclark: there is no backend for telegram I thin [21:21] no konsole update? [21:21] oh [21:21] still at 15.08.0 [21:21] I have not rebooted yet but [21:21] mm [21:21] let me look ahoneybun [21:21] dolphin says 15.08.3 [21:22] yup it shows 15.08.0 [21:22] mm I can no longer click new tab on top of firefox, omg how annoying [21:23] * ahoneybun heads out [21:24] sgclark: new tab click (+) works fine here [21:24] heh yes seems konsole was not in application list. Here is where yofel s handy work will come in handy I expect. [21:24] which? ^^ [21:24] keeping current list of applications? [21:25] weird, the package list file has konsole [21:26] hmm probably my fault then. Using an older rev to hack the backports bit. [21:29] nope, this is weird, it did get run. Just not uploaded. very strange [21:31] hm, I git-clone-all doesn't work for me [21:31] * yofel goes patching [21:31] err it did get uploaded konsole - 4:15.08.3-0ubuntu1~ubuntu15.10~ppa1 [21:33] sick_rimmit: whats up with your internet?!? [21:36] sgclark: Working great here, thanks for your work! :) [21:37] sgclark: I am upgrading 164 packages [21:42] santa_: what the hell is git-ssh-kubuntu? [21:45] ah, I'm blind [21:46] * clivejo whistles [21:46] lets try this [21:46] If muon does not progress under new maintainer, what will become the default package manager? [21:46] apt I guess? [21:47] Hm [21:47] cli is awesome [21:47] or well, people can go back to synaptic I guess [21:47] yofel: I generally use apt/dpkg myself, but I am thinking of the GUI people [21:48] hence synaptic. The use case for a *package* manager is so small that one application in the archive is probably enough [21:48] yofel: OK, thanks [21:48] muon was great, but qapt had and has too many problems [21:49] oh, git-clone-all also adds the remotes, nice [21:50] santa_: please merge our automation-ng branch, thanks [21:52] gulp [21:52] what did you do? ^^ [21:53] LOL [21:53] sorry, wrong window [21:53] XD [21:53] meteor app [21:53] was trying to run gulp [22:04] yofel: ping [22:05] hm? [22:06] yofel: system booted with nvidia profile .. After i changed it through nvidia-settings and tried to logout it freezed with some bbswitch command, but after reboot i'm on nvidia [22:06] interesting [22:06] haven't tried that lately, my uptime is 24 days ^^ [22:07] sgclark: I re-booted and Dolphin 15.08.3, Konsole, Muon Update Manager, Rekonq, and Kinfocenter show no obvious breakage. [22:07] great :) [22:08] brb [22:09] ximion: shadeslayer: do either of you have a blog about your trip to akademy I can link to from the community donations report? [22:10] yofel: ok, will do after dinner if I stay awake [22:11] mhall119: I only have http://blog.tenstral.net/2015/08/akademy-2015.html , no detailed report though [22:12] interesting blog ximion! [22:17] thanks ximion [22:18] mhall119: is that link working for you? [22:18] nope, just checked it [22:18] I just get "wat?" [22:18] same [22:18] ximion: ^^ [22:18] are you on IPv4-only? [22:18] yes [22:19] okay, then I know the cause - stupid Nginx [22:21] genii: I was under the impression that Muon Discover and Muon Updater are being maintained, and I think Muon-"proper" hasn't shipped by default in a while? So for CLI-phobic folks or just ease of quick use there'd still be GUI methods shipping with Kubuntu. [22:21] Hm [22:21] * keithzg isn't quite sure he's qualified, but has thrown his hat into the ring as possible help for maintaining Muon [22:22] I've grown to rather prefer it to Synaptic and I'd hate to see it go, although yeah, with Discover+Updater on one end and good ol' apt on the other it wouldn't be the end of the world. [22:23] mhall119, clivejo: should be fixed now, can you please verify? [22:23] ximion: fixed [22:23] wat he said! [22:23] ^^ [22:24] genii: if Muon does not progress, it will simply stay :P [22:24] only if it doesn't get ported to Frameworks6 it will vanish [22:25] but I am pretty sure it will find a new maintainer - I am still wondering if I could find someone to help with Apper for all the !Debian-based distros [22:26] ximion: Apper's the PackageKit frontend, eh? [22:26] yes [22:27] https://quickgit.kde.org/?p=apper.git [22:28] needs some bugfixing and finish of the KF5 port - but so far nobody did the work, and there are just numerous requests from Arch and Fedora to update it [22:28] in that regard, Debian and Kubuntu are much better off ;-) [22:28] Well, we have better package management anyways ;) [22:31] Although looking at the git repo commit messages at least it looks like it wasn't *that* long ago that the last work on porting to KF5 was done, just back in July, and some build fixes were done late-October. [22:35] Ah ha keithzg Hi Riddell mentioned you in respect to Muon-installer [22:37] sick_rimmit: Heya. Yeah, I saw Riddell's blog post and had commented there. [22:42] yofel: didn't we used to be able to create those new packages bugs via IRC? is that still possible? [22:42] no, which is why I asked about kubotu. The script the bot was running is in kubuntu-dev-tools [22:42] ah, oki [22:51] ok, git-clone-all + some random shell scripting and we hopefully have a working packageset [22:54] +1 [22:58] yofel: where is it up to? [22:58] clivejo: what? [22:59] the tools [22:59] https://code.launchpad.net/~kubuntu-packagers/+git/kubuntu-automation/+ref/automation-ng [23:05] clivejo: when do you plan to apply for membership btw? ^^ [23:05] membership of what? [23:05] kubuntu [23:06] is it a requirement? [23:07] to contribute, no. It's a requirement for ~kubuntu-dev eventually and some of our stuff is owned by ~kubuntu-members on LP [23:07] and has some additional benefits together with ubuntu membership [23:08] was just curious as you're past the 6 month mark around now [23:08] hmm I dont seem to have access to that, oh wait it is git. guess I have to fiddle with config somewhere. [23:09] sgclark: https://help.launchpad.net/Code/Git [23:10] ty [23:21] and I forgot to fix kwin again. Let me do that before going to bed... [23:46] ovidiu-florin: This is faster than emailing, re: Polylang [23:52] mm kwallet does not seem to want to do anything.