On Friday, December 14, 2018 at 5:28:19 AM UTC-5, Stefan wrote: > On Thursday, December 13, 2018 at 4:47:52 PM UTC+1, (unknown) wrote:In > upgrading from 1.9.x to the latest nightly build (1.11 dec 13), we found a > difference in the way Checkout over existing folder operates. > > > > In the past, when you checkout over an existing unrevisioned folder, it > prompts "folder not empty, are you sure?). Upon selecting yes, it proceeds > to checkout. Any files that already exist with the same name and are > different are marked as "MODIFIED". This is what we expect to happen. Using > a subsequent "revert to revision" would bring these modified files to the > checkout revision if so desired. > > > > In v1.11, if a file already exists in the checkout path, and that file is an > "svn external", you will get "Error The file external X can not be created > because the node exists". We only get node errors for files that are svn > external. > > > > > Yes, that's by design. A file external is a simple "link". For a file > external, there is no base file to which to compare it to, so there's no way > (without contacting the repository) to know whether an external is modified > or not. > That's why you get an error - it's not possible to restore an overwritten > external file. > >
Since our file externals point to HEAD revision, I guess In 1.9.X, it used to allow this operation and use the HEAD as a base of comparison for these file externals. We have a workaround for what we are doing, I just wanted to point out the difference in event someone else had difficulty here. Thanks for your explanation and quick response! -- You received this message because you are subscribed to the Google Groups "TortoiseSVN" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To view this discussion on the web visit https://groups.google.com/d/msgid/tortoisesvn/e0c3cde1-584c-4bc3-9848-58954156129d%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
