Bug 88051 - /usr/include/linux/swap.h owned by glibc-kernheaders and kernel-headers
/usr/include/linux/swap.h owned by glibc-kernheaders and kernel-headers
Status: CLOSED DUPLICATE of bug 87793
Product: Red Hat Enterprise Linux 2.1
Classification: Red Hat
Component: glibc (Show other bugs)
2.1
i386 Linux
medium Severity medium
: ---
: ---
Assigned To: Jakub Jelinek
Brian Brock
:
Depends On:
Blocks:
  Show dependency treegraph
 
Reported: 2003-04-04 16:52 EST by Glen A. Foster
Modified: 2016-11-24 10:17 EST (History)
1 user (show)

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


Attachments (Terms of Use)

  None (edit)
Description Glen A. Foster 2003-04-04 16:52:21 EST
Description of problem: <linux/swap.h> is owned by both the glibc-kernheaders 
and kernel-headers packages in the first "beta" drop of the Q2 errata.  This 
shows up ONLY on x86 -- on ia64 <linux/swap.h> is owned by glibc-kernheaders.

Version-Release number of selected component (if applicable):
x86-box# rpm -qf /usr/include/linux/swap.h
kernel-headers-2.4.9-e.17
glibc-kernheaders-2.4.7-16

ia64-box# rpm -qf /usr/include/linux/swap.h
glibc-kernheaders-2.4.7-16

How reproducible: 100%

Steps to Reproduce:
1. Install on x86 box such that kernel-headers is installed
2. Login as root
3. run "rpm -qf /usr/include/linux/swap.h"
Comment 1 dff 2003-04-11 11:17:44 EDT

*** This bug has been marked as a duplicate of 87793 ***
Comment 2 Glen A. Foster 2003-04-11 11:33:46 EDT
Um, bug 87793 is not viewable with just beta-permissions.  Can you either make 
the open bug viewable, or leave _this_ defect open and close the _other_?  I'd 
like to see when any progress is made on this defect.
Comment 3 Red Hat Bugzilla 2006-02-21 13:52:29 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.