You are viewing a plain text version of this content. The canonical link for it is here.
Posted to users@subversion.apache.org by "Brummer, Byron" <By...@LiveNation.com> on 2006/12/14 18:01:01 UTC
svn copy & mixed working copies with deleted or not-yet-existing revisions? Badly broken?
Situation: I have a mixed revision working copy that I want to tag
as-is, and so I do:
cd /home/byron/work/proj/trunk
svn copy . http://myserver/repos/proj/tag/qa-build-1
If I've back-dated (or updated) a subdirectory to a rev that is Deleted
I get:
$ svn up -r 1 foo
D foo
Updated to revision 1.
$ copy . http://myserver/repos/proj/tag/qa-build-1
svn: Commit failed (details follow):
svn: Directory '/home/byron/work/proj/trunk/foo' is missing
If I've back-dated a file to a rev that is Deleted I get:
$ svn update
A foo
A foo/fred.txt
Updated to revision 11.
$ svn update -r 1 foo/fred.txt
D foo/fred.txt
Updated to revision 1.
$ copy . http://myserver/repos/proj/tag/qa-build-1
svn: Commit failed (details follow):
svn: Out of date: '/proj/tag/tag-2/foo/fred.txt' in transaction
'11-1'
Now if I back-date foo/fred.txt to a revision that exists but is old
(ie,
is still technically "out of date"), svn copy is completely happy to
copy
the old version correctly. This problem only seems to happen with
revisions
of files and directories that do not exist (back-dated to a rev before
they
existed or updated to a rev where they have been deleted (and not
updating
the parent directory at the same time).
Am I doing something wrong here? This feels like a huge bug in SVN, so
huge that I can't help but think I'm just missing something obvious?
Thanks
-Byron
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Re: svn copy & mixed working copies with deleted or not-yet-existing revisions? Badly broken?
Posted by Bob Hiestand <bo...@gmail.com>.
On 12/14/06, Brummer, Byron <By...@livenation.com> wrote:
>
> Situation: I have a mixed revision working copy that I want to tag
> as-is, and so I do:
>
> cd /home/byron/work/proj/trunk
> svn copy . http://myserver/repos/proj/tag/qa-build-1
>
> If I've back-dated (or updated) a subdirectory to a rev that is Deleted
> I get:
>
> $ svn up -r 1 foo
> D foo
> Updated to revision 1.
> $ copy . http://myserver/repos/proj/tag/qa-build-1
> svn: Commit failed (details follow):
> svn: Directory '/home/byron/work/proj/trunk/foo' is missing
>
> If I've back-dated a file to a rev that is Deleted I get:
>
> $ svn update
> A foo
> A foo/fred.txt
> Updated to revision 11.
> $ svn update -r 1 foo/fred.txt
> D foo/fred.txt
> Updated to revision 1.
> $ copy . http://myserver/repos/proj/tag/qa-build-1
> svn: Commit failed (details follow):
> svn: Out of date: '/proj/tag/tag-2/foo/fred.txt' in transaction
> '11-1'
I see a similar issue when updating the entire working structure. I
bring that up because, frankly, if you want to delete something, you
should just delete it, not try to find an update that does so.
[bob@localhost trunk]$ svn update -r 8
D deleted.txt
Updated to revision 8.
[bob@localhost trunk]$ svn copy -m '' .
file:///home/bob/tmp/svnroot/tags/deletedtag1
svn: Commit failed (details follow):
svn: File not found: transaction '9-2', path '/tags/deletedtag1'
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org