> Thanks for report, but there was already one open about this. See bug > #354413 for previous discussion. Also note that we are going to build > against a newer libdb as soon as we have the necessary stuff in place > for a db upgrade. Sorry for missing that.