Re: SVN Externals 1.6 to 1.7 migration issue

While I have not had the issue you are having, assuming the externals are in the same repository I would highly recommend changing from using the syntax you have to using the carrot (^) operator as it will save you many headaches if your original svn location changes. I.e. use: ^/FOLDER_A FOLDER_C ^/FOLDER_B FOLDER_D Also, I think the specific issue you are having (looking more closely at the error message below) is that AFAIK, SVN does not let you import specific files via externals - you have to do name spaces (aka folders) instead. I would suggest doing one of two things in a batch file that gets run after checkout (manually by the user, though TSVN may be able to give you some automatic client-side scripting): 1. Use "mklink" to create an NTFS file link after the checkout for the file you are trying to relocate. 2. Copy the file from the one directory to the other Or 3. Copy the file as part of the SVN source tree to the other folder; but you'll also have to continuously merge the changes back and forth. #1 is your best option if you want to not change anything at all, but requires that you are running a newer version of Windows than Windows XP. I think Microsoft first started providing the "mklink" utility with Vista; but it could be WIn7, and might also depend on which edition of each of those you have as well. (e.g. it might not be in the Home Premium version, but might be in Pro and Ultimate). #2 is an okay backup if you can't do #1, but you'll need to treat the file as read-only as it will certainly be very much manual effort to maintain. #3 is automatic, but you'd have to ensure the file matches what is at its origin - a bit of a manual effort, but easy to do. $0.02 Ben >________________________________ > From: "Hutchinson, Steve (UK)" <steven.hutchinson_at_mbda-systems.com> >To: "users_at_subversion.apache.org" <users_at_subversion.apache.org> >Sent: Wednesday, May 1, 2013 7:01 AM >Subject: SVN Externals 1.6 to 1.7 migration issue > > >Hi, > >We're been using 1.6 svn externals to manage a FW task. > >In the repository we have a folder structure (which is pretty much defined by the tools we are using) as below :- > >FOLDER A -> file_a1.txt, file_a2.txt, file_a3.txt >FOLDER B -> file_b1.txt, file_b2.txt, file_b3.txt > >Then using externals we link to those folder to create a WC PROJECT structure that looks like :- > >PROJECT -> FOLDER C ->  file_a1.txt, file_a2.txt, file_a3.txt AND  file_b1.txt >PROJECT -> FOLDER D ->  file_b1.txt, file_b2.txt, file_b3.txt > >The externals on PROJECT FOLDER we used looked like (not actually using file protocol, just created for example purposes) :- > >file:///D:/FPGA/SVN_ISSUE/repo/FOLDER_A FOLDER_C >file:///D:/FPGA/SVN_ISSUE/repo/FOLDER_B FOLDER_D >file:///D:/FPGA/SVN_ISSUE/repo/FOLDER_B/file_b1.txt FOLDER_C/file_b1.txt > >Worked ok with 1.6. We get the below error in 1.7 when updating of :- > >External failed:    D:\FPGA\SVN_ISSUE\PROJECT\FOLDER_C\file_b1.txt  >Error:         Cannot insert a file external defined on 'D:\FPGA\SVN_ISSUE\PROJECT' into the  >Error:          working copy 'D:\FPGA\SVN_ISSUE\PROJECT\FOLDER_C'.  > >We have tried a few things (will not share all at this point due to info overload), but wondered if there were any others that achieve something like this with 1.7 or could offer some advise ? > >Thanks for any help. > >Regards >Steve H > >******************************************************************** >This email and any attachments are confidential to the intended recipient and may also be privileged. If you are not the intended recipient please delete it from your system and notify the sender. You should not copy it or use it for any purpose nor disclose or distribute its contents to any other person. > >MBDA UK Limited, a company registered in England and Wales, registration number 3144919 whose registered office is at Six Hills Way, Stevenage, Hertfordshire, SG1 2DA, England. > >******************************************************************** > > >
Received on 2013-05-01 17:02:33 CEST