On Jun 7, 2006, at 19:08, Bjorn Townsend wrote:
> Mac users of my SVN repository (myself included) are encountering an
> error when checking out large source trees from SVN. Smaller trees
> seem to check out without any problems -- it's only when a large
> checkout is being done that problems occur. This issue has not been
> reported by users of other operating systems, though we don't have
> very many, so the sample size may be inadequate.
>
> Here is the error I get:
>
> A sysad/website/html/pdfs/
> SourceLabsMySQLInnoDBScalabilityReport.pdf
> A sysad/website/html/pdfs/SLPR0206.pdf.LCK
> A sysad/website/html/pdfs/SLPR0306.pdf.LCK
> A sysad/website/html/pdfs/PHP4vsPHP5.pdf
> A sysad/website/html/pdfs/
> SpecialConsiderationsForFinancialServices.pdf
> subversion/libsvn_wc/log.c:338: (apr_err=155009)
> svn: In directory 'sysad/website/html/pdfs'
> subversion/libsvn_subr/io.c:565: (apr_err=2)
> svn: Can't copy 'sysad/website/html/pdfs/.svn/tmp/text-base/
> slpr0205.pdf.svn-base' to 'sysad/website/html/pdfs/slpr0205.pdf.tmp':
> No such file or directory
>
> I'm using OSX 10.4.6 with version 1.3.0 of the svn client. The svn
> server (a Fedora Core 4 box) is running version 1.1.3 -- could this be
> a backwards compatibility issue? Might upgrading the svn server to
> 1.3.x resolve the issue?
>
> I've checked the FAQ and the mailing list archives, and didn't find
> much helpful information. Someone had previously reported seeing
> something like this on Windows 2000, but it turned out to be due to
> having files with the same name but different capitalizations, which
> Windows (being case-insensitive) didn't like. I don't think that
> applies here.
Hi Bjorn. The default Mac OS X file system (HFS+) is also case-
insensitive, like whatever it is that Windows uses, so you can
certainly experience this same issue on a Mac. Do verify whether you
have, for example, both slpr0205.pdf and slpr0205.PDF (or other
variations in capitalization only) in the same directory, by using
"svn ls" on the directory's URL in the repository. If so, that
explains it. If this was unintentional, get rid of the "duplicate"
file and you're fine. If this was intentional and your project
requires multiple files whose names differ only in case, you'll have
to check out to a case-sensitive volume. On Mac OS X 10.4 you can
reformat your hard disk as case-sensitive HFS+, but that's probably
inconvenient, and I don't think Apple recommends doing that to your
startup volume anyway. Easier is to create a case-sensitive HFS+ disk
image using Disk Utility and check your working copy out to that.
AFAIK, all Subversion 1.x releases should be compatible with one
another, regardless of whether the server is newer or older than the
client. Nevertheless, 1.1.3 is old, and I would recommend upgrading
the server to 1.3.2.
You didn't say what protocol you use to access the server. http(s)?
svn? Possibly that's relevant. If you're using Apache, perhaps its
error log will provide additional insight. (svnserve, alas, has no
error log that I'm aware of.)
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Received on Wed Jun 7 21:07:29 2006