svn commands hang on Mac - macos

Need a help again. Whenever I try to run any svn command from command line on MacOS X 10.7, it hangs.
I have no clue why that's happening. svn commands work fine from within IntelliJ.
Can anyone help me find out what the problem is? Any help will be very much appreciated.
Thanks

Perhaps you need to use a proxy server to talk to the SVN repository, and you've got the proxy server configured in IntelliJ but not at the command line. Here's a random blog post showing how to set up proxies for SVN command-line tools.

I was able to solve the problem by moving to newer version:
...$ svn --version
svn, version 1.6.17 (r1128011)
compiled Aug 26 2011, 09:41:54

Related

Installing Jenkins on MAC OS X El Capitan

This is probably a stupid question but I can't get Jenkins installed on my MAC. I've searched the web and tried various different tutorials but it does not seem to work for me. Moreover it seems that nobody experiences the same problem. I've downloaded the Jenkins Installer from here. After running the installation process, the script tries to connect to http://localhost:8080 but I get the error message that the browser cannot connect to the server. Can anyone help me with this?
Thanks!
And again the solution was quite simple. The connection problem arises when you either don't or you have Java < 1.7 installed. What I did:
deleted my previous Jenkins installation by running /Library/Application\ Support/Jenkins/Uninstall.command
installed JDK 8 (OS X 64bit) from here
reinstalled MAC Jenkins from here
Works fine!

Why is git slow on my windows machine?

Just typing git at the command prompt (of powershell), takes 2.5 seconds until it returns with the help message.
I'm using the git for windows release, installed in C:\Program Files (x86)\Git. When I use cygwin (via babun), I get an error: Hint: your prompt is very slow. Check the installed 'BLODA' software. Maybe this is related? If it is, I'm using a corporate laptop, so can't uninstall antivirus or driver software, are there other options?
For me the reason seemed to be the "Inject ConEmuHk" setting in cmder under which I ran git. I've opened a bug https://github.com/bliker/cmder/issues/592
Try and see if the issue persists with the latest 2.4+ git for Windows release.
There is a bug related to the git bash startup time which is actively addressed.

svn: E155021: This client is too old to work with the working copy at xxx (format '31')

I am trying to import some gradle projects in my Spring Tool Suite . I have installed Subclipse 1.10.5 in my STS and svn client installed in my machine is 1.8.8 . I have tried downgrading to 1.7.10 on my mac but still I get the same problem while importing .
For others SVN 1.7.10 and Subclipse 1.10.5 seems to work fine but in my machine I am getting the error
svn: E155021: This client is too old to work with the working copy at
'/Users/agarg/Documents/Mars/trunk' (format '31')
Stuck here for some time now and unable to resolve this . Tried a lot of things as I found over the net but still stuck.
I had this problem on Mac OS Yosemite with Webstorm and IntelliJ.
svn --version on the command line printed 1.8, but even with command line client option enabled with value svn in Webstorm/IntelliJ I was getting the warning.
Running which svn and pasting the value (/usr/local/bin/svn for me) into WebStorm->Preferences->Version Control->Subversion->Use command line client removed the warning and fixed the issues I was having in Webstorm and IntelliJ.
The working copy has format understandable by SVN 1.8 client, but your client is SVN 1.7 or older.
You should double-check what Subclipse / SVNKit / svn.exe client versions you have on your system.
Try accessing the working copy from command-line and see whether you get the same error.
If you definitely have svn installed and running at the correct version you want, this error means the metadata in your project refers to an older version of subversion. Upgrade it by following this guide: http://www.robsearles.com/2008/12/svn-client-is-too-old-to-work-with-working-copy-solution-using-rsync/
I had this same issue on OSX. I have been able to upgrade the SVN by following the step by step guide here:
URL: http://andowebsit.es/blog/noteslog.com/post/how-to-upgrade-subversion-on-osx/
First check which svn version you have:
$ svn --version
svn, version 1.7.17 (r1591372)
compiled Aug 7 2014, 17:03:25
...
Seems like its old version, so update it.
$ brew update
$ brew install subversion
This will take some seconds to install. Now check how many svn you have. You will see the another entry belew.
$ which -a svn
/usr/bin/svn
/usr/local/bin/svn
Edit the ~/.bash_profile with
export PATH="/usr/local/bin:$PATH"
And then
$ source ~/.bash_profile
$ svn --version
svn, version 1.8.10 (r1615264)
compiled Aug 25 2014, 10:57:58 on x86_64-apple-darwin13.3.0
...
Now you will see the SVN verison is upgraded from 1.7 to 1.8.
Same problem here (SVN 1.8 client on W7, STS 3.6.3, eclipse-plugin: subversive SVN Team provider 1.1.x and SVNKit Implementation 3.0.x).
Upgrading (in STS) the SVN Team provider to 2.03.x and SVNKit to 4.1.2 solved the problem.
Got this error ON MAC OS X but you believe you have available the right version?
First look at how many svn
$ which -a svn
/usr/local/bin/svn
/usr/bin/svn
/usr/local/bin/svn
Look at the output for each of the output using the --version flag. You might notice that the default which output is not the same as the default command output:
$ command -v svn
/usr/bin/svn
$ which svn
/usr/local/bin/svn
You might be tempted to update some symlinks or your PATH variable but before doing so try from a new console, it might be just that you are hitting a console open before you installed the latest version. I would even try restarting before attempting to change PATH or symlinks.
Easiest way:
1. execute which -a svn in terminal;
2. modify the enviroment file(like ~/.bash_profile), and use the older version svn;
3. checkout svn code with your older svn;
4. import it into your IDE;
5. DONE.
I had similar issue in my program while checking out code from SVN through my Java program .
TO resolve i closed the eclipse workspace and deleted the folder in which i was checking out the files on my local directory.It worked for me.
Thanks to all for their solution. I was struggling with this issue for couple of days. I had installed old version 1.7 with PC login of Cygwin environment.
Later i had to install version 1.9 because i wanted to use svn command. For most of the time i was looking for a file /.bash_profile on my PC or file which would have path usr/local/bin.
But i always found path cygwin/usr/local/bin. I kept neglecting it.
After doing so many trial and error, i took simple chance.
Went to Environment Variable PATH, and cut path "C:\Program Files\TortoiseSVN\bin\bin" and pasted before "cygwin/usr/local/bin"
And later svn --version detected my latest version 1.9 :)

Reasons why git is not visible to Rstudio (OSX)

I have been trying for a few hours to use git within Rstudio on my macbook. However, the option to use git within version control is missing - the only option remains (none).
I have installed github, and then git directly, using the link given
in the rstudio website.
I have attempted to run the bash script
supplied with the git installation file.
I have verified that git is
active on the machine through both github and directly through the
command line.
I have located the git file in the hidden folder
/local/git/bin/git
and pointed Rstudio to this using global options.
I have reinstalled git a couple of times.
I have logged off and on again multiple times.
Any solutions very welcome.
Thanks,
Jon
The same just happened on my mac. I narrowed down the issue to the Xcode developers package update. The fix in my case was:
From a shell go to /usr/bin
sudo ./git
Agree to the terms
Close and reopen RStudio
VoilĂ . Git has returned to RStudio.
My RStudio git tab disappeared after upgrading to OS X El Capitan. I tried following the advice in the top answer:
but I got the error:
xcrun: error: invalid active developer path (/Library/Developer/CommandLineTools), missing xcrun at: /Library/Developer/CommandLineTools/usr/bin/xcrun
which led me to discover I had to reinstall XCode command-line tools. I did this via:
xcode-select --install
I also updated to latest release of RStudio. Then my git tab reappeared.
I just came across your question after I encountered a similar issue on windows. You've probably sorted yourself by now but just to let you & others know what worked for me.
From RStudio Tools, Global Options.
Option for Git Executable.
Browsed to git.exe in the git/bin folder.
Now working like a dream.
Andy
It's now working. As expected it took re-installing the operating system, as well as the following:
http://blog.rstudio.org/2013/10/22/rstudio-and-os-x-10-9-mavericks/
Using the preview version available from the link below solved the Rstudio/Git issue instantly.
Same issue with OSX High Sierra
This answer in this thread on GitHub helped me
In short, OSX seems to use another directory for the git file

SVN version in Maven tasks with SVNKit on MacOS

I am getting this error in a Maven build (mvn clean install) on a Mac with Mountain Lion
org.tmatesoft.svn.core.SVNException: svn: The path 'XYZ' appears to be part of Subversion 1.7 (SVNKit 1.4) or greater
working copy rooted at '/Users/XYZ/workspace/XYZ'.
Please upgrade your Subversion (SVNKit) client to use this working copy.
I had SVN installed as part of the Apple Command Line tools package and that gets installed at /usr/bin. I have installed the latest SVN as well but that got installed at /usr/local/bin.
When the maven build runs, it does not pick up the latest SVN, it picks the older one and fails.
Has anyone faced this kind of problem before?
I think there are 2 options -
1) Somehow force maven to use the new installed SVN.
2) Upgrade the SVN installed as part of Apple' Command Line tools to the latest SVN. I have reinstalled Command Line tools with the latest version but it still sticks to the older version.
I dont control the pom.xml so modifying it is not a viable option.
Any pointers in resolving this would be much appreciated.
Thanks!
This means your svn client is version 1.7 but the working copy(your project workspace) was checkout with the older version.
It's simple by execute the following command at your project root directory, where the pom.xml is there.
svn upgrade
please note, the maven use the svn client which is in your OS path.
After upgrade you should configure your IDE to use the version 1.7 as well. In my case I use the Eclipes Juno sr1 with Svnkit.
Anyhow if you would not like to change the working copy or IDE configuration. There is an alternative by install the svn clinet 1.4/1.5/1.6 and set it active via OS path instead.
I hope this may help.
Regards,
Charlee Ch.

Resources