Note: This is a public test instance of Red Hat Bugzilla. The data contained within is a snapshot of the live data so any changes you make will not be reflected in the production Bugzilla. Email is disabled so feel free to test any aspect of the site that you want. File any problems you find or give feedback at bugzilla.redhat.com.

Bug 1478133

Summary:	kf5-libkface requires libopencv_core.so.3.1 which is not available
Product:	[Fedora] Fedora	Reporter:	Phil <beaaegicfqmq6rykaqaakty3lqcg6btv>
Component:	kf5-libkface	Assignee:	Rex Dieter <rdieter>
Status:	CLOSED DUPLICATE	QA Contact:	Fedora Extras Quality Assurance <extras-qa>
Severity:	medium	Docs Contact:
Priority:	unspecified
Version:	26	CC:	rdieter
Target Milestone:	---
Target Release:	---
Hardware:	All
OS:	Linux
Whiteboard:
Fixed In Version:		Doc Type:	If docs needed, set a value
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2017-08-03 19:52:43 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 Phil 2017-08-03 16:12:59 UTC

Description of problem:
The installation of kf5-libkface-16.08.3-1.fc26 requires libopencv_core.so.3.1, which is not provided by F26.

Version-Release number of selected component (if applicable):
kf5-libkface-16.08.3-1.fc26
opencv-core-3.2.0-2.fc26

How reproducible:
always.

Steps to Reproduce:
1. dnf install kf5-libkface
2. ???
3. profit!

Actual results:
Error: 
 Problem: conflicting requests
  - nothing provides libopencv_core.so.3.1 needed by kf5-libkface-16.08.3-1.fc26.i686
  - nothing provides libopencv_core.so.3.1()(64bit) needed by kf5-libkface-16.08.3-1.fc26.x86_64

Expected results:
kf5-libkface was installed.

Additional info:
rpm -q opencv-core --provides | egrep '^opencv|libopencv_core'
libopencv_core.so.3.2()(64bit)
opencv-core = 3.2.0-2.fc26
opencv-core(x86-64) = 3.2.0-2.fc26

Comment 1 Rex Dieter 2017-08-03 19:52:43 UTC


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