Bug 1644743

Summary:	package libmypaint-1.3.0-9.fc29.x86_64 conflicts with mypaint < 1.3.0 provided by mypaint-1.2.1-19.fc29.x86_64
Product:	[Fedora] Fedora	Reporter:	Edgar Hoch <edgar.hoch>
Component:	mypaint	Assignee:	Sergey Avseyev <sergey.avseyev>
Status:	CLOSED DUPLICATE	QA Contact:	Fedora Extras Quality Assurance <extras-qa>
Severity:	medium	Docs Contact:
Priority:	unspecified
Version:	29	CC:	christoph.wickert, lizhenbo, phil, quantum.analyst, sergey.avseyev, tomspur
Target Milestone:	---
Target Release:	---
Hardware:	x86_64
OS:	Linux
Whiteboard:
Fixed In Version:		Doc Type:	If docs needed, set a value
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2019-01-27 11:00:55 UTC	Type:	Bug
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:

Description Edgar Hoch 2018-10-31 14:15:55 UTC

Description of problem:

When trying to install Fedora 29 with kickstart, I run into the following problem.

  - package libmypaint-1.3.0-9.fc29.x86_64 conflicts with mypaint < 1.3.0 provided by mypaint-1.2.1-19.fc29.i686
  - package libmypaint-1.3.0-9.fc29.x86_64 conflicts with mypaint < 1.3.0 provided by mypaint-1.2.1-19.fc29.x86_64
  - package gimp-2:2.10.6-2.fc29.x86_64 requires libmypaint-1.3.so.0()(64bit), but none of the providers can be installed

It seems that the versions of the dependend packages are not compatible.


Version-Release number of selected component (if applicable):
Fedora 29

How reproducible:
Currently

Comment 1 Sergey Avseyev 2018-10-31 14:19:26 UTC

Hi this is because mypaint cannot work with libmypaint 1.3.0. You just have to select one of the projects. As soon as upstream will release version which works with libmypaint 1.3.x, I will unbundle libmypaint and use the one from separate package.

Comment 2 Edgar Hoch 2018-10-31 14:41:46 UTC

Thanks for the fast reaction!. I have excludes mypaint from kickstart package list, now kickstart installs without error.

Comment 3 Zhenbo Li 2018-12-21 02:21:46 UTC

This should be a dup of bug 1633009

Comment 4 Elliott Sales de Andrade 2019-01-27 11:00:55 UTC


*** This bug has been marked as a duplicate of bug 1633009 ***