Opened 14 years ago
Closed 13 years ago
#29404 closed defect (invalid)
db46 @4.6.21: Unable to verify file checksums
Reported by: | pietro@… | Owned by: | blair (Blair Zajac) |
---|---|---|---|
Priority: | Normal | Milestone: | |
Component: | ports | Version: | 1.9.2 |
Keywords: | Cc: | ||
Port: | db46 |
Description
I tried to install ghostscript, everything was fine until this error came up. It couldn't verify the checksum of db46.
MacOS 10.6.7 Intel, Core 2 Duo, 2.66Ghz, 4G RAM
shambhala:~ zuco$ sudo port install db46 ---> Verifying checksum(s) for db46 Error: Checksum (md5) mismatch for patch.4.6.21.1 Error: Checksum (sha1) mismatch for patch.4.6.21.1 Error: Checksum (rmd160) mismatch for patch.4.6.21.1 Error: Checksum (md5) mismatch for patch.4.6.21.2 Error: Checksum (sha1) mismatch for patch.4.6.21.2 Error: Checksum (rmd160) mismatch for patch.4.6.21.2 Error: Checksum (md5) mismatch for patch.4.6.21.3 Error: Checksum (sha1) mismatch for patch.4.6.21.3 Error: Checksum (rmd160) mismatch for patch.4.6.21.3 Error: Checksum (md5) mismatch for patch.4.6.21.4 Error: Checksum (sha1) mismatch for patch.4.6.21.4 Error: Checksum (rmd160) mismatch for patch.4.6.21.4 *** The non-matching file appears to be HTML. See this page for possible reasons for the checksum mismatch: <http://trac.macports.org/wiki/MisbehavingServers> *** Error: Target org.macports.checksum returned: Unable to verify file checksums Log for db46 is at: /opt/local/var/macports/logs/_opt_local_var_macports_sources_rsync.macports.org_release_ports_databases_db46/main.log Error: Status 1 encountered during processing. To report a bug, see <http://guide.macports.org/#project.tickets> shambhala:~ zuco$
Change History (3)
comment:1 Changed 14 years ago by jmroot (Joshua Root)
Owner: | changed from macports-tickets@… to blair@… |
---|---|
Port: | db46 added |
Summary: | db46 @patch.4.6.21.1 Error: Target org.macports.checksum returned: Unable to verify file checksums → db46 @4.6.21: Unable to verify file checksums |
Type: | update → defect |
comment:2 Changed 14 years ago by pietro@…
Thanks I read it and made the modifications, anyway I did more research and found this ticket that had exactly the same problem as mine:
Now it's fixed.
Thanks!
comment:3 Changed 13 years ago by ryandesign (Ryan Carsten Schmidt)
Resolution: | → invalid |
---|---|
Status: | new → closed |
Note: See
TracTickets for help on using
tickets.
Please remember to fill in the Port field and cc the maintainer. As per the FAQ, you need to indicate which mirror your file was downloaded from.
Have you read the MisbehavingServers page? What does the HTML say?