This is an automatically created tracking bug! It was created to ensure that one or more security vulnerabilities are fixed in affected versions of fedora-all. 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. NOTE: this issue affects multiple supported versions of Fedora. While only one tracking bug has been filed, please correct all affected versions at the same time. If you need to fix the versions independent of each other, you may clone this bug as appropriate.
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 # testing, stable request=testing # Bug numbers: 1234,9876 bugs=1439639 # 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
Can you provide more technical information about that CVE? I cannot find it anywhere. Also it'd be good to have the script fixed to not open bugs with links to customer portal for fedora because they're simply broken.
Ok. Found it in the bug this depends on. A little bit unclear which bug is tracker and why tracker blocks normal bug not vice versa ...
(In reply to Pavel Zhukov from comment #3) > Ok. Found it in the bug this depends on. A little bit unclear which bug is > tracker and why tracker blocks normal bug not vice versa ... Well, this one Blocks: CVE-2016-10221, as the parent bug can be resolved only after the tracker is which sounds fine in my opinion. Parent bug always contains all relevant information. If there is a problem in the process somewhere, let me know, but trackers are always created this way. > Also it'd be good to have the script fixed to not open bugs with links to customer portal for fedora because they're simply broken. Default bugzilla behavior, CVE alias redirects to customer portal but in the case of community products the page is not created.
mupdf-1.10a-5.fc25 has been submitted as an update to Fedora 25. https://bodhi.fedoraproject.org/updates/FEDORA-2017-2d11503623
mupdf-1.10a-5.fc25 has been pushed to the Fedora 25 testing repository. If problems still persist, please make note of it in this bug report. See https://fedoraproject.org/wiki/QA:Updates_Testing for instructions on how to install test updates. You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2017-2d11503623
mupdf-1.10a-5.fc26 has been submitted as an update to Fedora 26. https://bodhi.fedoraproject.org/updates/FEDORA-2017-8150618774
mupdf-1.10a-5.fc25 has been pushed to the Fedora 25 stable repository. If problems still persist, please make note of it in this bug report.
mupdf-1.10a-5.fc26 has been pushed to the Fedora 26 testing repository. If problems still persist, please make note of it in this bug report. See https://fedoraproject.org/wiki/QA:Updates_Testing for instructions on how to install test updates. You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2017-8150618774
Closing F25 bug.
mupdf-1.10a-5.fc26 has been pushed to the Fedora 26 stable repository. If problems still persist, please make note of it in this bug report.