[svn.haxx.se] · SVN Dev · SVN Users · SVN Org · TSVN Dev · TSVN Users · Subclipse Dev · Subclipse Users · this month's index

Re: bugreport: filename containing a ? imports ok, but checkout fails

From: Harco de Hilster <harcoh_at_ATConsultancy.nl>
Date: 2004-05-04 08:46:44 CEST

kfogel@collab.net wrote:

>Harco de Hilster <harcoh@ATConsultancy.nl> writes:
>
>
>>Description:
>>
>>Filenames with a ? character import ok, but a checkout of the tree fails
>>with an XML parse error: non welformed xml ..... in a internal svn file.
>>(Sorry lost the exact filename). The isssue is reproduceable.
>>
>>Steps:
>>
>>- I did an import of an existing source tree. One of the files contained
>>a '?' mark in it the filename. Probably the result of an incorrect
>>character set translation. Although unpractical, a '?' is a valid
>>character in a filename. The import completed ok.
>>
>>- A checkout of the just imported tree proceded fine upto the '?' file.
>>Then the checkout failed with the XML parse error msg.
>>
>>
>
>You were checking out over http:// or https://, right?
>
>
>
Yes over https. I've included a tar.gz file with the 'offending'
filenames. These files give all sorts of trouble
with other utitlites as well, but it shouldn't break the svn repository.

Thanks for your response,

Harco

-- 
-----------------+--------------------+-------------------------------
Harco de Hilster  AT Consultancy       Phone:  +31(0)24-3527282      
Unix Consultant   Toernooiveld 104     Fax:    +31(0)24-3527292      
                  6501 BK  Nijmegen    E-mail: harcoh@ATConsultancy.nl
                  The Netherlands                                     
-----------------+--------------------+-------------------------------


---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org

Received on Wed May 5 03:37:44 2004

This is an archived mail posted to the Subversion Dev mailing list.

This site is subject to the Apache Privacy Policy and the Apache Public Forum Archive Policy.