Marc,
I will try this out this evening (I'm on my way out right now). At
least I am not losing my mind! Thank-you for testing this and
confirming the situation. Is this a SVN problem or a SmartSVN problem
and should I report it as a bug? Or, could it be a Windows
restriction on c:/ ?
Since I have 2 repositories, would the project be setup as
svn://localhost/someFolder/RecordsRepository (and similiarly for
ProjectsRepository)?
Many thanks for your help!
--
Geoff Wass
--- In smartsvn%40yahoogroups.com">smartsvn
yahoogroups.com, Marc Strapetz <marc.strapetz
...>
wrote:
>
> Hi Geoff,
>
> > I think the problem is the c:/ to which I have svnServe pointing
OR
> > that I have to reference my repositories in subFolders (ex:
> > c:/RecordsRepository).
>
> Interestingly I also have problems with repositories directly at c:
>
> svnserve -r c:/ -d
>
> does not work for me. However when moving the repositories to
c:temp
>
> svnserve -r c:/temp -d
>
> works for me.
>
> --
> Best regards,
> Marc Strapetz
> _____________
> syntevo.com
>
>
>
> geoff.wass wrote:
> > --- In smartsvn%40yahoogroups.com">smartsvn
yahoogroups.com, Marc Strapetz <marc.strapetz
>
> > wrote:
> >> Hello Geoff,
> >>
> >>> svnAdmin create c:RecordsRepository
> >>> svnAdmin create c:ProjectsRepository
> >> Please start
> >>
> >> svnserve -r c: -d
> >>
> >> from the command line ...
> >>
> >>> What should I be entering for "Server Name" and "Repository
Path"
> >>> when I want to add a Repository Profile if I am using the SVN
> > server
> >>> (svn:// protocol)?
> >> ... and on "Location" page use "Enter SVN URL" and
> > enter "svn://localhost".
> >> --
> >> Best regards,
> >> Marc Strapetz
> >> _____________
> >> syntevo.com
> >>
> >>
> >> geoff.wass wrote:
> >>> Hello everyone,
> >>>
> >>> I am very, very new to SmartSVN and Subversion. I am using
WinXP
> > SP2
> >>> with Subversion 1.4.3 and SmartSVN 2.1.8. I have everything
> > installed
> >>> on my computer (SVN, SmartSVN and the repositories) in the c:
> > drive.
> >>> I am using the SVN server.
> >>>
> >>> I seem to have Subversion installed correctly because I was
able
> > to
> >>> use svnAdmin to create the two repositories I want to start
with
> >>> (and, yes, I do want them to be separate). Here is what I did
to
> > make
> >>> the Subversion server:
> >>>
> >>> (all one line)
> >>> sc create svnServer binpath= ""C:Program
> >>> FilesSubversionbinsvnserve.exe" --service --root c: "
> >>> displayname= "Subversion Repository Server" depend= Tcpip
> >>>
> >>> Note, I needed to leave a space after the c: to get it to work.
> >>>
> >>> I used this to create the repositories and they were created as
> >>> expected:
> >>>
> >>> svnAdmin create c:RecordsRepository
> >>> svnAdmin create c:ProjectsRepository
> >>>
> >>> Now, I have SmartSVN installed and I want to create two
> > Repository
> >>> Profiles (one for each) and this is where I am running into
> > problems.
> >>> When I go into Repository Profiles and click "Add", I am having
> >>> trouble filling the first tab ("location").
> >>>
> >>> I did this:
> >>>
> >>> (1) Access Method: SVN
> >>> (2) Server name: localhost
> >>> (3) Repository Path: RecordsRepository (or
ProjectsRepository)
> >>> (4) Server port: default
> >>> (5) On the second tab ("Details") I chose user/password and
> > entered
> >>> them
> >>>
> >>> When I click "Next", the verification process comes back with
> > this
> >>> message:
> >>>
> >>> svn: No repository found in 'svn://localhost/RecordsRepository'
> >>>
> >>> I can use "svnadmin verify c:RecordsRepository" to confirm the
> >>> repository is there and fine.
> >>>
> >>> ---
> >>>
> >>> As an aside, if I do something stupid like this (put the c:
into
> > the
> >>> path):
> >>>
> >>> (1) Access Method: SVN
> >>> (2) Server name: localhost
> >>> (3) Repository Path: c:RecordsRepository
> >>>
> >>> I get this error message:
> >>>
> >>> svn: Can't open file 'C:WINDOWSsystem32
> >>> c:RecordsRepositoryformat': The filename, directory name, or
> >>> volume label syntax is incorrect.
> >>>
> >>> I don't dispute the error, but find it interesting that it
> >>> adds "WINDOWSsystem32" and "format" to the path name. Perhaps
> > it is
> >>> a clue to my problem?
> >>>
> >>> ---
> >>>
> >>> So after all this, I can get to my question:
> >>&g