Getting Package Control errors on OS X but command runs fine

[NobleUplift]

I am receiving the following two errors whenever I start Sublime Text 2:

Package Control

Error executing: /usr/bin/git symbolic-ref -q HEAD

Working directory: /Users/NobleUplift/Library/Application Support/Sublime Text 2/Packages/TypeScript

Invalid connection: com.apple.coresymbolicationd

VCS-based packages can be ignored by changing the "ignore_vcs_packages" setting to true.

Sublime Text will need to be restarted once the setting is changed.

And:

Package Control

The process git seems to have gotten stuck.

Command: /usr/bin/git symbolic-ref -q HEAD

Working directory: /Users/NobleUplift/Library/Application Support/Sublime Text 2/Packages/TypeScript

This is likely due to a password or passphrase prompt. Please ensure git works without a prompt, or change the "ignore_vcs_packages" Package Control setting to true.

Sublime Text will need to be restarted once these changes are made.

When I cd "/Users/NobleUplift/Library/Application Support/Sublime Text 2/Packages/TypeScript" and run /usr/bin/git symbolic-ref -q HEAD, it returns refs/heads/master. I don't see where the plugin errors are coming from.

[DanielRosenwasser]

Did you try setting "ignore_vcs_packages" to true in your settings?

[NobleUplift]

Yes, and I still receive the error. This is my Settings - User file:

{
    "ignored_packages":
    [
        "Vintage"
    ],
    "ignore_vcs_packages": true
}

[NobleUplift]

Now I have a new error:

Package Control

Error executing: /usr/bin/git pull --ff --commit origin master

Working directory: /Users/NobleUplift/Library/Application Support/Sublime Text 2/Packages/TypeScript

From https://github.com/Microsoft/TypeScript-Sublime-Plugin
 * branch            master     -> FETCH_HEAD error: Your local changes to the following files would be overwritten by merge:
    tsserver/lib.d.ts
    tsserver/lib.dom.d.ts
    tsserver/lib.dom.iterable.d.ts
    tsserver/lib.es2015.collection.d.ts
    tsserver/lib.es2015.core.d.ts
    tsserver/lib.es2015.d.ts
    tsserver/lib.es2015.generator.d.ts
    tsserver/lib.es2015.iterable.d.ts
    tsserver/lib.es2015.promise.d.ts
    tsserver/lib.es2015.proxy.d.ts
    tsserver/lib.es2015.reflect.d.ts
    tsserver/lib.es2015.symbol.d.ts
    tsserver/lib.es2015.symbol.wellknown.d.ts
    tsserver/lib.es2016.array.include.d.ts
    tsserver/lib.es2017.d.ts
    tsserver/lib.es2017.object.d.ts
    tsserver/lib.es2017.sharedmemory.d.ts
    tsserver/lib.es2017.string.d.ts
    tsserver/lib.es5.d.ts
    tsserver/lib.es6.d.ts
    tsserver/lib.scripthost.d.ts
    tsserver/lib.webworker.d.ts
    tsserver/protocol.d.ts
    tsserver/tsc.js
    tsserver/tsserver.js Please commit your changes or stash them before you merge. error: The following untracked working tree files would be overwritten by merge:
    tsserver/lib.es2016.full.d.ts
    tsserver/lib.es2017.full.d.ts
    tsserver/lib.es2017.intl.d.ts
    tsserver/lib.esnext.asynciterable.d.ts
    tsserver/lib.esnext.d.ts
    tsserver/lib.esnext.full.d.ts Please move or remove them before you merge. Aborting Updating eb57ceb..6da82b1

VCS-based packages can be ignored by changing the "ignore_vcs_packages" setting to true.

Sublime Text will need to be restarted once the setting is changed.

[DanielRosenwasser]

I'd try copying your TypeScript plugin directory to a temporary location, uninstalling the package from Package Control, and reinstalling through Package Control. Can you let me know if that takes care of it?

[NobleUplift]

For the last error received, I did the following:

cd ~/Library/Application Support/Sublime Text 2/Packages/TypeScript
git fetch --all
git reset --hard origin/master

And this fixed the error. I also have two Git installations on my MacBook, one from Apple (/usr/bin/git) and one from Git directly (/usr/local/git/bin/git) on versions 2.14.3 and 1.8.3.2, respectively. I upgraded the latter to 2.15.0. If this is the root cause of this issue I'll close it.

[DanielRosenwasser]

I can't say for sure; but hopefully if others run into this, they'll be able to try the same steps and see if that resolves the problem.