Your message dated Thu, 29 Oct 2009 19:24:26 +0100
with message-id <[email protected]>
and subject line closing
has caused the Debian Bug report #522288,
regarding ftp.debian.org: New package version refused due to no cross-signed
gpg key
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.)
--
522288: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=522288
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
Package: ftp.debian.org
Severity: important
Hello,
sorry for asking, but I have problem with uploading new version of my
package to Debian. Submit is every time refused with
GnuPG signature check failed on atari800_2.1.0-3_i386.changes
gpg: Signature made Thu Apr 2 03:46:42 2009 UTC using DSA key ID 1BF2305A
gpg: WARNING: signing subkey 1BF2305A is not cross-certified
gpg: please see http://www.gnupg.org/faq/subkey-cross-certify.html for more
information
gpg: Can't check signature: general error (Exit status 2)
/atari800_2.1.0-3_i386.changes has bad PGP/GnuPG signature!
Removing /atari800_2.1.0-3_i386.changes, but keeping its associated files for
now.
I am pretty sure, that I have cross-signed my key long time ago:
Command> cross-certify
signing subkey 1BF2305A is already cross-certified
I have tried to push my current key to keyring.debian.org (which was
fine), but without any luck from the package submission point of view.
I didn't find any helpful post in mailing list archives. Can you please
assist me with this problem?
Thank you, cheers,
Antonin
-- System Information:
Debian Release: squeeze/sid
APT prefers testing
APT policy: (990, 'testing'), (500, 'unstable'), (1, 'experimental')
Architecture: amd64 (x86_64)
Kernel: Linux 2.6.26-1-amd64 (SMP w/2 CPU cores)
Locale: LANG=en_US.UTF-8, LC_CTYPE=cs_CZ (charmap=ISO-8859-2)
Shell: /bin/sh linked to /bin/bash
--- End Message ---
--- Begin Message ---
Hey,
as Phil already said it takes time for the keyrings to get keyupdates
over to the machines, there is a sync delay. So in case your key got
added there without being cross-signed it could have been its just not
updated yet.
Also, long time nothing heard, I assume this issue is solved.
--
bye, Joerg
>D. You've just heard about this great program and would like to package
>it, what are your next steps?
I would start off by sighing deeply and wishing I were already a DD. :-)
[...]
If I were already a DD, I would perform most of these same steps. I
would omit the deep sigh and replace it with a gasp of excitement,[...]
--- End Message ---
