Sean Whitton writes ("Bug#1121367: tag2upload-obtain-origs: Needs to ask
git-deborig for .gz compression"):
> On Tue 25 Nov 2025 at 09:30am GMT, Debian tag2upload service wrote:
> > 1 orig file(s) could not be obtained
> > # some orig(s) not available from archive mirrors, trying to regenerate
> > + git deborig 93faf6e94766a092d1dd34aa889d83aace52116d
> > # created orig
> > sha256sum: golang-github-package-url-packageurl-go_0.1.3.orig.tar.gz: No
> > such
> > file or directory
> > golang-github-package-url-packageurl-go_0.1.3.orig.tar.gz: FAILED open or
> > read
> > sha256sum: WARNING: 1 listed file could not be read
> > t2u processor [dgit-repos-server]: failed command: tag2upload-obtain-origs
> > p=golang-github-package-url-packageurl-go v=0.1.3-2 s=unstable
> > u=93faf6e94766a092d1dd34aa889d83aace52116d
>
> I would guess what happened here is that git-deborig made a .tar.xz but
> tag2upload-obtain-origs was expecting to find a .tar.gz so it failed.
This is tag2upload-obtain-origs'a last-ditch attempt to get a copy of
the .orig, after it has found that there ia an existing .orig in the
archive, but that it couldn't obtain it.
The thing is, I think that nowadays we should almost always be able to
get the actual orig from the archive, from incoming if necessary.
I think this was job 1851? I looked at the transcript and I see it
trying
https://incoming.debian.org/debian-buildd/pool/main/g/golang-github-package-url-packageurl-go/golang-github-package-url-packageurl-go_0.1.3.orig.tar.gz
amonst other URLs. Evidently it got 404, but that URL works for me
now.
I looked at tracker and
https://tracker.debian.org/news/1692742/accepted-golang-github-package-url-packageurl-go-013-1-source-all-into-unstable/
The Accepted mail there is Date: Tue, 25 Nov 2025 09:10:14 +0000.
The t2u failure report for job 1851 [1] is dated Nov 25 09:45:36 GMT.
So IDK what happened here.
> git-deborig doesn't have a way to force .gz compression so I think we
> need to give it a new option to do that.
Having said all that, I think this is a reasonable way to try to make
this work despite all the headwinds.
> Ian, I'll add that to git-deborig, perhaps you could handle the changes
> to tag2upload-obtain-origs?
Sure. Would you do the test case? Ie hand me the branch with the new
test failing. (I think the test case is perhaps the hardest part
here, but if we don't write it, our iteration cycle will involve t2u
server-side deployment *and* waiting for a failure.)
Regards,
Ian.
[1] Please always quote the job number.
--
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.
