Hi,

can this be fixed to suggest Conflicts instead of Breaks/Replaces if the file 
in the other package is still shipped in the current version?

Breaks/Replaces implies that ownership should be transferred from the other 
package to this one. This is most often correct, but care needs to be taken to 
not build a Replaces loop, something that Conflicts nicely avoids.

Also, unversioned Breaks, Conflicts and Replaces should give a warning at least.

   Simon

Reply via email to