Hi,

I'm using svn, version 1.5.0 (r31699) on Linux Fedora Core release 4 OS,  when 
I trying committing a file I get this error message:

Sending        events/fms/index.php
Transmitting file data .svn: Commit failed (details follow):
svn: MERGE of '/repos/sites/trunk/www/STEC/aboutstec/events/fms': Could not 
read status line: Secure connection truncated (https://webbuild)

I am using Openssh openssh-4.0p1-3 and
LoadModule dav_svn_module     modules/mod_dav_svn.so
LoadModule authz_svn_module   modules/mod_authz_svn.so


I have done a lot of search, but have not found an answer to this.  Has anyone, 
seen this or know how to fix it?

Your help is greatly appreciated, since this is our development server and very 
important to get this resolved.

Best Regards,

Kathy Khaghani
Sr. Unix Admin
Office 949.476.1180 x8414 * Fax 949.851.2756

STEC, Inc. | The SSD CompanyTM
NASDAQ STEC * Web www.stec-inc.com<http://www.stec-inc.com>

[cid:image002.png@01CC5679.ACF28BF0]<http://www.facebook.com/userstecinc>[cid:image004.png@01CC5679.ACF28BF0]<http://twitter.com/#!/stec_inc>[cid:image006.png@01CC5679.ACF28BF0]<http://www.youtube.com/user/stecincssd>[cid:image008.png@01CC5679.ACF28BF0]<http://www.linkedin.com/in/stecinc>[cid:image010.png@01CC5679.ACF28BF0]<http://www.stecblog.com/>[cid:image012.png@01CC5679.ACF28BF0]<http://www.stec-inc.com/rss/>


PROPRIETARY-CONFIDENTIAL INFORMATION INCLUDED

This electronic transmission, and any documents attached hereto, may contain 
confidential, proprietary and/or legally privileged information. The 
information is intended only for use by the recipient named above. If you 
received this electronic message in error, please notify the sender and delete 
the electronic message. Any disclosure, copying, distribution, or use of the 
contents of information received in error is strictly prohibited, and violators 
will be pursued legally.

<<inline: image002.png>>

<<inline: image004.png>>

<<inline: image006.png>>

<<inline: image008.png>>

<<inline: image010.png>>

<<inline: image012.png>>

Reply via email to