Thanks David!
Regards,
Jeroen
David Crossley wrote:
Jeroen Reijn wrote:
Thanks Carsten!
I'll give it a try. If found this message, but it was a but inclear, but
after reading it 3 times.. I get it. I'll give it a go. Once I commit it
into SVN will it also appear on the /dist/ or is SVN the only place it
has to go in?
That KEYS file is a separate one to that at the /dist/ directory.
Most of the files there are in SVN at
https://svn.apache.org/repos/asf/cocoon/site/mirrors/
but not the KEYS file. It should be, and be kept synchonised
with the other one.
Probably need to then do:
ssh people.apache.org
cd /x1/www/www.apache.org/dist/cocoon
svn up
When verifying, consider the rsync delay:
http://apache.org/dev/project-site.html
-David
Reinhard P?tz wrote:
Jeroen Reijn wrote:
Hi all,
I uploaded the Cocoon 2.1.11 jars a couple of weeks ago into the m1
synch repository using the script from SVN. It turned out that when I
ran the script it did not create .asc files. As a complete newbie to
this kind of thing, I got a nice email from the repository team that
told me I had to create these specific files. I read through the FAQ
and release signing[1] documentation, but the thing that I'm stuck at
is how to import my public pgp key to the cocoon KEYS file.
Jeroen,
https://svn.eu.apache.org/repos/asf/cocoon/trunk/commons/KEYS contains
instructions how this can be done:
Developers:
pgp -kxa <your name> and append it to this file.
(pgpk -ll <your name> && pgpk -xa <your name>) >> this file.
(gpg --list-sigs <your name>
&& gpg --armor --export <your name>) >> this file.
HTH
