> That means your svn command is not only missing
> its SASL support, it's also missing its neon/serf
> support, without which it cannot connect to http
> repositories. You'll have to investigate why neon
> and/or serf are not present or working, and possibly
> reinstall them or your svn client.
I think the easiest and the safest thing to do is
to reinstall the entire subversion. Is there any
risk I am unaware of, that you can think of? Please
From: Ryan Schmidt [mailto:subversion-2009b_at_ryandesign.com]
Sent: Wed 10/14/2009 9:55 PM
To: Tena Sakai
Subject: Re: svnadmin: Expected repository format '3' or '5'; found format '4'
On Oct 14, 2009, at 23:39, Tena Sakai wrote:
>> This still won't work because you're still trying
>> to access the repository files directly, using a
>> file:-protocol URL. Instead, access the repository
>> by going through the apache server that CollabNet
>> Subversion has set up for you, using the repository's
>> http:-protocol URL shown to you above.
>> $ svn import ~/Projects/pivot http://vixen.egcrc.org:8099/svn/
>> tsakai -m "initial import"
> I just did:
> $ svn import -m "initial import" ~/Projects/pivot http://vixen.egcrc.org:8099/svn/tsakai
> and it is not happy:
> svn: Unrecognized URL scheme for 'http://vixen.egcrc.org:8099/svn/
That means your svn command is not only missing its SASL support, it's
also missing its neon/serf support, without which it cannot connect to
http repositories. You'll have to investigate why neon and/or serf are
not present or working, and possibly reinstall them or your svn client.
To unsubscribe from this discussion, e-mail: [users-unsubscribe_at_subversion.tigris.org].
Received on 2009-10-15 07:48:25 CEST