Hi Thorsten, On Fri, May 29, 2026 at 06:37:40PM +0200, Thorsten Alteholz wrote: > I read #966468 and #1003653 and still don't understand why a Conflicts: is > inappropriate here. > §7.4 of the policy says that a Conflicts: should be used "where one must > prevent simultaneous installation of two packages for reasons that are > ongoing". This is clearly the case here. It is not intended that one should > use both packages at the same time. Given vcheck's popcon I doubt that > anybody even wants to.
Indeed, §7.4 is not a good paragraph to justify this. A better one is §10.1: | Two different packages must not install programs with different | functionality but with the same filenames. This also applies when they | are installed into different directories on the default (user or root) | PATH. (The case of two programs having the same functionality but | different implementations is handled via “alternatives” or the | “Conflicts” mechanism. See Maintainer Scripts and Conflicting binary | packages - Conflicts respectively.) If this case happens, one of the | programs must be renamed. Evidently vcheck is a program installed by two different packages with different functionality. The requirement is that one of them must (not should) be renamed. Helmut
