Hello, On Tue, Aug 15 2017, Russ Allbery wrote: > Adrian Bunk <bunk@debian.org> writes: > >> Future policy versions might change this definition, but whatever >> latest policy states has to be the definition used by both packages >> and the reproducible builds team. > >> Another example is that a package that is reproducible according to >> the policy definition must not show up as non-reproducible in >> tracker/DDPO based on results from the reproducible infrastructure. > > This seems really inflexible and unnecessarily absolutist. I don't > agree with taking this approach. > > The point of adding this definition to Policy is that we're setting a > new minimum bar for packages in Debian to meet. Right. More generally, the only thing that this new section of policy constrains is the severities that may be used when filing bugs. This is how policy changes are meant to work -- they control bug severities against packages, not what appears on tracking web pages. -- Sean Whitton
Attachment:
signature.asc
Description: PGP signature