Bug 203771 - yum upgrade glibc fails due to glibc-devel requiring glibc-headers on multiarch
Summary: yum upgrade glibc fails due to glibc-devel requiring glibc-headers on multiarch
Alias: None
Product: Fedora
Classification: Fedora
Component: glibc
Version: rawhide
Hardware: x86_64
OS: Linux
Target Milestone: ---
Assignee: Jakub Jelinek
QA Contact: Brian Brock
Depends On:
TreeView+ depends on / blocked
Reported: 2006-08-23 17:32 UTC by John (J5) Palmieri
Modified: 2016-11-24 16:15 UTC (History)
2 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Last Closed: 2006-08-23 18:27:05 UTC

Attachments (Terms of Use)
attached is the output of yum upgrade glibc (1.99 KB, application/octet-stream)
2006-08-23 17:57 UTC, John (J5) Palmieri
no flags Details

Description John (J5) Palmieri 2006-08-23 17:32:36 UTC
Description of problem:

I think there is a multiarch packaging issue with the glibc-devel.  It needs
glibc-headers but there is only an x86_64 version available yet I have both the
x86_64 and i386 glibc-devel packages installed.  This is a rawhide machine that
was installed before FC-4.  I hadn't updated it in a couple of months.

Comment 1 Jakub Jelinek 2006-08-23 17:48:18 UTC
On x86_64, you are supposed to have glibc-headers.x86_64 installed and
either just glibc-devel.x86_64 (if you don't want to be able to build 32-bit
programs), or both glibc-devel.x86_64 and glibc-devel.i386.

Are you updating by hand and only specifying some of the glibc subpackages
on the command line, or yum update'ing only certain subpackages explicitly?

Please show the command you were trying and what errors you have been given.

Comment 2 John (J5) Palmieri 2006-08-23 17:57:13 UTC
Created attachment 134736 [details]
attached is the output of yum upgrade glibc

Comment 3 Jakub Jelinek 2006-08-23 18:27:05 UTC
Either you are looking at inconsistent repository (which contains some 2.4.90-23
and some 2.4.90-10 subpackages), or you chose to upgrade only glibc{,-common}
and not devel etc.
In any case, that's not a glibc packaging bug.

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