Re: Include git commit id and git tree id in *.changes files when uploading?
Simon Richter writes ("Re: Include git commit id and git tree id in *.changes files when uploading?"):
> On 12/25/25 11:53 AM, gregor herrmann wrote:
> > The last time I looked, using dgit for NMUs stil suffered from the
> > problem that it didin't cope with uploads cancelled (by the maintainer
> > or the uploader on their request). "Suffered" as in "the tag exists even
> > if the version never hit the archive." Has this changed?
>
> 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. Ideally this
information would be available via the
https://api.ftp-master.debian.org
API but it's not there right now (because that API doesn't seem to
know about queued uploads at all). I'm not sure the information is
even public! The last REJECT mail I got myself (a April 2022) was
sent only to me.
This is a problem that we will have to tackle as part of the
planned[1] whole-archive dsc importer.
In the meantime, "dgit fetch" and "dgit clone" produce a warning when
they find an upload in git thatis not visible the archive.
Ian.
[1] https://diziet.dreamwidth.org/20436.html#future-technology
--
Ian Jackson <ijackson@chiark.greenend.org.uk> These opinions are my own.
Pronouns: they/he. If I emailed you from @fyvzl.net or @evade.org.uk,
that is a private address which bypasses my fierce spamfilter.
Reply to: