Bugzilla Bug 179943

This is a new ebuild submission for version 6.3.4 version of ImageMagick. The
new version contains support for openexr and HDR Imaging.

new use flags:
q8 & q32: enables 8 or 32 bit quantum-depth
openexr: enables use of the openexr for exr file processing
hdri: enables hdr imaging.

Created an attachment (id=120404) [details]
imagemagick-6.3.4.ebuild

ebuild for ImageMagick version 6.3.4. This new version includes support for exr
images via openexr and HDRI.

new use flags: q8, q32, hdri, openexr

Created an attachment (id=120406) [details]
imagemagick-6.3.4-docs.patch

I forgot to mention, the q8 and q32 flags are taken from bug 152894

actually, when i tried to emerge imagemagick-6.3.4, it was looking for a
"missing" imagemagick-6.3.4-docs.patch. anyways, commenting the "epatch
"${FILESDIR}"/${PN}-${PV}-docs.patch"line in the 6.3.4 ebuild fixed the
problem.(i have "doc" USE flag, if it matters)

the imagemagick-6.3.4-docs.patch file is attached to this bug post, download it
and use it. However I use -doc flag so I'm not sure if it *actually* worked.

This version fixes security bug. As in imagemagick changelog:
2007-06-11 6.3.4-9 Cristy <quetzlzacatenango@image...>
# Converting a jpg to pdf is creating an empty pdf object (reference
http://www.imagemagick.org/discourse-server/viewtopic.php?f=3&t=8954).
# Respect the '-set type:hinting off option' (bug report from Richard Jones).
# WritePSDImage vulnerable to exploitable heap corruption (reference
http://www.imagemagick.org/discourse-server/viewtopic.php?f=3&t=8967).
#
2007-06-09 6.3.4-8 Cristy <quetzlzacatenango@image...>
# SetMagickRegistry() post-increment the value 'id' (reference
http://www.imagemagick.org/discourse-server/viewtopic.php?f=3&t=8944).

Removed s390, arm, x86-fbsd, sh because of additional deps. Please add to
testing.

I suggest replacing:
        local hdri
        if use hdri ; then
                hdri=" --enable-hdri"
        fi
...
        ${hdri} \

With:
        $(use_enable hdri) \

Thanks Arfrever, I've never written an ebuild before so I just looked up other
refs and modified the old one. Would I have to make this change and update the
ebuild or will someone else modify/attach a new ebuild?

(In reply to comment #8)
> Would I have to make this change and update the ebuild or will someone else
> modify/attach a new ebuild?

No. My suggestion was rather addressed to Karol Wojtaszek / Sekretarz who
committed your ebuild to the tree.
http://sources.gentoo.org/viewcvs.py/gentoo-x86/media-gfx/imagemagick/imagemagick-6.3.4-r1.ebuild?rev=1.1&view=markup

changed code to use use_enable

Reassigning to security.

Arches please test and mark stable. Target keywords are:

imagemagick-6.3.4-r1.ebuild:KEYWORDS="alpha amd64 arm hppa ia64 mips ppc ppc64
s390 sh sparc x86 ~x86-fbsd"

alpha/ia64/x86 stable

Stable for HPPA.

mips stable.

amd64 done

sparc stable.

ppc64 stable

marked ppc