Hi Filip On 2022-02-02 11:50:47 +0100, Filip Hroch wrote: > Dear Colleagues, > > I'm attempting to upload Fitspng into ftp-master, unfortunately, without any > success. Moreover, I haven't received any message why the upload has been > rejected, or anything else. I has understand it could be caused by GPG key > expiration, but I'm not sure if another action should be also invoked. > > Be nice to me, please. This is my first upload action without sponsor. > I don't know what can be expected having no experiences yet. > > > dput reports successful upload of the source build: > > f@dell:/tmp/fitspng$ dput -P fitspng_2.0-1_source.changes > Trying to upload package to ftp-master (ftp.upload.debian.org) > Checking signature on .changes > gpg: /tmp/fitspng/fitspng_2.0-1_source.changes: Valid signature from > 1E625DF64972FF9A > Checking signature on .dsc > gpg: /tmp/fitspng/fitspng_2.0-1.dsc: Valid signature from 1E625DF64972FF9A > Uploading to ftp-master (via ftp to ftp.upload.debian.org): > Uploading fitspng_2.0-1.dsc: done. > Uploading fitspng_2.0.orig.tar.gz: done. > Uploading fitspng_2.0-1.debian.tar.xz: done. > Uploading fitspng_2.0-1_source.buildinfo: done. > Uploading fitspng_2.0-1_source.changes: done. > Successfully uploaded packages. > > Immediately after the action, /pub/UploadQueue/ directory > listing looks appropriately: > > .. 40672 Feb 01 17:43 fitspng_2.0-1.debian.tar.xz > .. 2035 Feb 01 17:43 fitspng_2.0-1.dsc > .. 6389 Feb 01 17:43 fitspng_2.0-1_source.buildinfo > .. 2724 Feb 01 17:43 fitspng_2.0-1_source.changes > .. 1138938 Feb 01 17:43 fitspng_2.0.orig.tar.gz > > If I leave the ftp connection, any traces are lost, > like Fitspng fell down into a black hole. No information > has been received since the point. > > > Similar troubles describes > https://lists.debian.org/debian-devel/2014/03/msg00369.html. > They are due GPG key confusion. > > By following of suggestions related on the post, and knowing that > my GPG key has expired 2022-01-25, I uploaded renewed key > on hkp://keyring.debian.org during Sunday. However, keycheck > https://nm.debian.org/process/867/keycheck/ still indicates > the expiration, and rsync confirms that the last keyring > update was, accidentally, 25. January. > > Now, I'm in doubts if the problem is related on the expiration, > or if there is something different which should be investigated > as well as. From coccia.debian.org:/srv/upload.debian.org/queed/run/log: 20220201000342|process-upload|dak|fitspng_2.0-1_source.changes|Error while loading changes file fitspng_2.0-1_source.changes: No valid signature found. (GPG exited with status code 0) gpg: Signature made Sat Jan 29 15:29:40 2022 UTC gpg: using RSA key 50329FD7732E2AB08161435F1E625DF64972FF9A gpg: issuer "hroch@physics.muni.cz" gpg: Good signature from "Filip Hroch <hroch@physics.muni.cz>" [expired] gpg: WARNING: Using untrusted key! In that case you do not get a mail. You'll have to wait until your key with the new expiry date is synced to ftp-master (happens once a month) or ask a sponsor to upload it for you in the meantime. Cheers -- Sebastian Ramacher
Attachment:
signature.asc
Description: PGP signature