On 09.11.2011 13:22, Mads Grønfeldt wrote:
> We are seeing some unexpected behaviour with svn:externals, starting
> from Tortoise SVN version 1.7.x.
> Lets say we have an existing repository, i.e. Project A, which has an
> external to Project B in revision 43. My external on that repository
> would have been manually entered (with tortoise version 1.6.x) as:
> projbLib -r 43 https://server/projectb/trunk
> If I checkout this repository with the 1.6.x as well as the 1.7.x
> client all works as expected.
> If I create a new repository (Project C), and adds an external via
> the new Externals dialog in 1.7.x and locks this to revision 43 as
> well (NOTE: I do not enter a peg revision but leave the field empty),
> the external syntax generated is:
> -r 43 https://server/projectb/trunk ProjbLib (notice that the local
> directory now appears last)
> If I create a new empty directory on my desktop and select SVN
> Checkout of Project C, it will retrieve the head revision of my
> external (Project B), and not revision 43 as I would expect. If I
> immediately after right-click the newly checked out working copy and
> select Update, it will update the external to revision 43.
> If I change the external via the Advanced dialog in 1.7.x to match
> the format from Project A, the initial Checkout will retrieve
> revision 43 as expected.
> Am I missing something, or is this a bug?
What happens when you check out a working copy with the CL client (svn.exe)?
Does it behave differently?
If it also checks out the externals as HEAD, you have to report this on
the svn users mailing list:
oo // \\ "De Chelonian Mobile"
(_,\/ \_/ \ TortoiseSVN
\ \_/_\_/> The coolest Interface to (Sub)Version Control
/_/ \_\ http://tortoisesvn.net
To unsubscribe from this discussion, e-mail: [users-unsubscribe_at_tortoisesvn.tigris.org].
Received on 2011-11-09 20:06:05 CET