[MacPorts] #13513: python25 persistent checksum mismatch

[MacPorts]

#13513: python25 persistent checksum mismatch
-------------------------------+--------------------------------------------
  Reporter:  perfgeek at mac.com  |       Owner:  mww at macports.org        
      Type:  defect            |      Status:  closed                  
  Priority:  Normal            |   Milestone:  Port Bugs               
 Component:  ports             |     Version:  1.5.2                   
Resolution:  worksforme        |    Keywords:  python checksum mismatch
-------------------------------+--------------------------------------------
Comment (by perfgeek at mac.com):

 Hopefully this will format correctly...

 {{{
 bash-3.2$ sudo port clean --all python25
 --->  Cleaning python25
 bash-3.2$ sudo port install python25
 --->  Fetching python25
 --->  Attempting to fetch Python-2.5.1.tar.bz2 from
 http://www.python.org//ftp/python/2.5.1/
 --->  Verifying checksum(s) for python25
 Error: Checksum (md5) mismatch for Python-2.5.1.tar.bz2
 Error: Checksum (sha1) mismatch for Python-2.5.1.tar.bz2
 Error: Checksum (rmd160) mismatch for Python-2.5.1.tar.bz2
 Error: Target org.macports.checksum returned: Unable to verify file
 checksums
 Error: Status 1 encountered during processing.
 }}}

 I take it then that the checksums I reported are indeed incorrect. Where
 would I find the Portfile to make sure that my Portfile has the correct
 checksums?

 As for proxies, I've no clue - my ISP may indeed be running a transparant
 one on me, but I don't have any (known) of my own.  Mac, router,
 dlsmodem... big bad internet...

 I tried downloading the tar.bz2 by hand, and it wouldn't even unzip:

 {{{
 [rick:~] perfgeek% bunzip2 Python-2.5.1.tar.bz2

 bunzip2: Data integrity error when decompressing.
         Input file = Python-2.5.1.tar.bz2, output file = Python-2.5.1.tar

 It is possible that the compressed file(s) have become corrupted.
 You can use the -tvv option to test integrity of such files.

 You can use the `bzip2recover' program to attempt to recover
 data from undamaged sections of corrupted files.

 bunzip2: Deleting output file Python-2.5.1.tar, if it exists.
 }}}

 So, on a hunch/whim, I tried grabbing the file to netperf.org, and then
 pulling it down to my system via ssh, and that file would untar.  I've not
 gone so far as to try replacing the one port downloaded with it yet.

 {{{
 [rick:~] perfgeek% cmp Python-2.5.1.tar.bz2 Python-2.5.1.tar.bz2.httped
 Python-2.5.1.tar.bz2 Python-2.5.1.tar.bz2.httped differ: char 1146753,
 line 4963
 }}}

 So, the hypothesis of a proxy problem is plausible, or shudder - a data
 pattern induced error somewhere along the way.  It cannot be a "plain"
 proxy problem though, because when I arranged to pull the file via http
 from netperf.org, that one compared just fine with the one I ssh'd from
 netperf.org.

-- 
Ticket URL: <http://trac.macosforge.org/projects/macports/ticket/13513#comment:8>
MacPorts </projects/macports>
Ports system for Mac OS