On Tuesday 05 October 2004 23:19, Khairul Azhar wrote:
> On Tue, 5 Oct 2004 22:30:33 -0400, John Szakmeister
>
> <john@szakmeister.net> wrote:
> > I do have a couple of ideas. First, I know there were a few issues
> > with the first Win32 binaries that were released. You may want to
> > try and download the .zip file again.
>
> I downloaded svn-1.1.0-setup.exe (the installer version) and installed
> it. No joy.
Bummer.
> > Secondly, looking at the code, it appears that the above error can
> > occur if we fail to convert the path to the launched executable into
> > a valid UTF-8 sequence. Have you tried running something like 'svn
> > --help' from the same directory that you're running 'svnadmin' from?
>
> Okay. The following commands work (as far as I can tell):
>
> svn
> svnlook
> svnversion
> svndumpfilter
> The following commands do not work (gives the "Can't convert module
> path to UTF-8" error):
>
> svnadmin
> svnserve
This is what I find perplexing. 'svn', 'svnlook', 'svnversion', and
'svndumpfilter' all call svn_cmdline_init(), and they're fine. What in
the world is making 'svnadmin' and 'svnserve' work differently?
> What executable are you talking about here? What path? (You can talk
> in more technical terms if you want)
If you take a look at:
http://svn.collab.net/repos/svn/trunk/subversion/libsvn_subr/cmdline.c
you'll see that the svn_cmdline_init() function is generating this error.
If it's failing for 'svnadmin', then I'd expect it to be failing for
*all* of them. Is there another 'svnadmin' executable laying around in
your path somewhere that you might accidentally be executing instead?
-John
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Received on Wed Oct 6 12:53:32 2004