libdvdnav: checksum mismatch because HTML file

[chihangli@…]

The library in the subject does not exists in the 3 servers that MacPort was trying to contact and therefore failed the installation. The latest version there on tried servers all bearing names like *darwin_12x86* but not *darwin_13x86*.

Below is the exact screen capture of the error msg:

~ $ sudo port clean --all libdvdnav
Password:
Sorry, try again.
Password:
--->  Cleaning libdvdnav
~ $ sudo port install libdvdnav
--->  Computing dependencies for libdvdnav
--->  Fetching archive for libdvdnav
Warning: Your DNS servers incorrectly claim to know the address of nonexistent hosts. This may cause checksum mismatches for some ports.
--->  Attempting to fetch libdvdnav-4.1.3_0.darwin_13.x86_64.tbz2 from http://packages.macports.org/libdvdnav
--->  Attempting to fetch libdvdnav-4.1.3_0.darwin_13.x86_64.tbz2 from http://mse.uk.packages.macports.org/sites/packages.macports.org/libdvdnav
--->  Attempting to fetch libdvdnav-4.1.3_0.darwin_13.x86_64.tbz2 from http://lil.fr.packages.macports.org/libdvdnav
--->  Fetching distfiles for libdvdnav
--->  Attempting to fetch libdvdnav-4.1.3.tar.bz2 from http://www3.mplayerhq.hu/MPlayer/releases/dvdnav/
--->  Verifying checksums for libdvdnav
Error: Checksum (md5) mismatch for libdvdnav-4.1.3.tar.bz2
Error: Checksum (sha1) mismatch for libdvdnav-4.1.3.tar.bz2
Error: Checksum (rmd160) mismatch for libdvdnav-4.1.3.tar.bz2
***
The non-matching file appears to be HTML. See this page for possible reasons
for the checksum mismatch:
<https://trac.macports.org/wiki/MisbehavingServers>
***
The file has been moved to: /opt/local/var/macports/distfiles/libdvdnav/libdvdnav-4.1.3.tar.bz2.html
Error: org.macports.checksum for port libdvdnav returned: Unable to verify file checksums
Please see the log file for port libdvdnav for details:
    /opt/local/var/macports/logs/_opt_local_var_macports_sources_rsync.macports.org_release_tarballs_ports_devel_libdvdnav/libdvdnav/main.log
To report a bug, follow the instructions in the guide:
    http://guide.macports.org/#project.tickets
Error: Processing of port libdvdnav failed

[chihangli@…]

Sorry for the formatting of the captured text. Editing the description after the ticket has been open doesn't seem to be possible.

[ryandesign (Ryan Carsten Schmidt)]

A binary package not existing on our packages servers is not a problem. (In fact, we have no binary packages for any ports for Mavericks yet.) In that case, MacPorts will try to download and build the source on your machine. That's where the real problem is: MacPorts tried to download the source code, but it got an HTML file instead. Did you read the MisbehavingServers page to which you were referred by the error message? What does the HTML file libdvdnav-4.1.3.tar.bz2.html contain?

[chihangli@…]

Replying to ryandesign@…:

Thank you ryandesign, I didn't check this ticket often and didn't notice your reply as I thought I would get email notification.

Anyway, I didn't look at the file downloaded, it is indeed an jump html file that onload has a script to redirect me to www3.mplayerhq.h with some additional parameters.

As for the MisbehavingServer, I did check my laptop DNS setting, it is using the google DNS (208.67.222.222 & *.220) and opendns (8.8.8.8 & 8.8.2.2).

[ryandesign (Ryan Carsten Schmidt)]

Yes, you should have received email notification.

Google DNS (8.8.8.8 and 8.8.4.4) behaves properly. But by default, OpenDNS (208.67.222.222 and 208.67.220.220) behaves in the broken manner described by MisbehavingServers so I cannot recommend its use.

I have confirmed that the server address www3.mplayerhq.hu no longer resolves to an IP address and should therefore be removed from the libdvdnav port. I'll check if we need to update any other ports as well.

[ryandesign (Ryan Carsten Schmidt)]

Fixed libdvdnav in r113573. No other ports were affected.

[chihangli@…]

Thank you Ryandesign,

VLC now installed without problem.

With regard to your comment about Google DNS behaving poorly, do you have any recommendations as to which DNS is better? I too find Google's DNS slow compared to openDNS. So I put openDNS first in my setting. Any good DNS recommendations will be appreciated.

Joseph

[ryandesign (Ryan Carsten Schmidt)]

Google DNS does behave correctly; I use it. OpenDNS does not.

[ryandesign (Ryan Carsten Schmidt)]

It may be possible to make OpenDNS behave in an RFC-compliant manner by changing some OpenDNS settings. You'll have to ask them.