libmypaint-common: drop Conflicts: mypaint-data

Thorsten Glaser t.glaser at tarent.de
Wed Mar 13 14:14:46 GMT 2019


severity 906144 serious
reassign 906144 libmypaint-common
found 906144 1.3.0-2.1
thanks

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…

bye,
//mirabilos
-- 
tarent solutions GmbH
Rochusstraße 2-4, D-53123 Bonn • http://www.tarent.de/
Tel: +49 228 54881-393 • Fax: +49 228 54881-235
HRB 5168 (AG Bonn) • USt-ID (VAT): DE122264941
Geschäftsführer: Dr. Stefan Barth, Kai Ebenrett, Boris Esser, Alexander Steeg

*************************************************

**!!! NEU !!!** Mit der **tarent Academy** bieten wir ab sofort auch Trainings
und Schulungen in den Bereichen Softwareentwicklung, Agiles Arbeiten und
Zukunftstechnologien an. Besuchen Sie uns
auf [www.tarent.de/academy](http://www.tarent.de/academy). Wir freuen uns auf
Ihren Kontakt.

*************************************************



More information about the pkg-gnome-maintainers mailing list