[Touch-packages] [Bug 1507982] Re: OTA7 broke previously working app

2015-10-21 Thread Daniel van Vugt
OK, I have now hacked together a test environment on wily desktop and tried: 0.13.3 client --> 0.17.0 server (wily) FAILS 0.13.3 client --> 0.16.2 server (lp:mir/0.16) FAILS 0.13.3 client --> 0.15.2 server (lp:mir/0.15) WORKS I can confirm the primary issue is the first error:

[Touch-packages] [Bug 1507982] Re: OTA7 broke previously working app

2015-10-20 Thread Pat McGowan
** Also affects: mir (Ubuntu) Importance: Undecided Status: New ** Changed in: canonical-devices-system-image Status: New => Confirmed ** Changed in: canonical-devices-system-image Assignee: (unassigned) => kevin gunn (kgunn72) -- You received this bug notification

[Touch-packages] [Bug 1507982] Re: OTA7 broke previously working app

2015-10-20 Thread Daniel van Vugt
Hi dinamic, good to hear from you again. We do know of a protocol compatibility break that occurred in Mir 0.15.0, which was first reported as bug 1486496 (which due to disagreements got reworded and watered down such that mir-team was not required to fix the regression). I also mentioned back in

[Touch-packages] [Bug 1507982] Re: OTA7 broke previously working app

2015-10-20 Thread Launchpad Bug Tracker
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: mir (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to mir in Ubuntu.

[Touch-packages] [Bug 1507982] Re: OTA7 broke previously working app

2015-10-20 Thread Daniel van Vugt
Regarding option (c): It's possible that r2730 is no longer the only offending commit. We may have landed other similar breaks since then... kdub is the expert on all the related protocol semantic changes of late. -- You received this bug notification because you are a member of Ubuntu Touch

[Touch-packages] [Bug 1507982] Re: OTA7 broke previously working app

2015-10-20 Thread Daniel van Vugt
To clarify; I think this bug is effectively a duplicate of the problem I originally reported in: https://bugs.launchpad.net/mir/+bug/1486496/comments/0 However bug 1486496 was later reworded into a form that was less contentious and did not require any resolution of the protocol compatibility