Menu
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://[email protected]/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
629
Assembla supports connecting to SVN repositories using SVN+SSH protocol, which provides security advantages. In this section we will discuss how you can set up your SVN client to use this protocol on Linux, Mac, and Windows computers.
Locate TortoiseSVN and click on it. Select "Change" from the options available. Refer to this image for further steps. After completion of the command line client tools, open a command prompt and type svn help to check the successful install.
You can either store your repositories locally and access them using the file:// protocol or you can place them on a server and access them with the http:// or svn:// protocols. The two server protocols can also be encrypted. You use https:// or svn+ssh:// , or you can use svn:// with SASL.
Looks like svn+ssh support is broken in 1.9.0. I removed that, and used 1.8.11 instead, and it worked.
199
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
25
If you love us? You can donate to us via Paypal or buy me a coffee so we can maintain and grow! Thank you!
Donate Us With
