Bug 1517742

Summary:	PAckage system-config-kickstart fails to install
Product:	[Fedora] Fedora	Reporter:	Eduard Vopicka <eduard.vopicka>
Component:	system-config-kickstart	Assignee:	Chris Lumens <clumens>
Status:	CLOSED DUPLICATE	QA Contact:	Fedora Extras Quality Assurance <extras-qa>
Severity:	high	Docs Contact:
Priority:	unspecified
Version:	27	CC:	clumens, eduard.vopicka
Target Milestone:	---
Target Release:	---
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:		Doc Type:	If docs needed, set a value
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2017-11-27 18:13:42 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 Eduard Vopicka 2017-11-27 11:04:57 UTC

Description of problem:
Unsatisfied dependency reported during attempted install


Version-Release number of selected component (if applicable):
2.9.3-5.fc27

How reproducible:
always


Steps to Reproduce:
1) Make sure you do not have system-config-date instaolled from previous fedora release
2) 
[root@czlx-vopicka ~]# dnf list system-config-kickstart
Last metadata expiration check: 0:33:28 ago on Mon 27 Nov 2017 11:28:48 AM CET.
Available Packages
system-config-kickstart.noarch                2.9.3-5.fc27                fedora
[root@czlx-vopicka ~]# dnf list system-config-date
Last metadata expiration check: 0:33:35 ago on Mon 27 Nov 2017 11:28:48 AM CET.
Error: No matching Packages to list
[root@czlx-vopicka ~]# dnf install system-config-kickstart
Last metadata expiration check: 0:33:41 ago on Mon 27 Nov 2017 11:28:48 AM CET.
Error: 
 Problem: conflicting requests
  - nothing provides system-config-date needed by system-config-kickstart-2.9.3-5.fc27.noarch
[root@czlx-vopicka ~]# 


Actual results:
Package not installed due to error


Expected results:
Package should install.

Additional info:

Comment 1 Chris Lumens 2017-11-27 18:13:42 UTC


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