libidn 1.20 checksum mismatch

[soriyath@…]

[Users/soriyath] > install -d libidn
--->  Computing dependencies for libidn
--->  Verifying checksum(s) for libidn
Error: Checksum (md5) mismatch for libidn-1.20.tar.gz
Error: Checksum (sha1) mismatch for libidn-1.20.tar.gz
Error: Checksum (rmd160) mismatch for libidn-1.20.tar.gz
***
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 libidn is at: /opt/local/var/macports/logs/_opt_local_var_macports_sources_rsync.macports.org_release_ports_mail_libidn/main.log
Error: Status 1 encountered during processing.
To report a bug, see <http://guide.macports.org/#project.tickets>
[Users/soriyath] > install -df libidn
--->  Computing dependencies for libidn
--->  Verifying checksum(s) for libidn
Error: Checksum (md5) mismatch for libidn-1.20.tar.gz
Error: Checksum (sha1) mismatch for libidn-1.20.tar.gz
Error: Checksum (rmd160) mismatch for libidn-1.20.tar.gz
***
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 libidn is at: /opt/local/var/macports/logs/_opt_local_var_macports_sources_rsync.macports.org_release_ports_mail_libidn/main.log
Error: Status 1 encountered during processing.
To report a bug, see <http://guide.macports.org/#project.tickets>

[macsforever2000@…]

Please read the FAQ on checksum errors. You did not provide the download mirror. It checksums just fine for me.

[ryandesign@…]

Have you been able to resolve this issue?

[olaf@…]

Replying to ryandesign@…:

Have you been able to resolve this issue?

I don't see an issue:

$ sudo port -d checksum libidn
...
--->  Verifying checksum(s) for libidn
DEBUG: checksum phase started at Mon Apr 25 14:36:43 CEST 2011
DEBUG: Executing org.macports.checksum (libidn)
--->  Checksumming libidn-1.20.tar.gz
DEBUG: Correct (md5) checksum for libidn-1.20.tar.gz
DEBUG: Correct (sha1) checksum for libidn-1.20.tar.gz
DEBUG: Correct (rmd160) checksum for libidn-1.20.tar.gz

[ryandesign@…]

Right; I don't either. My remark was meant for the person who reported the issue.

[soriyath@…]

Hi,

I just tried again. I still have the same problem. Here's the log when I try to check the checksum :

soriyath@MacBookPro: ~ $  sudo port -d checksum libidn
DEBUG: Changing to port directory: /opt/local/var/macports/sources/rsync.macports.org/release/ports/mail/libidn
DEBUG: OS darwin/10.7.0 (Mac OS X 10.6) arch i386
DEBUG: org.macports.load registered provides 'load', a pre-existing procedure. Target override will not be provided
DEBUG: org.macports.unload registered provides 'unload', a pre-existing procedure. Target override will not be provided
DEBUG: org.macports.distfiles registered provides 'distfiles', a pre-existing procedure. Target override will not be provided
DEBUG: adding the default universal variant
DEBUG: Reading variant descriptions from /opt/local/var/macports/sources/rsync.macports.org/release/ports/_resources/port1.0/variant_descriptions.conf
DEBUG: Starting logging for libidn
DEBUG: Executing org.macports.main (libidn)
DEBUG: Skipping completed org.macports.fetch (libidn)
--->  Verifying checksum(s) for libidn
DEBUG: checksum phase started at Fri Apr 29 15:20:03 CEST 2011
DEBUG: Executing org.macports.checksum (libidn)
--->  Checksumming libidn-1.20.tar.gz
Error: Checksum (md5) mismatch for libidn-1.20.tar.gz
Portfile checksum: libidn-1.20.tar.gz md5 03996d474a696e59fdddbee87fc9519c
Distfile checksum: libidn-1.20.tar.gz md5 ecfd2adf907cd4089eedbca7811f8e21
Error: Checksum (sha1) mismatch for libidn-1.20.tar.gz
Portfile checksum: libidn-1.20.tar.gz sha1 2518486487c275b9d6f133b4688318b951af1580
Distfile checksum: libidn-1.20.tar.gz sha1 fc746fbfa4e2d695c6f0ed306b2902e2f916be4a
Error: Checksum (rmd160) mismatch for libidn-1.20.tar.gz
Portfile checksum: libidn-1.20.tar.gz rmd160 a84eeacbdf9ca04d8fe0dab7bd3a6265f8d4443a
Distfile checksum: libidn-1.20.tar.gz rmd160 76eca171b3b4aa5713f1c7007a5c065f14dcfe88
The correct checksum line may be:
checksums           md5     ecfd2adf907cd4089eedbca7811f8e21 \
                    sha1    fc746fbfa4e2d695c6f0ed306b2902e2f916be4a \
                    rmd160  76eca171b3b4aa5713f1c7007a5c065f14dcfe88
***
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
DEBUG: Backtrace: Unable to verify file checksums
    while executing
"$procedure $targetname"
Warning: the following items did not execute (for libidn): org.macports.checksum
Log for libidn is at: /opt/local/var/macports/logs/_opt_local_var_macports_sources_rsync.macports.org_release_ports_mail_libidn/main.log
Error: Status 1 encountered during processing.
To report a bug, see <http://guide.macports.org/#project.tickets>

[ryandesign@…]

Right, and what is in that HTML file? (/opt/local/var/macports/distfiles/libidn/libidn-1.20.tar.gz) What server did this file come from? Did you read FAQ? Did you read MisbehavingServers?

Also please use WikiFormatting when pasting terminal output into a ticket.

[soriyath@…]

I tried again and it works. No idea what went wrong

[ryandesign@…]

I checked all the http servers offering the libidn distfile (as listed by "port distfiles libidn"), and found all of them to be online, except our South Korean mirror. If that happened to be the server MacPorts chose when you downloaded the distfile 6 weeks ago, and if your DNS server is "helpful" (see MisbehavingServers), then that would explain the error you received. I've emailed the admin of that mirror to let them know the server is offline.

In any case, glad you got it working. If you ever find out what server it was that had the problem, let us know.

[ryandesign@…]

The South Korean mirror experienced a hardware failure and is offline for awhile so I removed it from the global mirror list in r78989. We can add it back in later when it comes back up.