[00:06] Anyone played with Plasma Next with an HiDPI screen? [00:07] Riddell: analitza didn't make it on armhf. Needs moar symbols. [00:17] Riddell: perlkde's pretty unhappy too. [00:19] Moar symbols on okteta too. [01:05] Riddell: I (hopefully) took care of pykde4. [01:11] armhf symbols needed on marble too. [02:42] thanks valorie for the tip about the metalinks [02:48] Looking at marble. [02:48] pykde4 is fine now. [03:17] Uploaded marble. [05:47] Good morning. [07:22] shadeslayer: mh, no, given the impact I'd say screw it at this point [07:29] "Aurélien Gâteau (agateau) renewed their own membership in the Kubuntu Members (kubuntu-members) team until 2015-06-27" yay agateau still loves us! === OnkV is now known as haudegen === ovidius2 is now known as ovidius === ovidius is now known as ovidius2 [09:11] anyone able to test saving a file in calligra 2.8.3 for ingwa? === Haudegen_ is now known as haudegen [10:32] 'Morning [11:06] shadeslayer: I guess we'll have to live with alpha 1 being oversized === rdieter_work is now known as rdieter [12:46] We've also got some work to do to get stuff from -proposed into -release. [12:47] I started working on it last night. [12:48] been looking at that this morning [12:49] and I'm a bit confused by it [12:50] stuff like nepomuk-core not transitioning and I can't work out why [12:51] * yofel suspects libav [12:53] also needs a rebuild according to http://people.canonical.com/~ubuntu-archive/transitions/html/libav10.html [12:54] aah [12:55] although it shouldn't be stuck on it if it still uses the old lib.. [12:55] britney is confusing [12:55] It is libav. [12:57] nope still don't get it, nepomuk-core-runtime 4:4.13.2-0ubuntu3 Depends: baloo, libavformat55 (>= 6:10~beta1~), libavutil53 (>= 6:10~beta1~) [12:57] that's the new ones it depends on [12:59] well, as long as libav won't migrate nepomuk-core won't either [12:59] but then ben is wrong [12:59] but why's it say bad on http://people.canonical.com/~ubuntu-archive/transitions/html/libav10.html ? [13:03] Good question. [13:06] I'm also confused by https://launchpadlibrarian.net/178435089/buildlog_ubuntu-utopic-armhf.ksudoku_4%3A4.13.2-0ubuntu2_FAILEDTOBUILD.txt.gz - the code in question hasn't changed in years. [13:06] GL code though so something might have changed in mesa for it [13:07] I'm also rebuilding analitza without precompiled headers on cjwatson's advise to see if that fixes it, maybe ksudoku has the same issue [13:07] although at only 3% done it might take my poor wee pandaboard a while to get through analitza [13:07] I'd say heave it at the archive and see what happens. [13:08] anyone want to chair the frameworks meeting today? [13:08] Only if that means I can change the maintenance policy. [13:08] might be a long shot [13:08] No, I've actually got a lot of $work to do today, so I should get on with that. [13:09] sgclark: fancy a new challenge? ↑ [13:10] * sgclark reads [13:10] sgclark: chairing a frameworks meeting [13:11] Riddell: not sure what the challenge is? [13:12] what does that entail? [13:12] sgclark: running the meeting on irc in 50 minutes [13:12] sgclark: pinging everyone who came last week, waiting a bit, announcing dates [13:13] asking each person in turn for any updates [13:13] lol, no idea what I am doing there and would with no problem if I had more than 50 mins to prepare [13:17] hmm, I wonder if I can find another victim [13:26] shadeslayer: In your draft message to ubuntu-devel you suggest not putting kf5 in the archive. I don't think that's what we discussed on the call. I'd think since upstream has released it, it'd be mature enough to put in the archive. [13:29] * shadeslayer looks again [13:30] upstream are also releasing plasma 5 [13:31] ScottK: that wasn't the intention, I simply managed to not write down the part about going into the archive [13:31] OK. [13:31] we could put that in the archive but I think we want to keep plasma 1 for now too so it would mean lots of package renaming [13:31] Riddell: I think we should put that in the archive too. [13:31] I just don't think we should ship it as "Kubuntu". [13:31] Just like we had KDE3 and KDE4 in Hardy. [13:32] yep [13:33] Whatever problems we're going to have due to upstream maintenance policy, I think it's better we have them sooner rather than later. [16:45] analitza (hopefully) fixed. [16:48] shadeslayer: Can you find someone to look into okteta and perlkde? Both are FTBFS and I'm out of time. [16:48] apachelogger: Maybe you? === Haudegen is now known as Guest51891 [17:15] kalzium should build on armhf now. [17:16] sgclark: Our armhf is differnt than Debian's so it's not rare for us to have armhf specific changes. When you did the kalzium merge, you dropped one that kept the package from building. Not a big deal, but FYI. [17:19] ScottK: ahh ok, I will remember that in the future, ty [17:19] * sgclark writes down in her notes [17:20] BTW, seriously, don't worry about making mistakes, only worry about not learning from them. [17:20] (or not following up on them and fixing them, although I already fixed this one) [17:21] ty, yes I fix mistakes I am aware of, sorry I was not aware. I think I need a calendar of releases heh [17:25] Right, I wasn't saying you didn't. I know you're conscientious. Just didn't want you to worry too much about this one. [18:03] * yofel looks at okteta [18:04] Thanks. [18:10] Is bug 1296425 known? Seems it affects only KDE... [18:10] bug 1296425 in alsa-plugins (Ubuntu) "pulseaudio is started twice - effectively making device management impossible." [High,Confirmed] https://launchpad.net/bugs/1296425 [18:12] now that you mention it, I do have pulse running twice o.O [18:14] That's the bug exactly ;) My workaround was disabeling PA's respawn and starting it through ~/.profile. [18:18] apachelogger: ^ any ideas? [18:20] fyi, here's something you might consider backporting in pulseaudio to help address that, http://cgit.freedesktop.org/pulseaudio/pulseaudio/commit/?id=2b85ae048970b7faa7505fd0cd4746541d1b09eb [18:21] (and followup fix, http://cgit.freedesktop.org/pulseaudio/pulseaudio/commit/?id=f46799579f438125b695dced4edf8bca05cbe90a ) [18:22] thanks [18:51] yofel: Can you do perlkde too? [18:51] hm, I'll look at it at least [18:52] ScottK: I'll give it a try [18:52] Thanks. [19:04] ScottK: done [19:04] Thanks. [19:05] I think that's everything for 4.13.2 built then. [21:33] Respinning those, so don't all rush in and test. [21:56] yofel: the real question is why the hell aplay is run actually :P [22:00] driver sl-modem detection calls aplay -l [22:00] this is spooky stuff [22:00] very spooky [22:01] OTOH that should not be run until 4 minutes in the session what with lazy init [22:03] ah, the lazyness in kubuntu-notification-helper is bugged actually [22:03] driver detection is bound to qapt init and that is bound to event construction which bypasses lazy init ^^ [22:03] many bugs piling up \o/ [22:23] apachelogger: Any chance you can fix that like right now so we can have an unbugged Alpha 1 (at least in that respect)? === ScottK changed the topic of #kubuntu-devel to: 14.10 Alpha 1 Candidate Images Available - Test, test, test!!! | https://trello.com/kubuntu | http://qa.kubuntu.co.uk/ | Polo Shirts are available again!! https://holvi.com/shop/Kubuntu/ (Womens also)