Hi Jan,

you are absolutely right: instead of the sha hash the file contained the md5 
hash.
I have corrected it now.
Please check again.

Regards
Rainer

> From: [email protected] [mailto:[email protected]]
> To: [email protected]
> Subject: Re: [VOTE] Release Apache Empire-db 2.4.6 (rc2)
> 
> Hello Rainer,
> 
> how did you create the sha sum? I cant validate its correct:
> 
> [jan ~/tmp] sha1 apache-empire-db-2.4.6-dist.zip
> SHA1 (apache-empire-db-2.4.6-dist.zip) =
> 9d0f4e28334561e15458671b7b093b7b3cc5f9cb
> 
> yours look a little bit short...?
> 
> 
> Which key did you use to create the PGP signature? I can't verify with they
> KEYS file from the website:
> 
> [jan ~/tmp] gpg --verify apache-empire-db-2.4.6-dist.zip.asc
> gpg: Warning: using insecure memory!
> gpg: assuming signed data in 'apache-empire-db-2.4.6-dist.zip'
> gpg: Signature made Mon Jan  9 11:46:48 2017 CET
> gpg:                using RSA key 0279D7D50B5DFB51
> gpg: Can't check signature: No public key
> 
> - jan
> 
> Zitat von Rainer Döbele <[email protected]>:
> 
> > Hi all,
> >
> > Due to an incorrect distribution file I have cancelled rc1 and
> > prepared a second release candidate for version 2.4.6.
> > Please do all check and vote again on this release candidate.
> >
> > A list of all resolved issues for this release can be found here:
> > https://issues.apache.org/jira/browse/EMPIREDB-
> 250?jql=project%20%3D%2
> > 0EMPIREDB%20AND%20fixVersion%20in%20(empire-db-
> 2.4.6%2C%20empire-db-2.
> >
> 4.5)%20ORDER%20BY%20due%20ASC%2C%20priority%20DESC%2C%20create
> d%20ASC
> >
> > Maven staging repository:
> > https://repository.apache.org/content/repositories/orgapacheempire-db-
> > 1004/
> >
> > The distribution files are located here:
> > https://dist.apache.org/repos/dist/dev/empire-db/apache-empire-db-2.4.
> > 6-rc2/
> >
> > The Rat report for the tag is available here:
> > https://dist.apache.org/repos/dist/dev/empire-db/apache-empire-db-2.4.
> > 6-rc2/rat.txt
> >
> > Vote open for 72 hours.
> >
> > [ ] +1
> > [ ] +0
> > [ ] -1
> 
> 

Reply via email to