Bug 100916 - Make rpmbuild warn when explicit __find_requires (etc) ignored.
Summary: Make rpmbuild warn when explicit __find_requires (etc) ignored.
Alias: None
Product: Red Hat Raw Hide
Classification: Retired
Component: rpm (Show other bugs)
(Show other bugs)
Version: 1.0
Hardware: All Linux
Target Milestone: ---
Assignee: Jeff Johnson
QA Contact: Mike McLean
Keywords: FutureFeature
Depends On:
TreeView+ depends on / blocked
Reported: 2003-07-27 02:41 UTC by Ralph Loader
Modified: 2007-04-18 16:56 UTC (History)
2 users (show)

Fixed In Version:
Doc Type: Enhancement
Doc Text:
Story Points: ---
Clone Of:
Last Closed: 2003-07-29 12:57:28 UTC
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)

Description Ralph Loader 2003-07-27 02:41:52 UTC
rpmbuild now seems to use builtin generation of requires (& provides).

This silently breaks .spec files that attempt to modify the requires generation
by changing __find_requires.

It would be nice if this breakage was not silent.  Something like:

if __find_requires is changed and _use_internal_dependency_generator != 0 then
print a warning message.

Alternatively, maybe overriding __find_requires could automagically turn off the
internal dependencies.

BTW there are some packages in severn that have been bitten by this (e.g.,
libao).  Not sure how many.

Comment 1 Jeff Johnson 2003-07-29 12:57:28 UTC
I disagree. %__find_requires needs to be removed entirely, will
happen at my earliest opportunity.

Comment 2 Steven Roberts 2005-09-06 08:34:43 UTC
Curious as to why you are thinking of removing __find_requires.  we use this
often on custom rpms to filter out bogus deps.  an Example:
the RPM includes samples or example or contrib binaruies that require lots of
extra packages to run but the core/real parts of the RPM itself run just fine
without the other packages.  so if we can't filter out these "bogus" deps then
we would have to install using --nodeps which is not a good thing in my mind.

or is there some other option?

which setting _use_internal_dependency_generator to 0 fixed things for me.

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