[Svnmerge] KeyError on svnmerge.py

Laurent PETIT laurent.petit at gmail.com
Fri Mar 7 14:15:40 PST 2008


I looked in svn svn repository.
It seems that --xml option appeared in revision 16014 on svninfo commande.
This corresponds roughly to the tag for version 1.3.0 of svn (revision
18100).
I'm not sure then that my patch will be accepted as is, since it prevents
users of clients lower than 1.3.0 to use svnmerge ?

-- 
Laurent

2008/3/7, Laurent PETIT <laurent.petit at gmail.com>:
>
> Hello,
>
> Here is a patch I would like to submit. It enables a better i18n handling
> of svnmerge, by adding i18n support to get_svninfo() method.
>
> --
> Laurent
>
> 2008/3/7, Laurent PETIT <laurent.petit at gmail.com>:
> >
> > Hello,
> >
> > I just did a patch that I will be able to submit in the following hours
> > to the translation problem.
> >
> > I switched the implementation of get_svninfo() from the parsing of the
> > plain text result to the parsing of the xml result.
> >
> > I'm currently downloading the unit tests to see if they all still pass,
> > and then I'll submit the patch.
> >
> > --
> > Laurent
> >
> > 2008/3/7, Raman Gupta <rocketraman at fastmail.fm>:
> > >
> > >  Hernán Martínez Foffani wrote:
> > > > I couldn't find a way to tell svn (and only the svn client) to send
> > > its
> > > > output in english and not in my locale. I can't change my global
> > > > settings because it would affect our development enviroment.
> > > >
> > > > svnmerge.py might try to read Subversion's LC_MESSAGE translating
> > > > "Repository root" before parsing the output. It won't be an easy
> > > > task and giving that you are all volunteers here I'll refrain
> > > > myself to ask for it.
> > >
> > >
> > > Another solution might be for svnmerge.py to try svn info --xml if it
> > > is available -- I believe that will always output in english. I don't
> > > know when the --xml option was added but it should work for all recent
> > > svn clients.
> > >
> > > This shouldn't be a major change, and if you want to attempt it,
> > > patches are welcome.
> > >
> > >
> > > > For the time being, I'm switching back to an older version.
> > > > Does anybody knows in which version was this feature commited?
> > > > I would like to have the latest version that doesn't include
> > > > "svn info" output parsing.
> > >
> > >
> > > I believe that svnmerge.py has always done this. However, some recent
> > > commits may have changed the behavior unintentionally as far as the
> > > svn info output is concerned. Can you verify if the problem occurs
> > > with rev 29665?
> > >
> > > Cheers,
> > >
> > > Raman Gupta
> > >
> > >
> > > _______________________________________________
> > > Svnmerge mailing list
> > > Svnmerge at orcaware.com
> > > http://www.orcaware.com/mailman/listinfo/svnmerge
> > >
> > >
> > >
> >
> >
>
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: </pipermail/svnmerge/attachments/20080307/bffcbe4c/attachment.html>


More information about the Svnmerge mailing list