<html><head></head><body>I suppose <a href="https://github.com/ImageMagick/ImageMagick/commit/f6242e725c819a69bee2a444f8e4a3c7718b2b3f">https://github.com/ImageMagick/ImageMagick/commit/f6242e725c819a69bee2a444f8e4a3c7718b2b3f</a><br>
<br>
Fix it. If so plezse merge this bug with the other one régression about pdf<br><br><div class="gmail_quote">Le 1 septembre 2016 00:38:34 GMT+02:00, Frank Heckenbach <f.heckenbach@fh-soft.de> a écrit :<blockquote class="gmail_quote" style="margin: 0pt 0pt 0pt 0.8ex; border-left: 1px solid rgb(204, 204, 204); padding-left: 1ex;">
<pre class="k9mail"><blockquote class="gmail_quote" style="margin: 0pt 0pt 1ex 0.8ex; border-left: 1px solid #729fcf; padding-left: 1ex;"> On Wed, Aug 31, 2016 at 8:42 AM, Bastien ROUCARIES<br /> <roucaries.bastien@gmail.com> wrote:<br /><br /><blockquote class="gmail_quote" style="margin: 0pt 0pt 1ex 0.8ex; border-left: 1px solid #ad7fa8; padding-left: 1ex;"> Patches are needed for a security point of view but it is likely a<br /> problem of backport intereaction.<br /><br /> Could you help by pin point the problem.<br /><br /> as root install a few package needed for imagemagick compilation:<br /> apt-get install git<br /> apt-get build-dep imagemagick<br /></blockquote></blockquote><br />Just for my reference:<br />libbz2-dev libdjvulibre-dev libexif-dev libharfbuzz-dev libharfbuzz-gobject0 libilmbase-dev libjasper-dev libjbig-dev liblcms2-dev liblqr-1-0-dev liblzma-dev libopenexr-dev libpango1.0-dev libperl-dev libtiff5-dev libtiffxx5 libwmf-dev pkg-kde-tools xsltproc<br
/><br /><blockquote class="gmail_quote" style="margin: 0pt 0pt 1ex 0.8ex; border-left: 1px solid #729fcf; padding-left: 1ex;"><blockquote class="gmail_quote" style="margin: 0pt 0pt 1ex 0.8ex; border-left: 1px solid #ad7fa8; padding-left: 1ex;"> as a user<br /> git clone git://<a href="http://git.debian.org/git/collab-maint/imagemagick.git">git.debian.org/git/collab-maint/imagemagick.git</a><br /> cd imagemagick<br /></blockquote><br /> HERE run<br /> git checkout debian-patches/<a href="http://6.8.9.9">6.8.9.9</a>-5+deb8u3<br /> <br /><blockquote class="gmail_quote" style="margin: 0pt 0pt 1ex 0.8ex; border-left: 1px solid #ad7fa8; padding-left: 1ex;"> git checkout debian-patches/<a href="http://6.8.9.9">6.8.9.9</a>-5+deb8u4<br /></blockquote></blockquote><br />So I ran both (first +deb8u3, then +deb8u4), right?<br />(Otherwise, +deb8u3 would be the same as in "good" below.)<br /><br /><blockquote class="gmail_quote" style="margin: 0pt 0pt 1ex 0.8ex; border-left: 1px solid
#729fcf; padding-left: 1ex;"><blockquote class="gmail_quote" style="margin: 0pt 0pt 1ex 0.8ex; border-left: 1px solid #ad7fa8; padding-left: 1ex;"> git bisect start<br /> git bisect bad<br /> git bissect good debian-patches/<a href="http://6.8.9.9">6.8.9.9</a>-5+deb8u3<br /><br /> Once you have specified at least one bad and one good commit, git<br /> bisect selects a commit in the middle of that range of history, checks<br /> it out, and outputs something similar to the following:<br /><br /> Bisecting: 675 revisions left to test after this (roughly 10 steps)<br /><br /> You should now compile the checked-out version and test it. If that<br /> version works correctly, type. Compiling is done by typing<br /> ./configure<br /> make check<br /></blockquote></blockquote><br />That already gave an error (see test-suite.log). (I first ran make<br />with "-j16", then reran "make check" (but didn't rebuild) without<br />"-j", same result.) I'll be ignoring this (and further
test-suite<br />errors I got while bisecting).<br /><br /><blockquote class="gmail_quote" style="margin: 0pt 0pt 1ex 0.8ex; border-left: 1px solid #729fcf; padding-left: 1ex;"><blockquote class="gmail_quote" style="margin: 0pt 0pt 1ex 0.8ex; border-left: 1px solid #ad7fa8; padding-left: 1ex;"> you could run the command without installing by runing the <a href="http://convert.sh">convert.sh</a> wrapper<br /> ./<a href="http://magick.sh">magick.sh</a> convert geometry 40% tux.png tux-scaled-old.ppm<br /><br /> if bad run<br /> git bisect bad<br /> and rerun compile and testing<br /> if good run<br /> git bisect good<br /><br /> Some pointer could be found in man git bisect<br /></blockquote></blockquote><br />26d910675e0cd1b62e988139dba8eb11931260ac is the first bad commit<br />commit 26d910675e0cd1b62e988139dba8eb11931260ac<br />Author: Cristy <urban-warrior@imagemagick.org><br />Date: Sat Jan 30 09:37:10 2016 -0500<br /><br /> Fix out of bound in quantum handling<br />
<br /> Bug: <a href="https://github.com/ImageMagick/ImageMagick/issues/105">https://github.com/ImageMagick/ImageMagick/issues/105</a><br /> bug-ubuntu: <a href="https://bugs.launchpad.net/ubuntu/+source/imagemagick/+bug/1539053">https://bugs.launchpad.net/ubuntu/+source/imagemagick/+bug/1539053</a><br /> origin: upstream, <a href="https://github.com/ImageMagick/ImageMagick/commit/c4e63ad30bc42da691f2b5f82a24516dd6b4dc70">https://github.com/ImageMagick/ImageMagick/commit/c4e63ad30bc42da691f2b5f82a24516dd6b4dc70</a><br /> bug-debian: <a href="https://bugs.debian.org/832506">https://bugs.debian.org/832506</a><br /><br />:040000 040000 41e16d89455879892777d50135af38993b5be722 e841bf15b62dee866b54eab729a93163d85aee68 M magick<br /><br />git diff 3e07cd10a9a2215c9edcc0c0e1541c125371cfbc 26d910675e0cd1b62e988139dba8eb11931260ac<br />shows that the change essentially replaced image->columns by<br />MagickMax(image->columns,image->rows) in several places. This
might<br />explain why the bug only occurs with portrait. I see that some<br />callers of GetQuantumExtent() use its result as the length parameter<br />to ReadBlob and similar, so it seems strange to use the max of width<br />and height here. Others callers might use it for a work buffer where<br />this might be correct (and probably what the change was meant to<br />fix), but it might be necessary to separate those two cases.<br /><br />Frank<br /></pre></blockquote></div><br>
-- <br>
Envoyé de mon appareil Android avec K-9 Mail. Veuillez excuser ma brièveté.</body></html>