Hi, I am the maintainer of kernel-patch-cryptoloop. I am not a DD, so my gpg key is not on the debian keyring. Almost noone uses kernel-patch-cryptoloop, so I let things slide. AFAIK, sarge is to use a 2.6.x kernel, so this package is mostly useless. However, a few people expressed interest recently, and added to the old bug report #255953. I tried to upload an up to date version of this package today, but got denied again. I can't remember how I got the initial version in. Questions: 1. Where does Katie look for public keys? 2. How can I get my key to such a place (it *is* on most public keyservers)? 3. If I cannot get upload permission, does anyone else want to take over? Jürgen Strobel ----- Forwarded message from Archive Administrator <katie@ftp-master.debian.org> ----- To: juergen@strobel.info Subject: Processing of kernel-patch-cryptoloop_2.4.22.0-30+1_i386.changes From: Archive Administrator <katie@ftp-master.debian.org> X-Spam-Status: No, score=-2.6 required=4.0 tests=BAYES_00 autolearn=ham version=3.0.2 PGP/GnuPG signature check failed on kernel-patch-cryptoloop_2.4.22.0-30+1_i386.changes gpg: Signature made Fri Apr 22 09:25:27 2005 EDT using RSA key ID A211F5ED gpg: Can't check signature: public key not found (Exit status 2) kernel-patch-cryptoloop_2.4.22.0-30+1_i386.changes has bad PGP/GnuPG signature! Removing kernel-patch-cryptoloop_2.4.22.0-30+1_i386.changes, but keeping its associated files for now. Greetings, Your Debian queue daemon ----- End forwarded message ----- -- The box said it requires Windows 95 or better so I installed Linux
Attachment:
signature.asc
Description: Digital signature