15:10:25 <rdieter> #startmeeting kde-sig
15:10:25 <zodbot> Meeting started Tue Dec 13 15:10:25 2016 UTC.  The chair is rdieter. Information about MeetBot at http://wiki.debian.org/MeetBot.
15:10:25 <zodbot> Useful Commands: #action #agreed #halp #info #idea #link #topic.
15:10:25 <zodbot> The meeting name has been set to 'kde-sig'
15:10:29 <rdieter> #topic roll call
15:10:42 <rdieter> friendly kde sig meeting, who's present today?
15:11:15 <pino|work> o/
15:12:32 <tosky> o/
15:12:36 <dvratil> hi
15:12:41 <than> present
15:12:43 <lupinix> .hello lupinix
15:12:44 <zodbot> lupinix: lupinix 'Christian Dersch' <lupinix@mailbox.org>
15:13:25 <rdieter> #info rdieter pino|work tosky dvratil than lupinix present
15:13:31 <rdieter> #chair pino|work tosky dvratil than lupinix
15:13:31 <zodbot> Current chairs: dvratil lupinix pino|work rdieter than tosky
15:14:11 * jreznik_ is here
15:14:19 <rdieter> #info jreznik_ here
15:14:26 <rdieter> #chair jreznik
15:14:26 <zodbot> Current chairs: dvratil jreznik lupinix pino|work rdieter than tosky
15:14:55 <rdieter> #topic agenda
15:14:59 <rdieter> ok, what to discuss today?
15:15:31 <lupinix> moc bug? e.g. required rebuilds?
15:15:53 <lupinix> don't know how to handle it best way
15:16:12 <rdieter> lupinix: good question, Qt5/moc topic added
15:16:50 <tosky> so, as mentioned on the channel, my issue with the non accessible input box in the lock screen, but apparently I'm the only one
15:17:57 <pino|work> i see it some times
15:18:02 <pino|work> often, but not always
15:18:32 <jreznik> I've never seen this
15:18:49 <rdieter> ok, topic added
15:19:25 <pino|work> wait, but in my case the input box does not seem to get focus, but the actual input (including unlock) works
15:19:56 <rdieter> anything else to discuss?
15:20:03 <lupinix> nothing else here
15:20:35 <rdieter> ok, let's start
15:20:45 <rdieter> #topic Qt5/moc bug #1396755
15:20:51 <rdieter> .bug .1396755
15:20:51 <zodbot> rdieter: HTTP Error 404: Not Found - https://bugzilla.redhat.com/.1396755
15:20:57 <rdieter> .bug 1396755
15:20:57 <zodbot> rdieter: Bug 1396755 – moc-qt4 issues with QT_VERSION_CHECK : Parse error at "defined" - https://bugzilla.redhat.com/1396755
15:21:12 <rdieter> oh, hrm, I thought we had one tracking Qt5 specifically, oh well
15:21:19 <rdieter> it's a variant of the qt4 issue
15:21:23 <linuxmodder> .hello linuxmodder
15:21:24 <zodbot> linuxmodder: linuxmodder 'None' <sheldon.corey@openmailbox.org>
15:21:38 <rdieter> initial rebasing to Qt-5.7.0 for f25/rawhide, dropped an important patch
15:22:03 <rdieter> https://codereview.qt-project.org/126102/
15:22:38 <rdieter> the result being that moc'd code didn't have QT_VERSION or QT_VERSION_CHECK properly defined and parsed
15:23:47 <rdieter> fixed now in rawhide's qt5-qtbase-5.7.1-9 and f25's 5.7.0-5
15:23:56 <rdieter> the latter is a buildroot override
15:24:18 <rdieter> only noticed this due to some weird rawhide FTBFS issues
15:24:25 <Kevin_Kofler> It's also an update in Bodhi that wants Karma, hint hint. :-)
15:24:35 <rdieter> Kevin_Kofler: thanks, I was just checking for that
15:24:38 <lupinix> yes, texstudio did not build die to this issue
15:24:41 <pino|work> what is the first qr version with the above ^ review?
15:24:42 <rdieter> https://bodhi.fedoraproject.org/updates/FEDORA-2016-d9cf484d19
15:24:45 <pino|work> *qt
15:25:08 <rdieter> Kevin_Kofler: actually, could you refresh bodhi to use 5.7.0-6 instead?
15:25:23 <rdieter> or maybe we can submit that one separately
15:25:33 <rdieter> backported a tzdata fix too
15:25:39 <Kevin_Kofler> The moc bug broke QupZilla KWallet support at runtime, a F25 update fixing that is already in stable.
15:25:51 <lupinix> the texstudio FTBFS was quite obvious, but there where more dubious ones
15:25:54 <lupinix> .bug 1394562
15:25:54 <zodbot> lupinix: Bug 1394562 – qupzilla: kwallet integration stopped working - https://bugzilla.redhat.com/1394562
15:26:01 <lupinix> exactly
15:26:12 <lupinix> so there *might* be more affected stuff
15:26:20 <rdieter> pino|work: we've been carrying the patch for awhile, since 5.6.0
15:26:50 <rdieter> finally got integrated upstream for 5.8.0 (I think)
15:26:51 <Kevin_Kofler> rdieter: Well, if you karma up my update and confirm critpath non-breakage, it'll be hopefully headed for stable (it already has karma +1) and you can file -6.
15:27:05 <rdieter> Kevin_Kofler: sure, ok
15:29:31 <rdieter> so, as far as rebuilds go, much of our usual stack of stuff will get done sooner or later
15:29:34 <lupinix> btw the fixed qupzilla is already stable :)
15:29:42 <rdieter> for example, I just did kde-apps-16.08.3 over the past couple of days
15:30:07 <rdieter> will get started on latest kf5 soonish, then we can do plasma
15:30:13 <lupinix> yes, so maybe we just should investigate if we get bug reports of dubious behaviour
15:30:15 <rdieter> (may or may not wait for plasma-5.8.5)
15:30:38 <lupinix> Kevin_Kofler: btw I think 1394562 can be closed now
15:30:46 <rdieter> the most dubious so far is the plasmsshell freezing issue widely reported
15:31:02 <rdieter> (which may or may not be related, it's just "dubious")
15:32:28 <Kevin_Kofler> Ah right, I should have referenced it in the update, did not find the bug ID, oh well. I'm closing the bug.
15:32:40 <Kevin_Kofler> Ah, because it was assigned to qt5-qtbase, no wonder I didn't find it.
15:34:36 <Kevin_Kofler> Bug closed.
15:34:37 * rdieter karma'd update
15:35:29 <rdieter> anyone think we should open a tracking bug for this?
15:35:45 <rdieter> in case other pkgs have issues, or just deal with it on a case-by-case basis?
15:35:53 <rdieter> (ie, just rebuild/submit-updates as needed)
15:36:22 <lupinix> maybe a tracking bug is nice to get an overview of the impact of such issues
15:37:20 * rdieter sees no harm, just a little more work. :)  any volunteer to make such a tracking bug (against qt5-qtbase/f25) ?
15:37:32 <Kevin_Kofler> A tracking bug with nothing to put on the tracker? Why?
15:38:01 <rdieter> Kevin_Kofler: it has at least one bug to add (qupzilla)
15:38:08 <lupinix> and texstudio
15:38:09 <rdieter> we may find others
15:38:12 <lupinix> i'll do it
15:38:32 <rdieter> no *open* bugs, true
15:38:53 <rdieter> once we have the tracker, probably worth sending notice to -devel list
15:39:00 <Kevin_Kofler> A tracker only makes sense if you have something to put on it.
15:39:08 <rdieter> so other maintainers of qt5-related packages can know about it
15:39:28 <rdieter> Kevin_Kofler: we have 2 (closed) bugs to put on it so far
15:39:36 <rdieter> once we advertise it's existence, we may get more
15:40:57 <rdieter> anything else on the topic ?
15:41:06 <lupinix> nothing else here
15:41:31 <rdieter> #topic kscreenlocker input/focus issues (f24)
15:42:08 <rdieter> tosky, pino|work: seems each of you see simliar symptoms sometimes, but not exactly the same?
15:42:25 <pino|work> ¯\_(ツ)_/¯
15:42:26 <tosky> uhm
15:42:47 <tosky> ok, so now it's strange
15:42:55 <rdieter> I suppose if you think we should pursue this more, should probably start by documenting it in a bug report
15:42:58 <tosky> I can confirm that the input text box does not show the input, but it works
15:43:23 <pino|work> just locked, and it accepted input :D
15:43:24 <tosky> previously, when I reported the issue in the bodhi update, it was not really working even if I was blindly typing
15:43:28 <rdieter> ok, so same (?)
15:43:29 <tosky> so it's the same issue
15:44:09 <rdieter> so it works, just oddly
15:44:22 <tosky> yes
15:44:46 <tosky> and I suspect that updating to F25 (scheduled for the upcoming holidays) and Qt 5.7 could improve it
15:44:47 <rdieter> that's a little less bad then
15:44:59 <tosky> but then I would not be able to notice if it gets fixed, but well :)
15:45:57 <lupinix> .bug 1404333
15:45:57 <zodbot> lupinix: Bug 1404333 – moc-qt5 issues with QT_VERSION macros - https://bugzilla.redhat.com/1404333
15:46:04 <lupinix> fyi
15:48:20 <rdieter> lupinix: thanks
15:49:15 <rdieter> pino|work, tosky: I'll leave it to each of you, if you want to file a bug or not (probably preferably upstream, but either is fine with me)
15:49:38 <tosky> probably upstream, yeah; let's see
15:49:45 <pino|work> if i were able to reproduce it every time, maybe...
15:51:37 <rdieter> ok, thanks
15:51:40 <rdieter> #topic open discussion
15:51:44 <rdieter> anything else to discuss today ?
15:51:49 <lupinix> nothing else here
15:52:38 <Kevin_Kofler> FYI, qt5-qtwebengine-freeworld is now in RPM Fusion Free updates-testing.
15:52:43 <Kevin_Kofler> For F23, F24, F25, Rawhide.
15:52:47 <rdieter> \o/
15:52:52 <lupinix> right, very nice!
15:53:01 <lupinix> already tested it (f25), works nice here
15:53:09 <rdieter> faster than I expected, given how long it takes to build
15:53:11 <lupinix> Kevin_Kofler: thank you very much!
15:53:31 <rdieter> that's also a good one to advertise
15:53:50 <Kevin_Kofler> It should play all the media the regular qt5-qtwebengine can play (but WAV is currently not working: https://bugreports.qt.io/browse/QTBUG-57547 ) plus the patent-encumbered codecs (at least H.264, MP3, AAC).
15:54:20 <lupinix> h.264 works fine here, did not test other ones right now
15:54:49 <Kevin_Kofler> You surely tested at least MP3 or AAC too, I doubt any H.264 video uses Vorbis or Opus audio. ;-)
15:55:21 * lupinix does not know about such details :D
15:55:51 <lupinix> for myself the free fedora version is already enough, but for *many* users the -freeworld is important imho
15:55:52 <Kevin_Kofler> It should also ENCODE at least H.264 for WebRTC.
15:56:00 <lupinix> mp3 works too
15:56:01 <Kevin_Kofler> But I didn't test WebRTC.
15:56:10 <lupinix> dito
15:56:30 <Kevin_Kofler> MP3 decoding should be built even in Fedora at some point, but for now there is no upstream support for that.
15:56:45 <Kevin_Kofler> "proprietary" codec support is an all-or-nothing flag.
15:56:58 <Kevin_Kofler> And the patent expiry was not taken into account yet.
15:57:17 <rdieter> <nod>, baby steps
15:59:38 <rdieter> anything else before closing meeting?
15:59:45 <rdieter> oh, status on what I'm working on:
16:00:12 <rdieter> adding exclusivearch to all pkgs (and recursive deps) that depend on qtwebengine
16:00:22 <rdieter> (kde-apps pim stuff mostly for now)
16:00:37 <rdieter> then, submit f24 kde-apps-16.08.3 updates
16:01:12 <rdieter> then start working on importing kde-apps-16.12.0/kf5-5.29.0 into rawhide
16:01:29 <rdieter> any help on kf5-5.29.0 would be appreciated, fwiw
16:01:50 * lupinix has to update INDI stuff for 16.12.0
16:01:51 <rdieter> due to other business and freezes, we ended up skipping kf5-5.28
16:05:52 <tosky> few tarballs from kde-apps 16.12 are still rebased due to (unfortunate) last minute (or unnoticed) issues
16:06:00 <tosky> so I'd really suggest to wait for the release
16:06:15 <tosky> there have been at least 5 or 6 respin
16:06:27 <rdieter> tosky: no problem with that, I have several tasks to do before looking at it :)
16:06:27 <tosky> (of single tarballs, not for all tarballs of course)
16:06:59 <rdieter> maybe will do kf5 first then too
16:08:15 <rdieter> alright, looks like we're out of time and things to talk about... thanks everyone
16:08:17 <rdieter> #endmeeting