Bug 45048 - isdn4k-utils SRPM needs several build dependencies
isdn4k-utils SRPM needs several build dependencies
Status: CLOSED RAWHIDE
Product: Red Hat Linux
Classification: Retired
Component: isdn4k-utils (Show other bugs)
7.1
i386 Linux
medium Severity medium
: ---
: ---
Assigned To: Ngo Than
Aaron Brown
:
Depends On:
Blocks:
  Show dependency treegraph
 
Reported: 2001-06-19 16:32 EDT by Jay Turner
Modified: 2015-01-07 18:46 EST (History)
1 user (show)

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Environment:
Last Closed: 2001-06-19 16:32:40 EDT
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---


Attachments (Terms of Use)

  None (edit)
Description Glen Foster 2001-06-19 16:32:36 EDT
Description of Problem: with the 7.1 product, you cannot build the
isdn4k-utils SRPM without having the following RPMs installed:
	XFree86-devel
	ncurses-devel

But, if "rpm -ba /usr/src/redhat/SPECS/isdn4k-utils*spec" is executed, you
do NOT get an error from rpm about missing/unsatisfied build dependencies
from the above list of RPMs. If you install the above list of RPMs, the
isdn4k-utils SRPM builds with no errors.

How Reproducible: Always

Steps to Reproduce:
    1. rpm -e <above-list-of-RPMs>
    2. rpm -Uvh <tree-path>/SRPMS/isdn4k-utils*.src.rpm
    3. rpm -ba /usr/src/redhat/SPECS/isdn4k-utils*spec
    4. rpm -Uvh <tree-path>/RedHat/RPMS/<above-list-of-RPMs> (and their
 associated dependencies)
    5. rpm -ba /usr/src/redhat/SPECS/isdn4k-utils*spec

Actual Results:
first 3 steps result in a failure WITHOUT a build-requires error from rpm
next 2 steps build the SRPM without fail

Expected Results:  I would expect an rpm error message to be written to
stderr informing me the isdn4k-utils SRPM cannot be built without
installing the above list of RPMs.
Comment 1 Ngo Than 2001-06-19 17:57:59 EDT
It's fixed in isdn4k-utils-3.1-41.

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