On Nov 24, 2010, at 05:00, Schroeder, Hartmut wrote:
> say,
> svn list http://server/repo/trunk/a/b/c
> gives:
> d/
> in revision 100.
>
> Then:
> svn del http://server/repo/trunk/a/b/c/d
> (r101)
>
> Then, the checkout
> svn co -p 100 http://server/repo/trunk/a/b/c/d
> won't work, but with the peg revision
> svn co http://server/repo/trunk/a/b/c/d@100
> it does.
>
> All external definitons using '-p 100 http://server/repo/trunk/a/b/c/d'
> won't work anymore and need to be changed. That leeds to heavy
> discussions cause some teams here using a lot of external definitons and
> run into that problem.
>
> We are using Subversion 1.5.5
>
> Does a reason exist for that behaviour?
> Is it a point of change in upcoming releases?
> Is there a nice workaround?
> Or, is the only solution to use always peg revisions in external
> definitions?
For exactly the reasons you've discovered, you should always use peg revisions in externals definitions.
Received on 2010-11-24 12:53:12 CET