Hello,

Thanks for your response.
Finally, we modify process to do a copy directly on the server.

Elise & Phillipe.



-----Original Message-----
From: Philip Martin [mailto:philip.mar...@wandisco.com]
Sent: mercredi 2 juillet 2014 11:30
To: Philippe Bartholme
Cc: users@subversion.apache.org; Elise Vanholsbeeck
Subject: Re: Tag issue

Philippe Bartholmé <philippe.bartho...@kelkoo.com> writes:

> Used commands are :
>
> svn copy trunk tags/R8_106
> svn commit
>
> The error message is:
>
> Deleting geppetto/prod/tags/R8_106/group/testchildren.yaml svn: Commit
> failed (details follow): svn: File 'R8_106/group/testchildren.yaml' is
> out of date svn:
> '/svn/geppetto/!svn/wrk/0077129d-cc9e-409e-9d26-c8c1f56e247f/prod/tags
> /R8_106/group/testchildren.yaml' path not found ]
>
> And svn status give this result :
>
> A  +    tags/R8_106
> D  +    tags/R8_106/group/testgroup1.yaml
> D  +    tags/R8_106/group/testchildren.yaml
> D  +    tags/R8_106/group/testgroup2.yaml
>
> The three files don't exist in trunk.
>
> This issue doesn't occur every time.
>
> Subversion version is 1.6.11
>
> Why do you think we have this strange behavior and how can we avoid this 
> issue ?

It looks like the trunk tree is mixed revision and that means the copy has 
deletes and/or replaces so that it is a copy of the various different 
revisions.  While Subversion should support a mixed-revision copy it may not be 
what you want when you make a tag.  If you do want a mixed-revision copy then 
this appears to be a bug in 1.6.11; that's a very old client and the problem 
may be fixed in newer versions.  If you do not wat a mixed-revision copy then 
you should run update on trunk to make it single-revision before making the 
copy.


--
Philip Martin | Subversion Committer
WANdisco // *Non-Stop Data*




Kelkoo SAS
Société par Actions Simplifiée
Au capital de € 4.168.964,30
Siège social : 8, rue du Sentier 75002 Paris
425 093 069 RCS Paris

Ce message et les pièces jointes sont confidentiels et établis à l'attention 
exclusive de leurs destinataires. Si vous n'êtes pas le destinataire de ce 
message, merci de le détruire et d'en avertir l'expéditeur.

Reply via email to