Hmm, OK. Seems the test only fails locally between r2407 and 2408. But on the wider scale between releases we've maintained compatibility from 0.11/0.12 to dev r2408.
It seems the problem was fixed in r2408 relative to previous releases. However revisions after 0.12.0 and prior to r2408 had ABI breaks. And yes, it does indeed seem that we've maintained ABI compatibility by virtue of having libmircommon.so.3 and libmircommon.so.4 loadable in the same client process simultaneously. Scary, but seems to work. ** Changed in: mir Status: In Progress => Incomplete ** Changed in: mir (Ubuntu) Status: New => Incomplete ** Changed in: mir Milestone: 0.13.0 => None -- 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/1434400 Title: [regression] Client ABI 8 broken in 0.13 series Status in Mir: Incomplete Status in mir package in Ubuntu: Incomplete Bug description: I've just done a little sanity testing of our client ABI changes and found we've broken the client 8 ABI at least once, maybe twice in series 0.13. Test case: Drop older demos client binaries (which still only use libmirclient8) into a newer build tree. Expected: demo clients still run. Observed: demo clients fail to start with: bin/.mir_demo_client_fingerpaint-uninstalled: relocation error: bin/.mir_demo_client_fingerpaint-uninstalled: symbol mir_surface_get_buffer_stream, version MIR_CLIENT_8 not defined in file libmirclient.so.8 with link time reference To manage notifications about this bug go to: https://bugs.launchpad.net/mir/+bug/1434400/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp