#50602 closed defect (fixed)
developer_cmds @62 Checksum Error
Reported by: | jwelcher@… | Owned by: | mfeiri |
---|---|---|---|
Priority: | Normal | Milestone: | |
Component: | ports | Version: | 2.3.4 |
Keywords: | Cc: | raimue (Rainer Müller) | |
Port: | developer_cmds |
Description (last modified by raimue (Rainer Müller))
I'm running Mac OS X 10.11.3 with Xcode 7.2.1 Build version 7C1002, but I don't think that matters.
I'm pretty sure there is just a checksum error in the port manifest for developer_cmds:
{hocallost:etc}# port install developer_cmds ---> Fetching distfiles for developer_cmds ---> Verifying checksums for developer_cmds Error: Checksum (rmd160) mismatch for developer_cmds-62.tar.gz Error: Checksum (sha256) mismatch for developer_cmds-62.tar.gz Error: org.macports.checksum for port developer_cmds returned: Unable to verify file checksums
So I think this is an accurate error. The checksums in the port aren't correct. Here's the trenchant part of the log:
:debug:fetch Executing org.macports.fetch (developer_cmds) :info:fetch ---> developer_cmds-62.tar.gz doesn't seem to exist in /opt/local/var/macports/distfiles/developer_cmds :notice:fetch ---> Attempting to fetch developer_cmds-62.tar.gz from http://opensource.apple.com/tarballs/developer_cmds/ :debug:fetch Privilege de-escalation not attempted as not running as root. :debug:checksum checksum phase started at Thu Feb 11 19:03:46 PST 2016 :notice:checksum ---> Verifying checksums for developer_cmds :debug:checksum Executing org.macports.checksum (developer_cmds) :info:checksum ---> Checksumming developer_cmds-62.tar.gz :debug:checksum Calculated (rmd160) is b5ddc5e442040bedf727480accbe723741ddf24c :error:checksum Checksum (rmd160) mismatch for developer_cmds-62.tar.gz :info:checksum Portfile checksum: developer_cmds-62.tar.gz rmd160 fc306cba8e6e974914efd352833d54d08466fc9b :info:checksum Distfile checksum: developer_cmds-62.tar.gz rmd160 b5ddc5e442040bedf727480accbe723741ddf24c :debug:checksum Calculated (sha256) is b11161df7a8dd293efe52213d8e968279dbff545a583e4706c4250d6cc122ce5 :error:checksum Checksum (sha256) mismatch for developer_cmds-62.tar.gz :info:checksum Portfile checksum: developer_cmds-62.tar.gz sha256 f6913ee3d9e26b59f503886e60e34bfce8e58cffea82874820b4fa037e394acf :info:checksum Distfile checksum: developer_cmds-62.tar.gz sha256 b11161df7a8dd293efe52213d8e968279dbff545a583e4706c4250d6cc122ce5 :info:checksum The correct checksum line may be: :info:checksum checksums rmd160 b5ddc5e442040bedf727480accbe723741ddf24c \ sha256 b11161df7a8dd293efe52213d8e968279dbff545a583e4706c4250d6cc122ce5 :error:checksum org.macports.checksum for port developer_cmds returned: Unable to verify file checksums :debug:checksum Error code: NONE
I pulled them down myself from http://opensource.apple.com/tarballs/developer_cmds/
to verify the checksums and it does look like the port registered ones are wrong.
$ openssl dgst -sha256 developer_cmds-62.tar.gz SHA256(developer_cmds-62.tar.gz)= b11161df7a8dd293efe52213d8e968279dbff545a583e4706c4250d6cc122ce5
Change History (4)
comment:1 Changed 9 years ago by raimue (Rainer Müller)
Cc: | raimue@… added |
---|---|
Description: | modified (diff) |
Owner: | changed from macports-tickets@… to mfeiri@… |
Port: | @62 (devel) removed |
comment:2 Changed 9 years ago by raimue (Rainer Müller)
This is a stealth update. I compared both tarballs and while the metadata (mtime and user/group) in the tarball differs, the actual content of the files is unchanged.
comment:3 Changed 9 years ago by mfeiri
Resolution: | → fixed |
---|---|
Status: | new → closed |
Thanks for the report, fixed in r145752
comment:4 Changed 9 years ago by jwelcher@…
Thanks all!
BTW, just in case anyone is interested, I was looking into this because it looks like Apple removed some commands, like "vgrind" which I sometimes use to format c, from El Capitan. Anyway, your guide on how to install older ports (https://trac.macports.org/wiki/howto/InstallingOlderPort) worked great, and I was able to install vgrind from developer_cmds@60.
Much appreciated.
Please remember to use WikiFormatting and add the maintainer to CC on reports.