NB this message is sent to *two* bugs, including a non-t2u one.
Please try to keep this subthread very narrowly focused.
Simon Josefsson writes ("Bug#1105766: [tag2upload 207] failed, git2cl 1:3.0-3
[and 1 more messages] [and 1 more messages]"):
> When I read your logic, I am a bit worried that things will break for
> multiple archives. And users normally have two archives: debian and
> debian-security. I'm not sure some of your versioning assumptions
> really hold cross-archives.
Indeed, they don't. So with the code as it stands a security upload
done with t2u might involve a regenerated .orig.tar.gz which is
undesirable.
But right now uploads to security aren't supported at all.
The underlying bug for that is #1050143.
> Maybe some reproducible rebuilder folks could provide advice here, the
> orig.tar issue comes up often in that context too.
In practice rebuilding archives with git-archive often reproduces the
same orig, but I don't think that would be good enough for security
uploads. I think we would need to tell the t2u service that "this
security archive has this other archive as a parent, and you should
look for origs there too".
Ian.
