On 8 September 2015 at 13:12, Branko Čibej wrote:
> On 07.09.2015 18:42, Ivan Zhakov wrote:
>> We developed patch that converts all ERROR_ACCESS_DENIED errors from
>> SetFileInformationByHandle() to SVN_ERR_UNSUPPORTED_FEATURE and
>> fallbacks to normal close + rename() (see attached file), but I'
On 07.09.2015 18:42, Ivan Zhakov wrote:
> We developed patch that converts all ERROR_ACCESS_DENIED errors from
> SetFileInformationByHandle() to SVN_ERR_UNSUPPORTED_FEATURE and
> fallbacks to normal close + rename() (see attached file), but I'm not
> sure it's the best solution and going to investi
On 7 September 2015 at 19:45, Ivan Zhakov wrote:
> [Moving to dev@s.a.o]
>
> On 4 September 2015 at 18:15, Daniele Pedroni
> wrote:
>> After updating from 1.8.X to 1.9.X (tried also 1.9.1, no luck), TortoiseSVN
>> as well as command line throw the following error after trying to checkout
>> or co
[Moving to dev@s.a.o]
On 4 September 2015 at 18:15, Daniele Pedroni
wrote:
> After updating from 1.8.X to 1.9.X (tried also 1.9.1, no luck), TortoiseSVN
> as well as command line throw the following error after trying to checkout
> or commit a Working Directory on a network share:
>
> Commit fail
[Moving to dev@s.a.o]
On 4 September 2015 at 18:15, Daniele Pedroni
wrote:
> After updating from 1.8.X to 1.9.X (tried also 1.9.1, no luck), TortoiseSVN
> as well as command line throw the following error after trying to checkout
> or commit a Working Directory on a network share:
>
> Commit fail
On 7 September 2015 at 11:12, Daniele Pedroni
wrote:
> Hi Ivan,
>
> thank you very much, but honestly speaking I don't know how to test it: I
> installed SVN server through Redmine Bitnami package, and I update SVN on my
> PC using TortoiseSVN installer.
> If you provide me some suggestions abou
On 4 September 2015 at 18:15, Daniele Pedroni
wrote:
> After updating from 1.8.X to 1.9.X (tried also 1.9.1, no luck), TortoiseSVN
> as well as command line throw the following error after trying to checkout
> or commit a Working Directory on a network share:
>
> Commit failed (details follow):
>
I have no problem using Subversion on 1.9.x on network drives, testing to
Windows servers and to Samba 4.x, so clearly not everyone using Subversion on a
network drive has this problem.
Perhaps you tried to say that most users seeing this problem have it on a
network drive?
Are there oth
