New mock logging

[Michael E Brown]

On Mon, Nov 12, 2007 at 05:15:04PM -0600, Michael E Brown wrote:
> On Mon, Nov 12, 2007 at 03:45:28PM -0700, Orion Poplawski wrote:
> > Michael E Brown wrote:
> > >On Fri, Nov 09, 2007 at 04:47:11PM -0700, Orion Poplawski wrote:
> > >>How do I get rid of the:
> > >>
> > >>2007-11-09 16:46:03,285 - util.py:194:DEBUG:
> > >>
> > >>prefix that seems to have appeared with mock 0.8 (0.8.4)?  At least from 
> > >>the build.log.  Might be useful in the other logs...
> > >
> > >Well, the problem I ran into was that the python logging module doesnt
> > >provide a nice way to pull handlers/formatters from the config file by
> > >name. The relevant code is in backend.py in the _resetLogging()
> > >function.
> > >
> > >On line 475, I set up the formatter. I can probably figure out a way to
> > >put the format line in the config file, but for now it is hardcoded.
> > 
> > It is nearly impossible to decipher what is going on in the builds as it 
> > stands.
> 
> I've made it configurable for the next release (0.8.8), and it is
> checked into the upstream git repo. I dont intend to make another
> release for another week or so. If you want the new logging, please
> check out git. (./configure && make rpm).
> 
> The default will be per your original request (build log is unadorned.)

Sorry to reply to myself, but I forgot to mention the config option
names (new for 0.8.8):

$ grep fmt /etc/mock/defaults.cfg 
# config_opts['build_log_fmt_name'] = "unadorned"
# config_opts['root_log_fmt_name']  = "detailed"
# config_opts['state_log_fmt_name'] = "state"

Where 'unadorned', 'state', and 'detailed' are names of formatters from
/etc/mock/logging.ini (or whatever log config file you have specified in
config_opts['log_config_file'])
--
Michael