On 13 February 2019 11:31:28 GMT, Dmitry Bogatov <[email protected]> wrote:
>
>[2019-02-11 20:14] Jelmer Vernooij <[email protected]>
>> > +echo 'Update standards version, no changes needed.'
>> > +echo 'Certainty: certain'
>> > +echo 'Fixed-Lintian-Tags: out-of-date-standards-version'
>> Standards-Version should reflect the latest version with which the
>> package is compatible.
>>
>>
>https://www.debian.org/doc/debian-policy/ch-controlfields.html#s-f-standards-version
>>
>> Upgrading to a newer version should be safe only if we're sure that
>> there are no changes needed because of changes in policy.
>
>True. But for my personal perspective, 99% of time latest debhelper
>imply latest policy. Maybe, just downgrate certainity to possible
>and make this check last (to simplify `git reset --hard')?
What's the value of the Standards-Version field if every package always just
sets it to the latest version of policy?
The goal for lintian-brush is that you can safely run it without having to
second-guess it.
>> Perhaps we could allow upgrades to a newer standards-versions if
>we've
>> verified that all of the steps in the upgrade checklist are taken or
>> irrelevant:
>
>Well, checking them automatically would be pain.
One way of doing this is to maintain a whitelist of versions that we know we
can safely upgrade between, either because there are no relevant changes or
because there are lintian-brush fixers for new policy.
