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

RE: subversion install, svn clients cannot connect

From: James D. Parra <Jamesp_at_MusicReports.com>
Date: 2007-04-05 21:09:32 CEST

On Apr 4, 2007, at 16:59, James D. Parra wrote:

> We are using the svn client and SmartSVN (server version is 1.4.3)
> with the
> svn protocol;
> ----------------------------------------------------------------------
> ------
> ------------------------------------------------------------
>
> Running SVN from command line:
> Action:
> svn checkout svn://192.168.20.14:/data/svnrepos/ /srv/www/htdocs/
> mcr_svn/
> Error:
> svn: URL 'svn://192.168.20.14:/data/svnrepos' doesn't exist

>There should not be a colon after the server name/address. The
>correct URL would be:

>svn://192.168.20.14/data/svnrepos

Yes, that was a typo. Using 'svn://192.168.20.14/data/svnrepos' produces the
same error.

> ----------------------------------------------------------------------
> ------
> ------------------------------------------------------------
>
> Running from SmartSVN ( Java GUI - Version 2.1.3):
> Action:
> Attempting to browse the repository
> Error:
> svn: Directory svn://terabyte/data/svnrepos does not exist in
> repository at
> revision HEAD
>
> Action:
> Attempting to commit back to repository
> Error:
> svn: File not found: transaction 'ii', path
> '/data/svnrepos/web/web_mcr/class/class_text.php'

Interesting...

> ----------------------------------------------------------------------
> ------
> ------------------------------------------------------------
>
> I also noticed that with both the command line version and
> SmartSVN, I am
> able to 'add' and
> 'update' to the repository. Every time the transaction goes through
> with
> revision 653.

>Wait, what? "'update' to the repository"? "update" is an action that
>retrieves data *from* the repository *to* the local working copy. It
>does not modify the repository. It will report to you the revision of
>the repository which your working copy now represents, apparently
>revision 653.

When I attempt to update my entire local directory with the newest changes
in the Subversion Repository, I get an error.
'svn: Target path does not exist'

When I choose a particular file that is modified locally, and want to
combine my newest changes with the latest version in the
repository, the transaction goes through with no errors.
'Update to HEAD: text.php at revision 653'

> Also we can access the repository, locally via 'file:///' with
> 'checkout'
> and
> 'add'
>
> Any ideas on how to fix this?

>How is svnserve started? Do you pass it a -r parameter? If so, is it
>correct -- is it where your repository really is on disk?

Using, #svnserve -d -r /data/svnrepos, to start the server.

Just to add a few more details. The repository was created using Subversion
1.1.* and we wanted to upgrade to Subversion 1.4.3. First, we copied the
'repos' to another location (actually, we made several copies). Second, we
did a dump of the 'repos' (svnadmin dump /data/repos > dumpfile.txt). After
upgrading to 1.4.3 and creating a new repository, we imported from the dump
file (svnadmin load /path/to/repository < dumpfile.txt) After starting the
server, folks reported the above errors. We even started the daemon by
pointing it to a copy of the original repository, but with identical
results.

I can browse the tree with 'svnlook';

# svnlook tree /data/svnrepos |grep web
 web/
   web_test/
    website_shut_down.php
<snip>

Since there aren't any logs to look at, I am having a hell of time trying to
figure out why the remote svn clients won't connect. All help is much
appreciated.

Thanks again,

~James

-- 
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
Received on Thu Apr 5 21:09:57 2007

This is an archived mail posted to the Subversion Users mailing list.