Skip to content
This repository has been archived by the owner on Jul 4, 2023. It is now read-only.

unable to install git-flow #15412

Closed
miguelfteixeira opened this issue Oct 11, 2012 · 6 comments
Closed

unable to install git-flow #15412

miguelfteixeira opened this issue Oct 11, 2012 · 6 comments

Comments

@miguelfteixeira
Copy link

Looks like is something wrong in the shFlags submodule.

➜ ~ brew install git-flow
==> Cloning https://github.com/nvie/gitflow.git
Updating /Library/Caches/Homebrew/git-flow--git
==> Checking out tag 0.4.1
Submodule 'shFlags' () registered for path 'shFlags'
fatal: Needed a single revision
Unable to find current revision in submodule path 'shFlags'
Error: Failure while executing: git submodule update

➜ ~ brew doctor
Warning: "config" scripts exist outside your system or Homebrew directories.
./configure scripts often look for *-config scripts to determine if
software packages are installed, and what additional flags to use when
compiling and linking.

Having additional scripts in your path can confuse software installed via
Homebrew if the config script overrides a system or Homebrew provided
script of the same name. We found the following "config" scripts:

/usr/local/opt/php53/bin/php-config

➜ ~

@adamv
Copy link
Contributor

adamv commented Oct 11, 2012

Upstream should package tarballs that include the submodules

@drakeguan
Copy link
Contributor

It might be the submodule, shFlags, is using git protocol instead of more non-firewall-blocked http protocol.

@jacknagel
Copy link
Contributor

Works fine here; try removing the cached checkout (rm -rf $(brew --cache git-flow)).

@jacknagel
Copy link
Contributor

Note that we don't have control over what protocol is used to fetch the submodules; if they are registered in the superproject as git:// URLs, that is what it will use.

@miguelfteixeira
Copy link
Author

After the cache cleanup everything worked fine.

Thanks :)

@killerwolf
Copy link

cache cleanup helped me too

@Homebrew Homebrew locked and limited conversation to collaborators Feb 16, 2016
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

5 participants