[Yum-devel] Logging bug (yum or python)

Mihai Ibanescu misa+yum at redhat.com
Thu Jul 20 18:15:44 UTC 2006


On Thu, Jul 20, 2006 at 01:58:52PM -0400, seth vidal wrote:
> On Mon, 2006-07-17 at 13:52 -0400, Mihai Ibanescu wrote:
> > On Mon, Jul 17, 2006 at 11:34:51AM -0400, James Bowes wrote:
> > > Mihai Ibanescu wrote:
> > > >Hello,
> > > >
> > > >This logging bug landed in the python component:
> > > >
> > > >https://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=198971
> > > >
> > > >If someone can produce a test case outside of yum (I don't have a rawhide
> > > >machine handy right now), please let me know.
> > > >
> > > 
> > > FYI, the bug now has a test case attached for outside of yum that 
> > > reproduces the problem for me on FC5.
> > 
> > Well, it's a test case for "INFO".lower() != "info".
> > Here's a test case for exhibiting the problem in python's logging library
> > (attached).
> > 
> > This works:
> > python /tmp/logging-broken.py
> > 
> > This doesn't:
> > 
> > LANG=tr_TR.UTF-8 python /tmp/logging-broken.py
> > 
> > Looks like it has to be the syslog handler, otherwise it won't attempt to
> > display the priority.
> > 
> 
> Just following up here - is this a bug we can get fixed in python or
> should we make a workaround in yum?

It's a bug in python, I'm negotiating a fix with upstream python :-)
It's unlikely upstream will fix it in time, I'll carry the fix in rawhide if
at least it gets accepted in HEAD. I prefer not to maintain the patches
forever :-)

Misa



More information about the Yum-devel mailing list