On Friday 14 October 2016 11.30.58 Brian May wrote:
> I haven't looked yet at the additional security issues. Might get time
> this evening. If you want to do so, feel free to do so.
I have been avoiding that for weeks. I can wait, don't worry :)
BTW, we don't have to fix all the issues together.
On Monday 10 October 2016 08.17.29 you wrote:
> I realize that there are more security issues in graphicsmagick, which
> may or may not apply to wheezy, however I plan to upload the above
> version to wheezy-security, tomorrow. Then I will look into these
> additional issues.
Hi Brian,
Did you
Brian May writes:
> I have a packaged version of graphicsmagick ready for testing:
>
> https://people.debian.org/~bam/debian/pool/main/g/graphicsmagick/
I realize that there are more security issues in graphicsmagick, which
may or may not apply to wheezy, however I plan to upload the above
versi
I have a packaged version of graphicsmagick ready for testing:
https://people.debian.org/~bam/debian/pool/main/g/graphicsmagick/
I have attached the debdiff patch to this email. Note that before doing
this upload, I renamed the last patch to CVE-2016-7800.patch, which was
incorrect in the above u
Brian May writes:
> Hello,
>
> Is this just me? Or has graphicsmagick really been packaged without
> debian/patches/*?
Ok, I fixed this up.
https://people.debian.org/~bam/debian/pool/main/g/graphicsmagick/
One of the patches is pretty big and could be split up, however for now
it seems to work
[Not sure why I am being CC'd here?]
> Is this just me? Or has graphicsmagick really been packaged without
> debian/patches/*?
Very likely; wheezy is old and the source/format wasn't universally adopted
overnight. :)
Regards,
--
,''`.
: :' : Chris Lamb
`. `'` la...@d
Hello,
Is this just me? Or has graphicsmagick really been packaged without
debian/patches/*?
⌁ [brian:~/tree/debian/debian-lts/wheezy/graphicsmagick] % dget
http://security.debian.org/debian-security/pool/updates/main/g/graphicsmagick/graphicsmagick_1.3.16-1.1+deb7u3.dsc
dget: retrieving
http:/
