Created attachment 210163 [details] py-pyjwt.diff QA: * portlint: OK (looks fine.) * testport: OK (poudriere: 12.0, amd64 tested) * maketest: OK (180 passed 1 xfailed 7 skipped)
Comment on attachment 210163 [details] py-pyjwt.diff Awaiting maintainer feedback from Terje
Comment on attachment 210163 [details] py-pyjwt.diff Approved by: portmgr (maintainer timeout: > 14 days) Pending QA
Created attachment 210733 [details] py-jwt.diff I changed only MAINTAINER line. If Terje wishes to keep maintaining the port, I will be more than glad to revert MAINTAINER back.
Hi Goran, I think changing the maintainer would need another 2 weeks to give terje enough time to see this change and respond with feedback. Can I suggest we progress this port update now without the maintainer change to get it in the ports tree, and perhaps you can submit the next patch / update with the maintainer change included?
A commit references this bug: Author: woodsb02 Date: Tue Jan 14 22:20:44 UTC 2020 New revision: 523072 URL: https://svnweb.freebsd.org/changeset/ports/523072 Log: www/py-pyjwt: Updtae to 1.7.1 Changes this release: https://github.com/jpadilla/pyjwt/blob/1.7.1/CHANGELOG.md PR: 242818 Submitted by: Goran Meki? <meka@tilda.center> Approved by: Terje Elde <terje@elde.net> (maintainer timeout) Changes: head/www/py-pyjwt/Makefile head/www/py-pyjwt/distinfo head/www/py-pyjwt/files/
Committed - thanks!
Comment on attachment 210163 [details] py-pyjwt.diff ^Triage: This is the patch that landed, "unobsolete" accordingly
Comment on attachment 210733 [details] py-jwt.diff ^Triage: This patch was skipped (do maintainer change later): obsolete it.