top button
Flag Notify
    Connect to us
      Site Registration

Site Registration

SVN: Unexpected behaviour when checking out a copy at an invalid revision

+2 votes
456 views

Checking out a copied directory at a revision prior to the copy results in a checkout of the data before the copy. I would expect this to fail in the same way that attempting to update to an invalid revision fails.

Is this the intended behaviour? If so, shouldn't there be some message that your working copy is using a different location than requested?

 > svn copy trunk mybranch -m 'copy test'
Committed revision 2

 > svn co mybranch -r1 mybranch

 > svn info mybranch
Relative URL: ^trunk

Checking out the branch at a valid revision then attempting to update to the earlier revision results in an error:

 svn: E160005: Target path 'mybranch' does not exist

(I was attempting to checkout the revision given by 'Last Changed Rev' from 'svn info' on a child of a copied directory - it points at a revision before the copy, but that's a different discussion)

posted May 12, 2014 by Jai Prakash

Looking for an answer?  Promote on:
Facebook Share Button Twitter Share Button LinkedIn Share Button

Similar Questions
+1 vote

With VisualSVN server version 2.1.4 (svn server version 1.6.13) When I try to checkout our project it throws an error message "svn: E175009: Missing update-report close tag". What could be the reason for this error message?
Can something could be corrupt in our server? If so is there any tool to verify and correct our repository?

+5 votes

Are there side effects from applying the same svn merge --record-only on the same revision number and a new commit each time it is applied ?

Would there be issues with SVN mergeinfo and/or SVN in general if one keeps applying svn merge --record-only on a revision number repeatedly and commit in a svn merge --record-only followed by commit followed by svn merge --record-only followed by commit and the next cycle begins ? Its not an infinite loop svn merge; it would stop at some point.

0 votes

Can anyone give me what is useful and when we actually use?

+1 vote

I have the following setup "trunk and branch A (created from trunk)"

Now, what I want to do is only commit my changes to the trunk and make sure that every committed change is replicated into branch A. This should be an automatic commit, triggered by the commit to trunk, while being aware of the fact that no other changes should be done in branch A but the autocommit from trunk.

Another "would-like" requirement is that the commit metadata like author and commit time/date are kept, but this is not a must have. Is that possible with svn, maybe with autocommit hooks? If not, what other way would you see to achieve that?

...