On Wed, Mar 09, 2016 at 07:41:57PM +0100, Moritz Muehlenhoff wrote: > Package: ftp.debian.org > Severity: wishlist > > This was discussed at one of the past security team meetings, but > there was never a bug for that: > > (This is a first high level view, the exact requirements can be hashed > out later.) > > It would be great to have a simple (single command) method to simplify > testing security updates. Right now these need to copied manually to > the respective test hosts. If it's not available via apt, this is a > problem for many people since they are unable to find out which binary > packages are installed and how to update them via dpkg. > > There should be a method to allow > - publishing a public security issue to a permanent staging repository > ala jessie-security-staging, which people can keep in their apt source > > - publishing an non-public security issue to a protected apt > repository to simplify testing for members of the security team
I am not very familiar with the internals of DAK, but to me this should be setup similarly to how the stable-proposed-updates currently are setup. Couldn't there be a suite before "security" in dak? For those, like me, who are struggling to keep in RAM all those suites, I've updated the flow diagram that madduck made a while back, so now it looks like this: https://wiki.debian.org/DebianReleases#Workflow There's probably a bunch of mistakes there, it's in the wrong place (moinmoin wiki that doesn't keep revisions instead of real docs somewhere) but i had to stop shaving yaks at *some* point. A. -- It is a miracle that curiosity survives formal education - Albert Einstein
signature.asc
Description: Digital signature
