Bug 1298859

Summary:	broken interaction with brew
Product:	[Fedora] Fedora	Reporter:	Lukáš Nykrýn <lnykryn>
Component:	thefuck	Assignee:	Matías Kreder <mkreder>
Status:	CLOSED EOL	QA Contact:	Fedora Extras Quality Assurance <extras-qa>
Severity:	unspecified	Docs Contact:
Priority:	unspecified
Version:	22	CC:	mkreder
Target Milestone:	---
Target Release:	---
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:		Doc Type:	Bug Fix
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2016-07-19 18:39:34 UTC	Type:	Bug
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:

Description Lukáš Nykrýn 2016-01-15 09:42:33 UTC

Description of problem:
thefuck seems to be calling brwe with --prefix parameter


Version-Release number of selected component (if applicable):
thefuck-1.48-1.fc22.noarch

How reproducible:
always

Steps to Reproduce:
[lnykryn@notas]$ git brnch
git: 'brnch' is not a git command. See 'git --help'.

Did you mean this?
	branch
[lnykryn@notas]$ fuck


Actual results:
[lnykryn@notas]$ fuck
Usage: brew [global-options] command [command-options-and-arguments]

brew: error: no such option: --prefix
Usage: brew [global-options] command [command-options-and-arguments]

brew: error: no such option: --prefix
git branch
  207


Expected results:
without the errors from brew command

Comment 1 Fedora End Of Life 2016-07-19 18:39:34 UTC

Fedora 22 changed to end-of-life (EOL) status on 2016-07-19. Fedora 22 is
no longer maintained, which means that it will not receive any further
security or bug fix updates. As a result we are closing this bug.

If you can reproduce this bug against a currently maintained version of
Fedora please feel free to reopen this bug against that version. If you
are unable to reopen this bug, please file a new report against the
current release. If you experience problems, please add a comment to this
bug.

Thank you for reporting this bug and we are sorry it could not be fixed.