Created attachment 245195 [details] security/py-pycryptodome-test-vectors: Update to 1.0.13 Changelog ========= * Update to 1.0.13 * Conform to upstream publishing only ZIP distfile QA == portlint: OK poudriere: OK -- testport on 13.2-RELEASE amd64 w/py38, py39, py310 (default), and py311
Is there a changelog for this update? Your changelog just says that you update to the new upstream version. But what actually changed up stream?
(In reply to Robert Clausecker from comment #1) The best I can offer is the trailing commit history of the test_vectors directory from the commit at which the version number changed [0]. While the pycryptodome-test-vectors' version number is its own, the upstream project does not maintain a separate change log for it. [0] https://github.com/Legrandin/pycryptodome/commits/bcfd82dcd6d94abb304930ec9ab5779abd8d89ef/test_vectors
Works for me!
A commit in branch main references this bug: URL: https://cgit.FreeBSD.org/ports/commit/?id=ba95123b0e7e3509c6d138987579ec30299ac564 commit ba95123b0e7e3509c6d138987579ec30299ac564 Author: John W. O'Brien <john@saltant.com> AuthorDate: 2023-09-29 21:33:31 +0000 Commit: Robert Clausecker <fuz@FreeBSD.org> CommitDate: 2023-09-30 20:00:01 +0000 security/py-pycryptodome-test-vectors: update to 1.0.13 Changelog: https://github.com/Legrandin/pycryptodome/commits/v3.19.0/test_vectors PR: 274067 security/py-pycryptodome-test-vectors/Makefile | 6 +++--- security/py-pycryptodome-test-vectors/distinfo | 6 +++--- 2 files changed, 6 insertions(+), 6 deletions(-)
Thank you for your contribution.