Carsten, Which key did you use to sign with. x43543-2:trunk ieb$ gpg --verify /tmp/sling-staging/066/org/apache/sling/org.apache.sling.jcr.api/2.0.6/org.apache.sling.jcr.api-2.0.6.jar.asc gpg: Signature made Tue 26 Jan 08:21:33 2010 GMT using RSA key ID F2F27A06 gpg: Can't check signature: public key not found
I cant find that key locally and its doesn't appear at pgp.mit.edu (AFAICT) Search results for 'org cziegeler apache' Type bits/keyID Date User ID pub 1024D/FA32C576 2003-09-26 Carsten Ziegeler <cziege...@apache.org> pub 1024D/E41EDC7E 2003-09-26 Carsten Ziegeler <cziege...@apache.org> pub 1024D/F6E0A8F8 2001-06-06 Carsten Ziegeler <cziege...@apache.org> Ian On 26 Jan 2010, at 08:31, Carsten Ziegeler wrote: > Hi, > > > this is an important fix release for the 2.0.4 release of the JCR API. > It fixes the exported package version and sets it to 2.0.2 (our first > release). > The 2.0.4 release has been important as it removed the JSR 170 api from > the bundle - this makes it independent from tje JCR version. > Unfortunately this release also increased the exported package version > of the sling api to 2.0.4. Bundles now depending on this version require > the 2.0.4 version of the Sling api package (at least the sling bundles > do as the import statements contain the patch version). > Therefore I cut the 2.0.6 release which is the same as the 2.0.4 release > except that it fixes the exported package version. > > Staging repository: > https://repository.apache.org/content/repositories/sling-staging-066/ > > You can use this UNIX script to download the release and verify the > signatures: > http://svn.apache.org/repos/asf/sling/trunk/check_staged_release.sh > > Usage: > sh check_staged_release.sh 066 /tmp/sling-staging > > Please vote to approve this release: > > [ ] +1 Approve the release > [ ] 0 Don't care > [ ] -1 Don't release, because ... > > This vote will be open for 72 hours. > > Regards > Carsten > -- > Carsten Ziegeler > cziege...@apache.org
