-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Package: ftp.debian.org Severity: Wishlist
When I uploaded vtk 5.2.1-8 I got an email from Archive Administrator <[email protected]> with the expected news: "vtk_5.2.1-8_amd64.changes uploaded successfully to localhost" However, I got no Reject message emailed to me. (Did it not get sent? Did I not receive it due to email problems?) The file merkel.debian.org:/org/ftp.debian.org/queue/reject/vtk_5.2.1-8_amd64.reason contains Rejected: Signature made by expired key 0x9306C9BCDAF1054C Rejected: The key used to sign vtk_5.2.1-8_amd64.changes has expired on 2009-08-11 But I didn't track that down until I was told about it on IRC. Of course, from my point of view, I had noticed the upcoming expiration and extended the expiration on my key a couple of months ago. I though I had pushed that to the keyservers back then. Even so, the Rejected message is wrong. It should mention the source of the expiration data so that I can track down what is out of date. My guesses: - a local keyring file used by the dinstall program, updated how? when? by who? - a local keyring file installed from the debian-keyring package, last updated 2009-05-29! - fetched from db.debian.org, which doesn't seem to let me manage my own key entry - fetched from keyring.debian.org, and I must have forgotten to --send-keys to it It would be more helpful if the script would report both to me as maintainer and uploader and to someone capable of updating whatever keyring is involved in the decision. - -Maitland -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.9 (GNU/Linux) Comment: Processed by Mailcrypt 3.5.8+ <http://mailcrypt.sourceforge.net/> iEYEARECAAYFAkqW0D0ACgkQkwbJvNrxBUxuhgCfcsn8XXFBF2Qbm+iQkyL7KDI3 hLwAmgO9Kv5eOoGyYXzz7HhQaMgN+moX =TPTT -----END PGP SIGNATURE----- -- To UNSUBSCRIBE, email to [email protected] with a subject of "unsubscribe". Trouble? Contact [email protected]
