[prev in list] [next in list] [prev in thread] [next in thread] 

List:       wink-dev
Subject:    RE: Unable to add public key to https://svn.apache.org/repos/asf/maven/project/KEYS
From:       "Snitkovsky, Martin" <martin.snitkovsky () hp ! com>
Date:       2009-07-30 13:22:25
Message-ID: 2C60AA1B234AC84D8486DC6BA56275FC4980E1412F () GVW1163EXB ! americas ! hpqcorp ! net
[Download RAW message or body]

I have just figured that out :)   Thanks Dan. 

All, Please ignore this e-mail (just trying to figure out how to do release) 

-----Original Message-----
From: Daniel Kulp [mailto:dkulp@apache.org] 
Sent: Thursday, July 30, 2009 3:56 PM
To: infrastructure@apache.org
Cc: Snitkovsky, Martin; repository@apache.org; wink-dev@incubator.apache.org
Subject: Re: Unable to add public key to https://svn.apache.org/repos/asf/maven/project/KEYS

On Thu July 30 2009 8:48:07 am Snitkovsky, Martin wrote:
> Hi,
>
> We are planning to release Wink project with Maven.
>
> Based on http://maven.apache.org/developers/release/releasing.html, release
> manager should add his public key to
> https://svn.apache.org/repos/asf/maven/project/KEYS

Uh...  no.   That KEYS file is for the Maven project.   Only Maven release 
managers should be adding keys there.

You need to create one in your own project someplace.   (usually 
wink/trunk/KEYS so it gets tagged with releases, but some just put it in 
wink/KEYS)

It would need to be copied to the dist directory as part of the release as 
well.

Dan


>
> I was trying to do it, but failed with:
>
>
>
> svn: Commit failed (details follow):
>
> svn: CHECKOUT of '/repos/asf/!svn/ver/782204/maven/project/KEYS': 403
> Forbidden
>
>
>
> Do I need special permissions to be granted?
>
>
>
> martin

-- 
Daniel Kulp
dkulp@apache.org
http://www.dankulp.com/blog


[prev in list] [next in list] [prev in thread] [next in thread]