Opened 6 years ago
Closed 6 years ago
#58305 closed defect (fixed)
libyaml 0.2.2 checksum error
Reported by: | snarkhunter (Steve Langer) | Owned by: | kencu (Ken) |
---|---|---|---|
Priority: | Normal | Milestone: | |
Component: | ports | Version: | 2.5.4 |
Keywords: | Cc: | ||
Port: | libyaml |
Description
When upgrading libyaml, I'm getting a checksum error.
% sudo port upgrade outdated ---> Computing dependencies for libyaml ---> Fetching distfiles for libyaml ---> Verifying checksums for libyaml Error: Checksum (rmd160) mismatch for yaml-0.2.2.tar.gz Error: Checksum (sha256) mismatch for yaml-0.2.2.tar.gz Error: Checksum (size) mismatch for yaml-0.2.2.tar.gz Error: Failed to checksum libyaml: Unable to verify file checksums
Attachments (1)
Change History (8)
Changed 6 years ago by snarkhunter (Steve Langer)
comment:1 Changed 6 years ago by reneeotten (Renee Otten)
comment:2 Changed 6 years ago by snarkhunter (Steve Langer)
No, that didn't change anything.
It looks like the downloaded file is the old version, from before that modification to the portfile.
% cd /opt/local/var/macports/distfiles/libyaml % wc -c yaml-0.2.2.tar.gz 79465 yaml-0.2.2.tar.gz % openssl dgst -rmd160 yaml-0.2.2.tar.gz RIPEMD160(yaml-0.2.2.tar.gz)= 69780e8ab84506e8c2422aa49c1c9743ee433251 % openssl dgst -sha256 yaml-0.2.2.tar.gz SHA256(yaml-0.2.2.tar.gz)= 46bca77dc8be954686cff21888d6ce10ca4016b360ae1f56962e6882a17aa1fe
comment:3 Changed 6 years ago by reneeotten (Renee Otten)
that's weird for me it installs just fine, you are sure that you did the clean
? If I do sudo port -dv livecheck libyaml
, it passes the checksum verification, can you try that as well? Please also post the output of port -v installed libyaml
.
comment:4 follow-up: 5 Changed 6 years ago by kencu (Ken)
OH -- maybe this port did a "stealth update" and I/nobody noticed....
try this:
sudo port clean --all libyaml sudo port -v install libyaml
which will get you a new distfile.
comment:5 Changed 6 years ago by ryandesign (Ryan Carsten Schmidt)
Replying to kencu:
OH -- maybe this port did a "stealth update" and I/nobody noticed....
What else could it be? You noticed, enough to commit a change to the checksums...
comment:6 Changed 6 years ago by kencu (Ken)
I had originally thought there might have just been a simple mistake, until I saw that the previous download file actually did exist from the other poster here.
comment:7 Changed 6 years ago by kencu (Ken)
Owner: | set to kencu |
---|---|
Resolution: | → fixed |
Status: | new → closed |
I assume that this was fixed with this commit. Can you please upgrade the ports tree, clean the port and try again?