Bugzilla will be upgraded to version 5.0 on a still to be determined date in the near future. The original upgrade date has been delayed.
Bug 109212 - Detecting CPU type change and telling rpm
Detecting CPU type change and telling rpm
Status: CLOSED DUPLICATE of bug 112950
Product: Fedora
Classification: Fedora
Component: kudzu (Show other bugs)
athlon Linux
medium Severity medium
: ---
: ---
Assigned To: Bill Nottingham
David Lawrence
Depends On:
  Show dependency treegraph
Reported: 2003-11-05 12:42 EST by Daniel Veillard
Modified: 2014-03-16 22:40 EDT (History)
1 user (show)

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Last Closed: 2006-02-21 13:59:46 EST
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)

  None (edit)
Description Daniel Veillard 2003-11-05 12:42:08 EST
From Bugzilla Helper:
User-Agent: Mozilla/5.0 Galeon/1.2.7 (X11; Linux i686; U;) Gecko/20030131

Description of problem:
I changed my motherboard from a Celeron to an Athlon.
When launching up2date after the fact I noted it was still
upgrading the kernel packages with i686.rpm instead of athlon.rpm
The kernel and I assume kudzu found the change but this wasn't
propagated to /etc/rpm/platform , as a result rpm/up2date/...
will not use the new patchform informations for upgrades.

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

How reproducible:
Didn't try

Steps to Reproduce:
1.upgrade your processor
2.launch up2date on kernel upgrade
3.see up2date using the older arch

Actual Results:  /etc/rpm/platform was kept as is.

Expected Results:  Ideally kudzu should keep /etc/rpm/platform up to
date on processor

Additional info:
Comment 2 Daniel Veillard 2004-09-16 04:57:13 EDT

*** This bug has been marked as a duplicate of 112950 ***
Comment 3 Red Hat Bugzilla 2006-02-21 13:59:46 EST
Changed to 'CLOSED' state since 'RESOLVED' has been deprecated.

Note You need to log in before you can comment on or make changes to this bug.