www-repository mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Gilles Scokart" <gscok...@gmail.com>
Subject Re: Bad checksum
Date Thu, 22 May 2008 06:40:02 GMT
http://repo1.maven.org/maven2/org/apache/ws/commons/axiom/axiom-dom/1.2.7/axiom-dom-1.2.7.pom.md5
and
http://people.apache.org/repo/m2-ibiblio-rsync-repository/org/apache/ws/commons/axiom/axiom-dom/1.2.7/axiom-dom-1.2.7.pom.md5

are still different.  How can we fix that?

Gilles


2008/5/15 Gilles Scokart <gscokart@gmail.com>:
> It looks like other version have a problem.
>
> An ivy user reported a problem with
> http://repo1.maven.org/maven2/org/apache/ws/commons/axiom/axiom-dom/1.2.7/axiom-dom-1.2.7.pom:
> invalid md5
>
> However, /www/people.apache.org/repo/m2-ibiblio-rsync-repository/org/apache/ws/commons/axiom/axiom-dom/1.2.7/axiom-dom-1.2.7.pom/md5
> is right (I guess fixed the 24 April).
>
> So it seems that there is a synchronization issue.
>
> Also, it seems that others might be wrong :
>> find . -name *.md5 -exec grep -H \\\\ {} \;
> ./axiom/axiom-api/1.2.6/axiom-api-1.2.6-sources.jar.md5:\40e578af663faf4fed225f14479372bb
> ./axiom/axiom-api/1.2.6/axiom-api-1.2.6.jar.md5:\9a0dc979a3bbc396c277d8d0ae72cc76
> ./axiom/axiom-api/1.2.6/axiom-api-1.2.6.pom.md5:\bf0b2cf514258ab525a21361cffe6623
> ./axiom/axiom-impl/1.2.6/axiom-impl-1.2.6-sources.jar.md5:\afcff7141339374d075f22c59873af49
> ./axiom/axiom-impl/1.2.6/axiom-impl-1.2.6.jar.md5:\3ff4929f96012c99149cb7703b0583e5
> ./axiom/axiom-impl/1.2.6/axiom-impl-1.2.6.pom.md5:\7fa032efce591b1bfdc5fef102dfb199
> ./axiom/axiom-dom/1.2.6/axiom-dom-1.2.6-sources.jar.md5:\cd0e966f591d66ebff9ca55152abf4f2
> ./axiom/axiom-dom/1.2.6/axiom-dom-1.2.6.jar.md5:\cb6bc34666088ac6524dac16c16ed742
> ./axiom/axiom-dom/1.2.6/axiom-dom-1.2.6.pom.md5:\c734049519348c4596a47c62e009bd37
> ./axiom/axiom-tests/1.2.6/axiom-tests-1.2.6-sources.jar.md5:\58ab86863a0faabe2660bbb5c4b89b8a
> ./axiom/axiom-tests/1.2.6/axiom-tests-1.2.6.jar.md5:\fc0be5fcb265af79f854321f7ab609fc
> ./axiom/axiom-tests/1.2.6/axiom-tests-1.2.6.pom.md5:\f5467feaaaab701469bd8bfd7e5c46fa
> ./axiom/axiom/1.2.6/axiom-1.2.6.pom.md5:\da89eec0025c2cd15d479a00aea2f962
> ./schema/XmlSchema/1.4.1/XmlSchema-1.4.1-javadoc.jar.md5:\b789328e7c567d2ecdb498067864f81e
> ./schema/XmlSchema/1.4.1/XmlSchema-1.4.1-sources.jar.md5:\10611b984ee7f70e5a06492d5b842ee9
> ./schema/XmlSchema/1.4.1/XmlSchema-1.4.1.jar.md5:\d7ffd5e6434703eff74345864fe19e05
> ./schema/XmlSchema/1.4.1/XmlSchema-1.4.1.pom.md5:\e7e19e9a501f31b02ba262c3594a5794
>
>
>
> Gilles
>
> ---------- Forwarded message ----------
> From: Marshall Pierce <marshall@genius.com>
> Date: 2008/5/15
> Subject: Overriding a bad checksum
> To: ivy-user@ant.apache.org
>
>
> A handful of packages I'm trying to use have invalid md5 checksums on
> repo1.maven.org, e.g.:
>
> [ivy:resolve]   problem while downloading module descriptor:
> http://repo1.maven.org/maven2/org/apache/ws/commons/axiom/axiom-dom/1.2.7/axiom-dom-1.2.7.pom:
> invalid md5: expected=\7986af8834017fafae425331b9d2dc6f
> computed=7986af8834017fafae425331b9d2dc6f (799ms)
>
> When I check the .md5 file
> (http://repo1.maven.org/maven2/org/apache/ws/commons/axiom/axiom-dom/1.2.7/axiom-dom-1.2.7.jar.md5),
> sure enough, there is a spurious \ at the beginning. Clearly, the file
> is actually valid, since the computed md5 would be the same as the
> expected md5 if it didn't have the \ in front. How can I get the
> resolver to ignore the "bad" md5?
>
> Thanks,
> Marshall Pierce
>
>
>
> 2008/4/24 Davanum Srinivas <davanum@gmail.com>:
>> Fixed all 3. XmlSchema, Axiom, and Neethi
>>
>> thanks,
>> dims
>>
>> On Thu, Apr 24, 2008 at 10:15 AM, Daniel Kulp <daniel.kulp@iona.com> wrote:
>>>
>>>  All of the latest releases from ws-commons have invalid md5 files.   They
>>>  all have a leading \ in the file.
>>>  Example:
>>>  \9d1ff1229a42b8a93fc1db8c349ce830
>>>
>>>  instead of just:
>>>  9d1ff1229a42b8a93fc1db8c349ce830
>>>
>>>  There is something wrong in the script or something that they are using.
>>>  This affects XmlSchema, Axiom, and Neethi at the very least, possibly
>>>  others.  I've sent a note to their dev list.
>>>
>>>
>>>  Dan
>>>
>>>
>>>
>>>
>>>  On Thursday 24 April 2008, Guillaume Nodet wrote:
>>>  > Well, it looks like the error message is wrong and displays twice the
>>>  > local checksum, because looking at the sha1 and md5, they don't match
>>>  > what's the output gives.  But yeah, i suppose the remote checksum of
>>>  > the artifact is wrong.
>>>  >
>>>  > On Thu, Apr 24, 2008 at 12:46 PM, Steve Loughran
>>>  >
>>>  > <steve.loughran@gmail.com> wrote:
>>>  > > Is it the checksum or the artifact that is at fault?
>>>  > >
>>>  > >  On Thu, Apr 24, 2008 at 9:16 AM, Guillaume Nodet <gnodet@gmail.com>
>>>  wrote:
>>>  > >  > It seems xmlschema 1.4 has a bad checksum:
>>>  > >  >
>>>  > >  >  [04:13:29]: Downloading:
>>>  > >  >
>>>  > >  > http://repo1.maven.org/maven2/org/apache/ws/commons/schema/XmlSch
>>>  > >  >ema/1.4/XmlSchema-1.4.jar [04:13:30]: 135K downloaded
>>>  > >  >  [04:13:30]: [WARNING] *** CHECKSUM FAILED - Checksum failed
on
>>>  > >  >  download: local = '1d834baf3843cc538b4b82f5b4085f78e17ddfcc';
>>>  > >  > remote = '1D834BAF3843CC538B4B82F5B4085F78E17DDFCC' - RETRYING
>>>  > >  >
>>>  > >  >  Should it be fixed somehow ?
>>>  > >  >
>>>  > >  >  --
>>>  > >  >  Cheers,
>>>  > >  >  Guillaume Nodet
>>>  > >  >  ------------------------
>>>  > >  >  Blog: http://gnodet.blogspot.com/
>>>
>>>
>>>
>>>  --
>>>  J. Daniel Kulp
>>>  Principal Engineer
>>>  IONA
>>>  P: 781-902-8727    C: 508-380-7194
>>>  daniel.kulp@iona.com
>>>  http://www.dankulp.com/blog
>>>
>>
>>
>>
>> --
>> Davanum Srinivas :: http://davanum.wordpress.com
>>
>
>
>
> --
> Gilles Scokart
>



-- 
Gilles Scokart

Mime
View raw message