PGP key and expiration

Do not assign random teams to support requests. This question seems to be one for the launchpad-users mailing list.

On Fri, Jun 09, 2006 at 04:52:28PM -0000, Daniel Holbach wrote:
> Support request #1020 on Launchpad changed:
> https://launchpad.net/products/launchpad/+ticket/1020
>
> Comment:
> Do not assign random teams to support requests. This question seems to be one for the launchpad-users mailing list.

These teams are support contacts for all Launchpad support requests.
They were automatically subscribed to this tickets and will be for all
launchpad requests.

--
Diogo M. Matsubara

Ah ok I see. May I ask why? It's not exactly, that any of these teams could do anything about the way how Launchpad works or are the right QA contact.

I helped Claude to solve this issue over IRC. Here's a summary of what we have
done so far:

    - First confirmed that Claude's key (with the new expiration date) wasn't
      uploaded to any key server;
    - Asked him to upload it with the following command: $ gpg --keyserver
      keyserver.ubuntu.com --send-keys <email address hidden>;
    - Confirmed that the server now have his key at:
      http://keyserver.ubuntu.com:11371/pks/lookup?search=paroz%40email.ch&op=vindex
    - Instructed him to try to revalidate the key again which he did without
      success. He got the following message:
      'The key 16946297 cannot be validated because it has expired.'

I think now that last step failed due bug 3052.

--
Diogo M. Matsubara

On Fri, Jun 09, 2006 at 06:13:25PM -0000, Daniel Holbach wrote:
> Support request #1020 on Launchpad changed:
> https://launchpad.net/products/launchpad/+ticket/1020
>
> Comment:
> Ah ok I see. May I ask why? It's not exactly, that any of these teams could do anything about the way how Launchpad works or are the right QA contact.

I agree with you. It seems to me that a member of those teams added the whole
team as a support contact to Launchpad. If you are a member of any of those
teams and think they're wrongly subscribed as the support contact, you can
unsubscribe here:
https://launchpad.net/products/launchpad/+support-contact

Cheers,
--
Diogo M. Matsubara

Thank you very much Diogo for the explanation, I removed gnome and desktop-bugs from that list.

Le vendredi 09 juin 2006 à 18:21 +0000, Diogo Matsubara a écrit :
> Support request #1020 on Launchpad changed:
> https://launchpad.net/products/launchpad/+ticket/1020
>
> Comment:
> I helped Claude to solve this issue over IRC. Here's a summary of what we have
> done so far:
>
> - First confirmed that Claude's key (with the new expiration date) wasn't
> uploaded to any key server;
> - Asked him to upload it with the following command: $ gpg --keyserver
> keyserver.ubuntu.com --send-keys <email address hidden>;
> - Confirmed that the server now have his key at:
> http://keyserver.ubuntu.com:11371/pks/lookup?search=paroz%40email.ch&op=vindex
> - Instructed him to try to revalidate the key again which he did without
> success. He got the following message:
> 'The key 16946297 cannot be validated because it has expired.'
>
> I think now that last step failed due bug 3052.

And what now ?

Claude

On Mon, Jun 12, 2006 at 07:51:04PM -0000, Claude Paroz wrote:
[snip]
> >
> > I think now that last step failed due bug 3052.
>
> And what now ?

Hello Claude,

I'd suggest you to try again. You might be able to successfully re-validate your
key now. Yesterday we had a code rollout that restarted the application
servers, cleaning the $GNUPGHOME env variable mentioned on bug 3052.
If it doesn't work, please contact me over IRC.

>
> Claude
>

--
Diogo M. Matsubara

Thanks to Diogo, my key is now revalidated. Many thanks.