Bug 61403

Summary: apache update erroniously Require:'s mod_bandwidth, mod_put, mod_throttle
Product: [Retired] Red Hat Linux Reporter: Kyle VanderBeek <kylev>
Component: apacheAssignee: Joe Orton <jorton>
Status: CLOSED WONTFIX QA Contact: Brian Brock <bbrock>
Severity: medium Docs Contact:
Priority: medium    
Version: 7.1   
Target Milestone: ---   
Target Release: ---   
Hardware: All   
OS: Linux   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2004-09-21 10:52:01 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:

Description Kyle VanderBeek 2002-03-19 08:34:08 UTC 
From Bugzilla Helper:
User-Agent: Mozilla/4.0 (compatible; MSIE 5.5; Windows 98; Win 9x 4.90; T312461)

Description of problem:
The apache update (1.3.22-1.7.1.i386.rpm) available on the FTP server appears 
to require the 3 above mentioned modules for no reason.  There is a Requires: 
line in the spec file that I think should not be there.  There is no reason for 
the parent package (apache) to require any of its separately available modules.

Version-Release number of selected component (if applicable):


How reproducible:
Always

Steps to Reproduce:
1. Attempt to install the apache update w/o any of the mentioned modules.


Actual Results:  Forced to install extra, undesired modules.

Expected Results:  Should just be able to install apache.

Additional info:

I don't like installing anything more than I have to.  I now have 3 modules 
that I don't really trust.
Comment 1 Joe Orton 2004-09-21 10:52:01 UTC 
Thanks for the report.  This is a mass bug update; since this release
of Red Hat Linux is no longer supported, please either:

a) try and reproduce the bug with a supported version of Red Hat
Enterprise Linux or Fedora Core, and re-open this bug as appropriate
after changing the Product field, or,

b) if relevant, try and reproduce this bug using the current version
of the upstream package, and report the bug upstream.