Opened 14 years ago

Closed 14 years ago

#28894 closed defect (invalid)

db46 patches(1-4) checksum problem

Reported by: paolo.bison@… Owned by: blair (Blair Zajac)
Priority: Normal Milestone:
Component: ports Version: 1.9.2
Keywords: Cc:
Port: db46

Description (last modified by jmroot (Joshua Root))

I am upgrading my ports. When trying to patch db46 with patch.4.6.21.1 through patch.4.6.21.4 I obtain the following message: 

--->  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: Problem while installing db46

Change History (2)

comment:1 Changed 14 years ago by jmroot (Joshua Root)

Description: modified (diff)
Owner: changed from macports-tickets@… to blair@…
Priority: High → Normal

Please remember to preview and use WikiFormatting, and cc the maintainer. As per the ticket guidelines, the High priority is reserved for the use of MacPorts team members.

Have you read the MisbehavingServers page? What do the downloaded files contain?

comment:2 Changed 14 years ago by ryandesign (Ryan Carsten Schmidt)

Resolution: → invalid
Status: new → closed
Note: See TracTickets for help on using tickets.