I also have this problem. Seems that the variable $ZSH is empty within the upgrade script. Works if I hardcode the path to .oh-my-zsh in the tools/upgrade.sh script.

I also had troubles upgrading.

Manually executing git pull origin master worked.

Iernies trick worked. Seems like $ZSH isn"t working inside upgrade.sh even though it is working otherwise.

Same problem here. Hopefully it will be fixed upstream soon.

This was introduced by commit 1a673fc

--- templates/zshrc.zsh-template
+++ templates/zshrc.zsh-template
@@ -1,18 +1,18 @@
 # Path to your oh-my-zsh configuration.
-export ZSH=$HOME/.oh-my-zsh
+ZSH=$HOME/.oh-my-zsh
…

Temporary workaround, change your ~/.zshrc to export ZSH again:

export ZSH=$HOME/.oh-my-zsh

Thanks for the temporary workaround

worked as well.. thanks #toolbear

+1

Folks: there"s no new update since August 30 hence no updates coming with "git pull origin master". When there are updates, this issue will be fixed. Just be patient… :)

Why doesn"t this issue warrant an update?

Hello,

I"m a bit lost, sorry. I"ve got this problem and I can"t install oh-my-zsh because I"ve already installed it (makes sense).

So what should I do?

Thank you!

_kud

@kud have you tried the temporary workaround #549 (comment)

I"ve pulled the git repo and added your line, seems ok. Cheers!

does anyone know why this isn"t being resolved? while not critical, it seems jarring and widespread.

I think most people get by with a simple git pull --rebase origin master to upgrade their OMZ forks. In that light, I personally think this upgrade script is redundant / overkill. 👮

@trevor it should be resolved. My pull request with a fix was accepted. However, once you"ve been bitten you have to fix your repo manually as @sunaku suggests. Alternatively you can do the workaround in my comment above. After that, auto update should work for you the next time.

+1 @toolbear

Workaround is known for 3 years, why it this still an issue?

Closing per the advice of #2568.

This was still an issue after I installed oh-my-zsh for the first time in my life. It was 7 days ago (as of comment above).
Why this issue was closed if it"s still there?

should be merged here.

old problems, but it works~ thank you! @toolbear

If you upgraded you MAC OS & you have XCode already installed, you should open XCode & accept agreements & install new components, then,, go back to terminal .. the issue will be resolved.