Hi Vagrant,
> This hasn't yet landed in the archive, was it actually uploaded to
> DELAYED/3?
Somewhat unclear. I am pretty sure it was uploaded as I can find an
.upload file for it:
$ cat tuxcmd-modules_0.6.70+ds-5.1_amd64.ssh-upload.upload
Successfully uploaded tuxcmd-modules_0.6.70+ds-5.1.dsc to
ssh.upload.debian.org for ssh-upload.
Successfully uploaded tuxcmd-modules_0.6.70+ds.orig.tar.gz to
ssh.upload.debian.org for ssh-upload.
Successfully uploaded tuxcmd-modules_0.6.70+ds-5.1.debian.tar.xz to
ssh.upload.debian.org for ssh-upload.
Successfully uploaded tuxcmd-modules-dbgsym_0.6.70+ds-5.1_amd64.deb to
ssh.upload.debian.org for ssh-upload.
Successfully uploaded tuxcmd-modules_0.6.70+ds-5.1_amd64.buildinfo to
ssh.upload.debian.org for ssh-upload.
Successfully uploaded tuxcmd-modules_0.6.70+ds-5.1_amd64.deb to
ssh.upload.debian.org for ssh-upload.
Successfully uploaded tuxcmd-modules_0.6.70+ds-5.1_amd64.changes to
ssh.upload.debian.org for ssh-upload.
> It could have been uploaded to DELAYED/0 (e.g. without delay) as a QA
> upload rather than as an NMU...
Oh sure, but 3 days delay easily allows issues to be caught...
However, in lieu of working out what has happened here, I'll re-upload
now without any DELAYED value. Thanks. :)
Regards,
--
,''`.
: :' : Chris Lamb
`. `'` la...@debian.org 🍥 chris-lamb.co.uk
`-
