Control: reopen -1 On Wed, Jan 02, 2019 at 12:45:08AM +0100, Andreas Beckmann wrote: > 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.
Actually, I think Breaks+Replaces is wrong here.
Breaks+Replaces allow for silent replacing of the old package, but here
you need to forcefully remove it, which is what you'd use Conflicts for.
As a data point, that what we usually use when renaming packages during
ABI breaks like what has been done for #916881.
Incidentally, I think that would also cover the just openend #918372,
as with a Conflicts the libgmsh3 package from testing woudln't be
installable, so it would force an upgrade to the version in unstable,
making the test pass.
--
regards,
Mattia Rizzolo
GPG Key: 66AE 2B4A FCCF 3F52 DA18 4D18 4B04 3FCD B944 4540 .''`.
more about me: https://mapreri.org : :' :
Launchpad user: https://launchpad.net/~mapreri `. `'`
Debian QA page: https://qa.debian.org/developer.php?login=mattia `-
signature.asc
Description: PGP signature
