touch-packages team mailing list archive

[Launchpad Bug Tracker <1445473@xxxxxxxxxxxxxxxxxx>]

This bug was fixed in the package mir - 0.13.1+15.10.20150520-0ubuntu1

---------------
mir (0.13.1+15.10.20150520-0ubuntu1) wily; urgency=medium

  [ Cemil Azizoglu ]
  * New upstream release 0.13.1 (https://launchpad.net/mir/+milestone/0.13.1)
    - ABI summary: No ABI break. Servers and clients do not need rebuilding.
      . Mirclient ABI unchanged at 8
      . Mircommon ABI unchanged at 4
      . Mirplatform ABI unchanged at 7
      . Mirserver ABI unchanged at 31
    - Bug fixes:
      . Can't load app purchase UI without a U1 account (LP: #1450377)
      . Crash because uncaught exception in mir::events::add_touch (LP: #1437357)

 -- CI Train Bot <ci-train-bot@xxxxxxxxxxxxx>  Wed, 20 May 2015 21:20:15
+0000

** Changed in: mir (Ubuntu)
       Status: New => Fix Released

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to mir in Ubuntu.
https://bugs.launchpad.net/bugs/1445473

Title:
  Acceptance tests link with static versions of client library and
  server components

Status in Mir:
  Fix Released
Status in mir package in Ubuntu:
  Fix Released

Bug description:
  Acceptance tests link with static versions of client library and
  server components [1]. This is bad because:

  1. mir_acceptance_tests ends up with multiples versions of static symbols, which can lead to strange errors
  2. We can inadvertently use private symbols, so the acceptance tests won't fail if we forget to make a symbol public

  The tests failures seen in https://code.launchpad.net/~afrantzis/mir/client-surface-buffering-mode/+merge/256455, are
  a result of (1). What happens is that we register valid surfaces with the built-in (picked up from mirclient-static) version of the MirSurface::is_valid() symbol (and therefore the corresponding valid_surfaces static container), but subsequently end up using the libmirclient.so.8 version of MirSurface::is_valid() symbol (and therefore the corresponding different and empty valid_surfaces static container).

  The aforementioned MP also suffers from (2), since although I forgot
  to expose the new client library symbol, the tests work fine.
  Depending on the particular case, we may only find out about the
  problem after the release, when a user tries to use the symbol and
  fail.

  [1] libmirclient-static.a, lib3rd_party.a, libmirclientrpc.a,
  libmirclientlttngstatic.a, libxcursorloader.a

To manage notifications about this bug go to:
https://bugs.launchpad.net/mir/+bug/1445473/+subscriptions