Bug 745171 - Request to add mongodb package
Summary: Request to add mongodb package
Keywords:
Status: CLOSED WONTFIX
Alias: None
Product: Red Hat Enterprise Linux 6
Classification: Red Hat
Component: distribution
Version: 6.3
Hardware: x86_64
OS: Linux
urgent
urgent
Target Milestone: rc
: ---
Assignee: RHEL Program Management
QA Contact: Jeff Needle
URL:
Whiteboard:
Depends On:
Blocks: 435010 745599
TreeView+ depends on / blocked
 
Reported: 2011-10-11 14:46 UTC by Irina Boverman
Modified: 2019-04-16 13:59 UTC (History)
5 users (show)

Fixed In Version:
Doc Type: Enhancement
Doc Text:
Clone Of:
: 745599 (view as bug list)
Environment:
Last Closed: 2012-05-03 21:01:52 UTC
Target Upstream Version:

Attachments (Terms of Use)
Add an attachment (proposed patch, testcase, etc.)

Description Irina Boverman 2011-10-11 14:46:22 UTC 
Description of problem:

MRG-Grid and CloudForms distributions depend on mongodb packages, currently they are:

mongodb srpm:
mongodb-1.6.4-3.el6.x86_64.rpm            mongodb-devel-1.6.4-3.el6.x86_64.rpm
mongodb-debuginfo-1.6.4-3.el6.x86_64.rpm  mongodb-server-1.6.4-3.el6.x86_64.rpm

It is more appropriate for RHEL to distribute them and support them as tier 2 packages (only supported as used by other packages).

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


How reproducible:


Steps to Reproduce:
1.
2.
3.
  
Actual results:


Expected results:


Additional info:
Comment 1 Bill Nottingham 2011-10-11 15:08:18 UTC 
It is odd for RHEL to distribute something as 'only supported as used by other packages' when it's not actually used by any other packages in RHEL.
Comment 6 Suzanne Logcher 2012-01-31 21:15:01 UTC 
This request was evaluated by Red Hat Product Management for inclusion in the
current release of Red Hat Enterprise Linux. Because the affected component is
not scheduled to be updated in the current release, Red Hat is unfortunately
unable to address this request at this time.  It has been proposed for the next
release. If you would like it considered as an exception in the current
release, please ask your support representative.
Note You need to log in before you can comment on or make changes to this bug.