git-core in Jaunty does not include git-* commands

Bug #301905 reported by K. Lange
2
Affects Status Importance Assigned to Milestone
git-core (Ubuntu)
Invalid
Undecided
Unassigned

Bug Description

Binary package hint: git-core

On Jaunty, I'm not finding the git-* commands:

[klange acerlaptop 11/24 7:55] ~$ sudo apt-get install git-core
[sudo] password for klange:
Reading package lists... Done
Building dependency tree
Reading state information... Done
git-core is already the newest version.
0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded.
[klange acerlaptop 11/24 7:55] ~$ git-[tab][tab]
git-receive-pack git-upload-archive
git-shell git-upload-pack
[klange acerlaptop 11/24 8:00] /usr/bin$ ls | grep git
git
git-receive-pack
git-shell
git-upload-archive
git-upload-pack
sgitopnm

This definitely causes a problem when I have this in a script:

if [ -z "$(which git-clone)" ]; then
    echo "You must have GIT installed to use this script. Install the git-core $
    exit 1;
fi

This is on Jaunty, fully updated, i386, git-core 1:1.6.0.4-1ubuntu1.

Revision history for this message
Anders Kaseorg (andersk) wrote :

This is an upstream change in Git 1.6.0. Commands like `git-clone` have been deprecated since 2006 in favor of `git clone`, and have now been removed from the default path. The dashed forms are still available in the directory returned by `git --exec-path`. See:
<http://www.kernel.org/pub/software/scm/git/docs/RelNotes-1.6.0.txt>
I am closing this report, but don’t hesitate to report any other bugs you may find.

Changed in git-core:
status: New → Invalid
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.