-
-
Notifications
You must be signed in to change notification settings - Fork 11.4k
brew doctor and brew upgrade stopped working #18045
Comments
Okay, I uninstalled gtk+ and octave. Still doctor or install octave don't work (verbose shows nothing for hours). |
Does |
Sounds like the issue @samueljohn described. |
Do |
@adamv Only half way.
It has been stuck there for hours (running |
@samueljohn I've been watching it for a while now, but it only seems to run ruby. At least I haven't noticed it switching |
I went and tried the PR of @samueljohn but it doesn't seem to fix my problem... |
Ok then this is unrelated to the xcrun bug. Does your mdfind hang on |
@samueljohn yes it does, after a while. So this means my spotlight is borked? How the hell do I debug that? |
My When I run either ~ > brew --config
HOMEBREW_VERSION: 0.9.4
ORIGIN: https://github.com/mxcl/homebrew
HEAD: c64a2a8fe19c300dd99af8cca665bd17fad64c90
HOMEBREW_PREFIX: /usr/local
HOMEBREW_CELLAR: /usr/local/Cellar
CPU: quad-core 64-bit ivybridge
OS X: 10.8.3-x86_64 |
@lancelakey Is Spotlight working? |
@MikeMcQuaid Spotlight seems to work fine. I just found a plain text file using Spotlight. |
What does |
Although I currently don't have this problem anymore: |
~ > xcode-select --print-path
/
I recently updated the xcode clitools using: xcode461_cltools_10_86938245a.dmg |
@lancelakey Setting the If you have Xcode installed, change it to the location of Xcode.app. Otherwise, unset it by deleting the files in |
@mistydemeo Awesome. Thanks! removing ~ > xcode-select
xcode-select: Error: no command option given.
xcode-select: Report or change the path to the active
Xcode installation for this machine.
Usage: xcode-select --print-path
Prints the path of the active Xcode folder
or: xcode-select --switch <xcode_path>
Sets the path for the active Xcode folder
or: xcode-select --version
Prints the version of xcode-select
~ > brew --config
HOMEBREW_VERSION: 0.9.4
ORIGIN: https://github.com/mxcl/homebrew
HEAD: c64a2a8fe19c300dd99af8cca665bd17fad64c90
HOMEBREW_PREFIX: /usr/local
HOMEBREW_CELLAR: /usr/local/Cellar
CPU: quad-core 64-bit ivybridge
OS X: 10.8.3-x86_64
CLT: 4.6.0.0.1.1362189000
LLVM-GCC: build 2336
Clang: 4.2 build 425
X11: N/A
System Ruby: 1.8.7-358
Perl: /usr/bin/perl
Python: /usr/local/bin/python => /usr/local/Cellar/python/2.7.3/Frameworks/Python.framework/Versions/2.7/bin/python2.7
Ruby: /Users/lance/.rbenv/shims/ruby
~ > brew upgrade
==> Upgrading 9 outdated packages, with result:
|
@mistydemeo Perhaps we can/should detect that before calling them? |
@MikeMcQuaid The effects of it seem to be severe enough maybe we should have |
I thought we had fixed this already a hundred times :-) For Xcode-only, I think, we have measures to deal with this. But if |
@mistydemeo Yep, I think have brew itself error out and also perhaps make it the first doctor check too. |
I have this same issue. If I pull up the activity monitor and kill mdfind a few times everything completes fine. If I run /usr/bin/mdfind "kMDItemCFBundleIdentifier == 'org.macosforge.xquartz.X11'" I get the proper return /Applications/Utilities/XQuartz.app but it hangs, never terminates. Again, if I kill mdfind manually, everything continues just fine. |
removing |
Closing since the original poster says he's not having an issue anymore. #17102 appears related, and should be used for further discussion. |
Just to leave my experience. From one day to another messing with ruby and gems, this started happening to me. I did not notice any
And then hanged. My I don't know why it works, but it does. I hope this does not break more stuff on the future... EDIT: |
I don't think this is a good way to fix it. I would recommend to name it back to original and set the Xcode-select path to /Applications/Xcode.app check with |
FWIW, removing /usr/share/xcode-select fixed the issue for me too. (OSX 10.8.5, brew 0.9.5) |
Today I updated for the 2nd or 3rd time my brew and ran upgrade.
Upgrading gtk+ brought everything to a standstill and it didn't do anything for hours. Then I tried running doctor but it too doesn't do anything for hours. Installing and removing still works...
I'm not really sure what's going on here. Any hints?
The text was updated successfully, but these errors were encountered: