On Wed 2021-12-01 09:43:18 +0000, Adam D. Barratt wrote:
> It looks like you've hit a (fairly) common issue with trying to upload
> the same upstream version to multiple suites in a short time.
thanks for keeping an eye on this, and giving a quick diagnosis, Adam.
> I assume both of your uploads included the .orig.tar.gz and were made
> close together.
This is exactly right.
> At this point your options are either to re-upload the .orig.tar.gz
> directly, or dcut and re-upload the complete bullseye upload.
i've taken the former approach, uploading directly with sftp. hopefully
that'll work :)
> In general, either don't include the orig in the later upload, or space
> them apart so that you receive the queued confirmation for the first
> before uploading the second. (If the orig is already in the archive, as
> I assume is the case here, then you don't actually need to include it
> in either upload.)
Thanks, this is useful guidance for a workaround.
I can't help but wonder whether there isn't some way to avoid the need
for a workaround in the backend anyway, though. for example, if the
orig.tar.gz is missing, look in neighboring suites for one with the
matching digest. Where would i look for a bug report on the
infrastructure that would cover this?
--dkg
Attachment:
signature.asc
Description: PGP signature