Bug 162448 - Hardcoded build dependency on docbook-dtds *release*
Summary: Hardcoded build dependency on docbook-dtds *release*
Status: CLOSED WONTFIX
Alias: None
Product: Red Hat Enterprise Linux 4
Classification: Red Hat
Component: gstreamer (Show other bugs)
(Show other bugs)
Version: 4.0
Hardware: All Linux
medium
medium
Target Milestone: ---
: ---
Assignee: Benjamin Otte
QA Contact:
URL:
Whiteboard:
Keywords: EasyFix, Patch
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2005-07-04 22:04 UTC by Jos Vos
Modified: 2012-06-20 13:22 UTC (History)
1 user (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Environment:
Last Closed: 2012-06-20 13:22:23 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)
Patch for gstreamer.spec file. (896 bytes, patch)
2005-07-04 22:04 UTC, Jos Vos
no flags Details | Diff

Description Jos Vos 2005-07-04 22:04:42 UTC
Description of problem:
The gstreamer spec file contains a hardcoded dependency (not in BuildRequires,
but only "hidden" in the code) to a specific version *and release* of
docbook-dtds. This makes building gstreamer with another release of docbook-dtds
impossible,

Version-Release number of selected component (if applicable):
0.8.7-4.EL.0

Additional info:
The attached patch solves the problem.

Comment 1 Jos Vos 2005-07-04 22:04:42 UTC
Created attachment 116335 [details]
Patch for gstreamer.spec file.

Comment 3 Jiri Pallich 2012-06-20 13:22:23 UTC
Thank you for submitting this issue for consideration in Red Hat Enterprise Linux. The release for which you requested us to review is now End of Life. 
Please See https://access.redhat.com/support/policy/updates/errata/

If you would like Red Hat to re-consider your feature request for an active release, please re-open the request via appropriate support channels and provide additional supporting details about the importance of this issue.


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