Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

bowtie conflicts with bowtie from homebrew/science #743

Closed
cooljeanius opened this issue Jul 12, 2013 · 8 comments
Closed

bowtie conflicts with bowtie from homebrew/science #743

cooljeanius opened this issue Jul 12, 2013 · 8 comments

Comments

@cooljeanius
Copy link

When running brew prune, I run into this warning:

Warning: Could not tap homebrew/science/bowtie over phinze/cask/bowtie

One of the two should probably be renamed.

I also filed this issue with homebrew/science as homebrew/homebrew-science#263

@vitorgalvao
Copy link
Member

Please refer to this issue, and see if it helps correct the problem.

If not, please run brew update, and post the results of brew doctor.

@sjackman
Copy link
Member

Since both applications are called "Bowtie", I don't see an obvious solution to this problem, other than renaming one arbitrarily, which doesn't appeal to me. Suggestions?

I think this situation is different than #619, since these are in fact two different software packages both named "bowtie".

@vitorgalvao
Copy link
Member

Yes, my question was if following the other issue would get rid of the warning (as it did there). Realistically speaking, once that’s done there’s no longer a problem, since to install apps with homebrew-cask you have to use the cask command, meaning that to install the bowtie from this project, you’d have to run brew cask install bowtie.

This means that both apps are installed with distinct commands, making the warning the only real issue, and a minor one, at that. In fact, I’ve just tapped homebrew/science to test, and there’s no problem at all. Following the instructions in #169 (particularly the last comment before it was closed), should take care of it.

@sjackman
Copy link
Member

Thanks for the clarification, Vitor. Is it possible to tap phinze/cask without the symlinks in the first place? Perhaps brew could use a tap --no-symlink option.

@vitorgalvao
Copy link
Member

Well, it shouldn’t be a problem in the future (when I did the test just now, it wasn’t). I’m just waiting on @cooljeanius’s confirmation that the issue is solved on his side, to close this (at which point you’ll be able to close yours, too), since it likely only occurred due to timing.

For some background, the solution in #169 came from a comment in a different issue, and was a fix to a known problem, that occurred due to the main homebrew project, and has been fixed recently, so new setups and setups that have that issue fixed and are updated, should not encounter the problem.

@vitorgalvao
Copy link
Member

What’s the status, @cooljeanius? Did you solve the problem with the instructions?

@cooljeanius
Copy link
Author

The one-liner from that thread wasn't working for me, so I did it this way instead:
file -h /usr/local/Library/Formula/* | grep phinze-cask | cut -d: -f1 | xargs rm -v
That seems to have removed all the brew cask symlinks from my forumla folder at least...

@vitorgalvao
Copy link
Member

Alright, I’ll close this, then. You should be able to do the same, @sjackman. If you have any further issues related to this, @cooljeanius, feel free to reopen the issue.

@Homebrew Homebrew locked and limited conversation to collaborators May 8, 2018
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

3 participants