Your message dated Wed, 8 Apr 2009 12:32:22 +1000
with message-id <[email protected]>
and subject line Re: [D-m-team] Bug#518954: Attempting to update my GPG key
with new expiration date
has caused the Debian Bug report #518954,
regarding Attempting to update my GPG key with new expiration date
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact [email protected]
immediately.)
--
518954: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=518954
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
Package: debian-maintainers
Version: 1.53
Just noticed i my GPG key expired.
I've updated the expiration date and now i'm attempting to propagate
that change to debian-maintainers keyring.
But i fail to generate a jetring changeset.
I'm told that no changes are needed.
A call to "gpg -K" shows me that i've correctly updated the expiration
date to 2009-12-22.
When doing the import into debian-maintainers.gpg, gpg tells me that
one key was processed but it's unchanged.
Consequently, calling jetring-gen doesn't generate any change either.
What am I doing wrong?
Cheers,
- -Pascal
- --
Homepage (http://organact.mine.nu)
Debian GNU/Linux (http://www.debian.org)
LACIME: École de technologie supérieure (http://lacime.etsmtl.ca)
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.9 (GNU/Linux)
iEYEARECAAYFAkm1IjMACgkQ1Lfd97FsypWWzgCfVFaBD3sERuxcUKmsTfOB8yRL
4c0An3n2H7T4t2uWtSMSvRDzs4/XuUPG
=w0ah
-----END PGP SIGNATURE-----
--- End Message ---
--- Begin Message ---
On Wed, Mar 18, 2009 at 09:23:44AM -0400, Pascal Giard wrote:
>Hi Aníbal!
>
>On Sat, Mar 14, 2009 at 2:32 AM, Aníbal Monsalve Salazar
><[email protected]> wrote:
>>You signed the message above with key B16CCA95 which is not in
>>debian-maintainers.gpg:
>
>Hmmm... as you can see in the archives, e.g. [1], that always been my
>GPG key. How is this possible?
>Did i neglect to do a crucial step?
>
>Of course, i'm willing to do whatever it takes to get my GPG key back
>in so i can continue to maintain my packages.
Just upload your key to keyring.debian.org as follows:
gpg --keyserver keyring.debian.org --send-keys D4B7DDF7B16CCA95
>Cheers,
>
>-Pascal
>[1] http://www.mail-archive.com/[email protected]/msg01860.html
>--
>Homepage (http://organact.mine.nu)
>Debian GNU/Linux (http://www.debian.org)
>LACIME: École de technologie supérieure (http://lacime.etsmtl.ca)
--- End Message ---
