Bug#428432: Does 'x11-common' need to conflict with package 'xv' when etch or sarge does not provide 'xv'?
Jeremy commented:
>
> since there is no package 'xv' in any current version of Debian,
> Debian (eg. x11-common in etch) should not prevent a package from
> being installed that goes by the name of 'xv' regardless of versions,
> as long as there are no _real_ conflicts.
The conflict with the potato xv is set up with a versioned Conflicts, so
that any hypothetical future xv could install alongside modern X
perfectly well simply by bumping up the new version to an appropriately
higher value. This is another reason why there is no bug here.
Drew
Reply to: