[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

uploading problems and massive email floods

Following the suggestion in the recent message to
debian-devel-announce, I tried using dupload to upload to the
anonymous queue.  Soon I got back this message:

Subject: Processing of autoconf_2.58-9_i386.changes

PGP/GnuPG signature check failed on autoconf_2.58-9_i386.changes

Could not read key from file '/org/queued/debianqueued-0.9/./debian-keyring.pgp'.

WARNING: Can't find the right public key-- can't check signature integrity.
gpg: Signature made Wed Dec  3 17:21:24 2003 EST using RSA key ID 797E641D
gpg: Can't check signature: public key not found
(Exit status 2)
autoconf_2.58-9_i386.changes has bad PGP/GnuPG signature!
Removing autoconf_2.58-9_i386.changes, but keeping its associated files for now.


	Your Debian queue daemon

I didn't understand that message--this is the same key I've
always used for Debian uploads; I haven't seen it on any lists of
keys removed from the keyring, its fingerprint shows up in my
entry on db.debian.org, and it appears to be still available from

After that, I've received over 134 copies of the following

Subject: Incomplete upload found in Debian upload queue

Probably you are the uploader of the following file(s) in
the Debian upload queue directory:
This looks like an upload, but a .changes file is missing, so the job
cannot be processed.

If no .changes file arrives within 22:59:37, the files will be deleted.

If you didn't upload those files, please just ignore this message.


	Your Debian queue daemon

Isn't that a bit excessive?  How do I make this stop?  And why
was my upload rejected?
"If a person keeps faithfully busy each hour of the working day, he
 can count on waking up some morning to find himself one of the
 competent ones of his generation."
--William James

Reply to: