Bug 807729
Summary: | RFE: update to a recent release | ||
---|---|---|---|
Product: | Red Hat Enterprise Linux 6 | Reporter: | Jonathan Underwood <jonathan.underwood> |
Component: | mercurial | Assignee: | Vojtech Vitek <vvitek> |
Status: | CLOSED WONTFIX | QA Contact: | qe-baseos-daemons |
Severity: | unspecified | Docs Contact: | |
Priority: | unspecified | ||
Version: | 6.2 | CC: | hripps, ovasik |
Target Milestone: | rc | Keywords: | FutureFeature, Rebase |
Target Release: | --- | ||
Hardware: | Unspecified | ||
OS: | Unspecified | ||
Whiteboard: | |||
Fixed In Version: | Doc Type: | Rebase: Bug Fixes and Enhancements | |
Doc Text: | Story Points: | --- | |
Clone Of: | Environment: | ||
Last Closed: | 2012-05-10 13:33:10 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
Jonathan Underwood
2012-03-28 15:09:06 UTC
Thanks for the suggestion, but without customers pushing for it via support ticket, the rebase is unlikely to happen - as the RHEL update capacity is limited. It is a kind of unfortunate situation - as the EPEL policy afaik forbids to ship newer than RHEL package - so you can't use EPEL for this. Therefore - if you have an active subscription - please contact product support with this request to raise its priority - bugzilla is just tracking tool for RHEL. Well, the issue is that holding back the rhel version prevents packaging things for EPEL (such as the eclipse plugin), which was my motivation for making the request - I'm an EPEL contributor - I don't have an RHEL active subscription, in fact. I see your point, but I don't see a mercurial rebase likely to happen in RHEL-6 at the moment - it still needs a slot for testing and introduces risk of regression in production environment. If there is some dependency issue for other potential epel packages/update, probably you could discuss some kind of exception on epel-devel list or on epel sig meeting - to have e.g. mercurial15 package in epel-6. It might be accepted by them, as you said, mercurial is leaf (and more toolchain) package. |