You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@cocoon.apache.org by Jeroen Reijn <j....@onehippo.com> on 2008/06/25 12:20:55 UTC
Import my key into the KEYS file
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.
Can somebody help me out?
Regards,
Jeroen
[1]http://www.apache.org/dev/release-signing.html#signing-basics
Re: Import my key into the KEYS file
Posted by Jeroen Reijn <j....@onehippo.com>.
Gregorz,
I'm not really sure if I have the karma to do that as well, but I just
changed the one in
http://svn.apache.org/repos/asf/cocoon/trunk/commons/KEYS
Did you copy it from there, or is the KEYS file in the dist folder
located elsewhere in the SVN?
Regards,
Jeroen
David Crossley wrote:
> Grzegorz Kossakowski wrote:
>> David Crossley pisze:
>>> 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.
>> David, could elaborate on this KEYS issue?
>>
>> Here is the output of svn st:
>> [gkossakowski@minotaur /www/www.apache.org/dist/cocoon]$ svn st
>> ? bricks-cms
>> ? 2.2
>> ? subprojects
>> ? KEYS
>> ? events/gt2004
>>
>>
>> It is clear that KEYS is not maintained by SVN. Should this be changed?
>
> Yes, as said above.
>
> Thanks for helping with such stuff.
>
> When faced with issues like this, i often look at
> how other projects have done it. Primarily i follow
> Apache HTTP Server, being the original project, and
> therefore most likely doing the proper stuff. So see:
> http://svn.apache.org/repos/asf/httpd/site/trunk/dist/
> Also APR because lots of old ASF hands there. So see:
> http://svn.apache.org/repos/asf/apr/site/trunk/dist
> Apache Forrest will also give some clues, as when i
> set it up as a top-level project i reviewed many other
> existing practices.
>
> There are also notes about KEYS and such in the
> "Guide for new committers" and "Release signing"
> http://apache.org/dev/
>
> Also Henk's guide says to put your own key at
> people.apache.org:~/.pgpkey
>
>> As for now I'm going to just replace this file with newer version I'm going
>> to commit right now.
>
> That is fine as a temporary measure, and will bring that
> static file up-to-date.
>
> -David
Re: Import my key into the KEYS file
Posted by David Crossley <cr...@apache.org>.
Grzegorz Kossakowski wrote:
> David Crossley pisze:
> >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.
>
> David, could elaborate on this KEYS issue?
>
> Here is the output of svn st:
> [gkossakowski@minotaur /www/www.apache.org/dist/cocoon]$ svn st
> ? bricks-cms
> ? 2.2
> ? subprojects
> ? KEYS
> ? events/gt2004
>
>
> It is clear that KEYS is not maintained by SVN. Should this be changed?
Yes, as said above.
Thanks for helping with such stuff.
When faced with issues like this, i often look at
how other projects have done it. Primarily i follow
Apache HTTP Server, being the original project, and
therefore most likely doing the proper stuff. So see:
http://svn.apache.org/repos/asf/httpd/site/trunk/dist/
Also APR because lots of old ASF hands there. So see:
http://svn.apache.org/repos/asf/apr/site/trunk/dist
Apache Forrest will also give some clues, as when i
set it up as a top-level project i reviewed many other
existing practices.
There are also notes about KEYS and such in the
"Guide for new committers" and "Release signing"
http://apache.org/dev/
Also Henk's guide says to put your own key at
people.apache.org:~/.pgpkey
> As for now I'm going to just replace this file with newer version I'm going
> to commit right now.
That is fine as a temporary measure, and will bring that
static file up-to-date.
-David
Re: Import my key into the KEYS file
Posted by Grzegorz Kossakowski <gr...@tuffmail.com>.
David Crossley pisze:
> 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.
David, could elaborate on this KEYS issue?
Here is the output of svn st:
[gkossakowski@minotaur /www/www.apache.org/dist/cocoon]$ svn st
? bricks-cms
? 2.2
? subprojects
? KEYS
? events/gt2004
It is clear that KEYS is not maintained by SVN. Should this be changed?
As for now I'm going to just replace this file with newer version I'm going to commit right now.
--
Grzegorz Kossakowski
Re: Import my key into the KEYS file
Posted by Jeroen Reijn <j....@onehippo.com>.
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
>>>
Re: Import my key into the KEYS file
Posted by David Crossley <cr...@apache.org>.
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
> >
Re: Import my key into the KEYS file
Posted by Jeroen Reijn <j....@onehippo.com>.
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?
Regards,
Jeroen
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
>
Re: Import my key into the KEYS file
Posted by Reinhard Pötz <re...@apache.org>.
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
--
Reinhard Pötz Managing Director, {Indoqa} GmbH
http://www.indoqa.com/en/people/reinhard.poetz/
Member of the Apache Software Foundation
Apache Cocoon Committer, PMC member reinhard@apache.org
________________________________________________________________________