- Update to 3.4.2 - Add JPEG2000 option Changes: https://github.com/python-pillow/Pillow/blob/master/CHANGES.rst py-pillow in the ports tree is 3.1.1 which is vulnerable [1]. [1] https://vuxml.freebsd.org/freebsd/bc4898d5-a794-11e6-b2d3-60a44ce6887b.html
Maintainer TIMEOUT, back to the pool. Looks good. Running build tests now.
Build passed: * Poudriere 11.0, amd64, python35 * Poudriere 11.0, amd64, python27 * Poudriere 10.3, amd64, python35 * Poudriere 10.3, amd64, python27
Port's unit tests passed, Ran 785 tests in 6.355s, skipped 119.
(In reply to Vladimir Krstulja from comment #1) @Vladimir, thank you for testing. I think this should be MFH'd to 2017Q1. BTW, it seems the timeout will be Jan 10 (14 days from Dec 27).
When it's security related we don't need maintainer approval / wait for timeout.
(In reply to Mark Felder from comment #5) Ok, so it's covered by portmgr blanket or ports-secteam blanket?
committed, thanks!
A commit references this bug: Author: feld Date: Mon Jan 9 18:00:01 UTC 2017 New revision: 430992 URL: https://svnweb.freebsd.org/changeset/ports/430992 Log: graphics/py-pillow: Update to 3.4.2 (security fixes) - Update to 3.4.2 - Add JPEG2000 option Changes: https://github.com/python-pillow/Pillow/blob/master/CHANGES.rst PR: 215615 MFH: 2017Q1 Changes: head/graphics/py-pillow/Makefile head/graphics/py-pillow/distinfo
A commit references this bug: Author: feld Date: Mon Jan 9 18:00:36 UTC 2017 New revision: 430993 URL: https://svnweb.freebsd.org/changeset/ports/430993 Log: MFH: r430992 graphics/py-pillow: Update to 3.4.2 (security fixes) - Update to 3.4.2 - Add JPEG2000 option Changes: https://github.com/python-pillow/Pillow/blob/master/CHANGES.rst PR: 215615 Approved by: ports-secteam (with hat) Changes: _U branches/2017Q1/ branches/2017Q1/graphics/py-pillow/Makefile branches/2017Q1/graphics/py-pillow/distinfo
(In reply to Po-Chuan Hsieh from comment #6) ports-secteam approval generally overrides need of maintainer approval (of course common sense presides)
(In reply to Po-Chuan Hsieh from comment #4) The reason I stated timeout, beside it being a security issue like feld said, is that I already have an issue open about it from November (the dependent bug #214412). I just never got around to producing a patch like you did :)