You are viewing a plain text version of this content. The canonical link for it is here.
Posted to users@subversion.apache.org by Olly Stephens <Ol...@arm.com> on 2006/05/22 13:14:31 UTC
BUG? svn status --show-updates can fail on a replaced file for no good reason
Can someone verify that this is a bug so I can report it? Thanks.
Tested against 1.3.0 and 1.3.1:
mkdir /tmp/svnbug
svnadmin create /tmp/svnbug/repos
echo hi >/tmp/svnbug/xxx
svn mkdir -mmkdir file:///tmp/svnbug/repos/dir1
svn import -mimport /tmp/svnbug/xxx file:///tmp/svnbug/repos/dir1/xxx
svn copy -mcopy file:///tmp/svnbug/repos/dir1
file:///tmp/svnbug/repos/dir2
svn remove -mremove file:///tmp/svnbug/repos/dir1/xxx
svn checkout file:///tmp/svnbug/repos/dir1 /tmp/svnbug/working1
svn merge -r4:3 file:///tmp/svnbug/repos/dir1 /tmp/svnbug/working1
echo hi2 >> /tmp/svnbug/working1/xxx
svn commit -mcommit /tmp/svnbug/working1
svn checkout file:///tmp/svnbug/repos/dir2 /tmp/svnbug/working2
svn merge -r3:4 file:///tmp/svnbug/repos/dir1 /tmp/svnbug/working2
svn merge -r4:5 file:///tmp/svnbug/repos/dir1 /tmp/svnbug/working2
# /tmp/svnbug/working2 is now in 'R' state
svn status /tmp/svnbug/working2
# 'svn status --show-updates' fails for no good reason
svn status --show-updates /tmp/svnbug/working2
# svn: Working copy path 'xxx' does not exist in repository
Olly
-- IMPORTANT NOTICE: The contents of this email and any attachments are confidential and may also be privileged. If you are not the intended recipient, please notify the sender immediately and do not disclose the contents to any other person, use it for any purpose, or store or copy the information in any medium. Thank you.
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Re: BUG? svn status --show-updates can fail on a replaced file for no good reason
Posted by Garrett Rooney <ro...@electricjellyfish.net>.
On 5/22/06, Olly Stephens <Ol...@arm.com> wrote:
>
> Can someone verify that this is a bug so I can report it? Thanks.
>
> Tested against 1.3.0 and 1.3.1:
>
> mkdir /tmp/svnbug
> svnadmin create /tmp/svnbug/repos
> echo hi >/tmp/svnbug/xxx
> svn mkdir -mmkdir file:///tmp/svnbug/repos/dir1
> svn import -mimport /tmp/svnbug/xxx file:///tmp/svnbug/repos/dir1/xxx
> svn copy -mcopy file:///tmp/svnbug/repos/dir1
> file:///tmp/svnbug/repos/dir2
> svn remove -mremove file:///tmp/svnbug/repos/dir1/xxx
> svn checkout file:///tmp/svnbug/repos/dir1 /tmp/svnbug/working1
> svn merge -r4:3 file:///tmp/svnbug/repos/dir1 /tmp/svnbug/working1
> echo hi2 >> /tmp/svnbug/working1/xxx
> svn commit -mcommit /tmp/svnbug/working1
> svn checkout file:///tmp/svnbug/repos/dir2 /tmp/svnbug/working2
> svn merge -r3:4 file:///tmp/svnbug/repos/dir1 /tmp/svnbug/working2
> svn merge -r4:5 file:///tmp/svnbug/repos/dir1 /tmp/svnbug/working2
> # /tmp/svnbug/working2 is now in 'R' state
> svn status /tmp/svnbug/working2
> # 'svn status --show-updates' fails for no good reason
> svn status --show-updates /tmp/svnbug/working2
> # svn: Working copy path 'xxx' does not exist in repository
It looks like this has been fixed in trunk, almost certainly also in
1.4.x, since 1.4.x is very similar to trunk at the moment.
-garrett
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org