** Description changed: couchdb-glib is built without --disable-debug-messages which results in a build which sets its own log handler for g_debug macro. This handler searches for the undocumented COUCHDB_ENV_DEBUG_MESSAGES environment variable to decide whether it should display debug message or not. It may confuse developers who depend on the g_debug default behaviour. According to rodrigo from #ubuntuone it's fixed in maverick. There may be some packages depending on the current for displaying debug only when some environment variable is set but I don't see why would anyone do it. + + TEST CASE: + download attached testcase.py + with libcouchdb-glib-1.0-2 0.6.3-0ubuntu1 you will get this result: + kklimo...@vm-desert:~$ python testcase.py + ** (process:1424): DEBUG: You will see this message + kklimo...@vm-desert:~$ + + and with libcouchdb-glib-1.0-2 0.6.3-0ubuntu1.1 this one instead: + pkklimo...@vm-desert:~$ python testcase.py + ** (process:1590): DEBUG: You will see this message + ** (process:1590): DEBUG: but not this with 0.6.3-0ubuntu1 installed + kklimo...@vm-desert:~$
** Patch added: "couchdb-glib.debdiff" https://bugs.edge.launchpad.net/ubuntu/+source/couchdb-glib/+bug/591873/+attachment/1509673/+files/couchdb-glib.debdiff -- couchdb-glib sets its own, custom log handler for the g_debug https://bugs.launchpad.net/bugs/591873 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
