Ruhe Julian wrote on Wed, Jun 20, 2012 at 09:17:53 +0000:
> Hello,
>
> try to assign a file p.txt containing the following lines as svn:external
>
> -r110 ^/mapping_services/global/testing/full_test/globalresource5.xml_at_110 "xml/globalresource5.xml"
> -r84 ^/mapping_services/global/testing/full_test/globalresource4.xml_at_84 "xml/globalresource4_renamed.xml"
> -r83 ^/mapping_services/global/testing/full_test/globalresource3.xml_at_83 "xsd/globalresource3.xml"
> -r82 ^/mapping_services/global/testing/full_test/globalresource2.xml_at_82 "xml/globalresource2.xml"
> -rHEAD ^/mapping_services/global/testing/full_test/globalresource6.xml_at_109 "xml/globalresource6.xml"
>
> Fails with error
> $ svn propset --file p.txt svn:externals .
> svn: E195005: Error parsing svn:externals property on '/cygdrive/g/Projekte/Mapping Services/workspaces-runtime/workspace-runtime-bom26-02/ShareProjektTest3': '-rHEAD ^/mapping_services/global/testing/full_test/globalresource6.xml_at_109 "xml/globalresource6.xml"'
>
> Skipping the -rHEAD part is no solution because in this case the operation-revision:=peg-revision which is obviously not the desired revision.
>
You're asking svn to trace history forward. (from r109 to rHEAD.) In
general there will be N places in rHEAD that are related to
gr6.xml_at_109. Is there a reason to expect that
^/mapping_services/global/testing/full_test/globalresource6.xml_at_HEAD and
^/mapping_services/global/testing/full_test/globalresource6.xml_at_r109
will at some point not be ancestrally related? If not, you could just
drop both -rHEAD and @109 and get the same result.
> I was using using:
> $ svn --version
> svn, version 1.7.5 (r1336830)
> compiled May 18 2012, 13:37:30
>
> Greetings,
> Julian
Received on 2012-06-22 01:47:51 CEST