Bug 121709
Summary: | yum offers to do nothing when exactarch=1 | ||||||
---|---|---|---|---|---|---|---|
Product: | [Fedora] Fedora | Reporter: | Sitsofe Wheeler <sitsofe> | ||||
Component: | yum | Assignee: | Jeff Johnson <jbj> | ||||
Status: | CLOSED WORKSFORME | QA Contact: | |||||
Severity: | medium | Docs Contact: | |||||
Priority: | medium | ||||||
Version: | 1 | ||||||
Target Milestone: | --- | ||||||
Target Release: | --- | ||||||
Hardware: | i686 | ||||||
OS: | Linux | ||||||
Whiteboard: | |||||||
Fixed In Version: | Doc Type: | Bug Fix | |||||
Doc Text: | Story Points: | --- | |||||
Clone Of: | Environment: | ||||||
Last Closed: | 2004-06-10 02:03:43 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: | |||||||
Attachments: |
|
Description
Sitsofe Wheeler
2004-04-26 15:07:56 UTC
what's your debug level set to in yum.conf? or are you setting it on the command line? From /etc/yum.conf debuglevel=2 run yum -d 6 update and send the output here. How did this machine originally get installed? Via anaconda or an upgrade? What kernel arch did anaconda originally put on it? Created attachment 99693 [details]
yum -d 6 update output
Find the yum output attached
AFAIK this machine started out as a RedHat 9 + Ximian updates install and was
taken kicking and screaming via up2date to Fedora Core 1.
To clarify a little, this machine was originally installed via the RedHat 9 anaconda and may have had a short stint being updated by Ximian's Red Carpet. It then had all traces of Ximian packaging removed and was upgraded using up2date to Fedora Core 1. I do not know how to find out what kernel arch anaconda originally put on it - I'm guessing i686 and at some later point during the up2date to FC1 someone munged an i586 kernel on but this is a blind guess. I found this within an old /var/log/rpmpkgs.4 file: kernel-2.4.20-20.9.i586.rpm so we can conclude that the i586 kernel was on the system before it was upgraded to FC1 (unfortunately that doesn't tell us what anaconda originally had on there since anaconda wouldn't have had that RPM available to it at CD creation time). ugh - so this machine has i686 and i586 kernels installed or more to the point it IS an i686 with i586 kernels installed. pain - ok I 'll look at the debug and see what I can find. Check /etc/rpm/platform and make sure that you have i686, not i586, there. On a i686, /etc/rpm/platform should contain: i686-redhat-linux There is no /etc/rpm/platform file. I'm not sure that WORKSFORME is the correct solution for this. If yum had *not* offered to do anything I don't think I would have a bug. Jeff, you do not say whether you have tried to reproduce the bug from my steps above. If you really don't want to fix this then it should be resolved NOTABUG or WONTFIX rather than WORKSFORME... yum used to cope with this situation and now does not so the behaviour has changed. Plus, an i586 kernel SHOULD work on an i686 so if the user has such a set up for whatever reason then why does it hurt to keep it up to date? Offering to do something then doing nothing is wrong. Sure the circumstances giving rise to this are weird but that doesn't excuse the behviour. |