Re: serious bugs because of missing build depends
Ben Collins <email@example.com> writes:
> I guess my concern would be to state that a) NEW packages must comply
> with current policy, and b) updated packages done by the maintainer
> (NMU's should not have to abide) should comply with the latest policy.
Policy (22.214.171.124) says:
| 2.4.1. Standards conformance
| You should specify the most recent version of the packaging standards
| with which your package complies in the source package's
| `Standards-Version' field.
| This value will be used to file bug reports automatically if your
| package becomes too much out of date.
AFAIK, we have never stipulated a minimum Standards-Version for
any release, but we probably should. The `too much out of date'
wording of current policy is too vague to be meaningful.
We should establish a policy along the lines Ben suggests. For
this purpose, what is `current policy'? Is it the version in stable,
in testing, or in unstable? In addition to requiring new and updated
packages to conform to current policy (however it is defined), should
there be a requirement that an old package be updated to reflect
current policy at some specified time?
|_) _ |_ Robert D. Hilliard <firstname.lastname@example.org>
|_) (_) |_) 1294 S.W. Seagull Way <email@example.com>
Palm City, FL USA GPG Key ID: 390D6559
PGP Key ID: A8E40EB9