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

Re: svn update 'skipping'

From: Bruce Webber <brucewebber_at_fastmail.us>
Date: 2005-12-13 16:58:26 CET

--Ita Ryan <itaryan@gmail.com> wrote:

> I use a batch file (in WinXP) to automatically download files from the
> Subversion master to my build machine and then build the project. This
> has been working fine for months, but today the 'svn update' command
> resulted in the message 'skipping mydir' where mydir is the name of the
> directory to be updated. The relevant directory was not updated and
> after several attempts I had to copy it over from my dev machine.
>
> The command was 'svn update d:\..\mydir'

"d:\..\mydir" works in Windows, but it's a bit strange. You're specifying
the mydir directory which is located under the parent directory of the root
of drive D. The root of drive D does not have a parent. In my tests on Win
2000, however, Windows assumes the parent of d:\ is d:\, so an equivalent
command is:

svn update d:\mydir

which is more readable (but functionally equivalent).

> What causes this 'skipping' action? I've done a search on the subversion
> site and in all the manuals I could find; I couldn't locate a mention of
> 'skipping' anywhere!

Is d:\mydir missing the hidden .svn directory? If that's the case,
Subversion will not recognize this as a working copy, and you will get the
"skipped" message.

If that's the case, you could rename the directory (in case you have any
unversioned files you want to save), create a new d:\mydir directory, and
do an svn checkout to get a new working copy.

-- 
Bruce Webber
brucewebber@fastmail.us
http://brucewebber.us
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Received on Tue Dec 13 17:06:47 2005

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.