[svn.haxx.se] · SVN Dev · SVN Users · SVN Org · TSVN Dev · TSVN Users · Subclipse Dev · Subclipse Users · this month's index

RE: Commit Error using ms onedrive repo

From: Bert Huijben <bert_at_qqmail.nl>
Date: Sun, 14 Feb 2016 18:15:41 +0100

> -----Original Message-----
> From: dennisj2 [mailto:djorgens2_at_gmail.com]
> Sent: zondag 14 februari 2016 01:22
> To: users_at_subversion.apache.org
> Subject: Commit Error using ms onedrive repo
>
> I have a basic cloud setup, primary windows 10 client with onedrive
> installed, and a remote server pointing to the onedrive url - I have full
> access to the repository and can update, export, et.al., but cannot commit
> changes made on the remote server. I get the following errors:
>
> <http://subversion.1072662.n5.nabble.com/file/n196123/svn-error.png>
>
> Thought this was going to be easy, thought wrong. Help?

file:/// access to a repository really needs a real filesystem behind the
local path you use. Onedrive (when mapped as a drive letter) doesn't provide
the proper filesystem semantics needed to directy store a Subversion
filesystem.

I wouldn't recommend storing a Subversion repository in a local directory
shadowed to onedrive/dropbox/other-store via its app either, as that doesn't
provide the necessary guarantees either.

Subversion really needs full read, write, lock, move, etc. access to the
repository to guarantee stable behavior.

If you want to run Subversion against some cloud you should install some
server (Apache Httpd, svnserve) in the cloud and use a proper network layer
to access it. File based repository access isn't designed for that scenario,
and will most likely cause problems if you somehow get it running...

The documentation even documents that you shouldn't run repositories on
network drives that don't provide the necessary ACID behavior.

        Bert
Received on 2016-02-14 18:15:57 CET

This is an archived mail posted to the Subversion Users mailing list.