Package: socklog Version: 2.1.0-8.1 Severity: normal Hi,
it's entirely valid and possible to run socklog to handle locally generated logs and e.g. syslog-ng to handle remote syslog clients. The new Conflicts: in the socklog package makes this unnecessarily hard in an attempt to prevent people from shooting themselves in the foot. Please also see #506173 and #893882. At the extreme, there could be a socklog-bin package that only provides the binaries with no configuration, no automatic service startup; and a socklog package which retains the Conflicts and Depends on socklog-bin. Thanks! András -- System Information: Debian Release: bullseye/sid APT prefers unstable APT policy: (350, 'unstable'), (350, 'stable'), (1, 'experimental') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 4.4.244-vs2.3.9.9 (SMP w/8 CPU threads) Kernel taint flags: TAINT_PROPRIETARY_MODULE, TAINT_OOT_MODULE Locale: LANG=en_US.UTF-8, LC_CTYPE=hu_HU.UTF-8 (charmap=UTF-8), LANGUAGE=en_US.UTF-8 Shell: /bin/sh linked to /bin/bash Init: runit (via /run/runit.stopit) Versions of packages socklog depends on: ii adduser 3.118 ii libc6 2.31-4 Versions of packages socklog recommends: ii ipsvd 1.0.0-3.1+b1 ii runit 2.1.2-36 pn socklog-run <none> socklog suggests no packages. -- no debconf information
