brew keeps saying "A newer Command Line Tools release is available"

[JetForMe]

Warning: A newer Command Line Tools release is available
Update them from Software Update in the App Store.

But no update shows up in the App Store, nor in Xcode (5.0.1).

Running "xcode-select --install" goes through an install process, then stops with "Can't install the software because it is not currently available from the Software Update server."

[adamv]

Please post your brew --config and brew doctor, for completeness.

But note that if Apple's servers are down there's not much we can do until they come back up.

[JetForMe]

$ brew --config
HOMEBREW_VERSION: 0.9.5
ORIGIN: https://github.com/mxcl/homebrew
HEAD: e406495
HOMEBREW_PREFIX: /usr/local
HOMEBREW_CELLAR: /usr/local/Cellar
CPU: 8-core 64-bit ivybridge
OS X: 10.9-x86_64
Xcode: 5.0.1
CLT: 5.0.1.0.1.1382131676
breClang: 5.0 build 500
X11: N/A
System Ruby: 1.8.7-358
Perl: /usr/bin/perl
Python: /usr/bin/python
Ruby: /usr/bin/ruby => /System/Library/Frameworks/Ruby.framework/Versions/2.0/usr/bin/ruby

$ brew doctor
Warning: "config" scripts exist outside your system or Homebrew directories.
./configure scripts often look for *-config scripts to determine if
software packages are installed, and what additional flags to use when
compiling and linking.

Having additional scripts in your path can confuse software installed via
Homebrew if the config script overrides a system or Homebrew provided
script of the same name. We found the following "config" scripts:

/usr/local/CrossPack-AVR/bin/libusb-config

Warning: /usr/local/share/python is not needed in PATH.
Formerly homebrew put Python scripts you installed via pip or pip3
(or easy_install) into that directory above but now it can be removed
from your PATH variable.
Python scripts will now install into /usr/local/bin.
You can delete anything, except 'Extras', from the /usr/local/share/python
(and /usr/local/share/python3) dir and install affected Python packages
anew with pip install --upgrade.

Warning: Unbrewed dylibs were found in /usr/local/lib.
If you didn't put them there on purpose they could cause problems when
building Homebrew formulae, and may need to be deleted.

Unexpected dylibs:
/usr/local/lib/libosxfuse_i32.2.dylib
/usr/local/lib/libosxfuse_i64.2.dylib
/usr/local/lib/libsvn_client-1.0.dylib
/usr/local/lib/libsvn_delta-1.0.dylib
/usr/local/lib/libsvn_diff-1.0.dylib
/usr/local/lib/libsvn_fs-1.0.dylib
/usr/local/lib/libsvn_fs_fs-1.0.dylib
/usr/local/lib/libsvn_fs_util-1.0.dylib
/usr/local/lib/libsvn_ra-1.0.dylib
/usr/local/lib/libsvn_ra_local-1.0.dylib
/usr/local/lib/libsvn_ra_neon-1.0.dylib
/usr/local/lib/libsvn_ra_svn-1.0.dylib
/usr/local/lib/libsvn_repos-1.0.dylib
/usr/local/lib/libsvn_subr-1.0.dylib
/usr/local/lib/libsvn_wc-1.0.dylib

Warning: Unbrewed .la files were found in /usr/local/lib.
If you didn't put them there on purpose they could cause problems when
building Homebrew formulae, and may need to be deleted.

Unexpected .la files:
/usr/local/lib/libosxfuse_i32.la
/usr/local/lib/libosxfuse_i64.la
/usr/local/lib/libsvn_client-1.la
/usr/local/lib/libsvn_delta-1.la
/usr/local/lib/libsvn_diff-1.la
/usr/local/lib/libsvn_fs-1.la
/usr/local/lib/libsvn_fs_fs-1.la
/usr/local/lib/libsvn_fs_util-1.la
/usr/local/lib/libsvn_ra-1.la
/usr/local/lib/libsvn_ra_local-1.la
/usr/local/lib/libsvn_ra_neon-1.la
/usr/local/lib/libsvn_ra_svn-1.la
/usr/local/lib/libsvn_repos-1.la
/usr/local/lib/libsvn_subr-1.la
/usr/local/lib/libsvn_wc-1.la

Warning: Unbrewed .pc files were found in /usr/local/lib/pkgconfig.
If you didn't put them there on purpose they could cause problems when
building Homebrew formulae, and may need to be deleted.

Unexpected .pc files:
/usr/local/lib/pkgconfig/osxfuse.pc

Warning: Unbrewed static libraries were found in /usr/local/lib.
If you didn't put them there on purpose they could cause problems when
building Homebrew formulae, and may need to be deleted.

Unexpected static libraries:
/usr/local/lib/libsvn_client-1.a
/usr/local/lib/libsvn_delta-1.a
/usr/local/lib/libsvn_diff-1.a
/usr/local/lib/libsvn_fs-1.a
/usr/local/lib/libsvn_fs_fs-1.a
/usr/local/lib/libsvn_fs_util-1.a
/usr/local/lib/libsvn_ra-1.a
/usr/local/lib/libsvn_ra_local-1.a
/usr/local/lib/libsvn_ra_neon-1.a
/usr/local/lib/libsvn_ra_svn-1.a
/usr/local/lib/libsvn_repos-1.a
/usr/local/lib/libsvn_subr-1.a
/usr/local/lib/libsvn_wc-1.a

Warning: You have unlinked kegs in your Cellar
Leaving kegs unlinked can lead to build-trouble and cause brews that depend on
those kegs to fail to run properly once built. Run brew link on these:

eigen
freetype

Warning: A newer Command Line Tools release is available
Update them from Software Update in the App Store.

[JetForMe]

Any way to tell if the servers are up or down? FWIW, I get a similar result whenever OS X tries to install a new printer driver.

[adamv]

Dunno, ask Apple.

[JetForMe]

By the way, when I first started with brew earlier today, it said the tools weren't installed. I ran the installer, and now it just says there's a newer version. So, I think brew is confused.

[jacknagel]

Maybe relevant: https://github.com/jacknagel/homebrew/commit/854281bc86b4a380001eeaa70bbd9859bb623fbf#commitcomment-4504854

[adamv]

Closing this as sooner or later Apple's download service will be back online and you will be able to update.

[thegrubbsian]

This is still happening for me. I don't know but it seems that Apple's download service wouldn't be out for 8 days. Anyone else still having this issue?

[adamv]

All I can think to suggest is brew update, then use Software Update to update your Xcode to 5.0.2, then xcode-select --install to get the new CLT.

[zackkatz]

This is fixed by the same solution as #23500 : sudo xcode-select -switch /

[JetForMe]

I installed the Xcode 5.0.2 RC, and that silenced the warning.

[AndrewShmig]

@zackkatz thanks! that helped me.

[mculp]

I'm having the same issue. I tried @zackkatz suggestion and now I'm getting something that sounds worse:

 ~  brew doctor
Warning: A newer Command Line Tools release is available
Update them from Software Update in the App Store.

 ~  brew update
Already up-to-date.

 ~  sudo xcode-select -switch /
Password:

 ~  brew doctor
Warning: Your compilers are different from the standard versions for your Xcode.
If you have Xcode 4.3 or newer, you should install the Command Line Tools for
Xcode from within Xcode's Download preferences.
Otherwise, you should reinstall Xcode.

Any ideas?

[jacobsvante]

@mculp I bumped into the same warning after running that command. Issuing sudo xcode-select --reset fixed it for me.

[virajp]

The following command fixed the issue for me as well.

sudo xcode-select --reset

[beeman]

Running sudo xcode-select --reset does not change a thing in my case...

[tb582]

I am getting this error as well - the reset mentioned above also didn't fix my issue

[mistydemeo]

@tb582 Check if your Xcode is up-to-date.

[tb582]

using just the command line tools and not full xcode required me to download the dmg from apples site vs updating but even now that I've installed the april release brew doctor still doesn't like it.

Seems to be the brew is looking for xcode when all thats really required is command line tools?

[mistydemeo]

All that's required is the command line tools; however, on 10.9, a bug is causing that test to check the Xcode version instead of the CLT version if you have both Xcode and the CLT installed. The check should work if you have only the CLT installed.

[tb582]

Is it a bug in OSx or brew? Is there a fix coming? different ticket it's tracked under other than this old'ish closed one?