Mir

ABI stability of libmirserver

Bug #1223393 reported by Didier Roche-Tolomelli
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Mir
Expired
High
Unassigned

Bug Description

We need ABI stability in libmirserver and proper soname handling.

Once it's assured:
- we'll add a symbols file (upstream Mir packaging)
- change the dependency to not force dependency to match the exact version of Mir it was built against (upstream Mir, u-s-c and unity-mir packaging)
- not force rebuilding anymore unity-mir and u-s-c when there is a mir change (daily-release side)
- merge u-s-c and mir stacks (daily-release side)

Related branches

tags: added: make-xmir-default
Revision history for this message
kevin gunn (kgunn72) wrote :

just to add to the reasoning - image build occuring ~ every 4 hours, and we want to reboot on u-s-c install, not a great experience to reboot on every upgrade

Changed in xmir:
assignee: nobody → Robert Ancell (robert-ancell)
Changed in mir:
status: New → Triaged
Changed in unity-system-compositor:
status: New → Triaged
Changed in xmir:
status: New → Triaged
Changed in mir:
importance: Undecided → Critical
Changed in unity-system-compositor:
importance: Undecided → Critical
Changed in xmir:
importance: Undecided → Critical
Changed in unity-system-compositor:
assignee: nobody → Robert Ancell (robert-ancell)
Changed in mir:
assignee: nobody → Robert Ancell (robert-ancell)
Revision history for this message
Daniel van Vugt (vanvugt) wrote :

Although it's more difficult to control ABIs with C++, this should become very easy to manage once we branch...

Why are we rebooting? Isn't "sudo restart lightdm" or equivalent sufficient?

Revision history for this message
Didier Roche-Tolomelli (didrocks) wrote :

On the rebooting: robert and kgunn things it's not sufficient to only restart lightdm (and we have no way to tell to people "please shut down your session manager" that they don't even know of)

Revision history for this message
Robert Ancell (robert-ancell) wrote :

The reboot is the fix for bug 1221209 - it's not very pretty but the only easy way to ensure a user is running the upgraded version. It will be less of a problem when we stop having to recompile u-s-c (it seems likely this will not change very much once it's stable).

Revision history for this message
kevin gunn (kgunn72) wrote :

for the moment, mir team will bump the mir server so name every server api change

kevin gunn (kgunn72)
Changed in mir (Ubuntu):
status: New → Triaged
importance: Undecided → High
assignee: nobody → Robert Carr (robertcarr)
Changed in mir:
assignee: Robert Ancell (robert-ancell) → Robert Carr (robertcarr)
Revision history for this message
kevin gunn (kgunn72) wrote :

we have a current workable mechanism in place, with mir dev branch, lowering priority
also this is not a requirement for phone v1

Changed in mir:
importance: Critical → High
Changed in xmir:
importance: Critical → High
Changed in unity-system-compositor:
importance: Critical → High
kevin gunn (kgunn72)
tags: removed: make-xmir-default
no longer affects: mir (Ubuntu)
no longer affects: unity-system-compositor
no longer affects: xmir
Revision history for this message
PS Jenkins bot (ps-jenkins) wrote :

Fix committed into lp:~mir-team/mir/development-branch at revision None, scheduled for release in mir, milestone Unknown

Changed in mir:
status: Triaged → Fix Committed
Changed in mir:
status: Fix Committed → Triaged
Revision history for this message
PS Jenkins bot (ps-jenkins) wrote :

Fix committed into lp:~mir-team/mir/development-branch at revision 1107, scheduled for release in mir, milestone Unknown

Changed in mir:
status: Triaged → Fix Committed
Revision history for this message
Daniel van Vugt (vanvugt) wrote :

Silly bot... thinks that mentioning a bug number in a merge proposal means that bug has been fully resolved.

Changed in mir:
status: Fix Committed → Triaged
assignee: Robert Carr (robertcarr) → nobody
Changed in mir:
assignee: nobody → Mir development team (mir-team)
status: Triaged → In Progress
Changed in mir:
milestone: none → 0.1.1
Changed in mir:
milestone: 0.1.1 → 0.1.2
Revision history for this message
Daniel van Vugt (vanvugt) wrote :

Incomplete. "ABI stability in libmirserver" is too vague a goal, with no clear end. We all agree we want the ABIs to be more stable than they are now. But that's not something which has a definitive resolution.

Thus I would say "ABI stability in libmirserver" is invalid. However keeping it "Incomplete" in case there's something we can do to resolve "proper soname handling" in the mean time.

I suggest removing mentions of "ABI stability in libmirserver", and clarifying what kind of "proper soname handling" is desired.

Changed in mir:
status: In Progress → Incomplete
milestone: 0.1.2 → none
Revision history for this message
PS Jenkins bot (ps-jenkins) wrote :

Fix committed into lp:~mir-team/mir/development-branch at revision None, scheduled for release in mir, milestone Unknown

Changed in mir:
status: Incomplete → Fix Committed
Changed in mir:
status: Fix Committed → Incomplete
Revision history for this message
kevin gunn (kgunn72) wrote :

i'm closing this as this is a long-running architectural task.
we do have the server api under control now.

Changed in mir:
status: Incomplete → Fix Released
Revision history for this message
Daniel van Vugt (vanvugt) wrote :

Not true. If anything we're just ramping up to do major changes now.

Changed in mir:
status: Fix Released → Incomplete
Revision history for this message
Alan Griffiths (alan-griffiths) wrote :

We definitely don't have this "under control" - not only are we continuing to make changes, we don't have a strategy for maintaining a consistent API, let alone a stable ABI.

I do have some ideas about this, but it certainly can't be addressed until we've got the issues about co-ordinating with external data models (like the Qt scenegraphs) have been solved and polished.

Changed in mir:
assignee: Mir development team (mir-team) → nobody
Revision history for this message
Launchpad Janitor (janitor) wrote :

[Expired for Mir because there has been no activity for 60 days.]

Changed in mir:
status: Incomplete → Expired
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.