both svn versions were 1.5.5 built from source code... the svn repo was moved with the raw method (has worked before). I want to go try the dump/load method, but host failed to heed my request to leave the older server active for a bit - so trying to see if it can be turned back on... For grins, I did do a dump/load from the svn on the new server to a new repo to see what happens since svn is working on the new server (except for commits)... got the same result (not really surprising)
the format file in svn has a 5 in it... sorry, subversion python binding? mod_python? Thanks! On May 9, 4:55 pm, Emmanuel Blot <[email protected]> wrote: > > Resyncing repository history... > > Command failed: Couldn't open Subversion repository /svn: > > SubversionException: ("Expected FS format '2'; found format '3'", > > 160043) > > It looks like you are using a wrong version of Subversion on the > server, a version that does not match the version that has been used > to create and manage the repository. > > Did you move your SVN repository using a "raw" method (save/restore > SVN directories), or did you use the "proper" method (svnadmin dump & > svnadmin load) ? > > I don't remember which SVN FS version numbering scheme, but it's something > like: > FS v2: SVN 1.4 > FS v3: SVN 1.5 (+upgrade) > FS v4: SVN 1.6 (+upgrade) > > Cross check that the Subversion Python binding you use do match the > SVN repository FS format. > > HTH > Manu --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Trac Users" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [email protected] For more options, visit this group at http://groups.google.com/group/trac-users?hl=en -~----------~----~----~----~------~----~------~--~---
