Rene Engelhard writes:
> So if I get this right any package having .buildinfo will fail at this stage.
>
> Which will get problematic in stretch security updates since anything built
> inside stretch will not only have the source but also the binary .buildinfo's.
>
> I think this must be (somehow) fixed before stretch releases to be able
> to do security updates (well, sync them into s-p-u and not get lost and
> needing
> manual recovery).
My current plan is to make dak handle .buildinfo files like .changes in
policy queues. That is, store them in dists/${suite} and copy them into
the Process-Policy::CopyDir directory when the upload is accepted.
Maybe only copy them into dists/${suite} when CopyDir is set so this
only happens on sec-master and not for p-u on ftp-master.
Ansgar
