Hi, On Sat, 27 Oct 2018 17:30:32 +0300 Adrian Bunk <b...@debian.org> wrote: > Properly handling this in package like libarcus3 becomes difficult once > you consider that such packages might be backported to stretch-backports > and would use libprotobuf10 there. > > We might even end up with upgrade failures if a user could end up with > a nonworking combination of packages installed during an upgrade, and > a maintainer script calls such a nonworking program.
This is a sensible concern, but I share László's view here: the two versions of protobuf are not in conflict and can happily coexist on the same system, so there is no reason to declare a Break. What must be ensured is that no package depends on both at the same time: wouldn't it be better that this last package declared Conflicts and possibly Build-Conflicts towards the version of protobuf that is not meant to be used? Hop this helps, Giovanni. -- Giovanni Mascellani <g.mascell...@gmail.com> Postdoc researcher - Université Libre de Bruxelles
signature.asc
Description: OpenPGP digital signature
