> -----Original Message-----
> From: Vincent Lefevre [mailto:vincent-svn_at_vinc17.net]
> Sent: maandag 29 februari 2016 16:24
> To: dev_at_subversion.apache.org
> Subject: Unversioned files with invalid UTF-8 sequence in name confuse svn
>
> With:
>
> svn, version 1.9.3 (r1718519)
> compiled Jan 16 2016, 04:46:46 on x86_64-pc-linux-gnu
>
> I have a working copy where "make check" has created files whose
> name contain invalid UTF-8 sequences. The consequence is that
> such files confuse svn:
>
> $ =svn st
> svn: E000022: Error converting entry in directory
> '/home/vlefevre/software/mpfr-3.1/tests' to UTF-8
> svn: E000022: Valid UTF-8 data
> (hex: 04 10 40 04 04 04 02 01 46 04 40)
> followed by invalid UTF-8 sequence
> (hex: c0 2e 69 64)
> zsh: exit 1 =svn st
>
> I think that a fatal error is a bug, i.e. "svn st" should just report
> that these files are unversioned. The requirement on the validity of
> filenames should just apply to versioned files or files to be versioned.
>
> These files can't even be removed with svn-clean, which reports the
> same error.
The problem is most likely not that they have an invalid utf-8 sequence in
their name, but that your settings report that filenames are encoded in one
way, while there is a file which name can't be expressed by that format.
You get this error when Subversion isn't able to convert the filename to its
internal utf-8 format, which should be capable to express any valid
filename. (If you declare that all filenames are utf-8, there wouldn't be a
conversion, so in most cases not an error)
To just handle it as unversioned as you suggest we need to at least be able
to express its name.
As you found out cleanup is not going to help here... we just can't access
this file (or directory, or symlink), so we can't delete it or anything to
help you.
Bert
Received on 2016-02-29 17:00:19 CET