#27814: checksum(s) for db46 Error: Checksum (md5) mismatch for patch.4.6.21.1 ------------------------------------+--------------------------------------- Reporter: culler@… | Owner: blair@… Type: defect | Status: new Priority: Normal | Milestone: Component: ports | Version: 1.9.2 Keywords: | Port: db46 ------------------------------------+--------------------------------------- Changes (by jmr@…): * owner: macports-tickets@… => blair@… * port: => db46 Old 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.

New 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. -- Comment: Please remember to preview and use WikiFormatting, fill in the Port field, and cc the maintainer. -- Ticket URL: <https://trac.macports.org/ticket/27814#comment:1> MacPorts <http://www.macports.org/> Ports system for Mac OS