[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: john-paul york <jp_york_at_hotmail.com>
Date: Thu, 13 Mar 2008 16:55:34 -0400

Thanks Hari for all your help that was it....I was deleting and re-creating the folder when I did the build...things are going smooth now...thanks a lot

Date: Thu, 13 Mar 2008 12:46:35 -0700From: hkodungallur_at_gmail.comTo: jp_york_at_hotmail.comSubject: Re: PMease using Subversion help needed...please helpCC: users_at_subversion.tigris.org
On Wed, Mar 12, 2008 at 6:21 AM, john-paul york <jp_york_at_hotmail.com> wrote:

Hari, This is the error I get when I do it through terminal: svn: Directory '/Volumes/Build/project/project_2.2.2/checkouts/project/web/lib/.svn' containing working copy admin area is missing this seems to go hand and hand with:ERROR: Failed to run command: Executing '/Volumes/OsX/opt/subversion/bin/svn' with arguments:
'update'
'/Volumes/Build/project/project_2.2.2/checkouts/project/web'
'--non-interactive'
'--quiet'
'--username'
'jyork'
'--password'
'******'
'-r'
'23' If I go into terminal and go to the web/lib folder there is a .svn folder there, so I don't konw why it would say it is missing.If I delete the web\lib folder and run the build it works, but this error seems to randomly pop up with different locations, before it was web\lib
I go the same error with bean\classes.
These directories are affected by the build in some way or the other. I am guessing that you might be deleting the directories (web/lib or bean/classes) during the build. That is, these are part of your repository, and got checked out during initial build. But during the build ('clean' target may be), you are deleting these directories and along with it deleting the svn metadata folder (.svn).That is the only explanation I can think of.rgds-HariPS: Please 'reply-all'. Thanks!

  

Date: Tue, 11 Mar 2008 14:42:29 -0700

From: hkodungallur_at_gmail.comTo: jp_york_at_hotmail.comSubject: Re: PMease using Subversion help needed...please helpCC: users_at_subversion.tigris.org
On Tue, Mar 11, 2008 at 12:55 PM, john-paul york <jp_york_at_hotmail.com> wrote:

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 --versionsvn, version 1.4.3 (r23084) compiled Mar 23 2007, 09:29:55Copyright (C) 2000-2006 CollabNet.Subversion is open source software, see http://subversion.tigris.org/This product includes software developed by CollabNet (http://www.Collab.Net/).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' schemeAs 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 /Volumes/Build/project/proejecttSubversion_2.2.2/checkouts/project --non-interactive --quiet --username jyork --password ****** -r 20What happens when you run this command?Regards,-HariPS: 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 -0700From: hkodungallur_at_gmail.comTo: jp_york_at_hotmail.comSubject: Re: PMease using Subversion help needed...please helpCC: 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 firsttime it grabs everything from the repository just fine, but the issue I amhaving is that if I try to run it a second time it fails very time becauseit 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

Snap and Share. From your phone to your space. Post your pics here.
_________________________________________________________________
Create a handy button so your friends can add U to their buddy list. Try it now!
http://g.msn.ca/ca55/211
Received on 2008-03-13 23:26:18 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.