This is an automatically created tracking bug! It was created to ensure that one or more security vulnerabilities are fixed in affected versions of epel-7. For comments that are specific to the vulnerability please use bugs filed against the "Security Response" product referenced in the "Blocks" field. For more information see: http://fedoraproject.org/wiki/Security/TrackingBugs When submitting as an update, use the fedpkg template provided in the next comment(s). This will include the bug IDs of this tracking bug as well as the relevant top-level CVE bugs. Please also mention the CVE IDs being fixed in the RPM changelog and the fedpkg commit message.
Use the following template to for the 'fedpkg update' request to submit an update for this issue as it contains the top-level parent bug(s) as well as this tracking bug. This will ensure that all associated bugs get updated when new packages are pushed to stable. ===== # bugfix, security, enhancement, newpackage (required) type=security # low, medium, high, urgent (required) severity=high # testing, stable request=testing # Bug numbers: 1234,9876 bugs=1740138,1740141 # Description of your update notes=Security fix for [PUT CVEs HERE] # Enable request automation based on the stable/unstable karma thresholds autokarma=True stable_karma=3 unstable_karma=-3 # Automatically close bugs when this marked as stable close_bugs=True # Suggest that users restart after update suggest_reboot=False ====== Additionally, you may opt to use the bodhi web interface to submit updates: https://bodhi.fedoraproject.org/updates/new
Does anybody feel responsible for the EPEL 7 branch of kdelibs3? I have not requested it (nor any other EPEL branch for any Fedora package, for the record) and really do not want to be coaxed into maintaining it. The EPEL 7 branch is currently stuck at kdelibs3-3.5.10-78 from 2016-12-03. The Fedora branches are at 3.5.10-101 (and the versioning is in sync, so the EPEL 7 branch is really missing all the changes from 3.5.10-79 onwards). The EPEL 7 branch is missing at least the security fixes for CVE-2016-6232, CVE-2017-6410, and now also CVE-2019-14744, that were fixed in Fedora. Be warned, however, that some of the changes in the Fedora branch are probably NOT wanted in EPEL, e.g., we now use the KF5 DrKonqi in Fedora, whereas RHEL 7 ships with Plasma 4. So you may have to either do selective backports or add specfile conditionals. Can somebody who wanted the EPEL branch please take care of it? Or if nobody wants it, is there a way the package can be withdrawn before the RHEL 7 EOL which is still years away?
The latest package that was actually pushed is even older, kdelibs3-3.5.10-65 from 2014-11-25! That build was included in the initial taskjuggler update group and then never updated. kdelibs3-3.5.10-78 was only committed in dist-git and built (by Rex Dieter), but never pushed in Bodhi. kdelibs3-3.5.10-65 also misses the fix for CVE-2015-7543 (in addition to the 3 I already listed).
I'll take a look to backport CVEs. Having kdelibs3 in EPEL is really for Taskjuggler support as there were requests for it. But it might not be the case anymore. Let me investigate this option too (and then we could remove it from EPEL if possible).
Hi, was this ever fixed? If no one's responsible for EPEL, please WONTFIX the bug and tombstone the branch.
This package has changed maintainer in Fedora. Reassigning to the new maintainer of this component.
EPEL 7 entered end-of-life (EOL) status on 2024-06-30. EPEL 7 is no longer maintained, which means that it will not receive any further security or bug fix updates. As a result we are closing this bug.