Re: Case sensitivity bug in windows with powershell.

On Mon, Nov 12, 2012 at 10:48 AM, Sebastian Andersson <bofh69_at_gmail.com> wrote:
> I searched the reports database but could not find this error reported.
>
> Use a powershell shell and stand in the working copy:
> PS c:\temp\WC> svn mkdir APA
> PS c:\temp\WC> Set-LocationEx apa
> PS c:\temp\WC\apa>svn mkdir banan
> results in:
> svn: E150000: Can't find parent directory's node while trying to add
> 'R:\products\PTI\ADAPTERS\SIRI\apa\banan'
> svn: E155010: The node 'R:\products\PTI\ADAPTERS\SIRI\apa' was not found.
>
> I don't really know how powershell/windows works when it comes to the
> current directory, but Get-Location will say you are in "apa" after
> the Set-LocationEx command, instead of the APA directory.
>
>
> This confuses users not familiar with other operating systems.

For those that are not too familiar with powershell (like me): what
does Set-LocationEx do?

Does it do a rename of APA to apa (like the more usual Windows command
'move APA apa' does)?

If so, then what you're seeing is normal. You're renaming the
directory on the filesystem, outside of SVN. In SVN's metadata the
directory is still known as APA, while on disk it's apa. SVN will then
consider APA "missing" and apa "unversioned".

You should do 'svn move APA apa' instead, if you want the move to be
consistent between the filesystem and SVN's metadata.

-- 
Johan