On Friday 03 October 2008 14:59:41 you wrote:
> Dear Bogdan,
>
> now when I try
> [root_at_staging ~]# svn co svn://192.168.1.250/ble /home/developer/svntest/
> Authentication realm: <svn://192.168.1.250:3690> My First Repository
> Password for 'root':
>
> What is the password it is asking for?
>
> Thanks and Regards
>
> marky
Hi Marky
Your repository is not yet configured. Go to /home/svn/ble and you should
see a folder conf which contains svnserve.conf file. Modify this file to suit
your needs. I don't use this option, but it should be enough to enable
anonymous access for this repository:
anon-access = write
As someone else suggested, use subversion help to learn how to configure
svnserve.
regards
Bogdan
>
> On Fri, Oct 3, 2008 at 5:13 PM, Bogdan Cristea <cristeab_at_gmail.com> wrote:
> > On Friday 03 October 2008 14:36:27 you wrote:
> > > 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.
> >
> > This could be a mistake if ble is a repository. You should give to
> > svnserve the path to the folder hosting your repositories:
> > svnserver -d –r /home/svn
> >
> > > Then I svn co svn://192.168.1.250/home/svn/ble /home/developer/svntest/
> > > ….Please correct me if I am wrong.
> >
> > If ble is your repository, then:
> > svn co svn://192.168.1.250/ble /home/developer/svntest/
> >
> > The path from ble above in the folders tree is already given as argument
> > to svnserve.
> >
> > > 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"
> >
> > --
> > Bogdan Cristea
> > software engineer
> > Sytron Technologies Overseas
> > www.sytron.ro
--
Bogdan Cristea
software engineer
Sytron Technologies Overseas
www.sytron.ro
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe_at_subversion.tigris.org
For additional commands, e-mail: users-help_at_subversion.tigris.org
Received on 2008-10-03 14:05:18 CEST