RHEL Engineering is moving the tracking of its product development work on RHEL 6 through RHEL 9 to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "RHEL project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs in the statuses "NEW", "ASSIGNED", and "POST" are being migrated throughout September 2023. Bugs of Red Hat partners with an assigned Engineering Partner Manager (EPM) are migrated in late September as per pre-agreed dates. Bugs against components "kernel", "kernel-rt", and "kpatch" are only migrated if still in "NEW" or "ASSIGNED". If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "RHEL project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/RHEL-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.
Bug 768292 - mercurial 1.4 too old for opening most repositories
Summary: mercurial 1.4 too old for opening most repositories
Keywords:
Status: CLOSED WONTFIX
Alias: None
Product: Red Hat Enterprise Linux 6
Classification: Red Hat
Component: mercurial
Version: 6.1
Hardware: x86_64
OS: Linux
unspecified
medium
Target Milestone: rc
: ---
Assignee: Ondrej Oprala
QA Contact: qe-baseos-daemons
URL:
Whiteboard:
Depends On:
Blocks: 1002711
TreeView+ depends on / blocked
 
Reported: 2011-12-16 09:10 UTC by Boris Folgmann
Modified: 2019-05-20 11:01 UTC (History)
1 user (show)

Fixed In Version:
Doc Type: Rebase: Bug Fixes and Enhancements
Doc Text:
Clone Of:
Environment:
Last Closed: 2013-10-07 01:39:30 UTC
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)

Description Boris Folgmann 2011-12-16 09:10:55 UTC
Description of problem:
Shouldn't be the latest RHEL 6.x somewhere at least in sighting distance of bleeding edge?? Every second day I stumble across RPMs which are too old to do their job. Migrating several systems from RHEL 4 and 5 I had the hope that the base distribution is current enough to avoid the use of 3rd party repos and manual rebuilds. Right now I'm disappointed.

mercurial 1.4 is too old for opening most repositories. Note that upstream 2.0 is current.

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

How reproducible:
always

Steps to Reproduce:
1. try to access a repo that was created with a later version of mercurial. In this special case 1.7 or later
  
Actual results:
abort: requirement 'dotencode' not supported!

Expected results:
successfully using the repo

Additional info:
http://mercurial.selenic.com/wiki/RequiresFile

Comment 3 Suzanne Logcher 2012-02-14 23:24:48 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. Red Hat invites you to
ask your support representative to propose this request, if
appropriate and relevant, in the next release of Red Hat
Enterprise Linux. If you would like it considered as an
exception in the current release, please ask your support
representative.

Comment 6 Andrius Benokraitis 2013-10-07 01:39:30 UTC
This Bugzilla has been reviewed by Red Hat and is not planned on being addressed in Red Hat Enterprise Linux 6, and will be closed. If this bug is critical to production systems, please contact your Red Hat support representative and provide sufficient business justification.


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