Dear Maintainer,

If I build a package that uses dh_runit to include runit service integration,
the ${runit:Conflicts} variable is defined and the build process warns if it is
not used. Is this still helpful or is ${runit:Breaks} sufficient in most cases?

If the conflicts variable is used, lintian complains thus:

I: stubby: conflicts-with-version runit (<< 2.1.2-51~)
N:
N:   An earlier-than version clause is normally an indication that Breaks
N:   should be used instead of Conflicts. Breaks is a weaker requirement that
N:   provides the package manager more leeway to find a valid upgrade path.
N:   Conflicts should only be used if two packages can never be unpacked at the
N:   same time, or for some situations involving virtual packages (where a
N:   version clause is not appropriate). In particular, when moving files
N:   between packages, use Breaks plus Replaces, not Conflicts plus Replaces.
N:
N:   Please refer to Conflicting binary packages - Conflicts (Section 7.4) in
N:   the Debian Policy Manual for details.
N:
N:   Visibility: info
N:   Show-Always: no
N:   Check: fields/package-relations

Thanks,

Andrew