15:11:00 #startmeeting kde-sig 15:11:00 Meeting started Tue Jun 28 15:11:00 2016 UTC. The chair is rdieter. Information about MeetBot at http://wiki.debian.org/MeetBot. 15:11:00 Useful Commands: #action #agreed #halp #info #idea #link #topic. 15:11:00 The meeting name has been set to 'kde-sig' 15:11:06 #topic roll call 15:11:14 .hello lupinix 15:11:16 lupinix: lupinix 'Christian Dersch' 15:11:16 hi all, who's present for a friendly kde-sig meeting today? 15:11:40 * jgrulich is present 15:11:41 hi 15:12:22 #info rdieter lupinix jgrulich tosky present 15:12:27 #chair lupinix jgrulich tosky 15:12:27 Current chairs: jgrulich lupinix rdieter tosky 15:15:17 #topic agenda 15:15:21 ok, what to discuss today? 15:15:49 * rdieter will report on recent updates: kf5-5.23, kde-apps-16.04.2 15:16:18 Qt 5 plans? I'm just curious whether we want to bring Qt 5.7 to Fedora 23 and F24 or we will keep Qt 5.6.1 for a while and maybe wait for Qt 5.7.1 15:17:18 or have you already decided/discussed that before? 15:17:58 if i remember correctly: qt 5.7 will be available @copr first,. then see how things go on? 15:17:59 jgrulich: we can discuss it, I think only informally so far (w/heliocastro mostly) 15:18:31 * jreznik is here 15:18:36 anything else to discuss today? 15:18:58 nothing here 15:19:43 ok, let's get started 15:19:50 #topic recent pkg updates 15:20:16 ok, so last week banged out plasma-5.6.5 and kf5-5.23.0 15:20:43 5.6.5 is in stable updates, and kf5 is on it's way (queue'd) 15:21:13 and 5.6.5 seems to be working properly (checked on f23) 15:21:15 doing kde-apps-16.04.2 for f24 today (kdepim-16.04.x stack is the highlight) 15:21:43 rdieter++ 15:21:43 lupinix: Karma for rdieter changed to 1 (for the f24 release cycle): https://badges.fedoraproject.org/tags/cookie/any 15:21:44 then can think about how much of that all can be built for f23 too (not pim of course) 15:22:17 *Then*, can work on Qt-5.6.1 updates 15:22:36 * jgrulich can do the Qt 5.6.1 update 15:22:39 .bug 1347385 15:22:39 rdieter: Bug 1347385 – Qt 5.6.1 tracker - https://bugzilla.redhat.com/1347385 15:22:44 tracker bug ^^, mentions the rebuilds needed 15:23:14 jgrulich: ok, you could do that almost right away I think 15:23:27 f24-kde f23-kde koji targets are ready 15:23:44 jgrulich: actually, wait until I get kde-apps done today before starting though 15:23:56 rdieter: I'll start tomorrow in the morning 15:23:57 (I'd rather not pollute the buildroot) 15:24:01 jgrulich: perfect, thanks 15:25:01 anything else? move on? 15:27:11 moving on... :) 15:27:14 #topic Qt5 plans 15:27:32 heliocastro has Qt 5.7.0 in qt5-next copr, fyi 15:27:51 https://copr.fedorainfracloud.org/coprs/g/kdesig/qt5-next/ 15:28:10 initial builds were done with clang (for fun I guess), next interation will use gcc 15:28:19 rdieter: is there any reason why to switch to Qt 5.7.0? Some visible improvements? 15:28:35 jgrulich: 5.7.x has some nice new features 15:28:48 which we'll want for rawhide at least sooner or later 15:29:18 since 5.6.x is LTS, definitely want to track that for EPEL builds moving forward 15:30:10 that also means we could seriously consider keeping f23 and possibly f24 on 5.6.x too 15:31:21 I don't think we can decide for sure prior to 5.7.x getting into rawhide, getting dependant pkgs built against it successfully, and some runtime testing 15:32:01 (the copr can help with at least some of that) 15:32:24 right, rawhide first and then we will see 15:32:38 In particular, once in rawhide, we can move 5.7 to https://copr.fedorainfracloud.org/coprs/g/kdesig/Qt5/ 15:33:56 ok, sounds like we have a plan 15:34:22 any other comments wrt Qt5 ? 15:35:54 * tosky agrees on LTS for f23 for sure, let's see f24 15:36:46 moving on... 15:36:48 #topic open discussion 15:36:53 anything else to discuss today? 15:38:22 when would be the right date to start default browser discussion again? :D 15:39:07 imho qupzilla works very well now, so imho (!) we could think about it @f25 15:39:10 I will try qupzilla after the update to f24 (hopefully really soon) 15:39:50 it's nasty to see konqueror trying to go in the way 15:40:11 i think about a version of qtwebengine in rpmfusion btw 15:40:23 with enabled codec stuff 15:40:35 lupinix: now's the time 15:40:43 have this locally here, works fine too (but default one from kevin also works with most stuff) 15:41:18 tosky: there's a qupzilla copr too, if you don't want to wait 15:41:41 I really really need to update 15:41:45 https://copr.fedorainfracloud.org/coprs/kkofler/qtwebengine/ name is a wee bit misleading 15:41:53 yes, just one important thing: don't try old 1.8 release :D 15:42:06 1.8 is the old webkit based one 15:42:26 btw i read there is an effort to continue qtwebkit 15:42:48 my main concern is supporting i686 moving forward (affects more than just qtwebengine though) 15:43:04 I see qupzilla mentioned - anyone tried it with kerberos? it should work as chrome works but maybe support has to be compiled, right path for config, not sure... it's huge package to (qtwebengine) to figure it out 15:43:14 that's what I want to try 15:43:15 lupinix: there is, but... are there any (good) browsers using qt5-qtwebkit ? 15:43:40 rdieter: i'm not thinking about browser, but other stuff using it 15:43:55 ok, I thought we were still discussing default browser 15:44:03 well... if the kpart works with an updated qtwebkit... 15:44:23 tosky: I think the ongoing work is only for qt5 15:44:33 rdieter: is the problem i686 in general or "only" non-sse2 15:44:43 rdieter: yes, sure 15:45:04 lupinix: sse2 mostly, the patches/hacks accumulating in qtwebengine packaging is becoming very non-trivial 15:45:33 do our guidelines allow to require sse2? 15:45:55 lupinix: baseline i686 arch support is no-sse2 15:46:44 what *is* allowed, is to build both non-sse2 and sse2-enabled libs (of course, that assumes that non-sse2 is still possible) 15:46:48 at least for some numerical packages (like numpy if i remember correctly) there are sse2 versions, 15:46:51 ok 15:47:14 so the other option would be dropping i686 in general... :( 15:47:39 yes, if it's a choice between that and accumulating more downstream hacks, I'd chose the former 15:48:11 i686 has already been demoted to be a non-blocking arch 15:51:55 ok, looks like we're winding down, will close meeting soon unless someone else chimes in 15:53:18 thanks everyone! 15:53:20 #endmeeting