No handlers could be found for logger "bzr"

This is generally caused when some action would normally write to the log file, but "bzrlib.trace.enabled_default_logging()" has not been called yet.

As you are directly importing bzrlib, I would recommend adding that call somewhere before the "Branch.open()" possibly before the "get_version_from_changelog" depending on what that does.

I've gotten this message on a fresh Ubuntu install - it turned out that as I had installed 'etckeeper' and 'bzr', the root user had initialized the ~/.bzr.log and ~/.bazaar/, why the local user could not write to these.

Doing 'chown -R $user:$user ~/.bzr.log ~/.bazaar/' solved the problem.

I'm seeing this problem when I do a simple 'bzr pull' in my home directory, but the permissions on ~/.bzr.log and ~/.bazaar are fine. I haven't figure it out yet.

Barry, how interesting - with what version?

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Martin Pool wrote:
> Question #42886 on Bazaar changed:
> https://answers.edge.launchpad.net/bzr/+question/42886
>
> Martin Pool requested for more information:
> Barry, how interesting - with what version?
>

I'm pretty sure Barry runs nightlies. I thought this was fallout from
your patch which disabled setting up logging inside of bzr itself. (no
more 'trace.enable_default_logging()'.)

The logging module seems to be designed that if there are no 'sinks' it
emits a failure to stderr.

John
=:->
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.9 (Cygwin)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/

iEYEARECAAYFAktEHtAACgkQJdeBCYSNAAPMRQCeJkVctIAuH0vpE+TwTDnxUhMv
Wf0AoM6JSHfzRre+jL5HI0D6sE2swXTh
=ROiT
-----END PGP SIGNATURE-----

2010/1/6 John A Meinel <email address hidden>:
> I'm pretty sure Barry runs nightlies. I thought this was fallout from
> your patch which disabled setting up logging inside of bzr itself. (no
> more 'trace.enable_default_logging()'.)
>
> The logging module seems to be designed that if there are no 'sinks' it
> emits a failure to stderr.

So in that case the question is, who (what code) is trying to write to
the bzr logger? It shouldn't be anything in the bzr codebase, but
possibly a plugin is trying to do it.

--
Martin <http://launchpad.net/~mbp/>

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Martin Pool wrote:
> Question #42886 on Bazaar changed:
> https://answers.launchpad.net/bzr/+question/42886
>
> Martin Pool proposed the following answer:
> 2010/1/6 John A Meinel <email address hidden>:
>> I'm pretty sure Barry runs nightlies. I thought this was fallout from
>> your patch which disabled setting up logging inside of bzr itself. (no
>> more 'trace.enable_default_logging()'.)
>>
>> The logging module seems to be designed that if there are no 'sinks' it
>> emits a failure to stderr.
>
> So in that case the question is, who (what code) is trying to write to
> the bzr logger? It shouldn't be anything in the bzr codebase, but
> possibly a plugin is trying to do it.
>
>

in bzrlib.transport.ssh.ParamikoVendor._connect:

t = paramiko.Transport((host, port or 22))
t.set_log_channel('bzr.paramiko')
t.start_client()

^- I *think* that loggers are hierarchical, so that 'bzr.paramiko'
requires 'bzr' to be active.

This is in bzr.dev@4934

John
=:->
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.9 (Cygwin)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/

iEYEARECAAYFAktElOIACgkQJdeBCYSNAAPp6gCeNLwz4mHqtseKbDxpP5LX1n9d
ANQAoNmkjoCQBzU6hv8wf0J0MwDpdUOy
=gFru
-----END PGP SIGNATURE-----

then this is bug 494345

Actually, I'm pretty sure this is bug #503886

The no logger for paramiko is a different bug with a different cause. no logger for paramiko is because we didn't set up logging at all. Which is only relevant in trunk right now, and starting in about 2.1.0rc1.

No logger for "bzr" is generally when we try to open .bzr.log but can't, we try to log a warning, but we haven't gotten to the point of setting it up yet) This has been true for a very long time.