Bug 138424

Summary:	new-kernel-pkg wrong param
Product:	[Fedora] Fedora	Reporter:	YOSHIMURA Keitaro <ramsydx>
Component:	kernel	Assignee:	Dave Jones <davej>
Status:	CLOSED NOTABUG	QA Contact:	Brian Brock <bbrock>
Severity:	high	Docs Contact:
Priority:	medium
Version:	3	CC:	pfrields, wtogami, zaitcev
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:	2004-11-11 04:39:15 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 YOSHIMURA Keitaro 2004-11-09 04:11:53 UTC

Description of problem:
 %post script was wrong.
 new-kernel-pkg wrong param.
 2.6.8-1.521: " --mkinitrd --depmod --install 2.6.8-1.521"
 2.6.9-1.667: " --package kernel --mkinitrd --depmod --install 2.6.9- 
1.667"

Version-Release number of selected component (if applicable):
 2.6.9- 1.667

How reproducible:
 remove " --package kernel"

Comment 1 Pete Zaitcev 2004-11-09 21:16:47 UTC

What did actually happen because of "--package kernel"?
What did you do and what was the result?

Comment 2 Pete Zaitcev 2004-11-09 21:27:44 UTC

Sorry, I understood it now. The new-kernel-pkg mkinitrd-3.5.22-1 (FC2)
does not have --package argument. The mkinitrd-4.1.18-2 (FC3) does.
Apparently, this is an issue when attempting to upgrade (the original
reporter used "agt-get dist-upgrade", ugh...)

Comment 3 YOSHIMURA Keitaro 2004-11-10 01:35:43 UTC

yes. I used apt-get dist-upgrade.
# Did you see /.j?
It was wrong package dependency.

Comment 4 Dave Jones 2004-11-11 04:39:15 UTC

mkinitrd needs to be updated first.
an anaconda update from fc2 -> fc3 should do this correctly.
if apt-get doesn't, it's a bug in apt-get afaics, as the
kernel spec already specifies a minimum mkinitrd of the
version in fc3 in its Requires: