Bug with bad characters in past versions when doing sparse checkout

3 views
Skip to first unread message

Edward Ned Harvey

unread,
Jan 30, 2009, 2:56:17 PM1/30/09
to d...@tortoisesvn.tigris.org

I haven’t been able to reproduce any bad behavior using svn command line, so I think it’s a Tortoise thing, and am reporting it here first.  Please let me know if there’s a procedure I should follow, or someplace else I should go instead.  Thank you.

 

I captured screen shots and put them here.  This is the best place to see what I’m reporting:

http://www.nedharvey.com/tortoise_svn_bug

 

For anyone who would prefer reading –

 

·         At some point in history (about a year ago) we had a mac user commit files with ‘foo (x|y) bar’ in the filename.

·         This caused problems back then for windows users, so the files were renamed to exclude the parens and vertical bar.  Via svn mv

·         In Tortoise now, if we do a sparse checkout (immediates) of the parent, and then try to go fully recursive (infinity) on the subdir which contains the formerly renamed files … Then Tortoise chokes while showing the filename which has not existed for over a year.

·         Using tortoise, if we do a fully recursive checkout of *just* the subdir containing the formerly renamed files, there is no problem.

 



This e-mail message may contain proprietary, confidential or legally privileged information for the sole use of the person or entity to whom this message was originally addressed. Any review, e-transmission dissemination or other use of or taking of any action in reliance upon this information by persons or entities other than the intended recipient is prohibited. If you have received this e-mail in error kindly delete this e-mail from your records. If it appears that this mail has been forwarded to you without proper authority, please notify us immediately at neta...@patni.com and delete this mail.

Stefan Küng

unread,
Jan 30, 2009, 3:05:45 PM1/30/09
to d...@tortoisesvn.tigris.org
Edward Ned Harvey wrote:
> I haven’t been able to reproduce any bad behavior using svn command
> line, so I think it’s a Tortoise thing, and am reporting it here first.
> Please let me know if there’s a procedure I should follow, or someplace
> else I should go instead. Thank you.
>
>
>
> I captured screen shots and put them here. This is the best place to
> see what I’m reporting:
>
> http://www.nedharvey.com/tortoise_svn_bug
>
>
>
> For anyone who would prefer reading –
>
>
>
> · At some point in history (about a year ago) we had a mac user
> commit files with ‘foo (x|y) bar’ in the filename.
>
> · This caused problems back then for windows users, so the files
> were renamed to exclude the parens and vertical bar. Via svn mv

The parens are not a problem, only the bar is.

> · In Tortoise now, if we do a sparse checkout (immediates) of


> the parent, and then try to go fully recursive (infinity) on the subdir
> which contains the formerly renamed files … Then Tortoise chokes while
> showing the filename which has not existed for over a year.
>
> · Using tortoise, if we do a fully recursive checkout of

> **just** the subdir containing the formerly renamed files, there is no
> problem.

Can you please try with the Subversion command line client?
Run an
$ svn update --depth infinity --set-depth infinity path/to/workingcopy

Stefan

--
___
oo // \\ "De Chelonian Mobile"
(_,\/ \_/ \ TortoiseSVN
\ \_/_\_/> The coolest Interface to (Sub)Version Control
/_/ \_\ http://tortoisesvn.net

------------------------------------------------------
http://tortoisesvn.tigris.org/ds/viewMessage.do?dsForumId=757&dsMessageId=1076336

To unsubscribe from this discussion, e-mail: [dev-uns...@tortoisesvn.tigris.org].

signature.asc

Edward Ned Harvey

unread,
Jan 30, 2009, 4:02:10 PM1/30/09
to d...@tortoisesvn.tigris.org
> The parens are not a problem, only the bar is.

I suspected as much.


> Can you please try with the Subversion command line client?
> Run an
> $ svn update --depth infinity --set-depth infinity path/to/workingcopy

FYI, I worked around this problem by removing the history of the file(s) as follows:
mv logistic_function.pdf tmp_logistic_function.pdf
svn rm --force logistic_function.pdf
svn commit -m ''
mv tmp_logistic_function.pdf logistic_function.pdf
svn add logistic_function.pdf
svn commit -m ''

So now I'm going to reproduce the behavior in a sandbox file:// repository.

First question ... Yes I'm able to reproduce it by creating a file with a bad name inside a subdir, then renaming the file, then doing a sparse checkout of the parent, then trying to go fully recursive with tortoise. So let's see what the command line does:

C:\>svn --version
svn, version 1.5.5 (r34862)

C:\working_dir>svn update --set-depth infinity dir1
svn: Can't check path 'dir1\New(x|y)Text Document.txt': The filename, directory name, or volume label syntax is incorrect.

Ok - So I guess that means it's a svn bug. I'll go talk to the other list.

This e-mail message may contain proprietary, confidential or legally privileged information for the sole use of the person or entity to whom this message was originally addressed. Any review, e-transmission dissemination or other use of or taking of any action in reliance upon this information by persons or entities other than the intended recipient is prohibited. If you have received this e-mail in error kindly delete this e-mail from your records. If it appears that this mail has been forwarded to you without proper authority, please notify us immediately at neta...@patni.com and delete this mail.

------------------------------------------------------
http://tortoisesvn.tigris.org/ds/viewMessage.do?dsForumId=757&dsMessageId=1076520

Reply all
Reply to author
Forward
0 new messages