Hi, On 6/29/23 04:49, Helmut Grohne wrote:
* Package A 1.0-1 is installed providing file F. * File F is moved to package B as of package A 1.0-3. * User installs package B, which replaces the file in package A. * User uninstalls package B.
F is now gone, even though it's supposed to be still shipped by A 1.0-1.
I am convinced by this. I think this is a sufficiently bad footgun to simply forbid Replaces that are not covered by a suitable Breaks or Conflicts relation.
That is already in Policy 7.6.1, with a footnote that gives exactly this explanation.
Simon
