On Thu, Dec 25, 2025 at 8:10 AM Ian Jackson <[email protected]>
wrote:
> > That would be the same as a REJECT, no?
>
> Indeed so. It's also very hard to distinguish from the upload still
> being queued.
>
> I'm not aware of a sensible way to tell, automatically and reliably,
> whether an upload is still queued, or has been rejected.
Have you considered having dgit create the tag with a timestamp so that
REJECTED uploads and
re-upload can be properly differentiated?
I understand the desire to be able to tell what the exact git commit that
is in the
archive. As such, I'd argue that can only be reliably determined *after*
the archive
accepted the package, whereas dgit creates and pushes that tag before that
happens.
Maybe that's the design bug that is causing confusion?
Maybe dgit (or some other tool) could query the archive programmatically or
by
downloading the (authenticated) changes file and take the git commit from
there
to construct the git tag representing the upload.
-rt
--
regards,
Reinhard
