15:01:30 #startmeeting kde-sig 15:01:30 Meeting started Tue Nov 28 15:01:30 2017 UTC. The chair is rdieter. Information about MeetBot at http://wiki.debian.org/MeetBot. 15:01:30 Useful Commands: #action #agreed #halp #info #idea #link #topic. 15:01:30 The meeting name has been set to 'kde-sig' 15:01:32 #meetingname kde-sig 15:01:32 The meeting name has been set to 'kde-sig' 15:01:36 #topic roll call 15:01:44 hi all, who's present for friendly kde-sig meeting? 15:01:52 * than is present 15:01:57 o/ 15:02:01 .hello2 15:02:02 lupinix: lupinix 'Christian Dersch' 15:03:01 #info rdieter than pino|work lupinix present 15:03:04 #chair than pino|work lupinix 15:03:04 Current chairs: lupinix pino|work rdieter than 15:03:34 .hello jbwillia 15:03:35 Southern_Gentlem: jbwillia 'Ben Williams' 15:03:47 #info Southern_Gentlem present 15:03:47 o/ 15:03:48 * jreznik_ is here 15:03:52 #info jreznik_ present 15:04:36 hello 15:04:57 #info mbriza present 15:05:06 #info tosky present 15:05:15 #topic agenda 15:05:19 ok, what to discuss today? 15:05:31 Kevin_Kofler had mentioned qt-5.9.3 in #fedora-kde earlier 15:05:53 I can include that as well as other recent updates I've been working on 15:07:49 no other points from me - thanks for the steady stream of updates 15:08:21 nothing else here 15:08:38 ok 15:08:43 #topic qt-5.9.3 status 15:09:16 so, thanks to jgrulich doing much of the heavy lifting late last week, got qt-5.9.3 imported into rawhide 15:09:41 and I helped with all the associated rebuilds (the list of private-api consumers is growing :( ) 15:10:26 did most of the work in a side tag to avoid any intermediate broken deps in rawhide (f28-kde) 15:10:28 thanks 15:10:38 rdieter++ 15:10:44 jgrulich++ 15:10:45 lupinix: Karma for jgrulich changed to 1 (for the f27 release cycle): https://badges.fedoraproject.org/tags/cookie/any 15:10:49 jgrulich++ 15:10:54 had f26 kf5-5.40.0 builds ready for a little while, finally submitted to bodhi yesterday 15:11:35 oh, and got pim stuff from kde-apps-17.11.80 imported into rawhide too (needed since libical-3.0 had been introduced) 15:11:58 one more thing to mention for transparency... 15:12:22 f28+ kf5-related macros updated %_kf5_metainfodir from /usr/share/appdata to /usr/share/metainfo 15:12:40 go for it 15:12:47 so... now's the time to check any package hard-coding .../appdata instead of using %_kf5_metainfodir 15:13:07 since it will fail now :-P 15:13:45 sorry, I guess I through in all updates there, not just qt 5.9.3 15:13:52 threw even 15:14:01 there was a note about qt 5.9.3 and kio on kde-distro-packagers 15:14:03 * tosky checks 15:14:14 I may have missed that 15:14:19 https://mail.kde.org/pipermail/kde-distro-packagers/2017-November/000297.html 15:14:25 kio needs a fix 15:14:34 and I think I've seen another relevant change $somewhere 15:15:24 thanks, that probably means we don't want to rush qt-5.9.3 to -updates 15:15:45 Kevin_Kofler: ^^ , fyi 15:15:47 and there is probably https://phabricator.kde.org/D9029 too 15:16:29 I've seen also Arch packagers mentioning an issue with digikam and Qt 5.9.3 (as if digikam didn't have enough) 15:16:47 https://bugs.kde.org/show_bug.cgi?id=387373 15:17:20 also think it unfortunate Qt introduced such a change into a minor release, but I'm sure they have their "reasons(tm)" 15:17:47 tosky: thanks 15:17:57 jgrulich++ 15:17:57 rdieter: Karma for jgrulich changed to 2 (for the f27 release cycle): https://badges.fedoraproject.org/tags/cookie/any 15:18:01 (overdue cookies) 15:18:04 tosky++ 15:18:05 rdieter: Karma for tosky changed to 1 (for the f27 release cycle): https://badges.fedoraproject.org/tags/cookie/any 15:18:48 hi 15:19:08 #info jgrulich present 15:19:09 hi 15:19:24 rdieter: OK 15:19:42 I'll review this qt-5.9.3 fixes/patches, etc... after meeting, and import into packaging as appropriate 15:19:45 WTF at Qt deliberately breaking POSIX compliance… 15:19:51 foo//bar == foo/bar in POSIX 15:20:15 iirc not 15:21:20 Maybe not in the letter of the standard, but all the *nix OSes implement things that way. 15:21:46 Declaring the construct invalid is just the worst possible thing to do, it will never do what the user expects. 15:22:50 I think we can debate the merits of the Qt change outside of this meeting, point is... there's a problem, and we need to take things slowly and deliberately 15:25:00 and including the workarounds should be a safe thing to do either way 15:25:48 this feels similar to the changes introduced in QUrl awhile back 15:25:57 that broke a lot of stuff 15:26:28 and that for a bugfix release… 15:26:34 they should read https://semver.org/ 15:27:16 I'm sure it's not that simple 15:28:02 i am 15:28:13 but thats an imho 15:28:47 does anyone know offhand why the change was introduced? 15:29:05 otherwise, we can discuss it more at length later 15:29:39 without that information, we're only speculating 15:31:30 #topic open discussion 15:31:42 anything else to mention or discuss today? 15:33:00 In other news, 5.9.3 made it out to the Rawhide master mirror, so I can build qt5-qtwebengine-freeworld-5.9.3 there now. 15:36:09 qt5-doc is outdated in Rawhide, by the way. 15:36:38 Any plans to get rid of that monolithic thing that does not match the actual qt5-* packages? 15:37:12 I think it's mostly harmless, nothing depends on it matching exactly, and I doubt the docs changed significantly in a minor release 15:37:45 so we have the luxery of updating at our convenience, or even not at all if needed 15:37:49 I want at least the QtWebEngine docs removed from qt5-doc, you disabled them in QtWebEngine without my permission (I explicitly told you not to do it), and I want QtWebEngine to come with matching docs. 15:38:39 Kevin_Kofler: please file a bug detailing exactly what you want omitted, and I'll take care of it 15:38:53 since qtwebengine releases independantly, it makes less/no sense to include in qt5-doc 15:39:31 probably same for qtwebkit, but there may have more bootstrapping consequences 15:39:49 I think I'll reenable docs for F27 at least, since I'm going to push 5.9.3 before you push the rest of Qt, this will end up having both versions on the mirrors, but 5.9.3>5.9.2. 15:40:10 (reenable in qt5-qtwebengine.spec, I mean) 15:40:37 And I am going to work on 5.10.0 soon, it should be released within the next few days. 15:40:51 , yay 15:40:57 But I want 5.9.3 out first, so I will likely not rush to 5.10.0 on the day of the release. 15:41:37 will have to think on that a bit too, since 5.9.x is LTS probably want to continue tracking that *somewhere* 15:41:59 f26 branch maybe 15:42:29 My experience with the previous LTS branch (5.9) was horrible. 15:42:35 (5.6, I mean) 15:42:56 that was their first try, hopefully better this time 15:42:56 It did not get security fixes for months and I had to ship a snapshot to get security fixes out to F24 before its EOL. 15:43:26 F25 is sticking on 5.9 LTS. Anything newer, just no. 15:43:27 again, I'm only speaking of core qt5 modules, we already treat qtwebengine separately 15:43:37 That's for QtWebEngine. 15:43:59 If you stick to Qt 5.9 LTS on F26, that should be workable for QtWebEngine, it should keep building against 5.9 LTS for a while. 15:44:40 5.10 dropped support for building against 5.7, I think it even still builds against 5.8. 15:45:05 Things are likely to keep building against LTS Qt. 15:45:13 well, also depends on how newer versions work… e.g. qt 5.8 was a mess (which is why we had non lts 5.7 for very long time…) 15:45:21 *how well 15:46:22 Well, my Konversation on F25 still eats characters in links when it wordwraps them, IIRC that was fixed in Qt 5.8, but that was never pushed to F25. :-/ 15:46:51 There are some annoying bugs in Qt 5.7 that did not get fixed because Qt 5.8 was not pushed, this is one of them. 15:47:29 well because 5.8 introduced new annoying bugs… but we discussed that several times ;) 15:48:51 qt5-qtwebengine-freeworld-5.9.3 in Rawhide will have to wait a bit, the RPM Fusion builders have outdated metadata cached and are trying and failing to fetch outdated packages. (I need to file a bug for that, they should really not be caching metadata at all.) 15:51:59 ok, looks like we're winding down, thanks everyone 15:52:04 #endmeeting