On 21/12/2021 10.07, Jochen Sprickerhof wrote:
While I agree that both packages conflict, I'm not sure if proposing a
Breaks+Replaces is the proper solution here (and in general). Normally
we want to have the library packages to be coinstallable and thus the
packages only provide non conflicting files. Could you maybe adopt your
template to mention that this hints to a problem in the package and
propose to look into resolving the conflict as an alternative solution?
What about
In case of shared library packages where the conflicting files do not
contain the SOVERSION in their name or path, please also consider
alternative solutions for solving the conflict and avoiding
Breaks+Replaces for easier upgrades in the future. Ideally shared
libraries of different SOVERSIONs should only contain non-conflicting
files and thus be co-installable for smooth upgrades.
Andreas
