You are viewing a plain text version of this content. The canonical link for it is here.
Posted to users@subversion.apache.org by Colleen Dick <pl...@peak.org> on 2007/03/25 22:28:56 UTC
Svn 1.4 on slackware
I had svn 1.2 server running very happily on a slackware box :P
until the box was hacked the OS was reinstalled.
One of the pieces I have to pick up is svn
Might as well move up to 1.4
but slackware doesn't get apt-get or rpm in a normal way.
I remember trying to install a special build of 1.2 for slackware
just trying to be logical and figure stuff out, but it didn't work
because of wierd slackware stuff that there's no way a normal person
would know.
what are the steps I take to install the server on slackware
thank you?
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Re: Svn 1.4 on slackware
Posted by Colleen Dick <pl...@peak.org>.
Hi Ryan and all,
Thank you for your help and I apologize for hitting reply instead of
reply all.
Basically Ryan told me to RTFM, but in fact the FM was open to just that
page already. I am trying to fix an installation that worked before.
I am using the -i option in my inetd.conf but I never specified the
repo. That is how the manual says to do it. I understand that -r is
an option to tell it root of the repo so that
you can have a shortened path which appends to the root in your .svns in
your various projects. Since I have the full path in the existing
projects I think it will hook up better if I don't alter that.
The fact I can telnet to it on the port tells me the network layer is
working, the ports are open when inetd opens them and the connection is
being made. It's just the client that can't connect. And I discovered
why by doing a svn info. It's because I'm a dyslexic idiot. I opened
ports 3690 as it says. But all my old repos list 3960 that was the port
I was using before and never noticed it was "wrong". So when I changed
my firewall to allow port 3960 everythings hunkie dorie.
On Sun, 2007-03-25 at 17:37 -0500, Ryan Schmidt wrote:
> On Mar 25, 2007, at 18:20, Colleen Dick wrote:
>
> > OK I think I see what the problem is, the newly installed
> > svn doesnt know where the repository is. Create will create a new one
> > but I'm rather attached to my old one, give it has 2 yrs worth of
> > work.
> > Where's the reattach commend.
> > I copied the old one back to the same place on the file system, How
> > can
> > I just tell svn where it is?
>
> There is no "reattach command", nor any reason for one. Depending on
> what server you're using to serve the repository (apache or
> svnserve), simply configure that server to tell it where the
> repository is. If you're using apache, set the proper repository path
> in your httpd.conf, in the SVNPath or SVNParentPath line. You said
> you're using svnserve, so you need to figure out where on Slackware
> the configuration file is that starts svnserve, and fix it to use the
> repository root parameter to tell it where your repository is.
>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Re: Svn 1.4 on slackware
Posted by Ryan Schmidt <su...@ryandesign.com>.
Please keep the discussion on the mailing list by using the Reply To
All feature of your email program when you reply. I may not
personally know the answers to your questions, so it's best to keep
it on the list so that others who know the answer can respond.
On Mar 25, 2007, at 18:56, Colleen Dick wrote:
>> There is no "reattach command", nor any reason for one. Depending on
>> what server you're using to serve the repository (apache or
>> svnserve), simply configure that server to tell it where the
>> repository is. If you're using apache, set the proper repository path
>> in your httpd.conf, in the SVNPath or SVNParentPath line. You said
>> you're using svnserve, so you need to figure out where on Slackware
>> the configuration file is that starts svnserve, and fix it to use the
>> repository root parameter to tell it where your repository is.
>
> I have a line in inetd to do svnserve but I've been looking all
> over the
> box for some config for svnserve that has that and I haven't found
> one.
It's not in a config file; it's a command line parameter that you
pass to the svnserve program when you start it. Please see the book...
http://svnbook.red-bean.com/en/1.2/svn.serverconfig.svnserve.html
...especially where it shows how to use the -r option to svnserve.
Since you're running it from inetd, you'll probably also want to make
sure svnserve is being started with the --inetd option.
> Also I'm still experience a fundamentally more basic problem when I
> run
> the svn commit like I use to from external host it times out when
> trying
> to talk to the server, but it does respond on the local box
On Mar 25, 2007, at 19:01, Colleen Dick wrote:
> Actually I ended up doing a dump, recreate and reload on one
> repository
> which seem to be OK but I lied. Connection is refused on localhost as
> well.
Ok, you can dump and load if you like. Some performance improvements
were made in 1.4 which you only get if you dump and load, so you may
enjoy those. But it didn't help with the fundamental inability to
connect, right? You still can't connect to your svnserve, either from
the local machine or from another?
On Mar 25, 2007, at 19:43, Colleen Dick wrote:
> Fails to connect
>
> My svnserve is set up to run on inetd. We only commit every day a
> couple of times, there is no reason for it to be a constant-on daemon
>
> In inetd.conf there is a command to run it, it says nothing of
> where the
> repo is, and it always worked before.
Have you in the past been specifying the absolute path to the
repository in your access URLs? As far as I know, that would be
necessary if you do not tell svnserve where to serve from. Something
like:
svn ls svn://svn.example.com/absolute/path/on/server/to/repository/
> If I telnet <svnhost> 3690 would that ever connect if it's inetd even
> if things work??
I have no experience with inetd so I don't know. But I have seen
telneting to 3690 suggested in the past for debugging svnserve
connectivity issues.
> There is a svnserve.conf down inside each repo but no mention of the
> repo loc (you're already there hahah)...
>
> In each users .svn dir it tells where the repo is for that directory
> that hasnt changed on external hosts
>
> I had to create the 3690 port in services. I restarted inetd. Is
> there anything else I need to restart. All networking is kinda tough
> cuz the svn server is remote if I ifdown eth0 it will kick me off
> and I
> can't get back on. What reads that services file?
I don't know; I'll let someone else answer.
--
To reply to the mailing list, please use your mailer's Reply To All
function
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Re: Svn 1.4 on slackware
Posted by Ryan Schmidt <su...@ryandesign.com>.
On Mar 25, 2007, at 18:20, Colleen Dick wrote:
> OK I think I see what the problem is, the newly installed
> svn doesnt know where the repository is. Create will create a new one
> but I'm rather attached to my old one, give it has 2 yrs worth of
> work.
> Where's the reattach commend.
> I copied the old one back to the same place on the file system, How
> can
> I just tell svn where it is?
There is no "reattach command", nor any reason for one. Depending on
what server you're using to serve the repository (apache or
svnserve), simply configure that server to tell it where the
repository is. If you're using apache, set the proper repository path
in your httpd.conf, in the SVNPath or SVNParentPath line. You said
you're using svnserve, so you need to figure out where on Slackware
the configuration file is that starts svnserve, and fix it to use the
repository root parameter to tell it where your repository is.
--
To reply to the mailing list, please use your mailer's Reply To All
function
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Re: Svn 1.4 on slackware
Posted by Colleen Dick <pl...@peak.org>.
OK I think I see what the problem is, the newly installed
svn doesnt know where the repository is. Create will create a new one
but I'm rather attached to my old one, give it has 2 yrs worth of work.
Where's the reattach commend.
I copied the old one back to the same place on the file system, How can
I just tell svn where it is?
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Re: Svn 1.4 on slackware
Posted by Colleen Dick <pl...@peak.org>.
Never mind, I was looking in the wrong place.
The server came with it installed (the old one didn't)
I had to create the svn ports in services and hook up my inetd
like it says in the manual but when I try to commit a test change
the commit hangs
On the local box using svn protocol to commit it tells me I can't
connect
On Sun, 2007-03-25 at 14:28 -0800, Colleen Dick wrote:
> I had svn 1.2 server running very happily on a slackware box :P
> until the box was hacked the OS was reinstalled.
>
> One of the pieces I have to pick up is svn
> Might as well move up to 1.4
> but slackware doesn't get apt-get or rpm in a normal way.
>
> I remember trying to install a special build of 1.2 for slackware
> just trying to be logical and figure stuff out, but it didn't work
> because of wierd slackware stuff that there's no way a normal person
> would know.
>
> what are the steps I take to install the server on slackware
>
> thank you?
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
> For additional commands, e-mail: users-help@subversion.tigris.org
>
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org