Opened 7 years ago
Closed 6 years ago
#56341 closed defect (fixed)
binwalk @2.1.1 (cross) : Verifying checksums failed
Reported by: | camoulin | Owned by: | stromnov (Andrey Stromnov) |
---|---|---|---|
Priority: | Normal | Milestone: | |
Component: | ports | Version: | 2.4.2 |
Keywords: | Cc: | ||
Port: | binwalk |
Description (last modified by ryandesign (Ryan Carsten Schmidt))
sudo port install binwalk ---> Computing dependencies for binwalk ---> Verifying checksums for binwalk Error: Checksum (rmd160) mismatch for binwalk-2.1.1.tar.gz Error: Checksum (sha256) mismatch for binwalk-2.1.1.tar.gz Error: Failed to checksum binwalk: Unable to verify file checksums Error: See /opt/local/var/macports/logs/_opt_local_var_macports_sources_github.com_macports_macports-ports_cross_binwalk/binwalk/main.log for details. Error: Follow https://guide.macports.org/#project.tickets to report a bug. Error: Processing of port binwalk failed
MacPorts 2.4.2
OSX Sierra Darwin Kernel Version 16.7.0
i use the git synchronization repository
file:///opt/local/var/macports/sources/github.com/macports/macports-ports/ [default]
Change History (5)
comment:1 follow-up: 3 Changed 7 years ago by raimue (Rainer Müller)
Keywords: | checksum sierra removed |
---|---|
Owner: | set to stromnov |
Port: | binwalk added |
Status: | new → assigned |
comment:2 Changed 7 years ago by ryandesign (Ryan Carsten Schmidt)
Description: | modified (diff) |
---|
comment:3 Changed 7 years ago by ryandesign (Ryan Carsten Schmidt)
Replying to raimue:
Looks like a stealth update. Probably caused by GitHub as described in #54839.
No, caused by the GitHub organization name changing from devttys0 to ReFirmLabs.
comment:4 Changed 7 years ago by pmetzger (Perry E. Metzger)
If this is literally just a checksum error, I encourage the submitter to make a GitHub pull request with the change — it may result in faster turnaround.
comment:5 Changed 6 years ago by kiwiroy (Roy Storey)
Resolution: | → fixed |
---|---|
Status: | assigned → closed |
Note: See
TracTickets for help on using
tickets.
Looks like a stealth update. Probably caused by GitHub as described in #54839.