Bug 460772

Summary: hgk and hbisect are missing from mercurial package
Product: [Fedora] Fedora Reporter: John Reiser <jreiser>
Component: mercurialAssignee: Neal Becker <ndbecker2>
Status: CLOSED NOTABUG QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: medium Docs Contact:
Priority: medium    
Version: 9CC: dennis, mmcgrath, ndbecker2
Target Milestone: ---   
Target Release: ---   
Hardware: All   
OS: Linux   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2008-09-09 14:55:40 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 John Reiser 2008-08-31 14:41:40 UTC 
Description of problem: The utilities hgk (graphical display of version history) and hbisect (binary search through version history) are missing from the mercurial package.


Version-Release number of selected component (if applicable):
mercurial-1.0.1-4.fc9.x86_64.rpm

How reproducible: always


Steps to Reproduce:
1. yum install hg
2. hgk
3. yum install hgk
  
Actual results:
Installed: mercurial.x86_64 0:1.0.1-4.fc9
$ hgk
bash: hgk: command not found
# yum install hgk
No package hgk available.


Expected results: hgk is installed as part of mercurial package


Additional info:
$ hg pull
*** failed to import extension hbisect: No module named hbisect
*** failed to import extension hgk: No module named hgk
pulling from   [snip]
Comment 1 John Reiser 2008-08-31 17:34:38 UTC 
hgk is in separate .rpm mercurial-hgk, which is OK because of the dependency on tck+tk.  hbisect and mq seem to be only in the upstream source.
Comment 2 Neal Becker 2008-09-09 14:55:40 UTC 
hbisect is there:
 rpm -qf /usr/lib64/python2.5/site-packages/mercurial/hbisect.py
mercurial-1.0.2-1.fc9.x86_64


hg bisect --help
hg bisect [-gbsr] [REV]

subdivision search of changesets

    This command helps to find changesets which introduce problems.
    To use, mark the earliest changeset you know exhibits the problem
    as bad, then mark the latest changeset which is free from the
    problem as good. Bisect will update your working directory to a
    revision for testing. Once you have performed tests, mark the
    working directory as bad or good and bisect will either update to
    another candidate changeset or announce that it has found the bad
    revision.

options:

 -r --reset     reset bisect state
 -g --good      mark changeset good
 -b --bad       mark changeset bad
 -s --skip      skip testing changeset
 -U --noupdate  do not update to target

use "hg -v help bisect" to show global options