popt-1.16 checksum match fails

[dustin.holden@…]

While trying to install gimp, a dependency "popt" fails its MD5 checksum. The HTML error given typically means the checksum is no longer available to check against.

The error code below was given:

--->  Verifying checksum(s) for popt
Error: Checksum (md5) mismatch for popt-1.16.tar.gz
Error: Checksum (sha1) mismatch for popt-1.16.tar.gz
Error: Checksum (rmd160) mismatch for popt-1.16.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
Error: Failed to install popt

[dustin.holden@…]

Cc Me!

[jmroot (Joshua Root)]

Please remember to fill in the Port field and cc the maintainer. You do not need to be in cc when you are the reporter. As per the FAQ, you need to indicate which mirror your file was downloaded from.

[curt@…]

This is happening because rpm5.org is no longer in the DNS. I worked around by doing the following

cd /opt/local/var/macports/distfiles/popt sudo wget ​ftp://anduin.linuxfromscratch.org/BLFS/svn/p/popt-1.16.tar.gz sudo port install popt

[curt@…]

Cc Me!

[cyberhomie@…]

Cc Me!

[cyberhomie@…]

I am having the same issue as Dustin except I am trying to install git-core (sudo port install git-core) and I could really use a hand. I am unsure of the mirror that it was downloaded from. I looked at the log and I am not seeing that indicated anywhere.

It does seem that rpm5.org is indeed down. I tried Curt's workaround but the last command gives me the same error as I do when trying to install it the regular way. Any other suggestions for workarounds?

Thanks

[curt@…]

@cyberhomie:

Are you getting the error while building popt as a dependency for git-core or while trying to install some other package? Also, are you on 10.5 or 10.6?

The workaround worked for me because once port(1) sees the souce tarball in the correct location with the correct checksum, it doesn't ask any more where it came from, it just assumes it was already downloaded. On 10.5 the "correct location" is /opt/local/var/macports/distfiles/popt. I think it's different on 10.6 but I don't have a machine handy to check. However, since rpm5 is down (and not just returning 404 or something), if you have a "helpful" DNS provider that redirects all invalid URLs to some ad-filled page, port(1) will save that output as popt.tar.gz and then complain about checksums not matching. So you could do this to find out where to save popt.tar.gz.

sudo port install popt # generates error
find /opt/local -name popt.tar.gz | xargs dirname

[curt@…]

Sorry, last should probably be

find /opt/local -name popt\*.tar.gz | xargs dirname

I think port(1) saves sources with the version number

[cyberhomie@…]

Replying to curt@…:

@cyberhomie:

Are you getting the error while building popt as a dependency for git-core or while trying to install some other package? Also, are you on 10.5 or 10.6?

The workaround worked for me because once port(1) sees the souce tarball in the correct location with the correct checksum, it doesn't ask any more where it came from, it just assumes it was already downloaded. On 10.5 the "correct location" is /opt/local/var/macports/distfiles/popt. I think it's different on 10.6 but I don't have a machine handy to check. However, since rpm5 is down (and not just returning 404 or something), if you have a "helpful" DNS provider that redirects all invalid URLs to some ad-filled page, port(1) will save that output as popt.tar.gz and then complain about checksums not matching. So you could do this to find out where to save popt.tar.gz.

sudo port install popt # generates error
find /opt/local -name popt.tar.gz | xargs dirname

Yes, I am getting the error while building popt as a dependency for get-core. I am using 10.6.7

I used the sudo port install popt # generates error to find the directory and reran the wget command and tried the install of popt again and it worked. I then reran the git-core install command and it seems to be going through now. Thanks for the assistance!

[curt@…]

rpm5.org is working for me now. This could probably be closed out by someone with the necessary privileges.