Bug 45209 - licq SRPM needs several build dependencies liste
Summary: licq SRPM needs several build dependencies liste
Alias: None
Product: Red Hat Linux
Classification: Retired
Component: licq   
(Show other bugs)
Version: 7.3
Hardware: i386
OS: Linux
Target Milestone: ---
Assignee: Bernhard Rosenkraenzer
QA Contact: David Lawrence
Keywords: FutureFeature
Depends On:
TreeView+ depends on / blocked
Reported: 2001-06-20 20:47 UTC by Jay Turner
Modified: 2015-01-07 23:46 UTC (History)
1 user (show)

Fixed In Version:
Doc Type: Enhancement
Doc Text:
Story Points: ---
Clone Of:
Last Closed: 2001-06-21 13:28:34 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 Glen Foster 2001-06-20 20:47:37 UTC
Description of Problem: with the 7.1 product, you cannot build the licq
SRPM without having the following RPMs installed:

But, if "rpm -ba /usr/src/redhat/SPECS/licq*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 licq SRPM
builds with no errors.  Un-installing any of the above RPMs also results in
a build failure due to unstated-yet-present dependencies.

How Reproducible: Always

Steps to Reproduce:
    1. rpm -e <above-list-of-RPMs>
    2. rpm -Uvh <tree-path>/SRPMS/licq*.src.rpm
    3. rpm -ba /usr/src/redhat/SPECS/licq*spec
    4. rpm -Uvh <tree-path>/RedHat/RPMS/<above-list-of-RPMs> (and their
 associated dependencies)
    5. rpm -ba /usr/src/redhat/SPECS/licq*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 licq SRPM cannot be built without installing the
above list of RPMs.

Comment 1 Bernhard Rosenkraenzer 2001-06-25 14:52:41 UTC
Fixed in 1.0.3-4

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