touch-packages team mailing list archive

[Launchpad Bug Tracker <1415321@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: 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/1415321

Title:
  [regression] Client functions residing in libmircommon

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

Bug description:
  We seem to now have a bunch of client functions living in
  libmircommon:

  $ nm -D lib/libmircommon.so | grep ' mir_'
  0000000000010287 T mir_event_get_close_surface_event
  000000000001012a T mir_event_get_input_event
  0000000000010264 T mir_event_get_orientation_event
  0000000000010241 T mir_event_get_prompt_session_event
  000000000001021e T mir_event_get_resize_event
  00000000000101fb T mir_event_get_surface_event
  0000000000010105 T mir_event_get_type
  000000000001038e T mir_event_ref
  00000000000103c6 T mir_event_unref
  000000000002dae2 T mir_input_event_get_device_id
  000000000002dbea T mir_input_event_get_event_time
  000000000002dcf0 T mir_input_event_get_key_input_event
  000000000002e5b5 T mir_input_event_get_pointer_input_event
  000000000002e003 T mir_input_event_get_touch_input_event
  000000000002d9d8 T mir_input_event_get_type
  000000000002ddc9 T mir_key_input_event_get_action
  000000000002de1e T mir_key_input_event_get_key_code
  000000000002dfab T mir_key_input_event_get_modifiers
  000000000002de43 T mir_key_input_event_get_scan_code
  0000000000010368 T mir_orientation_event_get_direction
  000000000002e6bb T mir_pointer_input_event_get_action
  000000000002e7d9 T mir_pointer_input_event_get_axis_value
  000000000002e733 T mir_pointer_input_event_get_button_state
  000000000002e68f T mir_pointer_input_event_get_modifiers
  0000000000010342 T mir_prompt_session_event_get_state
  000000000001031c T mir_resize_event_get_height
  00000000000102f6 T mir_resize_event_get_width
  00000000000102aa T mir_surface_event_get_attribute
  00000000000102d0 T mir_surface_event_get_attribute_value
  000000000002dfd7 T mir_touch_input_event_get_modifiers
  000000000002e1df T mir_touch_input_event_get_touch_action
  000000000002e453 T mir_touch_input_event_get_touch_axis_value
  000000000002e0dd T mir_touch_input_event_get_touch_count
  000000000002e0f7 T mir_touch_input_event_get_touch_id
  000000000002e349 T mir_touch_input_event_get_touch_tooltype

  I think this could cause serious risk to clients/toolkits that call
  them. As their symbol versions are no longer tied to the stable client
  ABI, but instead tied to the more volatile mircommon ABI.

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