Hmmm... Perhaps my problem is elsewhere then. Invoking the following command: gpg --list-key B16CCA95 --no-default-keyring --keyring /usr/share/keyrings/debian-maintainers.gpg
I get that the expiration date is 2009-12-22, the new (correct) one. How is this even possible? I changed the expiration date 2 days ago. I've uploaded my new public key to hkp://keyring.debian.org . But still, the last change to debian-maintainers was on feb. 24th. So i don't understand how /usr/share/keyrings/debian-maintainers.gpg could contain my new expiration date. I also figure there's still something wrong as i didn't get any email (either accept or reject) for the latest dput i did. If you have any hints as to what i'm doing wrong, it'd be greatly appreciated. Cheers, -Pascal On Mon, Mar 9, 2009 at 6:38 PM, Joey Hess <jo...@debian.org> wrote: > Christoph Berg wrote: >> That's a jetring bug. It needs to be taught that updated expiration >> dates are a change. > > When presented with two keyrings, in which a key's expiry date has > changed, jetring-gen will generate two changesets. The first deletes > the key, the second adds back the new version. > > -- > see shy jo > > -----BEGIN PGP SIGNATURE----- > Version: GnuPG v1.4.9 (GNU/Linux) > > iD8DBQFJtZp+d8HHehbQuO8RAgutAJ969v0TQSkDxeSiZeJNKgjCZ9iO+ACg25Ib > 2rfhILzbxPieUbzHR+A3gco= > =QwTR > -----END PGP SIGNATURE----- > > -- Homepage (http://organact.mine.nu) Debian GNU/Linux (http://www.debian.org) LACIME: École de technologie supérieure (http://lacime.etsmtl.ca) -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
