I'm having this issue when committing to SourceForge using TortoiseSVN:
https://sourceforge.net/p/forge/site-support/2636/
The feedback on that page recommends using SSH to get around the problem. So, I relocated my repository to this URL per the recommendation:
svn+ssh://mikh2161#svn.code.sf.net/p/datsville/code
My username is mikh2161 and the project is called "datsville". When I try to connect it asks me for my password, which I then enter. It seems to work okay. However, the actual commit fails with this error:
Commit failed (details follow):
Stream doesn't support this capability
Polling for available data on filestream failed: Bad file descriptor
Can anyone assist me? What am I doing wrong? Thanks!
I'm running Windows 7 Pro x64.
TortoiseSVN 1.9.0, Build 26652 - 64 Bit , 2015/08/03 19:33:09
Subversion 1.9.0, -release
apr 1.5.2
apr-util 1.5.4
serf 1.3.8
OpenSSL 1.0.2d 9 Jul 2015
zlib 1.2.8
SQLite 3.8.11.1
Looks like svn+ssh support is broken in 1.9.0.
I removed that, and used 1.8.11 instead, and it worked.
This problem is caused by the Subversion client libraries for Windows. It was introduced with version 1.9.0, and the fix will be released with 1.9.1 [1] [2] . So any windows client that is using it will not work with svn+ssh. TortoiseSVN is just one example, the same was observed with JavaHL/Subclipse, SmartSVN and the Subversion command line client itself.
Update: A downgrade to version 1.8.12 (which was released along with 1.9.0) helped in my case.[3]
[1] Subversion Dev: JavaHL, 1.9: "Bad file descriptor", "Stream doesn't support this capability" errors
[2] fixed with r1696225 (there is obviously no bug filed yet)
[3] TortoiseSVN - Browse Files at SourceForge.net
Related
This is really strange - I've found no help in the documentation, nor can we replicate the error on a machine of a similar build. The gcloud CLI has worked without any error on my Python 3 machine for months.
After today's update, any gcloud command is met with the below error message, looking for a Python 2.7 interpreter. I'm at a loss as to how to proceed - even when attempting to uninstall with the gcloud command the same error is thrown.
This is a known issue that is being tracked here
Version 2.74 installation is broken on Windows. You will need to install an older version. This can be fixed by hand-editing gcloud.cmd but I do not recommend this.
Use the following link to download a previous version after uninstalling the current version.
Installing from versioned archives
[UPDATE 12/30/2019]
Google has released a minor revision update that appears to fix this problem. The revised update is version 2.74.0.1.
I've downloaded MongoDB Community Edition for Windows from mongodb.org (Windows 64-bit 2008 R2+), and website says that this version has SSL support (there are alerts on other versions that say they haven't). I'm running Windows 10. From what I've understood, SSL is build in by default from version 3.0, and I'm running with an Ubuntu server a mongod Community Edition instance (64bit, 3.0.10) installed from repository that use SSL.
When I try to run mongo.exe on local Windows machine with --ssl parameter it says:
Error parsing command line: unrecognised option '--ssl'
and others tools say that it doesn't support ssl.
I'm sure that on a previous setup I was running a 3.0.x mongo instance with SSL support on windows, I've tried also to install older versions, but nothing works.
My questions: are 3.0 and 3.2 community edition branches (still) compiled with SSL support on Windows, and if yes, why they doesn't work on my current setup? I'm sure they worked on previous one, may be a configuration problem?
Not sure why the Downloads page links to the Non SSL bundle. The Official Help page indicates the installer file name is mongodb-win32-x86_64-2008plus-ssl-3.2.4-signed.msi which is not the same as the one downloaded via Downloads page (mongodb-win32-x86_64-3.2.4-signed.msi). Get the SSL enabled installer from https://www.mongodb.org/dl/win32/x86_64-2008plus-ssl
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 :)
I want to install Apache server on Windows.
The book says that i can go to official site http://httpd.apache.org/download.cgi and download latest Apache version (Book year 2008, and in example showed 2.2.9v, and this example how to install on Windows, not Linux). So i go to this address, and there latest version 2.4.7, but its .tar.bz2 and .tar.gz extension, and how i understand it will be difficult to install it cause its on Linux, for Windows must be .msi, but there no file with that extension, only 2.0.65 version and older. I understand that in Linux maybe appear earlier Apache version, but how it's real that in 2008 year, there was 2.2.9 version, but now in 2014 the latest .msi version 2.0.65 ?
Easy! Here you go:
http://www.apachelounge.com/download/
You'll find the latest Apache HTTP server's there pre-built for you (Binaries).
Edit: They are not provided in .MSI files like Apache would but you can unzip the files to C:\Apache2 and set it up manually, like a true developer!
I have set up CollabNet Subversion and now I am trying to check-out some repository from my Mac 10.8.2. I have checked-out the repository successfully from a Windows 7 using the exact same command on the same network:
svn co https://myserver.com/svn/repository repository --username=USERNAME
On Mac OS I get the error:
svn: OPTIONS of 'https://myserver.com/svn/repository': SSL handshake failed: SSL error code -1/1/336032856 (https://myserver.com)
BTW: I can access the repository from the Safari Browser with the same URL.
I could not find anything about the error code.
I am running on Mac OS 10.8.2
svn, version 1.6.18 (r1303927)
compiled Aug 4 2012, 19:46:53
OpenSSL 1.0.1c 10 May 2012
which all came with the XCode Developer Tools.
Has anybody an idea what is going on or can recommend any solutions?
The SubvesionEdge Server software version is: 3.2.2-3395.103 with Subversion version: 1.7.8-3395.103, OpenSSL on Server: 1.0.0j
Who was able get svn check-out working on Mac OS 10.8.2 and which version of svn, openssl and SubversionEdge did you use?
Thanks,
Nelson
That error code looks bogus (336032856 is 0xC84A8B70):
$ openssl errstr 0xC84A8B70
error:C84A8B70:lib(200):func(1192):reason(2928)
Usually you get a somewhat useful string, like the reason, the source file and line number.
OpenSSL on Server: 1.0.0j
That's a TLS 1.1 server.
OpenSSL 1.0.1c 10 May 2012
That's a TLS 1.2 client.
They should inter-operate OK.
Try dropping the --username=USERNAME, and let svn prompt you for it when needed.
Did you get prompted to trust the the certificate? Perhaps the SVN server is misconfigured.
Finally, Super User might be a better place for this. (I personally don't care, but there are folks who like to close questions and downvote for any reason. They hunt in packs).