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

Git Flow Fails on 10.8 #11958

Closed
ellisio opened this issue Apr 30, 2012 · 2 comments
Closed

Git Flow Fails on 10.8 #11958

ellisio opened this issue Apr 30, 2012 · 2 comments
Labels

Comments

@ellisio
Copy link
Contributor

ellisio commented Apr 30, 2012

Hey guys,

I just installed DP3 of OS-X 10.8 and tried to install Git Flow. Here is the output I received:

$ brew install git-flow
==> Cloning https://github.com/nvie/gitflow.git
Cloning into '/Library/Caches/Homebrew/git-flow--git'...
remote: Counting objects: 47, done.
remote: Compressing objects: 100% (41/41), done.
remote: Total 47 (delta 19), reused 22 (delta 3)
Unpacking objects: 100% (47/47), done.
==> Checking out tag 0.4.1
error: pathspec '0.4.1' did not match any file(s) known to git.
Error: Failure while executing: git checkout -q 0.4.1

To fix this I had to cd into /Library/Caches/Homebrew/git-flow--git and run git fetch origin --all and then re-run brew install git-flow.

Git Version (installed via brew install git): 1.7.10

Let me know if I can provide you with any more information.

@jacknagel
Copy link
Contributor

The GitDownloadStrategy has some known issues, and though I hadn't seen it fail this way before, I can reproduce it. I started work on fixing these issues a few days ago, but I haven't had a chance to get back to it.

(Note: if one runs brew install git-flow again immediately after it fails like this, it will work, as it will fetch the whole history and download tags when updating existing clones).

@jacknagel
Copy link
Contributor

I have a fix for this; will push it for review when GitHub's outage is resolved.

rohansingh pushed a commit to rohansingh/homebrew that referenced this issue May 7, 2012
The current series of fetch invocations in GitDownloadStrategy has the
unfortunate behavior of fetching full history even in shallow clones
that only need the history between the clone point and the remote HEAD.
It should be possible to determine if it is actually necessary to fetch
the full history, including all tags, and if it is not to avoid this
overhead.

Fixes Homebrew#11958, and several other recurring problems.

Signed-off-by: Jack Nagel <[email protected]>
Sharpie pushed a commit to Sharpie/homebrew that referenced this issue Jun 18, 2012
The current series of fetch invocations in GitDownloadStrategy has the
unfortunate behavior of fetching full history even in shallow clones
that only need the history between the clone point and the remote HEAD.
It should be possible to determine if it is actually necessary to fetch
the full history, including all tags, and if it is not to avoid this
overhead.

Fixes Homebrew#11958, and several other recurring problems.

Signed-off-by: Jack Nagel <[email protected]>
Sharpie pushed a commit to Sharpie/homebrew that referenced this issue Sep 12, 2012
The current series of fetch invocations in GitDownloadStrategy has the
unfortunate behavior of fetching full history even in shallow clones
that only need the history between the clone point and the remote HEAD.
It should be possible to determine if it is actually necessary to fetch
the full history, including all tags, and if it is not to avoid this
overhead.

Fixes Homebrew#11958, and several other recurring problems.

Signed-off-by: Jack Nagel <[email protected]>
snakeyroc3 pushed a commit to snakeyroc3/homebrew that referenced this issue Dec 17, 2012
The current series of fetch invocations in GitDownloadStrategy has the
unfortunate behavior of fetching full history even in shallow clones
that only need the history between the clone point and the remote HEAD.
It should be possible to determine if it is actually necessary to fetch
the full history, including all tags, and if it is not to avoid this
overhead.

Fixes Homebrew#11958, and several other recurring problems.

Signed-off-by: Jack Nagel <[email protected]>
@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
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants