git-clone fails

Bug #178603 reported by Adam Klobukowski
2
Affects Status Importance Assigned to Milestone
git-core (Ubuntu)
Invalid
Medium
Daniel Hahler

Bug Description

Binary package hint: git-core

invoking git with:

$ git clone http://git.0pointer.de/repos/libflashsupport.git/

fails with following error message:

/usr/bin/git-clone: 356: curl: not found

Installing curl package fixes the problem. git-core recommends curl, but it should require it.

Revision history for this message
Jonathan Davies (jpds) wrote :
Download full text (3.7 KiB)

Confirming and:

jon@rubycon:$ sudo apt-get install git-core ~
Reading package lists... Done
Building dependency tree
Reading state information... Done
The following extra packages will be installed:
  libdigest-sha1-perl liberror-perl
Suggested packages:
  git-arch git-cvs git-svn git-email git-daemon-run git-gui gitk gitweb cogito
Recommended packages:
  git-doc curl
The following NEW packages will be installed
  git-core libdigest-sha1-perl liberror-perl
0 upgraded, 3 newly installed, 0 to remove and 0 not upgraded.
Need to get 3671kB of archives.
After unpacking 7827kB of additional disk space will be used.
Do you want to continue [Y/n]? Y
Get: 1 http://es.archive.ubuntu.com gutsy/main liberror-perl 0.15-8 [15.5kB]
Get: 2 http://es.archive.ubuntu.com gutsy/main libdigest-sha1-perl 2.11-2 [24.7kB]
Get: 3 http://es.archive.ubuntu.com gutsy/main git-core 1:1.5.2.5-2build1 [3631kB]
Fetched 3671kB in 49s (74.8kB/s)
Selecting previously deselected package liberror-perl.
(Reading database ... 96282 files and directories currently installed.)
Unpacking liberror-perl (from .../liberror-perl_0.15-8_all.deb) ...
Selecting previously deselected package libdigest-sha1-perl.
Unpacking libdigest-sha1-perl (from .../libdigest-sha1-perl_2.11-2_i386.deb) ...
Selecting previously deselected package git-core.
Unpacking git-core (from .../git-core_1%3a1.5.2.5-2build1_i386.deb) ...
Setting up liberror-perl (0.15-8) ...
Setting up libdigest-sha1-perl (2.11-2) ...
Setting up git-core (1:1.5.2.5-2build1) ...
jon@rubycon:$ mkdir git-tmp ~
jon@rubycon:$ cd git-tmp ~
jon@rubycon:$ git clone http://source.djpig.de/git/packages.git ~/git-tmp
zsh: correct 'git' to '_git' [nyae]? n
Initialized empty Git repository in /home/jon/git-tmp/packages/.git/
/usr/bin/git-clone: 310: curl: not found
Cannot get remote repository information.
Perhaps git-update-server-info needs to be run there?
jon@rubycon:$ sudo apt-get install curl ~/git-tmp
Reading package lists... Done
Building dependency tree
Reading state information... Done
The following extra packages will be installed:
  libcurl3
The following NEW packages will be installed
  curl libcurl3
0 upgraded, 2 newly installed, 0 to remove and 0 not upgraded.
Need to get 357kB of archives.
After unpacking 680kB of additional disk space will be used.
Do you want to continue [Y/n]? Y
Get: 1 http://es.archive.ubuntu.com gutsy/main libcurl3 7.16.4-2ubuntu1 [182kB]
Get: 2 http://es.archive.ubuntu.com gutsy/main curl 7.16.4-2ubuntu1 [175kB]
Fetched 357kB in 3s (98.1kB/s)
Selecting previously deselected package libcurl3.
(Reading database ... 96622 files and directories currently installed.)
Unpacking libcurl3 (from .../libcurl3_7.16.4-2ubuntu1_i386.deb) ...
Selecting previously deselected package curl.
Unpacking curl (from .../curl_7.16.4-2ubuntu1_i38...

Read more...

Changed in git-core:
importance: Undecided → Medium
status: New → Confirmed
Revision history for this message
Daniel Hahler (blueyed) wrote :

git-core in Hardy recommends the different tools used for transportation:
Recommends: patch, less, rsync, curl, ssh-client

This appears to be the right solution (in contrast to "Depends"), because "curl" is only required for cloning a http repository.

Changed in git-core:
status: Confirmed → Fix Released
Revision history for this message
Daniel Hahler (blueyed) wrote :

I'm marking this as duplicate of bug 52711 instead.

Changed in git-core:
assignee: nobody → blueyed
status: Fix Released → 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.