mesa @7.11 checksum failure

[anwarghuloum@…]

mesa port is not checksumming on download:

$ sudo port install mesa
--->  Computing dependencies for mesa
--->  Fetching archive for mesa
--->  Attempting to fetch mesa-7.11_2+python27.darwin_11.x86_64.tgz from http://packages.macports.org/mesa
--->  Fetching mesa
--->  Verifying checksum(s) for mesa
Error: Checksum (sha1) mismatch for MesaLib-7.11.tar.bz2
Error: Checksum (rmd160) mismatch for MesaLib-7.11.tar.bz2
Error: Checksum (sha256) mismatch for MesaLib-7.11.tar.bz2
Error: Checksum (sha1) mismatch for MesaGLUT-7.11.tar.bz2
Error: Checksum (rmd160) mismatch for MesaGLUT-7.11.tar.bz2
Error: Checksum (sha256) mismatch for MesaGLUT-7.11.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>
***
Error: Target org.macports.checksum returned: Unable to verify file checksums
Log for mesa is at: /opt/local/var/macports/logs/_opt_local_var_macports_sources_rsync.macports.org_release_ports_x11_mesa/mesa/main.log
Error: Status 1 encountered during processing.
To report a bug, see <http://guide.macports.org/#project.tickets>

Livecheck returns a file not found error:

$ sudo port livecheck mesa
Error: cannot check if mesa was updated (The requested URL returned error: 404)

[anwarghuloum@…]

Check master sites in portfile, the files are there. I checked both files in both master sites with a manual shasum and the sha1 hashes match the port file in both cases. The error must be in how port is grabbing the file.

[anwarghuloum@…]

log file for mesa port install attempt

[anwarghuloum@…]

I just noticed that in the log file, port attempts to grab mesa-7.11_2+python27.darwin_11.x86_64.tbz2 from the macports web site, where only mesa-7.11_2+python27.darwin_10.x86_64.tbz2 exists.

[ryandesign@…]

Anything relating to the archive is irrelevant. The error message is about the distfile. What is in the distfile which got downloaded? According to the error message, it is unexpectedly an HTML file.

[anwarghuloum@…]

Turned out to be a firewall issue ... port clean --dist (or --all) resolves the issue getting rid of the stale distfiles. Thanks for the clue!