https://osmocom.org/https://osmocom.org/favicon.ico?16647414092019-05-22T16:37:30ZOpen Source Mobile CommunicationsOsmoNITB - Bug #4016: openbsc debian package build broken on Debian unstable, debian testing and Ubuntu 19.04https://osmocom.org/issues/4016?journal_id=145712019-05-22T16:37:30Zkeith
<ul></ul><p>This printf should really be commented:</p>
<p><a class="external" href="https://sourceforge.net/p/libdbi-drivers/libdbi-drivers/ci/master/tree/drivers/sqlite3/dbd_sqlite3.c#l1198">https://sourceforge.net/p/libdbi-drivers/libdbi-drivers/ci/master/tree/drivers/sqlite3/dbd_sqlite3.c#l1198</a></p>
<p><a class="external" href="https://stackoverflow.com/questions/21572800/what-causes-no-tables-in-statement-message">https://stackoverflow.com/questions/21572800/what-causes-no-tables-in-statement-message</a></p>
<p>Maybe upstream will fix it?</p>
<p>Maybe just not build legacy openbsc for unstable?</p> OsmoNITB - Bug #4016: openbsc debian package build broken on Debian unstable, debian testing and Ubuntu 19.04https://osmocom.org/issues/4016?journal_id=145732019-05-22T19:30:17Zlaforge
<ul></ul><p>On Wed, May 22, 2019 at 04:37:30PM +0000, keith [REDMINE] wrote:</p>
<blockquote>
<p>Maybe upstream will fix it?</p>
</blockquote>
<p>if they will, it will take too long to propagate.</p>
<blockquote>
<p>Maybe just not build legacy openbsc for unstable?</p>
</blockquote>
<p>As indicated, I think the fix will be in somehow disabling execution of that test,<br />or writing it in a way that only stderr output matters, but not stdout (or vice versa,<br />depending on where libdbi insists on writing).</p> OsmoNITB - Bug #4016: openbsc debian package build broken on Debian unstable, debian testing and Ubuntu 19.04https://osmocom.org/issues/4016?journal_id=145782019-05-23T09:50:34Zkeith
<ul></ul><p><a class="external" href="https://gerrit.osmocom.org/#/c/openbsc/+/14140/">https://gerrit.osmocom.org/#/c/openbsc/+/14140/</a></p> OsmoNITB - Bug #4016: openbsc debian package build broken on Debian unstable, debian testing and Ubuntu 19.04https://osmocom.org/issues/4016?journal_id=150002019-06-27T09:18:25Zosmith
<ul><li><strong>Status</strong> changed from <i>New</i> to <i>Resolved</i></li><li><strong>Assignee</strong> changed from <i>osmith</i> to <i>keith</i></li><li><strong>% Done</strong> changed from <i>0</i> to <i>100</i></li></ul><p>@keith's patch fixed the issue. Thank you!</p>