Impossible to reinitialize workspace #28

Closed
trivoallan opened this Issue Jul 5, 2010 · 6 comments

Comments

Projects
None yet
3 participants
@trivoallan

Using Ubuntu 10.04 and code from develop branch (4de01f2)

$ git flow init -f
flags:WARN getopt: option invalide -- 'f'
 -- 'init'
flags:FATAL unable to parse provided options with getopt.
@ghost

This comment has been minimized.

Show comment
Hide comment
@ghost

ghost Jul 5, 2010

This is a known issue with shFlags on Ubuntu's getopt. Will have to see whether the shFlags project can pick this up, or whether we could provide a patch for the shFlags repo ourselves.

A workaround for now is to run the following commands:

git config --unset gitflow.branch.master
git config --unset gitflow.branch.develop
git config --unset gitflow.prefix.feature
git config --unset gitflow.prefix.release
git config --unset gitflow.prefix.hotfix
git config --unset gitflow.prefix.support
git config --unset gitflow.prefix.versiontag

Then call git flow init without the -f option.

ghost commented Jul 5, 2010

This is a known issue with shFlags on Ubuntu's getopt. Will have to see whether the shFlags project can pick this up, or whether we could provide a patch for the shFlags repo ourselves.

A workaround for now is to run the following commands:

git config --unset gitflow.branch.master
git config --unset gitflow.branch.develop
git config --unset gitflow.prefix.feature
git config --unset gitflow.prefix.release
git config --unset gitflow.prefix.hotfix
git config --unset gitflow.prefix.support
git config --unset gitflow.prefix.versiontag

Then call git flow init without the -f option.

@trivoallan

This comment has been minimized.

Show comment
Hide comment
@trivoallan

trivoallan Jul 5, 2010

Ok. Thanks for the workaround. is there a place where i can vote for resolution of the upstream bug ?

Ok. Thanks for the workaround. is there a place where i can vote for resolution of the upstream bug ?

@ghost

This comment has been minimized.

Show comment
Hide comment
@ghost

ghost Jul 5, 2010

I've only recently tested gitflow on Ubuntu, so it's fairly fresh. Haven't had the time to figure out how to translate this exactly to a bug report on shFlags. Help is appreciated with this one.

ghost commented Jul 5, 2010

I've only recently tested gitflow on Ubuntu, so it's fairly fresh. Haven't had the time to figure out how to translate this exactly to a bug report on shFlags. Help is appreciated with this one.

@nvie

This comment has been minimized.

Show comment
Hide comment
@nvie

nvie Jul 11, 2010

Owner

Decided not to invest in shFlags. Will do a complete reimplementation of gitflow in Python soon (http://github.com/nvie/gitflow/issues#issue/33), which won't suffer from the command line platform difficulties.

Owner

nvie commented Jul 11, 2010

Decided not to invest in shFlags. Will do a complete reimplementation of gitflow in Python soon (http://github.com/nvie/gitflow/issues#issue/33), which won't suffer from the command line platform difficulties.

@nvie

This comment has been minimized.

Show comment
Hide comment
@nvie

nvie Oct 18, 2010

Owner

Fixed in e1ec57d and confirmed on Ubuntu!

Owner

nvie commented Oct 18, 2010

Fixed in e1ec57d and confirmed on Ubuntu!

@vdelau

This comment has been minimized.

Show comment
Hide comment
@vdelau

vdelau Oct 19, 2010

Can confirm this fixed on Debian as well. (was broken in 0.4-dev)

vdelau commented Oct 19, 2010

Can confirm this fixed on Debian as well. (was broken in 0.4-dev)

This issue was closed.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment