Mark Bohlman wrote:
> Max,
>
> Looks like I was a bit premature in being happy about the cygwin
> version. Initial testing with the following file:/// access command did
> not work.
>
> $ svn ls file:///ap
> svn: Unable to open an ra_local session to URL
> svn: Unable to open repository 'file:///ap'
>
> The native Windows build does work still:
> $ ./svn ls file:///ap
> t3/
> test/
> xml/
>
> Note that this was a repository that was built with the native Windows
> version of code.
>
> Building a repository with the Cygwin version of svnadmin generates the
> following error message when trying to access it with the native Windows
> svn command:
> $ svnadmin create /ap1
> #import some files
>
> $ svn ls file:///ap1
> t3/
> test/
> xml/
>
> # in the Windows version (e.g. Program Files/Subversion/bin/)
> $ ./svn ls file:///ap1
> svn: Unable to open an ra_local session to URL
> svn: Unable to open repository 'file:///ap1'
> svn: Berkeley DB error while opening environment for filesystem /ap1/db:
> Invalid argument
>
> So it looks like the modes of code being used cannot be mixed.
Ah, yes. Cygwin and native Windows are effectively different OSes as far as BDB is concerned.
Therefore, the format of shared region files (__db.00*) is not compatible between the two.
I do not run into this problem, because I'm so acclimated to a bash shell, I find the Windows cmd shell intolerable, and everything
in subversion.
If you need to access a repository via both a native Windows and a Cygwin client, you must use svn:// or http:// access for the
client which does not match the repository in terms of native/Cygwin. You may switch a repository from native to Cygwin and back
again by *making sure it is not being accessed* and running "svnadmin recover" on it.
Max.
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Received on Wed Jun 30 18:25:09 2004