Bug 38712 - Rebuild 2.4.2-2 from SRPM fails at patch 205
Summary: Rebuild 2.4.2-2 from SRPM fails at patch 205
Keywords:
Status: CLOSED WORKSFORME
Alias: None
Product: Red Hat Linux
Classification: Retired
Component: kernel
Version: 7.1
Hardware: i386
OS: Linux
medium
medium
Target Milestone: ---
Assignee: Arjan van de Ven
QA Contact: Brock Organ
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2001-05-02 06:16 UTC by kenneth_porter
Modified: 2007-04-18 16:32 UTC (History)
0 users

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2001-05-02 08:51:38 UTC
Embargoed:


Attachments (Terms of Use)

Description kenneth_porter 2001-05-02 06:16:45 UTC
From Bugzilla Helper:
User-Agent: Mozilla/4.74 [en] (WinNT; U)


Issuing "rpm --rebuild kernel-2.4.2-2.src.rpm" fails when applying patch 205:

Patch #205 (linux-2.4.2-parport.patch):
+ patch -p1 -s
The next patch would create the file `drivers/parport/ChangeLog',
which already exists! Assume -R? [n]

This file exists in the kernel tarball and is patched in Patch1 (patch-2.4.2-ac3.bz2), so its timestamp at the time patch 205 is applied is the 
build time.

I am building as a normal user, not root. I've rm'd the BUILD/kernel-2.4.2 directory before retrying to verify I'm not getting a stale copy.

Reproducible: Always
Steps to Reproduce:
su rpm
cd /home/rpm/download
rpm --rebuild kernel-2.4.2-2.src.rpm

Also fails with
rpm -i kernel-2.4.2-2.src.rpm
cd /home/rpm/SPECS
rpm -ba kernel-2.4.spec

Comment 1 kenneth_porter 2001-05-02 06:48:18 UTC
Doh! Looks like I've got an archaic version of patch. I grabbed the one from 7.1 and the build is now humming away. Guess the kernel SRPM needs a 
build prereq for patch.

(I need to upgrade an older box, but I need LUN support to handle both my logical drives on my MegaRAID, so I expect I need to build a custom kernel 
*before* I upgrade. Is LUN support so expensive that it can't be enabled in the stock kernel?)

Comment 2 Arjan van de Ven 2001-05-02 08:51:34 UTC
Yes you need a newer patch. We have the buildprereq there in our daily builds
for a week now. (you're the second person to notice). If you are running 6.2,
you also need a newer bash (well, the other guy did)

We don't enable LUN support as it breaks on WAY too many "cheap" devices.
If you have a device that needs it, we can "whitelist" it if you give
lspci output and the /proc/scsi/scsi content.


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