#64460 closed defect (fixed)
py-cwcwidth: checksum mismatch
Reported by: | ryandesign (Ryan Carsten Schmidt) | Owned by: | judaew (Vadym-Valdis Yudaiev) |
---|---|---|---|
Priority: | Normal | Milestone: | |
Component: | ports | Version: | 2.7.1 |
Keywords: | Cc: | ||
Port: | py-cwcwidth |
Description
$ port fetch --no-mirrors py310-cwcwidth ---> Fetching distfiles for py310-cwcwidth ---> Attempting to fetch cwcwidth-0.1.6.tar.gz from https://codeload.github.com/sebastinas/cwcwidth/legacy.tar.gz/v0.1.6?dummy= $ port checksum py310-cwcwidth ---> Verifying checksums for py310-cwcwidth Error: Checksum (rmd160) mismatch for cwcwidth-0.1.6.tar.gz Error: Checksum (sha256) mismatch for cwcwidth-0.1.6.tar.gz Error: Checksum (size) mismatch for cwcwidth-0.1.6.tar.gz Error: Failed to checksum py310-cwcwidth: Unable to verify file checksums
This was caused by [d5558057fc2aec6fa5605da00ef5f72dbd09b16c/macports-ports].
I don't understand the commit message
From GitHub the port is built with the correct library architecture.
at all, since the github portgroup has no influence on how a port builds (it only concerns itself with how it fetches and extracts), and the port is marked noarch.
Change History (5)
comment:1 Changed 3 years ago by ryandesign (Ryan Carsten Schmidt)
comment:2 Changed 3 years ago by ryandesign (Ryan Carsten Schmidt)
So the thing to do seems to be to revert the switch to the github portgroup; remove supported_archs noarch
; and increase revision
.
comment:3 Changed 3 years ago by Vadim-Valdis Yudaev <judaew@…>
Resolution: | → fixed |
---|---|
Status: | assigned → closed |
comment:4 Changed 3 years ago by judaew (Vadym-Valdis Yudaiev)
That's the problem. I caught a bug with the wrong architecture and thought there was some kind of bug in the PyPi package. I tried locally to rebuild port a few times. Didn't know supported_archs noarch
could affect CPython like that.
Thank you!
comment:5 Changed 3 years ago by ryandesign (Ryan Carsten Schmidt)
Python modules can contain compiled code or not. If no compiled code, usually you would use supported_archs noarch
, but if there is compiled code, then don't use that.
Replying to ryandesign:
Which it isn't: