Bug #4016
closedopenbsc debian package build broken on Debian unstable, debian testing and Ubuntu 19.04
100%
Description
It seems there's some difference in libdbi or sqlite3 behvior, which causes it to print "no table in statement" during the execution of db_test during make check :(
This is happening both for network:osmocom:nightly as well as for network:osmocom:latest
So I guess we have to come up with a way to avoid executing db_test if the package is built on an affected distribution.
We might also simply stop building legacy openbsc.git, at least in the nightly builds? But then the problem for latest remains.
Updated by keith almost 5 years ago
This printf should really be commented:
https://stackoverflow.com/questions/21572800/what-causes-no-tables-in-statement-message
Maybe upstream will fix it?
Maybe just not build legacy openbsc for unstable?
Updated by laforge almost 5 years ago
On Wed, May 22, 2019 at 04:37:30PM +0000, keith [REDMINE] wrote:
Maybe upstream will fix it?
if they will, it will take too long to propagate.
Maybe just not build legacy openbsc for unstable?
As indicated, I think the fix will be in somehow disabling execution of that test,
or writing it in a way that only stderr output matters, but not stdout (or vice versa,
depending on where libdbi insists on writing).
Updated by keith almost 5 years ago
Updated by osmith almost 5 years ago
- Status changed from New to Resolved
- Assignee changed from osmith to keith
- % Done changed from 0 to 100
@keith's patch fixed the issue. Thank you!