Policy 7.4 states
"Neither Breaks nor Conflicts should be used unless two packages cannot be installed at the same time or installing them both causes one of them to be broken or unusable. Having similar functionality or performing the same tasks as another package is not sufficient reason to declare Breaks or Conflicts with that package. "
Policy 10.1 states
"Two different packages must not install programs with different functionality but with the same filenames. (The case of two programs having the same functionality but different implementations is handled via "alternatives" or the "Conflicts" mechanism."
7.4 suggests it is appropriate to conflict if a package installs an executable
with the same name as another package but different functionality.
10.1 states two packages can not have executables with the same name - ever