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

Very Odd Behaviour of svn update from command line. Bug?

From: HAcland <hughacland_at_googlemail.com>
Date: Mon, 7 Jul 2008 08:12:23 -0700 (PDT)

I am using:

MS Windows 2003,
Apache/2.2.6 (Win32) DAV/2 SVN/1.4.5 mod_ssl/2.2.6 OpenSSL/0.9.8g,

It appears as though there is some kind of an issue with running 'svn
update' on a working copy from a 'post-commit.bat'. Here's what happens:

Scenario 1:

cd D:\***\***\workingCopy\
PATH C:\Program Files\subversion\svn-win32-1.4.6\bin\;
svn update
mkdir demoDirToProveAPoint
svn info > infofile.txt


Run post-commit.bat from command line directly. No problem at all. Works
fine and updates the working directory. Also a new directory is correctly
created called 'demoDirToProveAPoint' and the svn info is correctly piped to
a file called infofile.txt

All great and life is happy when running directly from command line.

Scenario 2:

with exactly the same post-commit.bat

however this time from a remote computer, using Tortoise, a commit is made
after modifying a file. One would expect the svn hook to kick in at the
desired time and automatically to run 'post-commit.bat' in exactly the same
way as if it was run from the command line directly.

The result is that the 'mkdir demoDirToMakeAPoint' and 'svn info >
infofile.txt' work correctly but the 'svn update' fails to action.

What is going on here? Looks like a weird bug. Any one help me out?


View this message in context: http://www.nabble.com/Very-Odd-Behaviour-of-svn-update-from-command-line.-Bug--tp18319051p18319051.html
Sent from the Subversion Users mailing list archive at Nabble.com.
To unsubscribe, e-mail: users-unsubscribe_at_subversion.tigris.org
For additional commands, e-mail: users-help_at_subversion.tigris.org
Received on 2008-07-07 17:12:43 CEST

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.