Made an issue to track this:
http://subversion.tigris.org/issues/show_bug.cgi?id=3912
smime.p7s
Description: S/MIME cryptographic signature
Am Dienstag, den 31.05.2011, 14:25 +0200 schrieb Stefan Sperling:
> On Tue, May 31, 2011 at 01:07:02AM +0200, Stefan Sperling wrote:
> > On Tue, May 31, 2011 at 01:41:54AM +0300, Daniel Shahaf wrote:
> > > > We should also make svnadmin verify complain if paths are not in UTF-8.
> > >
> > > +1.
>
On Tue, May 31, 2011 at 01:07:02AM +0200, Stefan Sperling wrote:
> On Tue, May 31, 2011 at 01:41:54AM +0300, Daniel Shahaf wrote:
> > > We should also make svnadmin verify complain if paths are not in UTF-8.
> >
> > +1.
> >
> > The validation that 'load' and 'commit' trigger is path_valid() in
>
> Subversion defines that it must be utf-8, so it can't answer this
> question
> for you.
Yes it can't anwer, but it may provide some option like to specify some
"encodings" e.g. via command line which it should try as fallback if it
encounters path names which are not UTF-8 - it may not be the "
> -Original Message-
> From: Daniel Shahaf [mailto:d...@daniel.shahaf.name]
> Sent: dinsdag 31 mei 2011 0:10
> To: Torsten Krah
> Cc: users@subversion.apache.org
> Subject: Re: svnadmin: Path '....' is not in UTF-8 - svnadmin load fails
>
> Torsten Kra
#define MBE multi-byte encoding
#defien SBE single-byte encoding
Stefan Sperling wrote on Tue, May 31, 2011 at 01:07:02 +0200:
> On Tue, May 31, 2011 at 01:41:54AM +0300, Daniel Shahaf wrote:
> > How would you handle a repository that contains the following
> > nodes/fspaths:
> >
> > /foo/bår
On Tue, May 31, 2011 at 01:41:54AM +0300, Daniel Shahaf wrote:
> How would you handle a repository that contains the following
> nodes/fspaths:
>
> /foo/bår(in UTF-8)
> /foo/bår(in latin1)
>
> ?
>
>
> How would you handle a repository that contains:
> /foo/barÉ (in latin1)
> /foo/barŠ
Stefan Sperling wrote on Tue, May 31, 2011 at 00:08:46 +0200:
> On Mon, May 30, 2011 at 11:47:30PM +0200, Torsten Krah wrote:
> > If <1.6 did not enforce this and 1.6 does - why does 1.6 not recode it
> > at the time it does encounter such "things" - at least via some optional
> > command line opti
> > Maybe Torsten would like to try this, but I doubt that modifying
> > Subversion's code is the kind of advice he was looking for.
>
> You're right ;-)
I was assuming that someone would point out a tool that does the
recoding at some point in the next 24 hours, which would render this
particula
Torsten Krah wrote on Mon, May 30, 2011 at 23:47:30 +0200:
> Am Dienstag, den 31.05.2011, 00:30 +0300 schrieb Daniel Shahaf:
> > then you could patch svnsync or one of those tools to do the
> > recoding. (just inject a filename-recoding editor at the right place)
>
> Of cause i'll take the source
Torsten Krah wrote on Mon, May 30, 2011 at 23:47:30 +0200:
> Am Dienstag, den 31.05.2011, 00:30 +0300 schrieb Daniel Shahaf:
> > Solution is to recode the pathnames (those that are neither in ASCII
> > nor in UTF-8).
>
> Sorry but your "solution" seems really a little bit odd to me.
> If <1.6 di
On Mon, May 30, 2011 at 11:47:30PM +0200, Torsten Krah wrote:
> If <1.6 did not enforce this and 1.6 does - why does 1.6 not recode it
> at the time it does encounter such "things" - at least via some optional
> command line option?
I think that is something we should add, yes.
We should also make
> I would try to edit the dump file with a hexeditor and replace the
> offending two bytes with two spaces (or the proper UTF-8 character
> if you know what should be there and the UTF-8 sequence has the same
> number of bytes).
Ok, lets take some hex editor and get rid of those bad sequences.
>
On Tue, May 31, 2011 at 12:30:54AM +0300, Daniel Shahaf wrote:
> 1.6 checks that paths are in UTF-8 at the time they enter the
> repository. This was always required but not always enforced.
>
> Solution is to recode the pathnames (those that are neither in ASCII nor
> in UTF-8).
Yes, that's wha
Am Dienstag, den 31.05.2011, 00:30 +0300 schrieb Daniel Shahaf:
> 1.6 checks that paths are in UTF-8 at the time they enter the
> repository. This was always required but not always enforced.
Ok - so 1.6 does things <1.6 did not but should.
>
> Solution is to recode the pathnames (those that ar
1.6 checks that paths are in UTF-8 at the time they enter the
repository. This was always required but not always enforced.
Solution is to recode the pathnames (those that are neither in ASCII nor
in UTF-8). If none of the third-party dump manipulation tools can do
that, then you could patch svn
Some more infos about those problem:
svnadmin verify tells me the revision in question is ok in the source
repo.
Using vim to view the revision dump show those 2 utf-8 chars at the end
of the path which i guess are making trouble:
Projektprofile/EMS(Newsletter, Infomails, À¦).doc
Maybe someone g
I want to load a repository with a fresh dump and did:
svnadmin -q dump /repo1 | svnadmin load /repo2
This is the error i get:
svnadmin: Path 'Projektprofile/EMS(Newsletter,
Infomails, ?\192?\166).doc' is not in UTF-8
How to fix this error - i am unable to load the dump in a new
repository?
Wh
18 matches
Mail list logo
