Hi Laurent! Thanks for taking the time to file this bug report!
Can you provide a working repeatable test case? The full log above doesn't actually seem to have something I can run to show the failure (so I can also show the success of the fix).
I was just now able to run the libdbi-drivers test suite, which does not produce this issue, as well as use rrdtool's libdbi integration without problems, querying from sqlite3. So I'm a little confused as to what is broken.
It should be noted that we went ahead and kept the ABI incompatible libdbi 0.8.3 in Maverick, as none of the packages in Ubuntu were affected by the ABI issues. Is it possible that you are using a custom compiled application that was built against 0.8.2, and needs to be rebuilt against 0.8.3?
Marking Incomplete pending a repeatable test case and confirmation that this is not due to the ABI incompatibilities.
Hi Laurent! Thanks for taking the time to file this bug report!
Can you provide a working repeatable test case? The full log above doesn't actually seem to have something I can run to show the failure (so I can also show the success of the fix).
I was just now able to run the libdbi-drivers test suite, which does not produce this issue, as well as use rrdtool's libdbi integration without problems, querying from sqlite3. So I'm a little confused as to what is broken.
It should be noted that we went ahead and kept the ABI incompatible libdbi 0.8.3 in Maverick, as none of the packages in Ubuntu were affected by the ABI issues. Is it possible that you are using a custom compiled application that was built against 0.8.2, and needs to be rebuilt against 0.8.3?
Marking Incomplete pending a repeatable test case and confirmation that this is not due to the ABI incompatibilities.