Bug 20499 - rpm ignore BuildPrereq: statement in the SPEC file
Summary: rpm ignore BuildPrereq: statement in the SPEC file
Status: CLOSED NOTABUG
Alias: None
Product: Red Hat Linux
Classification: Retired
Component: rpm   
(Show other bugs)
Version: 7.0
Hardware: i386
OS: Linux
medium
medium
Target Milestone: ---
Assignee: Jeff Johnson
QA Contact: David Lawrence
URL:
Whiteboard:
Keywords:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2000-11-07 23:33 UTC by Milan Kerslager
Modified: 2007-04-18 16:29 UTC (History)
1 user (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Environment:
Last Closed: 2000-11-08 13:33:10 UTC
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)
Add an attachment (proposed patch, testcase, etc.)

Description Milan Kerslager 2000-11-07 23:33:09 UTC 
RPM silently ignore the BuildPrereq statement in the SPEC file. I used rpm
-ba command.
The build process then fail by unresolved building dependencies.
Comment 1 Jeff Johnson 2000-11-08 13:13:28 UTC 
Add "--nodeps" to the build arguments if you wish to disable build dependency
checking.
Comment 2 Milan Kerslager 2000-11-08 13:33:07 UTC 
No, rpm *ignore* BuildPrereq: dependencies in SPEC file so when rebulding
packages the is no message about unresolved dependencies and compilation thus
fail (because there are no packages required by SPEC file in the system and rpm
did not inform about this unresolved dependencies). Simply BuildPrereq: do
nothing. I can write whatever here with no effect.
Comment 3 Jeff Johnson 2000-11-12 19:54:19 UTC 
Is your BuildPreReq: in the spec file preamble (i.e. near the top of the spec
file with other
tags?)

FWIW, I use BuildPreReq:'s routinely, and they "work for me" ...
Note You need to log in before you can comment on or make changes to this bug.