Bug 460772 - hgk and hbisect are missing from mercurial package
Summary: hgk and hbisect are missing from mercurial package
Keywords:
Status: CLOSED NOTABUG
Alias: None
Product: Fedora
Classification: Fedora
Component: mercurial
Version: 9
Hardware: All
OS: Linux
medium
medium
Target Milestone: ---
Assignee: Neal Becker
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2008-08-31 14:41 UTC by John Reiser
Modified: 2008-09-09 14:55 UTC (History)
3 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2008-09-09 14:55:40 UTC
Type: ---
Embargoed:


Attachments (Terms of Use)

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


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