Comment 4 for bug 2004580

Jammy needs a few more commits from upstream for a clean apply:

ubuntu-imagemagick % git checkout origin/applied/ubuntu/jammy
Previous HEAD position was d5cfbaeb8 8:6.9.10.23+dfsg-2.1ubuntu11.4 (patches applied)
HEAD is now at bc5d3ac18 8:6.9.11.60+dfsg-1.3build2 (patches applied)

ubuntu-imagemagick % curl -s https://github.com/ImageMagick/ImageMagick6/commit/be3b2a02cbb9c9affa7b0afa0665ed4b4bb0f47b.patch https://github.com/ImageMagick/ImageMagick6/commit/222845f6a0848c1e1c567bb1618617e786523bb2.patch https://github.com/ImageMagick/ImageMagick6/commit/87d719c194cc9356cdcf5df578bbea25582a290c.patch https://github.com/ImageMagick/ImageMagick6/commit/d77c01e560e973177feed4915ffd7dd1a45fd763.patch | patch
patching file 'magick/property.c'
patching file 'magick/property.c'
patching file 'magick/property.c'
patching file 'magick/property.c'
patching file 'wand/mogrify.c'

This then also includes https://github.com/ImageMagick/ImageMagick6/commit/be3b2a02cbb9c9affa7b0afa0665ed4b4bb0f47b which appears to fix another vulnerability.

At this point I am not sure if the fix applied to bionic (https://git.launchpad.net/ubuntu/+source/imagemagick/commit/?id=7b0f88e3da8a0aca0774318be77c6e476c537334) is even complete. The commit message sort of points to https://github.com/ImageMagick/ImageMagick6/commit/3c5188b41902a909e163492fb0c19e49efefcefe, and I believe https://github.com/ImageMagick/ImageMagick6/commit/23bf43133d5fc525afafdc47398cd92b3b68797d is related as well.

It appears like https://git.launchpad.net/ubuntu/+source/imagemagick/commit/?id=7b0f88e3da8a0aca0774318be77c6e476c537334 is the original upstream fix, and that was later improved, or fully fixed, using the patches I linked?