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

Re: PMease using Subversion help needed...please help

From: Hari Kodungallur <hkodungallur_at_gmail.com>
Date: Tue, 11 Mar 2008 14:42:29 -0700

On Tue, Mar 11, 2008 at 12:55 PM, john-paul york <jp_york_at_hotmail.com>

> If I am able to do the original checkout, this means that subversion
> should be installed correctly...correct? I am just worried that I have not
> installed subversion correctly...I am using MAC OsX...what is the simplest
> way to make sure it is installed properly?
> Thanks for your help

The simplest way to tell is to run the following command:

 $> svn --version

(you may have to give the full path - /Volumes/Build/subversion/bin/svn)

If it prints out valid info, then the installation is good.

On my linux machine, the above command prints:

[~] > svn --version
svn, version 1.4.3 (r23084)
   compiled Mar 23 2007, 09:29:55

Copyright (C) 2000-2006 CollabNet.
Subversion is open source software, see http://subversion.tigris.org/
This product includes software developed by CollabNet (

The following repository access (RA) modules are available:

* ra_dav : Module for accessing a repository via WebDAV (DeltaV) protocol.
  - handles 'http' scheme
  - handles 'https' scheme
* ra_svn : Module for accessing a repository using the svn network protocol.
  - handles 'svn' scheme
* ra_local : Module for accessing a repository on local disk.
  - handles 'file' scheme

As you said, your svn installation is good because you were able to
successfully checkout. But the problem is when you execute the 'svn update'
command. As per your email, it seems like you are constructing the command
that needs to be executed to do the svn update. I was suggesting that may be
the command that is formed is wrong or the directory mentioned in the
command is non-existent or something like that.

Are you able to run svn from command line successfully?

For this svn update, can you try the following command from command line:

  $> /Volumes/Build/subversion/bin/svn update
--non-interactive --quiet --username jyork --password ****** -r 20

What happens when you run this command?


PS: Can you please "reply-all" when posting to the list? That way many
others in the list can help answer the question. In addition, I happen to
look at the list very irregularly.

> ------------------------------
> Date: Tue, 11 Mar 2008 12:08:43 -0700
> From: hkodungallur_at_gmail.com
> To: jp_york_at_hotmail.com
> Subject: Re: PMease using Subversion help needed...please help
> CC: users_at_subversion.tigris.org
> On Tue, Mar 11, 2008 at 11:40 AM, jpyork <jp_york_at_hotmail.com> wrote:
> I have setup PMease to use subversion and when I run the build for the
> first
> time it grabs everything from the repository just fine, but the issue I am
> having is that if I try to run it a second time it fails very time because
> it can't perform an svn update. The error I get is:
> 2008-03-11 13:26:55,891 [Thread-593] ERROR - ERROR: Failed to run command:
> Executing '/Volumes/Build/subversion/bin/svn' with arguments:
> 'update'
> '/Volumes/Build/project/proejecttSubversion_2.2.2/checkouts/project'
> '--non-interactive'
> '--quiet'
> '--username'
> 'jyork'
> '--password'
> '******'
> '-r'
> '20'
> Can you also provide the actual error from the svn update command. The
> update command must have failed because of many reasons - starting from not
> forming the right set of arguments (it looks good above; but I have not used
> PMease to know how it passes it down) or not able to find the directory to
> update to invalid user/password and many such reasons. I doubt we can help
> without the actual error from the svn update command.
> One way to know is to run the command manually by cut pasting the above
> arguments and see what you get.
> Thanks,
> -Hari
Received on 2008-03-11 22:42:59 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.