Same here.
Michael
On 23.1.13 14:17, Marcel Reutegger wrote:
nope, unless I'm doing something wrong...
marcel@LinuxMint ~/devel/jackrabbit $ svn up
Updating '.':
U check-release.sh
Updated to revision 1437399.
marcel@LinuxMint ~/devel/jackrabbit $ sh check-release.sh 2.5.3
d143e1f4e87ee193b9c2a2f1c1092d33311878af
[INFO] ------------------------------------------------------------------------
[INFO] DOWNLOAD RELEASE CANDIDATE
[INFO] ------------------------------------------------------------------------
[INFO]
[INFO] Downloading release candidate, please wait...
[INFO] Release downloaded.
[INFO]
[INFO] ------------------------------------------------------------------------
[INFO] CHECK SIGNATURES AND DIGESTS
[INFO] ------------------------------------------------------------------------
[INFO]
[INFO] Step 1. Check release cheksum
[ERROR] Release checksum does not match provided checksum!
marcel@LinuxMint ~/devel/jackrabbit $
regards
marcel
-----Original Message-----
From: Jukka Zitting [mailto:jukka.zitt...@gmail.com]
Sent: Mittwoch, 23. Januar 2013 14:25
To: Jackrabbit Developers
Subject: Re: [VOTE] Release Apache Jackrabbit 2.5.3
Hi,
On Wed, Jan 23, 2013 at 3:16 PM, Marcel Reutegger
<mreut...@adobe.com> wrote:
and it contains a CR/LF at the end.
could this be the reason why the script thinks the hash
doesn't match?
Yes, that's most likely the reason. I just adjusted the
check-release.sh script to ignore end-of-lines. Does that help?
BR,
Jukka Zitting
