Control: severity -1 important
Debian tag2upload service writes ("[tag2upload 871] failed, scalene 1.5.54-2"):
> builder:work$ tag2upload-obtain-origs p=scalene v=1.5.54-2 s=unstable
> u=443afb7ab376dbe5c7eda6938730d40bd7368fa6
> + dgit --build-products-dir=../bpd -pscalene download-unfetched-origs
> --write-sha256sums=../bpd/origs.sha256sums
> canonical suite name for unstable is sid
> package in target suite is different upstream version, 1.5.51
> orig file is missing (404) at archive mirror:
> http://ftp.debian.org/debian/pool/main/s/scalene/scalene_1.5.54.orig.tar.gz
> 1 orig file(s) could not be obtained
> # some orig(s) not available from archive mirrors, trying to regenerate
> + git deborig 443afb7ab376dbe5c7eda6938730d40bd7368fa6
> # created orig
> sha256sum: scalene_1.5.54.orig.tar.gz: No such file or directory
> scalene_1.5.54.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=scalene v=1.5.54-2 s=unstable u=443afb7ab376dbe5c7eda6938730d40bd7368fa6
AFAICT:
scalene 1.5.54-1 was uploaded woth dput with a .orig.tar.gz.
Your 1.5.54-2 attempt followed an hour later. At that time, the .orig
hadn't made it to the mirror that the service is using. So it tried
to regenerate the origs.
But the orig that git-deborig made doesn't correspond to the one in
the archive, so then it bombed out.
I think this would have been avoided if we had implemented
#1111728 t2u: Try fetching orig from incoming
but that's still in our backlog.
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.
