Bug 704304 - Port to EL5?
Summary: Port to EL5?
Keywords:
Status: CLOSED CANTFIX
Alias: None
Product: Fedora
Classification: Fedora
Component: tortoisehg
Version: 14
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: Mads Kiilerich
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2011-05-12 17:50 UTC by Neal Becker
Modified: 2011-06-02 13:26 UTC (History)
1 user (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2011-06-02 13:26:28 UTC
Type: ---

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

Description Neal Becker 2011-05-12 17:50:06 UTC 
Description of problem:

A request for a port to EL5.
A colleague is stuck back on rh 5.4.

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


How reproducible:


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


Expected results:


Additional info:
Comment 1 Mads Kiilerich 2011-05-12 23:52:08 UTC 
Would 1.10 from http://koji.fedoraproject.org/koji/taskinfo?taskID=3068934 work for you?

I don't know if it would be possible to backport 2.x. I can't offer to make such a backport, but I can probably maintain it if you create it.
Comment 2 Neal Becker 2011-05-13 10:58:42 UTC 
Yes, 1.10 should be good.
Comment 3 Mads Kiilerich 2011-06-01 10:11:51 UTC 
Did you test the package on EL5?

AFAIK EPEL5 uses Mercurial 1.3 which recent TortoiseHg versions doesn't support.
Comment 4 Neal Becker 2011-06-01 10:48:14 UTC 
Sorry, is there a package available for me to test?
Comment 5 Mads Kiilerich 2011-06-02 12:50:23 UTC 
The koji scratch build I linked above contained binaries. They have expired now but a new build is on http://koji.fedoraproject.org/koji/taskinfo?taskID=3105633 .

The Mercurial version will however be a show stopper. Can you please comment on that?
Comment 6 Neal Becker 2011-06-02 12:58:10 UTC 
This is the version distributed for EL5

hg --version
Mercurial Distributed SCM (version 1.3.1)
Note You need to log in before you can comment on or make changes to this bug.