Red Hat Bugzilla – Bug 212968
kernel-xen-devel packages all of /xen/
Last modified: 2007-11-30 17:07:36 EST
Description of problem:
The kernel-xen-devel package contains the entire /xen/ build, including all
source and object files.
kernel-devel is there mainly just to allow modules to be built against a kernel,
so I can't see why we'd be packaging all these hypervisor files; and it results
in inflated -devel packages:
4.6M Oct 27 06:04 Server/kernel-devel-2.6.18-1.2739.el5.i686.rpm
13M Oct 27 06:05 Server/kernel-xen-devel-2.6.18-1.2739.el5.i686.rpm
I am not sure why we include the /xen/ directory AT ALL.
Should it not be enough to only include linux/include/xen/ ?
This request was evaluated by Red Hat Product Management for inclusion in a Red
Hat Enterprise Linux major release. Product Management has requested further
review of this request by Red Hat Engineering, for potential inclusion in a Red
Hat Enterprise Linux Major release. This request is not yet committed for
OK, it looks like fixing this is non-trivial for some reason :(
Simply not copying the files in the spec file makes rpmbuild run into a
RPM build errors:
Installed (but unpackaged) file(s) found:
This is quite interesting since there does not seem to be anything in the spec
file copying the things to that directory. Probably some debuginfo build magic
The question is, why does this not get called (or called differently?) if we do
copy all of xen/ into $BUILDROOT/usr/src/kernel ?
This request was evaluated by Red Hat Kernel Team for inclusion in a Red
Hat Enterprise Linux maintenance release, and has moved to bugzilla
(actually before then but..)
/xen/ is now gone from -36.
An advisory has been issued which should help the problem
described in this bug report. This report is therefore being
closed with a resolution of ERRATA. For more information
on the solution and/or where to find the updated files,
please follow the link below. You may reopen this bug report
if the solution does not work for you.