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

Re: svn co issue

From: Anto Marky <markysvn_at_gmail.com>
Date: Fri, 3 Oct 2008 17:06:27 +0530

Hi Bogdan,

I use a single repository without the native svn format trunk-branches, I
have created repository in /home/svn/ble and imported my files into the
repository.

I invoke svn using svnserver -d –r /home/svn/ble.

Then I svn co svn://192.168.1.250/home/svn/ble /home/developer/svntest/
….Please correct me if I am wrong.

Hi Marc,

I was doing a blunder mistake, I was trying the "svn status" in the
repository. I know I should read the book before I start doing this but my
superiors have assigned a task for me to create a production repository
before this weekend.

Hi Rayan,

It was a typo mistake, copied the error from the wrong machine, my actual
repository is in /home/svn/ble

My Current Scenario is as follows,

I have to set up a svn repository in my local linux box where my developers
would get their working copy from.

I have remote web server which would also take the latest update from the
repository(This will be done manually).This web server would be running on
linux and my developers would be using windows .

This is what I am trying to do, Now my developers are able to get their
working copy and are able to commit. My problem is, I am not able to check
out from my remote web server.

Am I going on the right path? Please suggest.

Thanks and regards

Marky

On Fri, Oct 3, 2008 at 4:04 PM, Ryan Schmidt <
subversion-2008c_at_ryandesign.com> wrote:

>
> On Oct 3, 2008, at 4:57 AM, Anto Marky wrote:
>
> I posted the below error earlier still hanging on with it, When I tried svn
>> status from my repository directory it gives an error like this -svn:
>> warning: '.' is not a working copy.
>>
>
> That warning is of course completely correct. Your repository directory is
> not a working copy, nor should it be; running "svn status" in your
> repository directory is not useful.
>
> Does anybody know what is happening? Could anybody please help me resolve
>> this issue?
>>
>> On Oct 3, 2008, at 2:30 AM, Bogdan Cristea wrote:
>>
>> On Friday 03 October 2008 10:13:03 Anto Marky wrote:
>>>
>>> > I created a repository under my /home/svn/ directory, I have edited my
>>> > svnserver.conf and changed the auth-access to reade write, and passwd
>>> file
>>> > to passwd and have added users to my passwd file.I am able to checkout
>>> and
>>> > commit from my windows machines.But when I try svn co with the command
>>> ,
>>> > svn co svn://192.168.1.250/home/svn/ble /home/developer/svntest/, I
>>> get the
>>>
>>> That command is wrong:
>>> after the IP address you should use your repository name, then the path
>>> in
>>> your repo, something like:
>>> svn://192.168.1.250/repo_name/trunk .
>>>
>>> > error svn: No repository found in 'svn://
>>> > 192.168.1.250/home/svn/blenglishcafe'.
>>>
>>
> I don't understand why if your checkout command referenced "ble" the error
> message references "blenglishcafe".
>
> > I even tried svn co --username {user} --password {password} svn://
>> > 192.168.1.250/englishcafe/ /home/developer/svntest/ that one too gives
>> the
>> > same error. When I try svnlook tree svn://192.168.1.250/home/svn/ble I
>> can
>> > see all the files and directories, When I try svn ls svn://
>> > 192.168.1.250/home/svn/ble I am able to see the repositories.I started
>> the
>> > dameon a svnserve -d -r /home/svn/ (I have one more repository inside
>> > /home/svn which bld).
>>
>
> Bogdan is right: the URL you're trying to check out from and the path you
> passed to "svnserve -d" are not compatible. You told svnserve your
> repositories are located in /home/svn, therefore you cannot include
> "/home/svn" in the URL you're checking out.
>
> "svnlook tree svn://192.168.1.250/home/svn/ble" can't have worked; when I
> run that, it says "'svn://192.168.1.250/home/svn/ble' is a URL when it
> should be a path"
>
>
Received on 2008-10-03 13:36:53 CEST

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.