search

palimadra / svnx

Automatically exported from code.google.com/p/svnx
0 stars 0 forks source link

Error "Can't set position pointer in file C:\Windows..." when Updating repository on mac #191

Closed GoogleCodeExporter closed 9 years ago

GoogleCodeExporter commented 9 years ago 
svn: Can't set position pointer in file 
'C:\Windows\SERVIC~2\NETWOR~1\AppData\Local\Temp\tempfile.2.tmp': There is not 
enough space on the disk.  

What steps will reproduce the problem?
1. I had revision 100*
2. Then made some changes
3. I wanted to update revision 101 and having the problem

(it's not really 100, number is just for instance)

What is the expected output? What do you see instead?
>I'd like to have my working copy updated. It's really strange that SvnX tries 
to open/modify file on _that_ path.

What version of the product are you using? On what operating system?
>1.3.4 SvnX on Mac OS X 10.8.2
> svn, version 1.6.18 (r1303927)

Please provide any additional information below.
> It worked a while ago but now it doesn't.  I didn't change anything expect 
repository files.

Original issue reported on code.google.com by Yuriy...@gmail.com on 19 Nov 2012 at 8:22

GoogleCodeExporter commented 9 years ago 
I'm able to update each file individually but its inconvenient. I thought it 
might be a server error (it runs on Windows) but Tortoise SVN was able to 
update entire working copy.

Original comment by Yuriy...@gmail.com on 19 Nov 2012 at 8:33

GoogleCodeExporter commented 9 years ago 
SvnX is a Mac application.  It does nothing with Windows paths.
Besides - checking out with svnX it simply executes `svn checkout …`.
Therefore, the error is most probably at the server end.
Have you checked that there is “enough space on the disk” on the server?
Are you working with large files?  ≥ 2GB?

Original comment by chris...@gmail.com on 19 Nov 2012 at 12:48

GoogleCodeExporter commented 9 years ago 
Looks like the error really was at the server, I manage to update the working 
copy right now.

However, its really strange that I could checkout repo to another location, I 
could update any individual file, and I even made full update using Tortoise, 
but SvnX ended with the error.

[Issue solved, I suggest to close this issue]

Original comment by Yuriy...@gmail.com on 19 Nov 2012 at 5:44

GoogleCodeExporter commented 9 years ago

Original comment by chris...@gmail.com on 21 May 2014 at 1:04