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

[TSVN] Bug report (version 1.0.8)

From: Peter Mounce <pete_at_x-rm.com>
Date: 2004-09-09 12:41:53 CEST


I consistently get an error when I do an admittedly silly thing:

* If I check out a WC of a tag of my project to someplace (in this
case our staging server),

* create a file in it (but not add it to version control) to check if
something works,

* see that the thing to do with the new file _does_ work,

* absent-mindedly create the same file in the same place in my local
development working copy

* commit my local dev working copy to the trunk (repo layout is one
repo per project, each repo top level is branches, tags, trunk)

* create a new tag from the trunk

* attempt to switch the staging WC to the new tag

- I quite rightly get an error saying that the file already exists -
because I left it there when I was being absent-minded earlier.

- What now? If I delete the file from staging WC (to make room for the
versioned-copy-from-SVN) and attempt to switch again, I get an
always-reproducible error:

REPORT request failed on '/svn/dls/!svn/vcc/default'
File not found: revision '1043', path '/tags/milestone-03/rc23/core'

Note that the path it is trying to find is _wrong_ the path (I think)
it should be attempting is "/tags/milestone-03/rc23/Website/core" -
ie, it's correct up until the last / in the error message, but is
missing bits.

I have run clean up on my staging WC and reproduced the above error.

The staging WC is now in a state where if I turn on the SVN columns,
it doesn't appear to all be in the same shortUrl - that is, not all in
the same tag.

Peter Mounce  ( mailto:pete@x-rm.com )
Software Developer    http://www.x-rm.com - X-RM Ltd, Winchester
To unsubscribe, e-mail: dev-unsubscribe@tortoisesvn.tigris.org
For additional commands, e-mail: dev-help@tortoisesvn.tigris.org
Received on Sat Sep 11 20:18:05 2004

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

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