www-repository mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Steve Loughran" <steve.lough...@gmail.com>
Subject bad checksums?
Date Mon, 20 Mar 2006 13:49:02 GMT
I got some checksum failure warnings today:

[m2:libraries] Downloading:
ws-commons/axiom/1.0-SNAPSHOT/axiom-1.0-SNAPSHOT.jar[m2:libraries]
[WARNING] Unable to get resource from repository remote
(http://ibiblio.org/maven2)
[m2:libraries] Downloading: ws-commons/jars/axiom-1.0-SNAPSHOT.jar
[m2:libraries] Transferring 188K
[m2:libraries] [WARNING] *** CHECKSUM FAILED - Checksum failed on
download: local = 'ea78ab20f48a69ffbe508be54b93511475d0f6b5'; remote =
'c8bb3e3249b4b43a591de0358be83cf2e1401538' - RETRYING
[m2:libraries] Downloading: ws-commons/jars/axiom-1.0-SNAPSHOT.jar
[m2:libraries] Transferring 188K
[m2:libraries] [WARNING] *** CHECKSUM FAILED - Checksum failed on
download: local = 'ea78ab20f48a69ffbe508be54b93511475d0f6b5'; remote =
'c8bb3e3249b4b43a591de0358be83cf2e1401538' - IGNORING

Putting aside the fact that there is either a repository or a
transport problem (like a bad proxy), should our apps really be just
warning about a checksum failure? I'd expected a checksum mismatch to
react in a strict download failure. As it is, there are now bad files
in my local cache.

Mime
View raw message