[SERVER-9987] Generate rhel 5.7 Enterprise RPM Created: 21/Jun/13 Updated: 11/Jul/16 Resolved: 08/Feb/14 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | Packaging |
| Affects Version/s: | 2.4.4 |
| Fix Version/s: | 2.6.0-rc0 |
| Type: | New Feature | Priority: | Major - P3 |
| Reporter: | Ernie Hershey | Assignee: | Ernie Hershey |
| Resolution: | Done | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||||||||||
| Backwards Compatibility: | Fully Compatible | ||||||||||||
| Participants: | |||||||||||||
| Description |
|
This should correspond to the 5.x enterprise build tgz release. We already generate a rhel 6.x enterprise package at release time based on the rhel 6 binary tarball we release. We should do the same for rhel 5. |
| Comments |
| Comment by Githook User [ 08/Feb/14 ] |
|
Author: {u'username': u'ehershey', u'name': u'Ernie Hershey', u'email': u'ernie.hershey@10gen.com'}Message: The "Release" rpm field has previous been 'mongodb_1' in all RPM's |
| Comment by Githook User [ 20/Dec/13 ] |
|
Author: {u'username': u'ehershey', u'name': u'Ernie Hershey', u'email': u'ernie.hershey@10gen.com'}Message: |
| Comment by Ernie Hershey [ 07/Aug/13 ] |
|
I was able to build and test a rhel 5.x RPM manually and am working now on a standardized method for generating it on an ongoing basis. |
| Comment by Ernie Hershey [ 27/Jun/13 ] |
|
I'm sorry that I don't have an ETA yet. I'm going to be working on mapping out how this will work. The RPM will almost definitely contain the same binary files we distribute in the .tgz for enterprise builds so if using that is an option for you, you can run the same version of the product that the RPM will ultimately provide. |
| Comment by Clare Holley [ 26/Jun/13 ] |
|
Do we have an ETA on when the *.rpm files will be availble for Red Hat 5.X? We do not have Red Hat 6.X deployed and we are told we have to wait for the *.rpm to be created by your team. |