Package: dh-runit
Version: 2.16.4
Severity: minor
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
-- System Information:
Debian Release: trixie/sid
APT prefers unstable
APT policy: (500, 'unstable'), (1, 'experimental')
Architecture: amd64 (x86_64)
Foreign Architectures: i386
Kernel: Linux 6.12.19-amd64 (SMP w/24 CPU threads; PREEMPT)
Locale: LANG=en_GB.UTF-8, LC_CTYPE=en_GB.UTF-8 (charmap=UTF-8),
LANGUAGE=en_GB:en
Shell: /bin/sh linked to /usr/bin/dash
Init: sysvinit (via /sbin/init)
LSM: AppArmor: enabled
Versions of packages dh-runit depends on:
ii debhelper 13.24.2
ii libfile-copy-recursive-perl 0.45-4
ii libfile-slurp-perl 9999.32-2
ii libtext-hogan-perl 2.03-2
ii perl 5.40.1-3
dh-runit recommends no packages.
dh-runit suggests no packages.
-- no debconf information
