Stephan Hermann <sh@sourcecode.de> writes:
> On Wednesday 06 August 2003 17:23, kfogel@collab.net wrote:
> > Stephan Hermann <sh@sourcecode.de> writes:
> > > When you are trying to import now the files into the repository, this
> > > action will abort with the failure: failure during string recode
> > > (utf.c:173) (libsvn_subr).
> > > After this action, the DB is completly broken.
> >
> > What does "broken" mean exactly?
>
> broken means, that there is no repository after the aborted import.
>
> after checkout the repository db is not broken at all.
Sorry, I'm looking for a *much* more detailed answer... When you say
there is "no repository", do you mean something like this:
$ svnadmin create myrepos
$ cd import-tree
$ svn import file:///path/to/myrepos ...
[see error happen]
$ cd ..
$ ls myrepos
ls: myrepos: no such file or directory
:-) ? (I assume that's not what's happening.)
or Do you just mean that the files you tried to import are not present
in the repository? That's expected for a failed import. Subversion
does all or none, no halfway.
If you could simply post a complete transcript, from beginning to end,
that might help.
By the way, as other people in this thread have said: if you try to do
character conversion in a locale that doesn't support the characters
in question, I'm not sure that failure is a "bug". At least, I'm not
sure what the correct behavior for Subversion would be. It has no way
to guess at a correct representation for the characters...
Again, I might be misunderstanding what's happening, though.
-Karl
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Received on Thu Aug 7 18:20:33 2003