Bug#906144: libmypaint-common: drop Conflicts: mypaint-data
Control: tags -1 buster-ignore
Hi,
On Wed, Mar 13, 2019 at 03:14:46PM +0100, Thorsten Glaser wrote:
> As documented in #894757, gimp and mypaint not being coïnstallable is
> clearly RC.
>
> I’ve just poked around: it’s *only* the libmypaint.mo files that
> are affected, that is, the translation files of the *library*.
> Does GIMP use them at all? If not, they likely can be dropped from
> GIMP’s fork of the library.
>
> Otherwise, perhaps a solution can be made where the libmypaint.mo
> files are moved into a separate package and depended on by both
> libmypaint-common and mypaint-data, shipping a superset, if needed.
>
> A quick hack would be a Replaces. (Downside is, when the package
> carrying the Replaces is removed the other needs a reinstall to
> restore its version of the files.)
>
> Also consider that having both installable, but one lacking some
> translations, might be preferable over not being able to install
> both.
>
> Anyway, the current situation is somewhat untenable for a release,
> and a coworker justifiedly complains about it…
I don't think this can be fixed for buster, so I'm tagging this -ignore.
Unfortunately, this (once again) shows that "Short-term the breakage isn't
that bad" (https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=894757#50)
usually isn't the case. This should never have migrated to testing...
Ivo
Reply to: