How to fire a new ticket? and there is a checksum error in Python25.
Jin Hyung Park
jenix at jinhyung.org
Thu Nov 30 18:48:51 PST 2006
Hello. I'm Park, Jin Hyung.
My system is Powerbook G4 1.5Ghz with Tiger 10.4.8
(Darwin Cocoa.local 8.8.0 Darwin Kernel Version 8.8.0: Fri Sep 8
17:18:57 PDT 2006; root:xnu-792.12.6.obj~1/RELEASE_PPC Power Macintosh
powerpc)
When I tried to install python25 in this morning, I got an error
related with checksum
---------------------------------------------------------------------------
---> Python-2.5.tar.bz2 doesn't seem to exist in
/opt/local/var/db/dports/distfiles/python25
---> Attempting to fetch Python-2.5.tar.bz2 from
http://www.python.org/ftp/python/2.5
% Total % Received % Xferd Average Speed Time Time Time Current
Dload Upload Total Spent Left Speed
100 9137k 100 9137k 0 0 99k 0 0:01:31 0:01:31 --:--:-- 88463
---> Verifying checksum(s) for python25
DEBUG: Executing com.apple.checksum (python25)
---> Checksumming Python-2.5.tar.bz2
Error: Checksum (sha1) mismatch for Python-2.5.tar.bz2
Portfile checksum: Python-2.5.tar.bz2 sha1
98ce9346cc4a7ef4621ecdcfc3957d595d97a078
Distfile checksum: Python-2.5.tar.bz2 sha1
fa24649cfd5db305f16d79aba8776c332d76a672
Error: Checksum (rmd160) mismatch for Python-2.5.tar.bz2
Portfile checksum: Python-2.5.tar.bz2 rmd160
f6977a6c3d3ca54c27ad9270918237a7e6521d0b
Distfile checksum: Python-2.5.tar.bz2 rmd160
67c42f1d8cfe61b8f2f5812014a9739ff21af734
Error: Target com.apple.checksum returned: Unable to verify file checksums
Warning: the following items did not execute (for python25):
com.apple.activate com.apple.extract com.apple.checksum
com.apple.patch com.apple.configure com.apple.build com.apple.destroot
com.apple.archive com.apple.install
Error: Status 1 encountered during processing.
Cocoa:/opt/local/var/db/dports/sources/rsync.rsync.darwinports.org_dpupdate_dports/lang/python25
jenix$
---------------------------------------------------------------------------
I had tried to fire a new bug ticket in MacPorts Trac, but I couldn't do that,
So, I mail this problem to macports-dev. is it a right way to report a bug?
More information about the macports-dev
mailing list