Gimp conflict with MyPaint

Bug #1803924 reported by imatt.au on 2018-11-19
28
This bug affects 6 people
Affects Status Importance Assigned to Milestone
MyPaint
New
Unknown
gimp (Ubuntu)
Undecided
Unassigned
libmypaint (Ubuntu)
Undecided
Unassigned
mypaint (Ubuntu)
Undecided
Unassigned

Bug Description

When trying to install MyPaint (via Software Center) error occurred stating unmet dependencies.

Installed via command line using apt-get. apt-get advised that gimp would be removed if mypaint was installed.

After installing mypaint, and attempting to reinstall gimp, apt-get stated that mypaint would be removed.

Gimp (Snap version) is unaffected by mypaint installation.

ProblemType: Bug
DistroRelease: Ubuntu 18.10
Package: gimp (not installed)
ProcVersionSignature: Ubuntu 4.18.0-11.12-generic 4.18.12
Uname: Linux 4.18.0-11-generic x86_64
NonfreeKernelModules: wl
ApportVersion: 2.20.10-0ubuntu13.1
Architecture: amd64
CurrentDesktop: GNOME
Date: Mon Nov 19 15:24:17 2018
InstallationDate: Installed on 2018-10-20 (29 days ago)
InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725)
SourcePackage: gimp
UpgradeStatus: Upgraded to cosmic on 2018-10-21 (29 days ago)

imatt.au (imatt-au) wrote :
Jeremy Bicha (jbicha) wrote :

I am unmarking this a duplicate. The other bug is closed in Ubuntu & isn't specific about this issue so let's keep this bug open.

Changed in mypaint:
status: Unknown → New
Erich Eickmeyer (eeickmeyer) wrote :

@jbicha I agree, but I am not sure if this is really a bug with gimp since the problem is MyPaint's reliance on an older version of the library, and ultimately their failure to release a newer version that relies on libmypaint 1.3. We first approached this topic over 6 months ago (prior to Bionic's release) and it went nowhere. This is frustrating since we want to get MyPaint back in Ubuntu Studio, but we're stuck with them being not coinstallable.

@immatt-au This is a known issue, see http://ubuntustudio.org/2018/05/regarding-gimp-2-10/ and http://ubuntustudio.org/2018/10/ubuntu-studio-18-10-released/ (specifically in "Other Changes). That said, thanks for this report as it does bring more attention to the matter. Additionally, according to the github issue linked above, it is a known issue in Fedora as well.

Launchpad Janitor (janitor) wrote :

Status changed to 'Confirmed' because the bug affects multiple users.

Changed in gimp (Ubuntu):
status: New → Confirmed
Changed in libmypaint (Ubuntu):
status: New → Confirmed
Changed in mypaint (Ubuntu):
status: New → Confirmed

Same issue here on Ubuntu 18.04
I guess it's time for me to check out the snap system if I want to use both applications

xChris (cs-.) wrote :

ubuntu is on 19.04 and still this bug exist...amazing incompetence

Erich Eickmeyer (eeickmeyer) wrote :

@cs-. Such belittling comments are inappropriate in a bug comment. If you have nothing to contribute, please refrain from making such comments in the future.

Malix (malix0) wrote :

Now that MyPaint 2.0.0-alpha is available, it's worth packaging it?

Erich Eickmeyer (eeickmeyer) wrote :

@malix0 The MyPaint package is inherited from Debian. They typically do not package alpha or beta packages, but only final releases since the focus is on stability as opposed to having the latest thing. Therefore, this is likely not to happen until MyPaint has released 2.0.0.

To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.