Package: dgit-infrastructure
Severity: important
Simon Josefsson writes ("Re: [tag2upload 207] failed, git2cl 1:3.0-3"):
> Debian tag2upload service <[email protected]> writes:
> > dgit (build host): error: archive contains git2cl_3.0.orig.tar.xz with
> > different checksum
> > dgit (build host): archive g/git2cl/git2cl_3.0.orig.tar.xz: sha256sum:
> > c16fb604903d7a370fd15c10323195a3f86e89f5016bdd8e718e9f31d50d323c
> > (archive) !=
> > d1aa305eea506d95f1083f7faf4be10ede512d1584ee38d05f099206b57f3c0f
> > (local .dsc)
>
> Hah, the classic failure mode strikes again. Was this my fault? My
> local orig.tar.xz file looks fine:
>
> jas@kaka:~/dpkg/git2cl$ sha256sum ../git2cl_3.0.orig.tar.xz
> c16fb604903d7a370fd15c10323195a3f86e89f5016bdd8e718e9f31d50d323c
> ../git2cl_3.0.orig.tar.xz
> jas@kaka:~/dpkg/git2cl$
> I'm not sure where tag2upload got the d1aa305 file from.
It will have made it with git-deborig. It shouldn't have done so -
it's supposed to find the ...
... oh wait. You're uploading to experimental, aren't you. Where the
package isn't. So that didn't leave the existing orig in the bpd like
it was supposed to. The approach I wrote in the service, to try to
find the existing .orig, is fundamentally wrong.
We need to somehow query the ftpmaster API for all origs with this
filename. Is there an existing tool for this, maybe in devscripts, I
wonder.
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.
