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

Re: issue with relative externals after a rename

From: Branko ─îibej <brane_at_apache.org>
Date: Wed, 28 Mar 2018 05:36:53 +0200

On 28.03.2018 01:38, Jonathan Schell wrote:
> I have a tree that looks like:
>
> https://svn/repo/name1/externs/normal_files_here
>
> The folder "externs" has two external properties:
> ../fold1_at_18 fold1
> ../fold2/file1.txt_at_18 file1.txt
>
> These folders and file exist at rev 18. The commit to add the properties to "externs" is commit 32.
>
> I then do a rename of "name1" to "name2".
>
> The externs now break, as the item they were pointing to no longer exists.

Because the default operative revision is HEAD and there's no such
object in HEAD, yes.

> So I edit the properties to:
> -r 18 ../fold1 fold1
> -r 18 ../fold2/file1.txt file1.txt
>
> And then did an update and the file got brought in, but there was still an error on the folder.

You need both peg and operative revisions:

-r 18 ../fold1 fold1_at_18
-r 18 ../fold2/file1.txt_at_18 file1.txt

The peg revision tells Subversion which object to look for and the
operative revision tells it which version of that object to use.

-- Brane
Received on 2018-03-28 05:36:59 CEST

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.