linux/poky.git/bitbake/lib/bb/init.py, branch bernard

bitbake:init.py: Fix debug log level handling to correct debug output

2011-02-07T14:50:27+00:00

Signed-off-by: Richard Purdie

Inject taskpid into log records via our log handler

2011-01-10T22:09:11+00:00

It turns out that while log filters added with addFilter are only associated with that logger, and not its children, handlers are inherited, and handlers can be filters. So, let's add filtering to our existing LogHandler class which dispatches our log records as bitbake events. (Bitbake rev: 0153ace246e7c88366f45c8f035a2b4505a1c115) Signed-off-by: Chris Larson Signed-off-by: Richard Purdie

bitbake: For poky only, force the use of fetch2 codebase

2011-01-10T18:13:53+00:00

Signed-off-by: Richard Purdie

bitbake: Switch to fetch2 fetcher code based on the environment variable BBFETCH2

2011-01-10T18:12:53+00:00

Signed-off-by: Richard Purdie

bitbake/init.py: Add taskpid to all LogRecords (subclassed to be BBLogRecords)

2011-01-08T00:02:00+00:00

This allows us to identify which task messages are from. Signed-off-by: Richard Purdie

Work around issue with pickling of traceback objects

2011-01-04T14:46:34+00:00

(Bitbake rev: 82928613256bad92fde9f4071244a53e20fc89ee) Signed-off-by: Chris Larson Signed-off-by: Richard Purdie

Apply fix for issue where the loggers were constructed with the wrong class

2011-01-04T14:46:34+00:00

(Bitbake rev: 1b21daf052c49f3126dac001712ec01ad63c5f60) Signed-off-by: Chris Larson Signed-off-by: Richard Purdie

Switch bitbake internals to use logging directly rather than bb.msg

2011-01-04T14:46:33+00:00

We use a custom Logger subclass for our loggers This logger provides: - 'debug' method which accepts a debug level - 'plain' method which bypasses log formatting - 'verbose' method which is more detail than info, but less than debug (Bitbake rev: 3b2c1fe5ca56daebb24073a9dd45723d3efd2a8d) Signed-off-by: Chris Larson Signed-off-by: Richard Purdie

Use the python logging module under the hood for bb.msg

2011-01-04T14:46:33+00:00

(Bitbake rev: 47ca82397bc395b598c6b68b24cdee9e0d8a76d8) Signed-off-by: Chris Larson Signed-off-by: Richard Purdie

Use PendingDeprecationWarning for functions moved from bb to bb.utils

2010-07-02T14:41:36+00:00

This is necessary, as there has not yet been a release with the bb.utils versions in place. We can't show them a deprecation warning when they can't safely change it yet. Show a PendingDeprecationWarning until 1.10 releases and OE requires it, then we can move to DeprecationWarning. (Bitbake rev: 43700fa1ca1d2635de4ed46110057cb164ee82d1) Signed-off-by: Chris Larson Signed-off-by: Richard Purdie

linux/poky.git/bitbake/lib/bb/__init__.py, branch bernard

bitbake:__init__.py: Fix debug log level handling to correct debug output

Inject taskpid into log records via our log handler

bitbake: For poky only, force the use of fetch2 codebase

bitbake: Switch to fetch2 fetcher code based on the environment variable BBFETCH2

bitbake/__init__.py: Add taskpid to all LogRecords (subclassed to be BBLogRecords)

Work around issue with pickling of traceback objects

Apply fix for issue where the loggers were constructed with the wrong class

Switch bitbake internals to use logging directly rather than bb.msg

Use the python logging module under the hood for bb.msg

Use PendingDeprecationWarning for functions moved from bb to bb.utils

linux/poky.git/bitbake/lib/bb/init.py, branch bernard

bitbake:init.py: Fix debug log level handling to correct debug output

bitbake/init.py: Add taskpid to all LogRecords (subclassed to be BBLogRecords)