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

Re: Import Problems...

From: <cmpilato_at_collab.net>
Date: 2002-01-22 17:35:00 CET

Shaun Deacon <sdeacon@fma.fujitsu.com> writes:

> My problem is importing into a locally created repository. I
> get the following error :
>
> > svn_error: #21085 : <URL is not a versioned resource>
> > svn_ra_local__split_URL: Unable to find valid repository

Hrm...I usually expect to see this when you don't have ra_local, but
you do. Or, when permissions are all wrong, but I doubt they are (so
long as you were running the import as sdeacon:wwslt).

> I created a repository using :
>
> $ svnadmin create /home/sdeacon/svn_repository

Yep, doesn't get much easier than that.

> The create seemed to work OK - the top level contents of
> the repository are :
>
> > drwxrwxrwx 7 sdeacon wwslt 96 Jan 17 17:07 .
> > drwxr-xr-x 57 sdeacon wwslt 8192 Jan 17 17:11 ..
> > -rw-rw-rw- 1 sdeacon wwslt 285 Jan 17 17:07 README
> > drwxrwxrwx 2 sdeacon wwslt 96 Jan 17 17:07 conf
> > drwxrwxrwx 2 sdeacon wwslt 96 Jan 17 17:07 dav
> > drwxrwxrwx 2 sdeacon wwslt 8192 Jan 17 17:07 db
> > drwxrwxrwx 2 sdeacon wwslt 8192 Jan 17 17:07 hooks
> > drwxrwxrwx 2 sdeacon wwslt 96 Jan 17 17:07 locks

Looks good so far.

> The following command produces the problem :
>
> $ svn import file:///home/sdeacon/svn_repository test/data

This looks good, too.

My only suggestion at this point is run "ld" (or its equivalant on
whatever system you are on) to verify that both svnadmin and svn are
linking against Berkeley 4.0. Also, use the appropriate Berkeley util
(db_status, maybe? can't recall) to verify that the environment you
created had the right DB version.

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Sat Oct 21 14:36:58 2006

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

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