Bug#689813: libgraphite2-3: misses Breaks: libgraphite2-2.0.0

[Rene Engelhard <rene@debian.org>]

Hi,

On Sat, Oct 06, 2012 at 05:29:56PM +0200, Andreas Beckmann wrote:
> during a test with piuparts I noticed your package is missing a Breaks
> or Conflicts relation with libgraphite2-2.0.0.

No, IMHO it isn't. Read the policy 7.6 again.[1]
Replaces: is fully correct for replacing files in older packages.

Yes, you can argue it's a case of 7.6.2, but see below.

> Debsums reports errors due to the incomplete replacement of that
> package:
> 
> 0m46.5s ERROR: FAIL: debsums reports modifications inside the chroot:
>   /usr/lib/libgraphite2.so.2.0.0

Then that's a bug in the checking. Of course the new package replaces
the old file with a symlink. 

And libgraphite2-3 Provides: libgraphite-2.0.0, so a Breaks:/Conflicts: would
need to be versioned, given the whole point of this symlink and the Provides: is
to save a tansition for a library which didn't really change ABI/API (yet).

I am not sure if with a conflicts: it would seamlessly upgrade to libgraphite3-2
even with packages still depending on libgraphite2-2.0.0....

Regards,

Rene

[1] yes, it talks about Breaks: but this is for the split, as the old package wouldn't
work with the new as the example, which doesn't apply here.