15:12:34 <rdieter> #startmeeting kde-sig
15:12:34 <zodbot> Meeting started Tue Jan 31 15:12:34 2017 UTC.  The chair is rdieter. Information about MeetBot at http://wiki.debian.org/MeetBot.
15:12:34 <zodbot> Useful Commands: #action #agreed #halp #info #idea #link #topic.
15:12:34 <zodbot> The meeting name has been set to 'kde-sig'
15:12:38 <rdieter> #topic roll call
15:12:46 <rdieter> hi all, friendly kde-sig meeting, who's present today?
15:13:32 <pino|work> o/
15:13:34 <tosky> o/
15:14:58 <rdieter> may be a fast meeting
15:15:05 <rdieter> #info rdieter pino|work tosky present
15:16:04 <rdieter> #topic agenda
15:16:15 <rdieter> alright, anything specific to discuss?
15:16:30 <rdieter> I can give a general update on my doings for the past week or so (kde-apps-16.12.1 stuff mostly)
15:16:45 * rdieter fetches quick coffee
15:18:36 <rdieter> #topic general updates
15:18:50 <tosky> uh, 16.12
15:19:12 <rdieter> ok, for me, been working the past couple of weeks to get kde-apps-16.12.1 into rawhide...largest task was packaging/reviewing new pim-related modules,
15:19:23 <than> present
15:19:31 <rdieter> #info than present
15:19:35 <rdieter> #chair than tosky pino|work
15:19:35 <zodbot> Current chairs: pino|work rdieter than tosky
15:19:44 <rdieter> and I think they're all done now
15:20:01 <rdieter> oh, and kde-baseapps was split too (and ported to kf5)
15:20:51 <rdieter> than: hi, do you have anything interesting to share you've worked on the past week or so?
15:20:55 <tosky> and kdewebdev
15:21:02 <tosky> split, but not ported
15:21:12 <rdieter> oh gosh, kdewebdev too?  OK, on todo list
15:22:13 <than> rdieter:  bz#1409597, CVE-2016-10040
15:22:53 <than> it looks like upstream doesn't intent to fix this issue
15:23:03 <tosky> -> https://community.kde.org/Applications/16.12_Release_Notes
15:23:08 <rdieter> .bug 1409597
15:23:08 <zodbot> rdieter: Bug 1409597 – CVE-2016-10040 qt: stack buffer overflow in QXmlSimpleReader - https://bugzilla.redhat.com/1409597
15:23:33 <rdieter> silly question, is upstream even aware of it?
15:23:38 <than> it seems to effected in all qt version
15:23:50 <than> rdieter: yes,
15:24:18 <rdieter> wait, I follwed some links, which reference
15:24:20 <rdieter> http://lists.qt-project.org/pipermail/announce/2013-December/000036.html
15:24:26 <rdieter> which is old, claims to be fixed
15:24:31 <lupinix> hi
15:24:37 <than> it's the the old one
15:24:48 <than> CVE-2016-10040 is newer
15:24:55 <rdieter> #info lupinix present
15:25:49 <rdieter> fyi, lupinix is the hero that packaged new kde-baseapps modules and reviewed all the new pim ones.
15:25:51 <rdieter> lupinix++
15:26:00 <lupinix> :D
15:26:21 <rdieter> than: is there an upstream bug tracking it?
15:26:42 <rdieter> (I can't find one quickly)
15:27:14 <rdieter> than: and, has upstream said they're not going to fix it, or just been quiet and said nothing about it?
15:27:22 <than> rdieter: it's only discussed on the mailing list, i haven't seen the report
15:28:11 <rdieter> than: if you can find a link to reference the discussion, can you add that to 1409597  ?
15:28:34 <than> rdieter:  the issue is only happen in depricated class and they don't have resource to look at it
15:28:40 * heliocastro here
15:28:44 <heliocastro> ( finally )
15:28:46 <rdieter> #info heliocastro present
15:28:54 <rdieter> #chair lupinix heliocastro
15:28:54 <zodbot> Current chairs: heliocastro lupinix pino|work rdieter than tosky
15:29:03 * than is looking...
15:29:04 <rdieter> than: ok :(
15:29:45 <rdieter> in that case, we may have to admit defeat and close the bug as WONTFIX ?
15:29:51 <than> rdieter:  i can try to fix it, but need an working testcase
15:30:18 <rdieter> than: you think it worth your time and effort (ie, not better spent on other things)?
15:33:07 <than> rdieter:  i full agree with you, it's only affected in depricated class which should not be used.so close as as wontfix is fine with me
15:33:34 <rdieter> lupinix, heliocastro: anything notable you've been working on the past week or 2 /
15:33:35 <rdieter> ?
15:33:44 <rdieter> that is worth sharing?
15:33:50 <lupinix> nothing here
15:34:04 <rdieter> heliocastro: maybe Qt 5.8 ?
15:34:18 <heliocastro> Yep
15:34:24 <heliocastro> So, good news on that
15:34:43 <heliocastro> I'm wroking on last step ( webengine ) and tomorrow we will have 5.8 on copr
15:34:51 <heliocastro> and ready to go to rawhide
15:35:04 <lupinix> nice
15:35:06 <lupinix> heliocastro++
15:35:06 <zodbot> lupinix: Karma for heliocastro changed to 1 (for the f25 release cycle):  https://badges.fedoraproject.org/tags/cookie/any
15:35:07 <heliocastro> There's a small change on documentation generation
15:35:27 <heliocastro> Since i noted ( and later talked with qt guys )
15:35:38 <heliocastro> The documentation and examples need rely on base-doc package
15:35:51 <rdieter> heliocastro++
15:35:51 <zodbot> rdieter: Karma for heliocastro changed to 2 (for the f25 release cycle):  https://badges.fedoraproject.org/tags/cookie/any
15:35:53 <heliocastro> and all the doc of BuildRequires packages as well
15:36:15 <heliocastro> Because it creates inter links
15:36:15 <rdieter> makes sense
15:36:30 <heliocastro> The onnly thing that is unresolvable on a single build is qtcreator
15:36:40 <heliocastro> Since some docs try to link agains qtcreator doc
15:36:54 <heliocastro> I i personally thinks not worth the effort
15:37:07 <rdieter> "some docs" is what exactly?
15:37:13 <heliocastro> At least for now we have all the docs and examples been properly generates
15:37:31 <rdieter> (either way, I agree with the sentiment)
15:37:35 <heliocastro> "some docs, for examples qt3d that have examples poointing to qtcreator doc
15:38:11 <rdieter> heliocastro: how is that fixable?  making qtcreator (docs?) be avialable in buildroot?
15:38:21 <heliocastro> rdieter: Guys from Qt don't know
15:38:28 <rdieter> heh
15:38:42 <rdieter> ok, if they don't know, then we shouldn't worry about it too much either
15:38:43 <rdieter> I guess
15:38:55 <heliocastro> But yes, if we have qtcreator doc built as a noarch and put as buildrequires work
15:39:06 <heliocastro> Yes, we should not be worried with that
15:39:26 <heliocastro> I think we do need a meta doc package anyway
15:39:38 <heliocastro> Pointing to all doc packages we have on the current build
15:39:53 <heliocastro> And qtcreator should Requires this one
15:40:03 <Kevin_Kofler> kdewebdev is "special" in that it is still the KDE 3 version in Fedora.
15:40:05 <heliocastro> Otherwise we not see any examples
15:40:10 <Kevin_Kofler> There is not all that much left from kdewebdev these days.
15:40:18 <Kevin_Kofler> Quanta was never ported to kdelibs 4. :-(
15:40:24 <rdieter> I'm not sure if adding a dependency to *all* qt5 docs to qtcreator is wise
15:41:03 <rdieter> Kevin_Kofler: <nod>, having the pkgs be split now may make the task of updating individual components easier
15:41:12 <rdieter> (I'll take a look after meeting)
15:43:45 <rdieter> heliocastro: when copr is ready, let us know the link
15:44:30 <rdieter> heliocastro: I wouldn't be against adding a -doc (or -docs?) metapackage to existing qt5 module
15:45:44 <heliocastro> rdieter: is in https://copr.fedorainfracloud.org/coprs/g/kdesig/qt-5.8/
15:46:05 <heliocastro> The other good thing is that is compiled for even epel-7 and f23
15:48:59 <rdieter> surprised f23 buildroots are still available in copr.  imo, little point doing builds for eol releases
15:49:13 <heliocastro> Was there, so i built :-)
15:50:14 <rdieter> anything else for today's meeting?
15:50:46 <lupinix> nothing here
15:50:47 <rdieter> oh, wrt kde-apps-16.12.  I think I'll try making a copr, so that some of the new stuff is testable on f25 at least
15:50:52 <rdieter> like ... kf5 konqueror
15:51:34 <lupinix> what is the general plan? updating all except the ones which made the step kdelibs4 → kf5?
15:52:39 <rdieter> lupinix: updating all... you mean for f24/f25?  yeah
15:52:47 <lupinix> yes 24/25
15:53:00 <rdieter> and even some minor leaf packages kde4->kf5 is doable too
15:53:11 <rdieter> (like games)
15:53:30 <lupinix> yes, but e.g. konqueror based on kf5 is not yet ready for that step
15:53:44 <rdieter> right
15:56:18 <rdieter> ok, looks like that's all for today then, thanks everyone!
15:56:21 <rdieter> #endmeeting