Re: E125005: Cannot accept 'svn:ignore' property because it is not encoded in UTF-8

On 10/01/2012 01:48 PM, Michael Herrmann wrote:
> SELES 11, cvs2svn 2.4.0-dev. During migration I get the following error:
> 
> ERROR: svnadmin failed with the following output while loading the dumpfile:
> svnadmin: E125005: Invalid property value found in dumpstream; consider
> repairing the source or using --bypass-prop-validation while loading.
> svnadmin: E125005: Cannot accept 'svn:ignore' property because it is not
> encoded in UTF-8
> 
> I use the following options:
> encoding = iso8859_1
> fallback-encoding = ascii
> default-eol = native
> tmpdir = /opt/data/mig1/cvs2svntemp/ebacode
> retain-conflicting-attic-files

Hmmm, I don't think I've seen this problem before.

From the error message, it sounds like Subversion insisting that the
contents of the svn:ignore property be UTF-8 encoded.  This property is
derived from the contents of .cvsignore files in your repository.
Presumably you have non-ASCII filenames listed in one of your .cvsignore
file in an encoding that is not UTF-8.  Perhaps this has never come up
before, or (IMO more likely) perhaps "svnadmin load" has become more
picky about rejecting invalid svn:ignore values.

The code where this is done is in svn_dump.py:
DumpstreamDelegate._add_or_change_path() and the function
generate_ignores().  It doesn't attempt any decoding of the file
contents.  The contents of the .cvsignore file should be run through the
cvs_filename_decoder.

I am working on a fix.  I hope to have it done in the next day or so.

Michael

-- 
Michael Haggerty
[email protected]
http://softwareswirl.blogspot.com/

------------------------------------------------------
http://cvs2svn.tigris.org/ds/viewMessage.do?dsForumId=1670&dsMessageId=3011601

To unsubscribe from this discussion, e-mail: [[email protected]].