Opened 14 years ago
Closed 14 years ago
#25569 closed defect (invalid)
checksum error on aircrack-ng-1.0.tar.gz - seems corrupt
Reported by: | clemc@… | Owned by: | macports-tickets@… |
---|---|---|---|
Priority: | Normal | Milestone: | |
Component: | ports | Version: | 1.9.1 |
Keywords: | Cc: | ||
Port: | aircrack-ng |
Description
Have rm'd and try to force a reload from the port server. Unless told otherwise will google for the tarball elsewhere and see if I can find one with with the proper checksum.
---> Verifying checksum(s) for aircrack-ng DEBUG: Executing org.macports.checksum (aircrack-ng) ---> Checksumming aircrack-ng-1.0.tar.gz Error: Checksum (md5) mismatch for aircrack-ng-1.0.tar.gz Portfile checksum: aircrack-ng-1.0.tar.gz md5 dafbfaf944ca9d523fde4bae86f0c067 Distfile checksum: aircrack-ng-1.0.tar.gz md5 42357175c6e04936ef67623203bb332c Error: Checksum (sha1) mismatch for aircrack-ng-1.0.tar.gz Portfile checksum: aircrack-ng-1.0.tar.gz sha1 8a3c5b8e322ea11e5559109a9f9d668ad6aee5f0 Distfile checksum: aircrack-ng-1.0.tar.gz sha1 2f20d154ddd944d98b18becca6f1083ad23687ff Error: Checksum (rmd160) mismatch for aircrack-ng-1.0.tar.gz Portfile checksum: aircrack-ng-1.0.tar.gz rmd160 e8360aabbec1e7e038f86579e1004234f0899409 Distfile checksum: aircrack-ng-1.0.tar.gz rmd160 5597d42bf9612ce84e07dbb2100d55722342f130 The correct checksum line may be: checksums md5 42357175c6e04936ef67623203bb332c \ sha1 2f20d154ddd944d98b18becca6f1083ad23687ff \ rmd160 5597d42bf9612ce84e07dbb2100d55722342f130 Error: Target org.macports.checksum returned: Unable to verify file checksums
Attachments (1)
Change History (7)
Changed 14 years ago by clemc@…
Attachment: | typescript added |
---|
comment:1 Changed 14 years ago by clemc@…
Hmmm - Gentle folk - if you would please tell me if the checksum is fine on the server copy - I think we can close this. I'm now seeing other strange things happen here with Safari having nothing to do with ports and I'm beginning to think the local network at work has gone rogue .. sigh...
Thanks, Clem
comment:2 Changed 14 years ago by mf2k (Frank Schima)
Port: | aircrack-ng added |
---|---|
Summary: | checksum error on airport-ng-1.0.tar.gz - seems corrupt → checksum error on aircrack-ng-1.0.tar.gz - seems corrupt |
Please read the FAQ on checksum errors. You did not provide the download mirror.
FYI, it downloads fine for me.
comment:3 Changed 14 years ago by clemc@…
Thanks. I'll try again at home on a network - I control ;-) If that fails again, I'll dig through what it's using for the server - I tend to use portcus front end.
comment:5 follow-up: 6 Changed 14 years ago by clemc@…
Folks - thank you for the help. Indeed the build works properly and the tar ball can be found as expected by the build with a working network!. My issue was my employer's internal network (sigh). If I see this type of error again, I'll know where to look, so I can tell our IT folks that they have issue.
However ... in the course of debugging this, I learned that in this case tool, the airport-ng folks are no longer advertising version 1.0 - if you try to go to the web site directly, they do not seem to have a pointer to that tarball, only the newer version (1.1). However clearly, the old path you have in your build still works. But I think that may be a warning, we might want to look into updating before that path goes away and/or moving the *1.0 tarball ball to intermediate location ???FreeBSD distfile archive maybe - you tell me??? in case the link does go away.
Thank you all for the help,
Clem
comment:6 Changed 14 years ago by ryandesign (Ryan Carsten Schmidt)
Resolution: | → invalid |
---|---|
Status: | new → closed |
Replying to clemc@…:
My issue was my employer's internal network (sigh). If I see this type of error again, I'll know where to look, so I can tell our IT folks that they have issue.
Ok, glad you got it figured out. Maybe a case of #25128.
However ... in the course of debugging this, I learned that in this case tool, the airport-ng folks are no longer advertising version 1.0 - if you try to go to the web site directly, they do not seem to have a pointer to that tarball, only the newer version (1.1). However clearly, the old path you have in your build still works. But I think that may be a warning, we might want to look into updating before that path goes away
Good idea. I filed #25645 for this.
and/or moving the *1.0 tarball ball to intermediate location ???FreeBSD distfile archive maybe - you tell me??? in case the link does go away.
MacPorts maintains its own distfiles mirrors. The aircrack-ng 1.0 distfile for example is safely stored for all time at http://distfiles.macports.org/aircrack-ng/
dialog of complete port command typed.