Dear maintainer,

I recently joined the LTS Security Team and found that I had to relearn
how to build source packages with dpkg-buildpackage in order to upload.

It would be nice to have dgit support uploads to security master, in
particular because dgit could work out whether or not to include the
orig.tar.

The most convenient thing would be to upload to security-master when the
suite name ends in '-security'.  So, perhaps some sort of mapping of
upload targets to upload hosts.

Sean Whitton writes ("Bug#1050143: dgit: support uploading to security-master"):

Isn't it annoying ?  Unfortunately because security uploads can be
embargoed, this isn't something we can just do here.

Ian.

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]"):

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.

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.