Two problems with that statement: (1) That's just a test and not a fix or workaround; and (2) It's for Mir, not to be "applied in the protobuf package".
The relevant workaround for Mir is actually: https://code.launchpad.net/~vanvugt/mir/fix-1391976/+merge/262678 but we'll hold off reapplying that while Alan is proposing proper fixes for protobuf itself. ** Changed in: protobuf (Ubuntu) Assignee: (unassigned) => Alan Griffiths (alan-griffiths) ** Changed in: protobuf (Ubuntu) Importance: Undecided => High ** Changed in: protobuf (Ubuntu) Status: New => In Progress ** Changed in: mir Status: In Progress => Confirmed ** Changed in: mir Assignee: Alan Griffiths (alan-griffiths) => (unassigned) ** Changed in: mir (Ubuntu) Assignee: Alan Griffiths (alan-griffiths) => (unassigned) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1619616 Title: Mir test fails with protobuf3: Protobuf-can-be-reloaded (SEGFAULT) To manage notifications about this bug go to: https://bugs.launchpad.net/mir/+bug/1619616/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
