[svn.haxx.se] · SVN Dev · SVN Users · SVN Org · TSVN Dev · TSVN Users · Subclipse Dev · Subclipse Users · this month's index

Re: locked out of my svn 1.1.4 repository

From: Ryan Schmidt <subversion-2006c_at_ryandesign.com>
Date: 2006-08-12 13:22:16 CEST

On Aug 12, 2006, at 06:15, Michael Driscoll wrote:

> i recently created my first SVN repository and imported my files
> into it, but i cannot checkout those files. i'm running svn,
> version 1.1.4 (r13838), with berkeley DB version 4.2.52-7.1, on a
> fedora core 4 machine.

Ideally, you should have been using the latest version of Subversion,
which is currently 1.3.2, and I personally would have recommended not
using BerkeleyDB (it's no longer the default as of Subversion 1.2.0).
But now that you have an issue, probably best to fix it before trying
to upgrade anything.

> so i went and ran 'svnadmin recover' on this, and it did something, i
> suppose.
>
> gtp:/svn/affydb/db$ svnadmin recover /svn/affydb/
> Repository lock acquired.
> Please wait; recovering the repository may take some time...
>
> Recovery completed.
> The latest repos revision is 0.
>
> now, however, when i checkout files, i get no errors
>
> gtp:~$ svn co file:///svn/affydb
> Checked out revision 0.
>
> but to my chagrin, the checked out directory that is created
> 'affydb', is empty.

Revision 0? That's the revision before you check anything in. A
repository at revision 0 contains no data. Unfortunately I can't
offer any advice since I haven't had to recover a repository before
and I've never worked with the BerkeleyDB backend... But many on the
list have experience with BDB so hopefully someone will have an idea.

---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Received on Sat Aug 12 13:23:45 2006

This is an archived mail posted to the Subversion Users mailing list.

This site is subject to the Apache Privacy Policy and the Apache Public Forum Archive Policy.