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

Re: Problems uploading libpsm2



Hi Adam,


On Thu, Aug 6, 2020 at 4:00 PM Adam D. Barratt <adam@adam-barratt.org.uk> wrote:
>
> On Thu, 2020-08-06 at 15:48 -0500, Brian Smith wrote:
> > The upload succeeds. I see the files sitting in
> > ftp://ftp.upload.debian.org/pub/UploadQueue/. Eventually, I see the
> > .changes file disappear and the remaining files are:
> >
> > libpsm2_11.2.185-1.debian.tar.xz
> > libpsm2_11.2.185-1.dsc
> > libpsm2_11.2.185-1_amd64.buildinfo
> > libpsm2_11.2.185.orig.tar.gz
> >
> > These seem to hang around until something decides to delete them.
>
> The logs on the upload side say:
>
> Aug  5 23:57:30 processing /libpsm2_11.2.185-1_amd64.changes
> Aug  5 23:57:30 GnuPG signature check failed on libpsm2_11.2.185-1_amd64.changes
> Aug  5 23:57:30 /libpsm2_11.2.185-1_amd64.changes has bad PGP/GnuPG signature!
> Aug  5 23:57:30 Removing /libpsm2_11.2.185-1_amd64.changes, but keeping its associated files for now.
> Aug  6 19:07:13 processing /libpsm2_11.2.185-1_amd64.changes
> Aug  6 19:07:13 GnuPG signature check failed on libpsm2_11.2.185-1_amd64.changes
> Aug  6 19:07:13 /libpsm2_11.2.185-1_amd64.changes has bad PGP/GnuPG signature!
> Aug  6 19:07:13 Removing /libpsm2_11.2.185-1_amd64.changes, but keeping its associated files for now.
> Aug  6 20:02:18 processing /remove-libpsm2.commands
> Aug  6 20:02:18 GnuPG signature check failed on remove-libpsm2.commands
> Aug  6 20:02:18 /remove-libpsm2.commands has bad PGP/GnuPG signature!
> Aug  6 20:02:18 Removing /remove-libpsm2.commands
>
> The .changes file has been removed, as per the logs, but the .dsc
> appears to be signed by a key that is not the one you have in the DM
> keyring.
>
> > I don't receive any email notifications from Debian FTP Masters,
> > regarding the accept/reject of the source or any other
> > acknowledgement.
>
> You won't receive notifications about signature verification failures,
> because there's no way for the infrastructure to verify who should be
> notified.
>

Thank you for the analysis.  The signing key is new, as of yesterday,
due to the expiration of my previous signing key. The new subkey
0x93FF37DA54760549 was pushed to keyring.debian.org, but I guess I
will have to wait for the monthly update before I can upload.

Thanks, again.

> Regards,
>
> Adam
>


-- 
Brian T. Smith
System Fabric Works
Senior Principal Engineer
bsmith@systemfabricworks.com
GPG Key: 0xB3C2C7B73BA3CD7F


Reply to: