and it contains a CR/LF at the end. could this be the reason why the script thinks the hash doesn't match?
regards marcel > -----Original Message----- > From: Marcel Reutegger [mailto:mreut...@adobe.com] > Sent: Mittwoch, 23. Januar 2013 14:10 > To: dev@jackrabbit.apache.org > Subject: RE: [VOTE] Release Apache Jackrabbit 2.5.3 > > d143e1f4e87ee193b9c2a2f1c1092d33311878af > > looks correct to me... > > regards > marcel > > > -----Original Message----- > > From: Jukka Zitting [mailto:jukka.zitt...@gmail.com] > > Sent: Mittwoch, 23. Januar 2013 13:41 > > To: Jackrabbit Developers > > Subject: Re: [VOTE] Release Apache Jackrabbit 2.5.3 > > > > Hi, > > > > On Wed, Jan 23, 2013 at 1:35 PM, Michael Dürig <mdue...@apache.org> > > wrote: > > > [INFO] Step 1. Check release cheksum > > > [ERROR] Release checksum does not match provided checksum! > > > > Hmm, what do you have in > > target/jackrabbit-staging-*/2.3.5/jackrabbit-2.5.3-src.zip.sha after > > getting the above error? > > > > BR, > > > > Jukka Zitting
