Ian Jackson writes ("Bug#1105766: [tag2upload 207] failed, git2cl 1:3.0-3 [and
1 more messages]"):
> This URL is helpful
>
>
> https://api.ftp-master.debian.org/file_in_archive/%25git2cl%5C_3.0.orig.tar.xz
I discovered something quite exciting:
$ curl -Ss
'https://api.ftp-master.debian.org/file_in_archive/%25/guile-fibers%5c_1.3.1.orig%25.tar.%25'
| jq .
[
{
"filename": "g/guile-fibers/guile-fibers_1.3.1.orig.tar.xz",
"component": "main",
"sha256sum":
"9384ce475cb9af6b20b80b36f21c0e6d847517e0b8e5648afb215d4ed6883160"
},
{
"filename": "g/guile-fibers/guile-fibers_1.3.1.orig.tar.gz",
"component": "main",
"sha256sum":
"a5e1a9c49c0efe7ac6f355662041430d4b64e59baa538d2b8fb5ef7528d81dbf"
}
]
What should we do in this case? (Also, what if the orig tarball(s)
are supposed to exist, but cannot be obtained from the mirror?)
Options are:
* Don't provide any origs and hope everything works anyway.
Often it will simply fail since dgit's quilt fixup will want those
origs. In principle it might sometimes result in a REJECT, but not
very often I think because dgit push-source will bomb out.
But I think it may have a chance of working anyway.
* Fail right away.
* If some origs are available, somehow pick one (maybe via a
dsc_in_suite query). This seems complicated. And it won't arise
in a purely-git-based workflow where everyone is just using
git-deborig.
Ian.
--
Ian Jackson <ijack...@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.
