Created attachment 206163 [details] mitmproxy-prepare-for-py-openssl-and-fix-runtime-error.patch Hi, attached is a patch that does following actions to www/mitmproxy: - Relax the requirements for security/py-openssl (to update that port to 19.0.0) - Since security/py-cryptography has been updated to 2.6 in ports r496506 www/mitmproxy fails at runtime. Thus also relax the requirements for security/py-cryptography and unbreak it. QA: ~~~ - poudriere (11.2-, 11.3-, 12.0-RELEASE, 13.0-CURRENT@r349352 amd64 + i386) -> OK
Looks good to me. Thanks very much.
A commit references this bug: Author: kai Date: Sun Aug 4 21:12:29 UTC 2019 New revision: 508126 URL: https://svnweb.freebsd.org/changeset/ports/508126 Log: www/mitmproxy: Prepare for py-openssl 19.0.0 and unbreak at runtime Relax the version ranges for security/py-openssl to avoid breakage at runtime when release 19.0.0 lands into the Ports tree. Also unbreak the port as it's already broken at runtime because the given requirements for security/py-cryptography are too narrow. PR: 239540 Approved by: Hung-Yi Chen <gaod@hychen.org> (maintainer) MFH: 2019Q3 (runtime fix) Changes: head/www/mitmproxy/Makefile head/www/mitmproxy/files/patch-setup.py
A commit references this bug: Author: kai Date: Sun Aug 4 21:15:37 UTC 2019 New revision: 508127 URL: https://svnweb.freebsd.org/changeset/ports/508127 Log: MFH: r508126 www/mitmproxy: Prepare for py-openssl 19.0.0 and unbreak at runtime Relax the version ranges for security/py-openssl to avoid breakage at runtime when release 19.0.0 lands into the Ports tree. Also unbreak the port as it's already broken at runtime because the given requirements for security/py-cryptography are too narrow. PR: 239540 Approved by: Hung-Yi Chen <gaod@hychen.org> (maintainer) Approved by: ports-secteam blanket (runtime fix) Changes: _U branches/2019Q3/ branches/2019Q3/www/mitmproxy/Makefile branches/2019Q3/www/mitmproxy/files/patch-setup.py
Comment on attachment 206163 [details] mitmproxy-prepare-for-py-openssl-and-fix-runtime-error.patch Approved by maintainer
Thank you for your review and approval, the changes have been committed to the head and 2019Q3 branch!