This is an automatically created tracking bug! It was created to ensure that one or more security vulnerabilities are fixed in affected Fedora versions. For comments that are specific to the vulnerability please use bugs filed against "Security Response" product referenced in the "Blocks" field. For more information see: http://fedoraproject.org/wiki/Security/TrackingBugs When creating a Bodhi update request, please include the bug IDs of the respective parent bugs filed against the "Security Response" product. Please mention CVE ids in the RPM changelog when available. Bodhi update submission link: https://admin.fedoraproject.org/updates/new/?type_=security&bugs=652860 Please note: this issue affects multiple supported versions of Fedora. Only one tracking bug has been filed; please only close it when all affected versions are fixed. [bug automatically created by: add-tracking-bugs]
In rawhide new version 6.6.5.10 which shouldn't be affected (according to https://bugzilla.redhat.com/show_bug.cgi?id=652860).
This is for _all_ versions of Fedora, not just rawhide. Has the fix been pushed to supported versions of Fedora? If not, then this can't really be closed as this does affect older versions. Unless you have no intention of fixing this in the stable releases? Re-opening because not all versions of Fedora are fixed.
As stated in linked bug it have low impact, but update in stable branches lead to rebuild all dependencies (via create by FESCO separate tag) and strongly undesired. If you do not insist, I do not want update it in stable branches.
I don't understand. Sure, updating to the latest stable release would cause a rebuild of all dependencies, but the patch to fix this is very small: http://trac.imagemagick.org/changeset?new=3022%40ImageMagick%2Ftrunk%2Fmagick%2Fconfigure.c&old=2002%40ImageMagick%2Ftrunk%2Fmagick%2Fconfigure.c Surely we can patch and rebuild ImageMagick and it would _not_ require a rebuild of all dependencies?
It in any case lead to rebuild at least _some_ dependencies who require exact version of IM (f.e. Rmagick) because release bump already will. In any case, for what do it?
Seriously? If you bump the release, you'll have to rebuild some dependant packages? They don't just have requires on a particular version, but on a particular release as well? That doesn't make much sense. However, if that's the case, then I guess it isn't worth the effort. I wasn't aware that there were such strange tight dependencies in place here. If that truly is the case, you can close this as it isn't worth forcing (what should be unnecessary, really) rebuilding of dependant packages.
Hm, I look closer and ruby-RMagick require "ImageMagick = 6.6.4.1". So, we can try push updates with this backported patch for Fedora 13 and 14. Updates follow.
ImageMagick-6.5.8.10-7.fc13 has been submitted as an update for Fedora 13. https://admin.fedoraproject.org/updates/ImageMagick-6.5.8.10-7.fc13
ImageMagick-6.6.4.1-15.fc14 has been submitted as an update for Fedora 14. https://admin.fedoraproject.org/updates/ImageMagick-6.6.4.1-15.fc14
ImageMagick-6.6.4.1-15.fc14 has been pushed to the Fedora 14 testing repository. If problems still persist, please make note of it in this bug report. If you want to test the update, you can install it with su -c 'yum --enablerepo=updates-testing update ImageMagick'. You can provide feedback for this update here: https://admin.fedoraproject.org/updates/ImageMagick-6.6.4.1-15.fc14
ImageMagick-6.6.4.1-15.fc14 has been pushed to the Fedora 14 stable repository. If problems still persist, please make note of it in this bug report.
ImageMagick-6.5.8.10-7.fc13 has been pushed to the Fedora 13 stable repository. If problems still persist, please make note of it in this bug report.