Eric Carlson wrote:
>> Eric did the file:// method of checking out work? E.g.
>>
>> svn co file:///j2me delme
>
> Yes - perfectly, as well as the url based way using localhost.
>
> There is an issue here you guys might (like to?) be aware of, but its
> something I can live with. I mentioned I'm moving from Windows to
> Linux. Well it seems the repositories are not compatible, or more
> likely my process is flawed. What I did was mount the linux folder as
> a samba share on the Windows box and drag the repositories over (svn
> was stopped, created copies). The files seemed ok. I started svnserve
> (don't use Apache) and tried a checkout - it failed, I got the same
> Berkely db error I originally reported. So I used svnadmin to create a
> new repos in Linux and that was fine, its the one I've been doing
> these tests with. Similarly browsign the ex-windows repositories from
> a remote client using Tortoise fails, the nbew native ones are fine.
> (with that it connects but I just get the word "Dummy" in the panel).
>
> I actually used windows just to test svn having moved from SourceSafe.
> Its passed :-) So its really only lightly loaded, and recreating the
> repositories manually doesn't cause too much pain. I can see it could
> in other circumstances though. Does it sound like the copy process I
> used was at fault, or is there a platform issue here?
You can move repositories between OSes providing the source and destination machines have the same byte order (i.e.
big-endian/little-endian). *But* you need to "svnadmin recover" the repository on the new machine to rewrite the Berkeley DB shared
memory backing files to be compatible with the new OS.
Max.
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Received on Fri Jul 9 12:33:03 2004