Bug 174411

Summary:	Update from clean fc4 to devel tree not possible because of conflict
Product:	[Fedora] Fedora	Reporter:	Christian Nolte <ch.nolte>
Component:	kudzu	Assignee:	Bill Nottingham <notting>
Status:	CLOSED NOTABUG	QA Contact:	David Lawrence <dkl>
Severity:	high	Docs Contact:
Priority:	medium
Version:	rawhide	CC:	rvokal
Target Milestone:	---
Target Release:	---
Hardware:	All
OS:	Linux
Whiteboard:
Fixed In Version:		Doc Type:	Bug Fix
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2005-11-28 20:24:59 UTC	Type:	---
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:

Description Christian Nolte 2005-11-28 20:19:57 UTC

Description of problem:
After installing a clean fc4 distribution and updating the 2.6.11 kernel to
2.6.14, the yum-update to the current fedora-devel/fedora-extras-devel fails
because of a reported conflict: kernel < 2.6.12.


Version-Release number of selected component (if applicable):
1.2.13-1

How reproducible:
Install a clean fc4, update the kernel, activate
fedora-devel/fedora-extras-devel repos, deactivate fedora repo, issue a "yum update"


Steps to Reproduce:
1. Install fc4
2. Update kernel: yum install kernel
3. Activate the mentioned repos
4. yum update fails with conflict: kernel < 2.6.12
  
Actual results:
The update to the devel-repo cannot be done

Expected results:
The update should run smoothly...

Additional info:
This problem could be solved by removing the kernel-entry in line 20 of the
kudzu.spec file:

Conflicts: mkinitrd < 4.0, kernel < 2.6.12

And adding the kernel dependency to a Requires dependency:

Requires: kernel > 2.6.12

A rather dirty workaround is to manually do 'rpm -ev kernel-2.6.11-1-1369_FC4'
to remove the old kernel after the new one is installed.

Another thing is, that the same problem occurs during the update with the
current initscripts-8.17-1 package.

Comment 1 Bill Nottingham 2005-11-28 20:24:59 UTC

Neither of them works with prior kernels. Since a Requires: allows them to be
booted with an old kernel, a Conflict: is more appropriate.