I know that there is an svn command I can use to delete the public key so we 
can file the new one. I could scour the lists for the command, but...

svn rm 
https://repos.apache.org/private/documents/iclas/__keys__/E22F7D9D0428D1C4B38DCA7BF6665E960DA9AF2A

> Begin forwarded message:
> 
> From: Craig Russell <[email protected]>
> Subject: Re: Individual Contributor License Agreement
> Date: August 24, 2024 at 07:09:17 PDT
> To: Secretary <[email protected]>
> 
> The original gpg public key was filed last week. I suppose that we now need 
> to delete that key and file the new key that contains the updated email 
> address?
> If so, how do we do that?
> 
> Craig
> 
> 
>> On Aug 23, 2024, at 18:49, Craig Russell <[email protected]> wrote:
>> 
>> The email on the form is [email protected]
>> 
>> But there is no such email in the gpg key we have on file. That key has 
>> [email protected] and [email protected] .
>> 
>> If you can double check we can see if there is a problem on our side.
>> 
>> Warm regards,
>> Craig
>> 
>> 
>>> On Aug 23, 2024, at 01:19, Jurgen Doll <[email protected]> wrote:
>>> 
>>> Hi Craig
>>> 
>>> I've updated my public key to include the name/email on the form and 
>>> resigned the PDF.
>>> 
>>> Thanks, regards
>>> Jurgen
>>> 
>>> 
>>> On Thu, 22 Aug 2024 23:46:24 +0200, Craig L Russell <[email protected]> wrote:
>>> 
>>>> Dear Jurgen Doll,
>>>> 
>>>> We received this document but we cannot file it as is.
>>>> - the public key does not match the name/email on the form
>>>> - the document appears to be unsigned
>>>> - a name typed in a script font is not a signature
>>>> 
>>>> Please complete all required fields and resubmit all pages
>>>> to [email protected]
>>>> https://apache.org/licenses/contributor-agreements.html#submitting
>>>> 
>>>> Warm Regards,
>>>> 
>>>> --
>>>> Craig L Russell
>>>> Assistant Secretary, Apache Software Foundation
>>> <icla.pdf.asc><icla.pdf>
>> 
>> Craig L Russell
>> [email protected]
>> 
> 
> Craig L Russell
> [email protected]
> 

Craig L Russell
[email protected]

Reply via email to