Opened 13 years ago
Last modified 13 years ago
#27814 closed defect
checksum(s) for db46 Error: Checksum (md5) mismatch for patch.4.6.21.1 — at Initial Version
| Reported by: | culler@… | Owned by: | macports-tickets@… |
|---|---|---|---|
| Priority: | Normal | Milestone: | |
| Component: | ports | Version: | 1.9.2 |
| Keywords: | Cc: | ||
| Port: | db46 |
Description
Re: Ticket #27620 (closed defect: worksforme) - the problem persists,
It seems that the patch request gets redirected. cf
Fetching db46 ---> Attempting to fetch patch.4.6.21.1 from http://www.oracle.com/technology/products/berkeley-db/db/update/4.6.21/ ---> Attempting to fetch patch.4.6.21.2 from http://www.oracle.com/technology/products/berkeley-db/db/update/4.6.21/ ---> Attempting to fetch patch.4.6.21.3 from http://www.oracle.com/technology/products/berkeley-db/db/update/4.6.21/ ---> Attempting to fetch patch.4.6.21.4 from http://www.oracle.com/technology/products/berkeley-db/db/update/4.6.21/ ---> Attempting to fetch db-4.6.21.tar.gz from http://download-east.oracle.com/berkeley-db/ ---> Verifying checksum(s) for db46 Error: Checksum (md5) mismatch for patch.4.6.21.1 Error: Checksum (md5) mismatch for patch.4.6.21.2 Error: Checksum (md5) mismatch for patch.4.6.21.3 Error: Checksum (md5) mismatch for patch.4.6.21.4 Error: Target org.macports.checksum returned: Unable to verify file checksums
The patch files that end up in /opt/local/var/macports/distfiles/db4/4.6.21_6 are html, not patch files. Downloading the patchfiles manually as indicated by the workaround does allow the build to proceed. The defect is that the bad ones should not have been there in the first place.