Uploaded image for project: 'Sourcetree For Mac'
  1. Sourcetree For Mac
  2. SRCTREE-3172

Sourcetree fails to install command line tools on El Capitan (Mac OS X 10.11)

    • Icon: Bug Bug
    • Resolution: Fixed
    • Icon: Highest Highest
    • 3.0b1
    • None
    • None
    • None
    • Mac OS X 10.11
      Mac OS X 10.12.3

    • Severity 1 - Critical

      Installing command line tools from SourceTree menu fails on OS X 10.11

      ------------------

      (UPDATED) Possible workaround:

      Run this command in the terminal:

      alias stree='/Applications/SourceTree.app/Contents/Resources/stree'

      Right after running this command, the command tool should work. Users can use it by just typing stree in the terminal and see if it opens up SourceTree. Or to be more specific: stree /path/to/repo to see if it opens up a repository.

        1. command_line_tools_error_2_7_141.png
          command_line_tools_error_2_7_141.png
          154 kB
        2. convoluted.png
          convoluted.png
          104 kB
        3. Screen Shot 2015-10-02 at 5.19.15 PM.png
          Screen Shot 2015-10-02 at 5.19.15 PM.png
          52 kB
        4. Screen Shot 2018-05-15 at 5.26.20 PM.png
          Screen Shot 2018-05-15 at 5.26.20 PM.png
          90 kB
        5. sourcetree.log
          0.3 kB

            [SRCTREE-3172] Sourcetree fails to install command line tools on El Capitan (Mac OS X 10.11)

            This worked for me:

            cd to /usr/local/bin and run

            sudo ln -s /Applications/Sourcetree.app/Contents/Resources/stree

            stree runs completely normally for me after doing that.

            Mark Kenny added a comment - This worked for me: cd to /usr/local/bin and run sudo ln -s /Applications/Sourcetree.app/Contents/Resources/stree stree runs completely normally for me after doing that.

            Tristan Tran added a comment - - edited

            I am on 3.0.1 and am getting this issue when installing command line tools 

            Installation Failed

            Failed to install command line tools, please see the system log for details.

            Tristan Tran added a comment - - edited I am on 3.0.1 and am getting this issue when installing command line tools  Installation Failed Failed to install command line tools, please see the system log for details.

            The command line tools will install over the old ones. That said, there's a bug in 3.0 that prevents them from working properly. We've fixed it for 3.0.1 (currently in beta) and will begin rolling that out to all users this week.

            Brian Ganninger (Inactive) added a comment - The command line tools will install over the old ones. That said, there's a bug in 3.0 that prevents them from working properly. We've fixed it for 3.0.1 (currently in beta) and will begin rolling that out to all users this week.

            AlecRust added a comment -

            This doesn't work as expected? "stree" command now opens SourceTree, but "stree ." fails to open the current folder in SourceTree which is surely the main use case.

            Will have to go back to the alias workaround. How to uninstall the command line tools?

            AlecRust added a comment - This doesn't work as expected? "stree" command now opens SourceTree, but "stree ." fails to open the current folder in SourceTree which is surely the main use case. Will have to go back to the alias workaround. How to uninstall the command line tools?

            Brian, thank you.

            I appreciate this specific information, over the previous "I'll see whether we can get it into the release". You say, "previously noted", but that was 3 months ago, so please forgive us for thinking it was vaporware.

            Deleted Account (Inactive) added a comment - Brian, thank you. I appreciate this specific information, over the previous "I'll see whether we can get it into the release". You say, "previously noted", but that was 3 months ago, so please forgive us for thinking it was vaporware.

            As previously noted, this is fixed for the next major release.

            Brian Ganninger (Inactive) added a comment - As previously noted, this is fixed for the next major release.

            It's hard to assume that the SourceTree team cares, because if they did, they'd fix it.

             

            Deleted Account (Inactive) added a comment - It's hard to assume that the SourceTree team cares, because if they did, they'd fix it.  

            Also confirmed on 10.14, so reached a point where this bug was not fixed while Apple did 4 major OS releases. Maybe tweeting would help getting priorities right.

            Sorin Sbarnea added a comment - Also confirmed on 10.14, so reached a point where this bug was not fixed while Apple did 4 major OS releases. Maybe tweeting would help getting priorities right.

            Confirmed on 10.13.4

            I'll see whether we can get it into the release in progress or if we'll wait a little bit and bundle with other fixes.

            Brian Ganninger (Inactive) added a comment - Confirmed on 10.13.4 I'll see whether we can get it into the release in progress or if we'll wait a little bit and bundle with other fixes.

            Andrey Saksonov added a comment - - edited

            Looks like this affects all Homebrew users and connected with /usr/local/bin permissions set by brew. However, you can use `brew cask` which will handle symlinks for command-line tools automatically: `brew cask install sourcetree` (you can use `stree` from command line immediately). So I am not sure this should be considered a Sourcetree bug, just use brew-way installation if you use Homebrew on the machine to avoid this.

            Andrey Saksonov added a comment - - edited Looks like this affects all Homebrew users and connected with /usr/local/bin permissions set by brew. However, you can use `brew cask` which will handle symlinks for command-line tools automatically: `brew cask install sourcetree` (you can use `stree` from command line immediately). So I am not sure this should be considered a Sourcetree bug, just use brew-way installation if you use Homebrew on the machine to avoid this.

              bganninger Brian Ganninger (Inactive)
              vchoo Vivian C
              Affected customers:
              66 This affects my team
              Watchers:
              60 Start watching this issue

                Created:
                Updated:
                Resolved: