Hi,
No, we don't keep log files for each and every users.
# bzr wants to write a ~/.bzr.log. Suppress that (see
# https://bugs.edge.launchpad.net/bzr/+bug/106117 for more).
$ENV{'BZR_LOG'} = '/dev/null';
- Sylvain
On Sat, Oct 16, 2010 at 10:10:44AM +0200, Jan Djärv wrote:
> Thanks for the answer. You don't happen to have that logfile available?
>
> Jan D.
>
> 15 okt 2010 kl. 19:59 skrev Sylvain Beucler <b...@gnu.org>:
>
> > Hi,
> >
> > There's no locale. The 'locales' packages, in particular, is not
> > installed.
> >
> > I also think that the GECOS' encoding is generally independant from
> > the user's current locale.
> >
> > - Sylvain
> >
> > On Fri, Oct 15, 2010 at 08:02:39AM +0200, Jan Djärv wrote:
> >> Hello.
> >>
> >> I recently had a problem where commit to bzr failed.
> >> Sylvain Beucler correctly assumed non-ascii characters in the
> >> GECOS-field where the problem and that a bzr was at fault. I filed
> >> a bug report on bzr that stated that the bzr server fails when there
> >> are non-ascii characters in the GECOS field. They now request more
> >> information, can you help?
> >>
> >> The bug report is here:
> >>
> >> https://bugs.launchpad.net/bugs/659763
> >>
> >> I qoute the last entry where they request information:
> >>
> >> "I would speculate that Python may run on savannah with the locale set
> >> such that it expects gecos to be in ascii. You would think that LANG=
> >> whatever gets passed across ssh, but perhaps not. If you can get the
> >> server-side traceback, which should be in .bzr.log there, that could
> >> help."
> >>
> >> Thanks,
> >>
> >> Jan D.
> >>
> >
