[Pkg-gmagick-im-team] Bug#835650: Imagemagick regression pin point patch

[Bastien ROUCARIES]

Some correction

On Wed, Aug 31, 2016 at 8:42 AM, Bastien ROUCARIES
<roucaries.bastien at gmail.com> wrote:
> Hi,
>
> Patches are needed for a security point of view but it is likely a
> problem of backport intereaction.
>
> Could you help by pin point the problem.
>
> as root install a few package needed for imagemagick compilation:
> apt-get install git
> apt-get build-dep imagemagick
>
> as a user
>  git clone   git://git.debian.org/git/collab-maint/imagemagick.git
> cd imagemagick


HERE run
git checkout debian-patches/6.8.9.9-5+deb8u3

> git checkout debian-patches/6.8.9.9-5+deb8u4


> git bisect start
> git bisect bad
> git bissect good debian-patches/6.8.9.9-5+deb8u3
>
>   Once you have specified at least one bad and one good commit, git
> bisect selects a commit in the middle of that range of history, checks
> it out, and outputs something similar to the following:
>
>            Bisecting: 675 revisions left to test after this (roughly 10 steps)
>
>  You should now compile the checked-out version and test it. If that
> version works correctly, type. Compiling is done by typing
> ./configure
> make check
>
> you could run the command without installing by runing the convert.sh wrapper
> ./magick.sh convert geometry 40% tux.png tux-scaled-old.ppm
>
> if bad run
> git bisect bad
> and rerun compile and testing
> if good run
> git bisect good
>
> Some pointer could be found in man git bisect
>
> Bastien