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

Re: problem with "svn switch"

From: <cmpilato_at_collab.net>
Date: 2002-07-10 06:34:04 CEST

=?ISO-8859-1?Q?F=E9liciano?= Matias <feliciano.matias@free.fr> writes:

> First, excuse my very poor english.
> I try to play with subversion :
> subverion-0.13.2 (r 2376)
> db4-4.0.14
> neon-0.21.2
> libapr 2002.06.25
> apache 2.0.40-dev (?)
> "make check" in source tree of subversion is ok.


I ran the following script using Subversion revision 2448, and had no
errors at all:

   svn mkdir file://${REPOS}/trunk -m "add trunk"
   svn mkdir file://${REPOS}/branch -m "add branch"
   svn mkdir file://${REPOS}/branch/dev1 -m "add dev1"
   svn co file://${REPOS}/trunk -d .
   touch foo
   svn add foo
   svn commit -m "add foo"
   svn rm foo
   svn status foo
   svn switch . file://${REPOS}/branch/dev1
   svn commit -m "do not remove foo."
   svn switch . file://${REPOS}/trunk
   svn update
   svn ci -m ""
   svn switch . file://${REPOS}/trunk

My output was:

   Committed revision 1.
   Committed revision 2.
   Committed revision 3.
   Checked out revision 3.
   A foo
   Adding foo
   Transmitting file data .
   Committed revision 4.
   D foo
   D foo
   D ./foo
   Updated to revision 4.
   A ./foo
   Updated to revision 4.
   At revision 4.
   At revision 4.

Now, I *think* my script does the same thing yours did. As you can
see, though, I did see any errors in the output. Wonder what's
different about your setup...

Now, I *did* see problems (slightly different ones, but...) when,
between runs of this script, I forgot to `rm -rf .svn' to
un-working-copy-ize my current working directory. Perhaps you made
the same error?

To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Wed Jul 10 06:35:01 2002

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

This site is subject to the Apache Privacy Policy and the Apache Public Forum Archive Policy.