Date: Mon, 26 Apr 2021 02:31:57 +0000 From: bugzilla-noreply@freebsd.org To: python@FreeBSD.org Subject: [Bug 255237] devel/py-importlib-metadata: Update 3.3.0 -> 4.0.0 Message-ID: <bug-255237-21822-Qy9BPt0Kg0@https.bugs.freebsd.org/bugzilla/> In-Reply-To: <bug-255237-21822@https.bugs.freebsd.org/bugzilla/> References: <bug-255237-21822@https.bugs.freebsd.org/bugzilla/>
index | next in thread | previous in thread | raw e-mail
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=255237 --- Comment #8 from Steve Wills <swills@FreeBSD.org> --- It seems to me, the problem is the update to py-keyring in 38825393978e, which lacked the dependency on importlib-metadata and was done without checking the version of importlib-metadata. And further it seems that what should happen to solve that is that that commit to update py-keyring should be reverted and PORTEPOCH bumped on py-keyring, for now. Then, it should be re-done after importlib-metadata is updated, along with a further change to add a dependency on importlib-metadata to the py-keyring port. But there's no need to MFH any of this, as the py-keyring update was done after the branch was created. For reference: https://github.com/jaraco/keyring/compare/18.0.1...v23.0.1#diff-fa602a8a75dc9dcc92261bac5f533c2a85e34fcceaff63b3a3a81d9acde2fc52R28 https://cgit.freebsd.org/ports/commit/?id=38825393978e4606227947eeefa062454e449b3e https://cgit.freebsd.org/ports/tree/security/py-keyring/Makefile?h=2021Q2 -- You are receiving this mail because: You are on the CC list for the bug.help
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?bug-255237-21822-Qy9BPt0Kg0>