[ 
https://issues.apache.org/jira/browse/SVN-4678?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Johan Corveleyn resolved SVN-4678.
----------------------------------
    Resolution: Invalid

I'm sorry, but I'm closing your issue as "Invalid" for now. As I mentioned 
already in my previous comment, you should report your issue to our 
[email protected] mailinglist, which is a much better place for 
troubleshooting. We use the issue tracker only for new confirmed bugs, after 
discussion / validation on our mailinglist (see the big orange box on 
http://subversion.apache.org/reporting-issues.html).

So please send the same information to our users-mailinglist and we'll try to 
help you there (you don't need to be subscribed to the list to send to it; but 
if you're not subscribed please mention it in your post, so you'll be cc'ed on 
replies).

> Checksum Mismatch Error on checkout, update, commit
> ---------------------------------------------------
>
>                 Key: SVN-4678
>                 URL: https://issues.apache.org/jira/browse/SVN-4678
>             Project: Subversion
>          Issue Type: Bug
>          Components: unknown
>    Affects Versions: 1.8.16
>         Environment: Windows 8.1,10
> Tortoise SVN 1.9.4
> SVN 1.8.16
> Laptop- Dell
> Antivirus- Symentac Endpoint Protection
> DLP- Symentac Endpoint Protection
>            Reporter: Sumit Kumar Katiyar
>            Priority: Blocker
>              Labels: check-in, chekcout, commit, update
>         Attachments: screenshot-1.png, screenshot-2.png
>
>
> We have 6 repository on SVN Server all have java code but in one there is 
> .net code.
> All the users who used that .net code's repository are facing problem in 
> SVN-Checkout, SVN-Commit and SVN-Update the problem that all are faced is 
> cheksum mismatch error while updating, commiting and chekout.
> Kindly fix this.
> And this error is not come not only single file every time this will come on 
> new file.



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

Reply via email to