Package: security.debian.org dgit cannot currently push to *-security suites. I would like this to be possible. (That way people who get security update source code via dgit will get the actual git branch pushed by a dgit user, rather than a .dsc import.)
Things I know I need are: * Something like the ftpmaster data API service which I can use to find (a) the canonical names of suites (b) the current .dsc for each package in each suite. * An understanding of what extra safety catches `dgit push' should have when uploading to *-security. Currently I notice that dput asked me something interactively. I think for dgit, a --deliberately option would be appropriate. However, I suspect that I am missing part of the picture. Are there private security queues ? Are the *-security queues private ? If so then maybe it will be necessary to set up a private git server. I think dgit offers an opportunity to people doing security work, because a gitish workflow is less error-prone than a source-package-based one. I used dgit to help prepare my (just-uploaded) Xen 4.4 security update for jessie-security. But I wasn't able to share my git branch, which is a shame. Ian. -- Ian Jackson <ijack...@chiark.greenend.org.uk> These opinions are my own. If I emailed you from an address @fyvzl.net or @evade.org.uk, that is a private address which bypasses my fierce spamfilter.
