"svn up -r" sometimes removes externals
Hi, Today I tried to update a custom OFBiz working copy to a specific revision and got this C:\>svn up -r1634839 Mise à jour de '.' : U hot-deploy Removed external 'hot-deploy\core' Removed external 'hot-deploy\po' Left local modifications as 'hot-deploy\***po' Removed external 'hot-deploy\-theme' Removed external 'hot-deploy\hh' Removed external 'hot-deploy\comlead' Removed external 'hot-deploy\accnt' Removed external 'hot-deploy\common' Left local modifications as 'hot-deploy\common' Removed external 'hot-deploy\productconfig' Left local modifications as 'hot-deploy\productconfig' Actualisé à la révision 1634839. C:\> So it removed most of my externals, but not all. I have 12 externals from 2 different repos (from ASF-OFBiz) . 4 remains untouched, 2 are from the different repos, si it does not depend on the repo. 3 are left with only their build folder The others are totally removed Weirdly, just before, I did the same with another copy I did some days ago which was not up to date (the above was already updated at r1634839) and got not problems Anybody an idea (did not find anything clear in Google)? Thanks Jacques PS: C:\>svn --version svn, version 1.8.11 (r1643975) compiled Dec 17 2014, 21:04:03 on x86-microsoft-windows It's SlikSvn
Re: "svn up -r" sometimes removes externals
Thanks Andrew, That made it. I though hoped that by using svn up -r1634839 It would also update the externals independently of the main repo revision Like svn up alone does Fair enough! Jacques Le 10/02/2015 12:44, Andrew Hemp a écrit : Hi Jacques, This should leave the externals properties as is: svn update -rXXX --ignore-externals cheers Andrew On 10 February 2015 at 13:36, Stefan Sperling mailto:s...@apache.org>> wrote: On Tue, Feb 10, 2015 at 12:04:24PM +0100, jler...@apache.org <mailto:jler...@apache.org> wrote: > Hi, > > Today I tried to update a custom OFBiz working copy to a specific revision and got this > > C:\>svn up -r1634839 > Mise à jour de '.' : > U hot-deploy > Removed external 'hot-deploy\core' > Removed external 'hot-deploy\po' > Left local modifications as 'hot-deploy\***po' > Removed external 'hot-deploy\-theme' > Removed external 'hot-deploy\hh' > Removed external 'hot-deploy\comlead' > Removed external 'hot-deploy\accnt' > Removed external 'hot-deploy\common' > Left local modifications as 'hot-deploy\common' > Removed external 'hot-deploy\productconfig' > Left local modifications as 'hot-deploy\productconfig' > Actualisé à la révision 1634839. > > C:\> > Anybody an idea (did not find anything clear in Google)? Have the relevant svn:externals properties changed? If someone removed an external definition from the property (or removed the property entirely) then this behaviour would be entirely expected. If you need more help, please clearly state which URL you checked out and which revision numbers were involved so that others can reproduce your problem.
Re: "svn up -r" sometimes removes externals
Le 10/02/2015 12:36, Stefan Sperling a écrit : On Tue, Feb 10, 2015 at 12:04:24PM +0100, jler...@apache.org wrote: Hi, Today I tried to update a custom OFBiz working copy to a specific revision and got this C:\>svn up -r1634839 Mise à jour de '.' : U hot-deploy Removed external 'hot-deploy\core' Removed external 'hot-deploy\po' Left local modifications as 'hot-deploy\***po' Removed external 'hot-deploy\-theme' Removed external 'hot-deploy\hh' Removed external 'hot-deploy\comlead' Removed external 'hot-deploy\accnt' Removed external 'hot-deploy\common' Left local modifications as 'hot-deploy\common' Removed external 'hot-deploy\productconfig' Left local modifications as 'hot-deploy\productconfig' Actualisé à la révision 1634839. C:\> Anybody an idea (did not find anything clear in Google)? Have the relevant svn:externals properties changed? If someone removed an external definition from the property (or removed the property entirely) then this behaviour would be entirely expected. If you need more help, please clearly state which URL you checked out and which revision numbers were involved so that others can reproduce your problem. Thanks Stefan, Nothing was changed. I was (unconsciously) hoping that svn up -r*** would have the same behaviour than svn up regarding externals (it updates them also, of course their HEADs is at different revisions) I can live with Andrew's solution :) Jacques
