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

Re: commits overs ssh

From: Ryan Schmidt <subversion-2009a_at_ryandesign.com>
Date: Tue, 27 Jan 2009 22:04:07 -0600

On Jan 3, 2009, at 03:33, Harry Putnam wrote:

> Its really a lame question but I'm on the verge of just throwing
> myself on my desk and boohooing in big sickening sobs. Maybe someone
> can save me fron totally embarrassing my self in front of wife and
> children.
> I'll admit I flaked out on the manual reading... I read through some
> of it but it seems like acres of text are required to get to any
> punchlines. I thought I'd try working through it with the `quick
> start'.
> I'm brand new to subversion but a (light) cvs user for quite some
> time. Not sure if that is a help or a hindrance.

I must recommend you do read the book. It's very thorough. There's
even an appendix for CVS converts.

> I'm going along nicely with the manual right up to the point of trying
> my first commit across my home lan via ssh, not tunneled, just plain
> ssh to another box.
> I'm an old hand at the ssh-agent and have that setup so that no dialog
> is required.
> First I fell into the trap that I see on google, dozens of others have
> fallen into. That is, expecting to need a CVSROOT type variable to
> establish the repo address.
> But the googling tells me repeatedly I don't need it since the repo
> address is stored in the checked out module. And I see it there in
> the
> .svn file.
> I'm told just the simple ci syntax will do it.
> So I'm cd'ed into the top level of my working copy:
> svn ci -m "My first commit .. with fingers crossed" <ENTER>
> The prompt is quickly and silently returned... nice...

There should not be silence; you should be informed what was
committed, and what the new revision number was. Since that didn't
happen, something went wrong during the commit. Maybe ssh was unable
to start the svnserve process. Is svnserve in the path that ssh knows

> Just one problem.
> When I test it by going to a directory not part of the co'd module and
> try checking out again:
> svn co svn+ssh://my.home.server/usr/local/svnrepo/trunk base
> I get a brand new copy but .. whoops .. my changes that were just
> checked in are not there.
> The ci appears to go off with no problems... in total silence.. so
> what gives?
> At least a solid dozen answers to the question... How to ci via ssh
> have told me the same thing... just simple ci syntax is all you need.
> So someone please tell me where my stupidity lies.

I'm not certain, as I've never set up svn+ssh access myself. That's a
bit of a complicated setup to dive right into for your first attempt.
You might have better luck starting off with just plain svnserve and
the svn protocol, or no svnserve and the file protocol, while you're
learning the basics of Subversion.


To unsubscribe from this discussion, e-mail: [users-unsubscribe_at_subversion.tigris.org].
Received on 2009-01-28 06:22:19 CET

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.