15:05:28 #startmeeting kde-sig 15:05:28 Meeting started Tue Aug 9 15:05:28 2016 UTC. The chair is rdieter. Information about MeetBot at http://wiki.debian.org/MeetBot. 15:05:28 Useful Commands: #action #agreed #halp #info #idea #link #topic. 15:05:28 The meeting name has been set to 'kde-sig' 15:05:32 #topic roll call 15:05:37 * lupinix is here 15:05:39 o/ 15:05:41 hi all, friendly kde-sig meeting, who's present today? 15:06:01 * Kevin_Kofler present in the role of QtWebEngine maintainer and QupZilla comaintainer. 15:06:21 #info rdieter tosky_ pino|work lupinix Kevin_Kofler present 15:06:35 * jgrulich is present 15:07:23 hi 15:08:11 #info jgrulich dvratil present 15:08:23 #chair tosky_ pino|work lupinix jgrulich dvratil 15:08:23 Current chairs: dvratil jgrulich lupinix pino|work rdieter tosky_ 15:08:42 than sends regrets (pto) 15:09:05 sends them from some far away island? 15:09:11 Surely a well-deserved vacation. 15:10:01 #topic agenda 15:10:20 ok, we've got the browser vote to do, anything else to discuss today? 15:10:58 i think not, kf5 5.25 is in progress, right? 15:11:04 How to deal with the blockers breaking QtWebEngine and Chromium? 15:11:18 lupinix: yep 15:11:20 we should file them as blockers 15:12:07 https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org/thread/5J74ZUAESCPFPZNJ3HS7ZKCKD2Z32U7U/ 15:12:09 talk with the chromium maintainer too? 15:13:20 ok, let's get started then 15:13:31 #topic f25 kde spin default browser 15:14:44 I think it's been discussed pretty thoroughly onlist, anyone want to have any *limited* discussion here before voting? 15:15:00 nope 15:15:02 ... yet more discussion? 15:15:16 * rdieter will limit to 5-10 minutes at most, if needed 15:15:22 i think points are clear 15:16:44 I thought this was pretty much settled already, but then a new proposal brought yet another non-native browser on the table… 15:17:06 maybe just one note: qtwebengine is really well maintained, checked the git and they backport all chromium fixes :) is also easy to build an updated qtwebengine 15:17:07 I recall we agreed to revisit the issue, which is precisely what we're doing 15:17:37 lupinix: Right, good point. 15:17:50 http://code.qt.io/cgit/qt/qtwebengine-chromium.git/ close to chromium upstream 15:18:31 i'm mentioning it because someone started to discuss the security stuff 15:18:35 Yes. You just need to know which branch is for which Qt version. 15:18:43 exactly 15:18:47 45-based = 5.6, 49-based = 5.7 15:18:50 we have 3 choices: firefox (current default), qupzilla, and chromium, each kde-sig member can cast a range vote of 0-2 for each. 15:19:10 please do so now 15:19:16 47-based is dead because 5.7 was rebased to 49 before release. That's why you see 45-based and 49-based updated and not 47-based. 15:19:35 +2 for qupzilla, 0 for others 15:21:10 +2 chromium, +1 firefox, 0 qupzilla 15:21:15 2 qupzilla, 1 firefox, 0 chromium 15:21:18 +2 firefox, +1 chromium, 0 qupzilla 15:21:24 +2 firefox, 0 chromium (too new), +1 qupzilla 15:21:33 +2 firefox, 0 the rest 15:23:29 Those voting for Firefox, would you care to elaborate why you still insist on Firefox? QupZilla is at least as compatible with current websites as Firefox (which was the argument for picking it over Konqueror). QupZilla is also faster. 15:23:32 ok, I think that's all present kde-sig members, and if I count right, current tally is 15:23:40 Kevin_Kofler: discussion is over for now, maybe later 15:23:50 let's not muddle the results and log 15:24:09 firefox: 6, qupzilla: 5, chromium: 3 15:24:13 Sigh… 15:24:17 Folks, I'm done for it. 15:24:21 rdieter: firefox=8 15:24:26 You can maintain QtWebEngine yourself. 15:24:39 ah, right, thanks 15:24:45 I'm fed up of doing lots of work and then you refusing to ship it. 15:24:55 um, we *are* shipping it 15:25:16 I really worked a lot to provide a good default browser for the KDE Spin. 15:25:28 #info current vote tally: firefox 8, qupzilla 5, chromium 3 15:25:36 Yet you still insist on defaulting to Firefox, which is completely out of place. 15:25:37 we still have several members not present that could swing the vote 15:25:54 Kevin_Kofler: last warning, discussion is over 15:26:05 (here, for now) 15:26:43 Go ahead and ban me if you think that is going to increase the chances that I will continue working for you for free and watching you throw my work away. 15:26:44 I'll reach out to remaining kde-sig members onlist for ask for their formal voting 15:27:13 didn't we vote for removing qupzilla, did we? 15:27:27 Kevin_Kofler: are you really going to make us do that? just sit and relax, the voting is not final (yet) 15:28:30 pino|work: correct, we did not 15:29:27 *if* firefox gets replaced as default, I was going to consider a followup proposal to remove it from the spin too 15:30:06 ok, let's move on 15:30:07 Of course, Firefox should be removed entirely. 15:30:18 Shipping 2 browsers doesn't make sense. 15:30:24 #topic recent updates 15:30:28 dvratil: kf5 status ? 15:31:08 KF5 5.25 is done in rawhide, F23, F24, F25 and EPEL7 builds are running, will be done during today 15:31:50 found a bug in flex-2.6.0 in rawhide which breaks build, needed some small patching in CMakeLists.txt 15:32:23 .rhbz 1364943 15:32:38 thx, plasma-5.7.3 went to f24 stable updates earlier this week, currently still in -testing (5 days) for f23 15:32:40 in case you run to "C++ style comments are not allowed" error when building some KDE apps 15:32:41 * pino|work found a (small) behaviour change in flex 2.6.1 generated output few days ago :/ 15:33:10 pino|work: the problem is fixed in 2.6.1, but rawhide ships 2.6.0 atm 15:33:55 5.25 is still not officially out, let's cross fingers and hope that won't be rebases 15:33:57 good, sounds like the fix is easy then :) 15:35:04 * rdieter imported kde-apps-16.07.90 into rawhide recently, and got almost all into f25 before alpha freeze 15:35:25 (minus digikam unfortunately) 15:35:47 (which needed rebuilding due to soname changes) 15:36:01 dvratil: ah it was triggered by building solid 15:36:34 dvratil: slightly unrelated: if you spot build/compatibility/etc issues in the lex/yacc code in solid and kservice, just poke me asap 15:37:06 pino|work: ok, I only ran int othis issue with flex which is easilly fixed by forcing C99 mode 15:37:23 rdieter: nice! 15:40:42 oh, still didn't import the pim stuff from kde-apps-16.07.90, due to 3 new packages needing review 15:41:03 .bug 1361940 15:41:03 rdieter: An error has occurred and has been logged. Please contact this bot's administrator for more information. - https://bugzilla.redhat.com/1361940 15:41:06 If the version now in the frozen F25 Alpha has broken dependencies, try filing a freeze exception. 15:41:07 silly zodbot 15:41:24 they're on the kde-reviews tracker, https://bugzilla.redhat.com/show_bug.cgi?id=kde-reviews 15:41:46 (for Digikam) 15:41:47 kf5-akonadi-contacts, kf5-akonadi-mime, kf5-akonadi-notes 15:41:59 these 3 replace the formerly monolithic kf5-akonadi (aka kdepimlibs) 15:42:30 Kevin_Kofler: will do, yes 15:43:14 I think that's all I've got, anyone else? 15:44:13 The QtWebEngine blockers are a separate agenda item? 15:44:37 sure, let's move on to that 15:44:52 #topic QtWebEngine and Chromium bugs/blockers 15:45:31 https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org/thread/5J74ZUAESCPFPZNJ3HS7ZKCKD2Z32U7U/ 15:45:43 regardless of default browser, I think the app-crashing bugs are still arguably blockers 15:45:53 We have 3 blockers breaking QtWebEngine (and probably Chromium) on F25 and Rawhide: 15:45:57 (for qupzilla at least, since we do ship it on the spin) 15:46:22 https://bugzilla.redhat.com/show_bug.cgi?id=1363914 ← SELinux issue, the cause is apparently already found and a fix proposed 15:46:30 https://qa.fedoraproject.org/blockerbugs/milestone/25/alpha/buglist we should file them here 15:46:40 https://bugzilla.redhat.com/show_bug.cgi?id=1347436 ← (/dev/shm permissions) initscripts issue, also already debugged 15:47:09 https://bugzilla.redhat.com/show_bug.cgi?id=1364781 ← obscure issue, apparently due to glibc 2.24, but we really really need to track this down in some way 15:47:26 Neither the glibc folks nor me know so far how to find out what is going wrong. 15:47:44 All 3 should probably be filed as release blockers, maybe even Alpha blockers. 15:48:00 (sorry, I need do drop out) 15:48:34 alpha or at least beta 15:48:52 #1347436 already is? 15:48:54 I'm not sure of the criteria, but I'd suggest beta 15:49:19 pino|work: yes, beta blocker 15:50:09 Then there's also the assorted Nouveau breakage (4 bugs linked in the mail), where I don't know how to do anything about them. 15:50:18 They have good backtraces, all pointing straight to Nouveau code. 15:50:28 But the Nouveau developers have not looked at any of them, or at least not replied. 15:50:29 talk with the nouveau people? 15:50:56 Can somebody with better diplomatic skills than me try to poke them? :-) 15:51:20 In an ideal world, reassigning the bugs should be sufficient, but it doesn't look like it. 15:51:36 Having been on the receiving end of floods of ABRT spam, I can also relate to why. 15:51:48 Kevin_Kofler: I suppose we could consider proposing those as blockers too 15:51:50 You just can't manage to even read the mails you get, let alone respond to them. 15:52:16 then be patient with them, really 15:56:09 sounds like a tentative plan, moving on... 15:56:12 #topic open discussion 15:56:16 anything else to discuss today? 15:57:09 How long can we be patient? 15:57:40 The first of the crashes was reported 1½ months ago. 16:01:56 ok, sounds like not, thanks everyone 16:02:13 fyi, I'll followup onlist asking those kde-sig members not present today to vote on the browser proposal 16:02:18 #endmeeting