On 15-Dec-2017, Alf Gaida wrote: > % dput -d ftp-eu qps_1.10.17-2_source.changes > […] > Checking signature on .changes > gpg: /home/agaida/work/code/pkg-main/qps/qps_1.10.17-2_source.changes: > error 58: gpgme_op_verify > gpgme_op_verify: GPGME: No data > > > Can you send that upload control file, as an attachment on a message > > to this bug report? > done
Thanks. As can be seen from the file you attached to that message ‘qps_1.10.17-2_source.changes’, there is no GnuPG data. So checking the signature produces the above error. On 15-Dec-2017, Alf Gaida wrote: > Now the same package released: Note that the file you attached to that message is now GnuPG-signed. That is what makes the difference, and which is why the above behaviour is not seen. > % dput -d ftp-eu qps_1.10.17-2_source.changes > […] > Checking signature on .changes > gpg: /home/agaida/work/code/pkg-main/qps/qps_1.10.17-2_source.changes: > Valid signature from CD280A0B4D72827C This is because the file ‘qps_1.10.17-2_source.changes’, as attached to that message, is GnuPG-signed. So the GnuPG signature check has data to work with, and it doesn't produce the error. So I think you've demonstrated this is not anything to do with the Distribution field. -- \ “Pinky, are you pondering what I'm pondering?” “I think so, but | `\ where will we find an open tattoo parlor at this time of | _o__) night?” —_Pinky and The Brain_ | Ben Finney <bign...@debian.org>
signature.asc
Description: PGP signature
