[svn.haxx.se] · SVN Dev · SVN Users · SVN Org · TSVN Dev · TSVN Users · Subclipse Dev · Subclipse Users · this month's index

Re: svn:externals to older revision of deleted path

From: Ryan Schmidt <subversion-2009a_at_ryandesign.com>
Date: Wed, 11 Mar 2009 13:51:01 -0500

On Mar 11, 2009, at 13:05, Alves, Pedro Maia (NSN - PT/Amadora) wrote:

> I have two repositories and in one I have an svn:externals property
> to the other with fixed revision.
> For example I have in on directory of REP1 an svn:externals
> property, to get a directory from REP2, similar to:
> -r49 http://REP2/trunk/xpto xpto
> Now, I decide that I don't want anymore to have the xpto directory
> and in revision 76 of REP2 I deleted the directory.
> If I don't change the svn:externals property on REP1 I should be
> able to get revision 49 of the xpto directory when I'm checking out
> the directory from REP1 because on revision 49 the directory still
> existed on REP2.
> However if I try to check out REP1 I'm getting the following message:
> '/svn/REP2/!svn/bc/76/trunk/xpto' path not found
> It seams that it is looking for the directory first on the HEAD
> revision (76)

That is correct.

> which doesn't make sense because I want revision 49.
> I'm using 1.5.5-SlikSvn-tag-1.5.5_at_34877-WIN32.
> Do you think this is a bug on svn?

No, it works as intended.

You need to understand the difference between peg and operative


You'll see that externals definitions now support both peg and
operative revisions.


So the correct externals definition now would be

-r49 http://REP2/trunk/xpto@49 xpto

That would definitely work, or possibly it can be shortened to just
specify the peg revision.

http://REP2/trunk/xpto@49 xpto

But I'm never sure if the operative revision defaults to the peg
revision or to HEAD.


To unsubscribe from this discussion, e-mail: [users-unsubscribe_at_subversion.tigris.org].
Received on 2009-03-11 19:52:05 CET

This is an archived mail posted to the Subversion Users mailing list.

This site is subject to the Apache Privacy Policy and the Apache Public Forum Archive Policy.