Bugzilla will be upgraded to version 5.0 on a still to be determined date in the near future. The original upgrade date has been delayed.
Bug 133309 - spec build buglet
spec build buglet
Product: Red Hat Enterprise Linux 3
Classification: Red Hat
Component: lvm (Show other bugs)
All Linux
medium Severity low
: ---
: ---
Assigned To: Heinz Mauelshagen
Brian Brock
Depends On:
  Show dependency treegraph
Reported: 2004-09-22 22:11 EDT by John Morris
Modified: 2007-11-30 17:07 EST (History)
0 users

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Last Closed: 2004-12-10 04:06:39 EST
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)

  None (edit)
Description John Morris 2004-09-22 22:11:24 EDT
From Bugzilla Helper:
User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.4.3)

Description of problem:
Determining the target kernel to build for should not depend on the
kernel on the buildhost.  Line 126 of the .spec says:

OS_VERSION=`uname -r`

This of course will cause problems when building in a chroot
environment and setarch can only fake the arch, not the version
number.  Suggest using the version of the kernel or kernel-sources
package as a safer indicator of the target kernel.

Version-Release number of selected component (if applicable):

How reproducible:

Steps to Reproduce:
1. Drop a RHEL tree on a buildhost running a 2.6 kernel.
2. Rebuild lvm
3. list the filelist from the package.

Actual Results:  All of the binaries get .lvm1 added to the name.

Additional info:
Comment 1 John Morris 2004-09-22 22:18:35 EDT
Duh.  Multiple kernel and kernel-sources packages can exist, but I
don't think kernel-headers can so it would be a better candidate.
Comment 2 Heinz Mauelshagen 2004-12-10 04:06:39 EST
Fixed by katzj by removing the kernel version dependent part from the RHEL-3
branch specfile.

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