touch-packages team mailing list archive

[Launchpad Bug Tracker <1423591@xxxxxxxxxxxxxxxxxx>]

This bug was fixed in the package mir - 0.12.0+15.04.20150228-0ubuntu1

---------------
mir (0.12.0+15.04.20150228-0ubuntu1) vivid; urgency=medium

  [ Alberto Aguirre ]
  * New upstream release 0.12.0 (https://launchpad.net/mir/+milestone/0.12.0)
    - Packaging changes:
      . Client platform packages now include the Mir client platform ABI
        number. Thusly, mir-client-platform-(mesa|android) is replaced by
        mir-client-platform-(mesa|android)2
      . Server graphics platform packages now include the Mir graphics
        platform ABI number. Thusly, mir-platform-graphics-(mesa|android)
        is replaced by mir-platform-graphics-(mesa|android)1
    - ABI summary: Servers need rebuilding, but clients do not;
      . Mirclient ABI unchanged at 8
      . Mircommon ABI unchanged at 3
      . Mirplatform ABI unchanged at 6
      . Mirserver ABI bumped to 30
    - Bug fixes:
      . [regression] Platform libraries and packages are not versioned thus
        are not installable in parallel (LP: #1423591)
      . [regression] Deadlock in TimeoutFrameDroppingPolicy logic (LP: #1421255)

  [ CI Train Bot ]
  * New rebuild forced.
 -- CI Train Bot <ci-train-bot@xxxxxxxxxxxxx>   Sat, 28 Feb 2015 10:30:53 +0000

** Changed in: mir (Ubuntu)
       Status: Triaged => 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/1423591

Title:
  [regression] Platform libraries and packages are not versioned

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

Bug description:
  Our graphics/client platform libraries and packages are not versioned
  and thus are not installable in parallel.

  Since our other libraries are installable in parallel, this can lead
  to problems like the one seen in [1]:

  1. Start with a system that has Mir 0.11 (mirserver19, mirplatform6, MIR_GRAPHICS_PLATFORM_1).
  2. Bump mirserver ABI 20 in *trunk*, build and install packages (mirserver20, mirplatform7, MIR_GRAPHICS_PLATFORM_2).
  3. Applications that use mirserver19 (e.g. USC) will load the new graphics platform modules, try to load a symbol with version 
  MIR_GRAPHICS_PLATFORM_1 (which is what mirserver19 works with) and fail.

  Note that this doesn't happen if we don't bump the mirserver ABI,
  because in that case when installing the new package we replace the
  system mirserver19 with a version that looks for
  MIR_GRAPHICS_PLATFORM_2, which is the correct version for the new
  graphics platform binaries.

  [1] https://code.launchpad.net/~alan-griffiths/mir/test-ABI-bump-
  libmirserver/+merge/250177

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