Opened 14 years ago

Closed 14 years ago

#27620 closed defect (worksforme)

db46 fails to build

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

Description (last modified by ryandesign (Ryan Carsten Schmidt))

[hammackj@fajitas:~/Projects/private/tenable/vmware]$ sudo port upgrade outdated
--->  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
***
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
To report a bug, see <http://guide.macports.org/#project.tickets>

Oracle seems to have deleted the webpage for it...

Change History (3)

comment:1 in reply to:  description Changed 14 years ago by ryandesign (Ryan Carsten Schmidt)

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

Replying to Jacob.Hammack@…:

Oracle seems to have deleted the webpage for it...

What makes you say that? It's working fine for me.

Did you read the MisbehavingServers page referenced above?

Please remember to use WikiFormatting and to Cc tickets to their ports' owners.

comment:2 Changed 14 years ago by Jacob.Hammack@…

I was able to get one of the patches via wget http://download.oracle.com/berkeley-db/patches/db/4.6.21/patch.4.6.21.1 and the hash matched the hash in the portfile. I am not sure why there is a mismatch on my sudo port upgrade outdated

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

Resolution: worksforme
Status: newclosed

Seems fine to me. Clean --dist and try again.

Note: See TracTickets for help on using tickets.