Bug 230485
Summary: | yum attempts to install packages for a "wrong arch" | ||
---|---|---|---|
Product: | [Fedora] Fedora | Reporter: | Michal Jaegermann <michal> |
Component: | yum | Assignee: | Jeremy Katz <katzj> |
Status: | CLOSED RAWHIDE | QA Contact: | |
Severity: | medium | Docs Contact: | |
Priority: | medium | ||
Version: | rawhide | CC: | corbet |
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: | 2007-03-01 17:00:10 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
Michal Jaegermann
2007-02-28 22:54:14 UTC
I'm seeing this too. I wonder if it's all yum, though? I go through the "yum update" process and I see: Updating: GConf2 i386 2.16.1-1.fc7 development 1.6 M GConf2-devel x86_64 2.16.1-1.fc7 development 102 k GConf2-gtk x86_64 2.16.1-1.fc7 development 17 k (and lots of other packages too). I have no i386 version of GConf2 installed, and don't really want one. I get some strange stuff out of RPM: [root@bike corbet]# rpm -q GConf2 GConf2-2.16.0-6.fc7 [root@bike corbet]# rpm -q GConf2.i386 [root@bike corbet]# rpm -q GConf2.x86_64 GConf2-2.16.0-6.fc7 Any attempt to query the i386 version does *not* give a "no such package" message - it just goes silent. The repodata yesterday was definitely a bit screwed up due to some fun with sqlite + nfs. Are you still seeing this today? Today seems a lot better, the problem has definitely gone away, thanks. I still wonder about the RPM behavior, though. It seems to not quite understand when you tell it to do something with a package for one architecture when only a different architecture is installed. Maybe that needs a separate bug? Yeah, that is a strange rpm bug and I can reproduce it also. Went ahead and filed it as bug 230580. |