group.of.nepali.translators team mailing list archive

[Launchpad Bug Tracker <1588330@xxxxxxxxxxxxxxxxxx>]

This bug was fixed in the package libodb-qt - 2.4.0-2build0~16.04.1

---------------
libodb-qt (2.4.0-2build0~16.04.1) xenial; urgency=medium

  * No change rebuild for c++11 ABI transition to fix incompatible builds
    with libodb. LP: #1588330.

 -- Dimitri John Ledkov <xnox@xxxxxxxxxx>  Thu, 16 Feb 2017 13:06:28
+0000

** Changed in: libodb-sqlite (Ubuntu Xenial)
       Status: Fix Committed => Fix Released

-- 
You received this bug notification because you are a member of नेपाली
भाषा समायोजकहरुको समूह, which is subscribed to Xenial.
Matching subscriptions: Ubuntu 16.04 Bugs
https://bugs.launchpad.net/bugs/1588330

Title:
  Incompatible builds of libodb and libodb-mysql

Status in libodb package in Ubuntu:
  Fix Released
Status in libodb-boost package in Ubuntu:
  Fix Released
Status in libodb-pgsql package in Ubuntu:
  Fix Released
Status in libodb-qt package in Ubuntu:
  Fix Released
Status in libodb-sqlite package in Ubuntu:
  Fix Released
Status in libodb source package in Xenial:
  Fix Released
Status in libodb-boost source package in Xenial:
  Fix Released
Status in libodb-pgsql source package in Xenial:
  Fix Released
Status in libodb-qt source package in Xenial:
  Fix Released
Status in libodb-sqlite source package in Xenial:
  Fix Released
Status in libodb source package in Yakkety:
  Fix Released
Status in libodb-boost source package in Yakkety:
  Fix Released
Status in libodb-pgsql source package in Yakkety:
  Fix Released
Status in libodb-qt source package in Yakkety:
  Fix Released
Status in libodb-sqlite source package in Yakkety:
  Fix Released
Status in libodb source package in Zesty:
  Fix Released
Status in libodb-boost source package in Zesty:
  Fix Released
Status in libodb-pgsql source package in Zesty:
  Fix Released
Status in libodb-qt source package in Zesty:
  Fix Released
Status in libodb-sqlite source package in Zesty:
  Fix Released

Bug description:
  Only release all packages together!

  [Impact]

  * libodb stack changes abi when build with new enough g++ (due to c++11 abi tagging)
  * things that are compiled with new abi are ok (libodb-mysql); linking against mixed build things does not work (e.g. 3rd party apps, like odb-tests building against new libodb-mysql and old libodb)

  [Solution]
  * In debian, simply binNMUs were done without bumping the ABI =/

  * Whilst libodb-boost and libodb-qt do not appear to be affected, imho
  it is best to rebuild them too.

  [Testcase]
  * download odb-tests
  * autoreconf -fi
  * Build and link with following configs (./configure; make clean; make)
  + ./configure --with-database=sqlite
  + ./configure --with-database=mysql
  + ./configure --with-database=pgsql

  There appears to be some incompatibility between libodb and libodb-
  mysql in that the latter cannot resolve symbols from the former. More
  details are in this odb-users mailing list thread:

  http://www.codesynthesis.com/pipermail/odb-users/2016-May/003277.html

  My suspicion (discussed in the second post of the above thread) is
  that libodb is built in the C++11 mode while the rest of the ODB
  runtimes (libodb-mysql and libodb-pgsql were confirmed by the users)
  -- C++98. I, however, couldn't find the package build logs (neither on
  Ubuntu nor on Debian) to confirm this.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/libodb/+bug/1588330/+subscriptions