-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On 2/26/10 12:48 PM, Daniel Lietha wrote: > Hi, > I am having problems to install ccp4 with fink on a Macbook pro (15'' Core 2 > Duo de Intel a 2,8 GHz) running OS 10.6.2. I already installed coot with > fink, so fink seems ok. > > when running "fink install ccp4" (after selfupdate and so) I am getting the > following error: > > ---------- > The checksum of the file ccp4-6.1.2-core-src.tar.gz of package ccp4-6.1.2-4 > is incorrect. The most > likely cause for this is a corrupted or incomplete download > Expected: c7ad8074668ccb7ae805e850079ce721 > Actual: MD5(bbc72fc9375f1ac3454fa8e81c673ec8) > SHA1(2423178d3877dd44d3671a7eb4d6666de6852cb7) > It is recommended that you download it again. How do you want to proceed? > > (1) Give up > (2) Delete it and download again > (3) Assume it is a partial download and try to continue > (4) Don't download, use existing file > --------------- > > Trying to download again results in the same problem. Should I use option (4)? > Any help appreciated, > Dan > **NOTA DE CONFIDENCIALIDAD** Este correo electrónico, y en su caso los > ficheros adjuntos, pueden contener información protegida para el uso > exclusivo de su destinatario. Se prohíbe la distribución, reproducción o > cualquier otro tipo de transmisión por parte de otra persona que no sea el > destinatario. Si usted recibe por error este correo, se ruega comunicarlo al > remitente y borrar el mensaje recibido. > **CONFIDENTIALITY NOTICE** This email communication and any attachments may > contain confidential and privileged information for the sole use of the > designated recipient named above. Distribution, reproduction or any other use > of this transmission by any party other than the intended recipient is > prohibited. If you are not the intended recipient please contact the sender > and delete all copies. > > > >
You can probably use option 4), though I've updated the package description to use the right checksum (hopefully the maintainer won't mind too much). Checksum errors come from two places, normally: 1) The maintainer puts the wrong checksum in--typically this occurs when a package gets updated and the maintainer happens to forget to check that. 2) The upstream developers change the source tarball without putting out a new version number. That appears to be what happened here. - -- Alexander Hansen Fink User Liaison -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.10 (Darwin) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/ iEYEARECAAYFAkuIGiwACgkQB8UpO3rKjQ/31ACgliABQQWdvlYQcGlEvlAVC1pJ vmwAn0nnNRn58aStfVo5jmVKdaiWnn3q =D+Gu -----END PGP SIGNATURE----- ------------------------------------------------------------------------------ Download Intel® Parallel Studio Eval Try the new software tools for yourself. Speed compiling, find bugs proactively, and fine-tune applications for parallel performance. See why Intel Parallel Studio got high marks during beta. http://p.sf.net/sfu/intel-sw-dev _______________________________________________ Fink-users mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/fink-users
