Hi, Reinhard. We are investigating an anomaly with dgit/tag2upload relating to golang-github-microsoft-didx509go.
I don't think you did anything wrong, but I'd like you to confirm some things to make sure I understand the order of events. This package currently doesn't work with dgit clone. The dgit-repos server seems to have erroneously thought the upload was rejected. It looks like you did this upload https://deb.debian.org/debian/pool/main/g/golang-github-microsoft-didx509go/golang-github-microsoft-didx509go_0.0.3-1.dsc https://tracker.debian.org/news/1655777/accepted-golang-github-microsoft-didx509go-003-1-all-source-into-unstable/ The .changes was generated "Sat, 09 Aug 2025 08:25:35 -0400" ie 2025-08-09T12:25:35Z. The .dsc contains this Dgit: 8a259de4d07ac3fc487b1e0c5ce7585e1f074097 debian archive/debian/0.0.3-1 https://git.dgit.debian.org/golang-github-microsoft-didx509go so I think you used dgit to do the upload. Q. to Reinhard: Can you confirm that you used dgit to do this upload? Do you recall anything going wrong (or weirdly) with it? It appears that at 2025-08-09T16:37:27Z, the dgit-repos service decided that your package had been REJECTed. There is an entry in our taint database with that timestamp, for the commit names above, saying: tag archive/debian/0.0.3-1 referred to this object in git tree but all previously pushed versions were found to have been removed from NEW (ie, rejected) (or never arrived) I don't think this can be right. The package was in fact ACCEPTed (see URL above) at 2025-08-15T18:00:15Z. But dgit-repos cannot tell the difference between a package that is REJECTed and one that is still en route. (This is IMO a brokenness in the legacy Debian Archive.) I conjecture that the tarballs version of the upload was delayed somehow. Q. to Reinhard: do you still have copies of the mails from the archive systems, particularly the ones saying "Processing of ... .changes" "golang-github-microsoft-didx509go is NEW" ? If so can you please forward them to here to this bug. I looked on the server and at a similar time we have golang-github-microsoft-go-winio too. Q. to Reinhard: If you are able, can you confirm that you did these two packages roughly the same way and with the same experience ? Subject to confirmation from Reinhard I propose to manually fix this up on the server, by restoring the two repositories (from "_garbage") and by removing the taint indications from the database. Thanks, and sorry for the inconvenience. Ian. -- Ian Jackson <[email protected]> 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.
