RE: Error after subversion upgrade

The main problem is that I didn't do the upgrade (and I'll admit that I don't know much about the administration of subversion). I can see that a dump file of the old repository was created. I also see a directory that appears to be a backup of the old repos directory. There is a new repos directory in place. Is it safe to do a load of the dump file? What will happen if this was already done?

Thanks,

Nicole
---------------------------
Nicole Swan
Web Programming Specialist
Carroll College CCIT
(406)447-4310

-----Original Message-----
From: Eric Hanchrow [mailto:offby1@blarg.net]
Sent: Tuesday, June 22, 2004 11:28 AM
To: Swan, Nicole
Subject: Re: Error after subversion upgrade

>>>>> "NS" == Swan, Nicole <NSwan@carroll.edu> writes:

    NS> After a recent upgrade of subversion from .37 (I believe) to
    NS> 1.0.5, I cannot commit back to the repository.

I don't know if this is the cause of your exact problem, but: I'm
pretty sure you need to upgrade your database. It's not too painful:

* reinstall 0.37 or whatever version you had

* do `svnadmin dump /your/repos > big-dump'

* remove 0.37, install 1.0.5

* move old repository out of the way: `mv /your/repos
  /your/repos.backup'

* `svnadmin create /your/repos'

* `svnadmin load /your/repos < big-dump'

-- 
Governing the U.S. is like playing 200 simultaneous chess
matches (while whiny columnists second-guess every move on every
board).
        -- Nicholas Kristof, New York Times columnist
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org