On Sun, 30 Dec 2018 09:21:03 -0600 Kurt Kremitzki <kurt@kwk.systems> wrote: > I was just about to open a bug on this same issue. It's actually present > in both libmed11 and libmedc11. Instead of Conflicts, they both need > Breaks + Replaces, see Policy 7.6 [1] or #906110 [2] for a similar
In this special case, you probably need to add Breaks+Replaces: libmed1v5 (>= 4) respectively Breaks+Replaces: libmedc1v5 (>= 4) since the versions before 4 should not have any file conflicts. Andreas
