unity-system-compositor FTBFS on trusty against new Mir (libmirserver9)

Bug #1244192 reported by Timo Jyrinki
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Mir
Fix Released
Critical
Alan Griffiths
Unity System Compositor
Fix Released
Critical
Michael Terry
mir (Ubuntu)
Fix Released
Critical
Unassigned
unity-system-compositor (Ubuntu)
Fix Released
Undecided
Unassigned

Bug Description

While bug #1244131 got resolved, meanwhile Mir was bumped to libmirserver9, and we have a new build problem:

https://launchpadlibrarian.net/154881432/buildlog_ubuntu-trusty-amd64.unity-system-compositor_0.0.1%2B14.04.20131024.1-0ubuntu1_FAILEDTOBUILD.txt.gz
---
/usr/include/mirserver/mir/default_configuration_options.h: In member function 'virtual void SystemCompositorServerConfiguration::parse_options(boost::program_options::options_description&, mir::options::ProgramOption&) const':
/usr/include/mirserver/mir/default_configuration_options.h:83:18: error: 'virtual void mir::DefaultConfigurationOptions::parse_options(boost::program_options::options_description&, mir::options::ProgramOption&) const' is protected
     virtual void parse_options(boost::program_options::options_description& options_description, options::ProgramOption& options) const;
                  ^
/build/buildd/unity-system-compositor-0.0.1+14.04.20131024.1/src/system_compositor.cpp:86:84: error: within this context
         mir::DefaultServerConfiguration::parse_options(options_description, options);
                                                                                    ^
/build/buildd/unity-system-compositor-0.0.1+14.04.20131024.1/src/system_compositor.cpp:86:84: error: 'mir::DefaultConfigurationOptions' is not an accessible base of 'const SystemCompositorServerConfiguration'
make[3]: *** [src/CMakeFiles/unity-system-compositor.dir/system_compositor.cpp.o] Error 1
---

This is blocking the release of the mir stack and other stacks depending on the mir update.

Related branches

Changed in unity-system-compositor:
assignee: nobody → Michael Terry (mterry)
description: updated
Changed in mir:
status: New → In Progress
assignee: nobody → Alan Griffiths (alan-griffiths)
milestone: none → 0.1.1
Changed in mir:
status: In Progress → Fix Committed
Changed in mir:
importance: Undecided → Critical
Changed in mir (Ubuntu):
importance: Undecided → Critical
status: New → Triaged
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

Revision history for this message
PS Jenkins bot (ps-jenkins) wrote :

Fix committed into lp:unity-system-compositor at revision 92, scheduled for release in unity-system-compositor, milestone Unknown

Changed in unity-system-compositor:
status: New → Fix Committed
Revision history for this message
Launchpad Janitor (janitor) wrote :
Download full text (5.1 KiB)

This bug was fixed in the package mir - 0.1.0+14.04.20131028-0ubuntu1

---------------
mir (0.1.0+14.04.20131028-0ubuntu1) trusty; urgency=low

  [ Daniel van Vugt ]
  * Bump version 0.1.0
  * Add method for testing if Rectangle::contains(Rectangle), which is
    the basis of any occlusion detection. (LP: #1227739)
  * Add support for traversing the Scene from front surface to back.
    This is required for occlusion detection at least (coming soon). .
    (LP: #1227739)
  * Optimization: Turn off blending for surfaces that are not blendable.
    On some systems this can have a noticeable performance benefit.
  * Avoid rendering surfaces that are fully hidden by other surfaces.
    This is particularly important for mobile device performance. (LP:
    #1227739) . (LP: #1227739)
  * Remove orphaned tags, which appear to have come from the Compiz
    project (!?) Add tags for the most recent releases up to 0.0.16. No
    files changed, only tags.
  * Fix significant performance issues LP: #1241369 / LP: #1241371, and
    probably more(!) Added regression test to catch such regressions and
    revert the offending commit r1049. (LP: #1241369, #1241371)

  [ Brandon Schaefer ]
  * When Scroll events come in we don't keep around the android vscroll
    hscroll data. Store it now. (LP: #1233089)

  [ Albert Astals ]
  * Fix mismatched free() / delete / delete [] reported by valgrind

  [ Alexandros Frantzis ]
  * server: Extend server status (formerly pause/resume) listener to
    report "started" events This change is needed by users of
    libmirserver, so they can properly synchronize external interactions
    with the server. (LP: #1239876)
  * graphics,examples: Don't enable more outputs than supported when
    changing the display configuration. (LP: #1217877)
  * client: Allow clients to call API functions after a connection break
    has been detected When a client tries to call an API function after
    a connection break has been detected in a previous API call, the
    client blocks in the new call. This happens because in
    MirSocketRpcChannel::notify_disconnected() the pending RPC calls are
    not forced to complete, since the channel has already been marked as
    'disconnected' by the failure in the previous call. Note that if the
    break is first detected while calling an API function, then that
    call doesn't block, since this is the first time we call
    MirSocketRpcChannel::notify_disconnected() and the pending RPC calls
    are forced to complete. This commit solves this problem by always
    forcing requests to complete when a communication failure occurs,
    even if a disconnection has already been handled. This is preferred
    over the alternative of manually calling the completion callback in
    a try-catch block when calling an RPC method because of: 1.
    Correctness: In case the communication problem first occurs in that
    call, the callback will be called twice, once by
    notify_disconnected() and once manually. 2. Consistency: The
    callback is called from one place regardless of whether the
    communication problem is first detected during that call or not.
    (LP: #1201436)
  * graphics: Improve si...

Read more...

Changed in mir (Ubuntu):
status: Triaged → Fix Released
Revision history for this message
Launchpad Janitor (janitor) wrote :

This bug was fixed in the package unity-system-compositor - 0.0.1+14.04.20131028.1-0ubuntu1

---------------
unity-system-compositor (0.0.1+14.04.20131028.1-0ubuntu1) trusty; urgency=low

  [ Michael Terry ]
  * Mir trunk changed some symbols on us, so we shall follow suit.
  * Bump required version of Mir to 0.1.0. (LP: #1244192)

  [ Ubuntu daily release ]
  * Automatic snapshot from revision 92
 -- Ubuntu daily release <email address hidden> Mon, 28 Oct 2013 18:26:37 +0000

Changed in unity-system-compositor (Ubuntu):
status: New → Fix Released
Changed in mir:
status: Fix Committed → Fix Released
Changed in unity-system-compositor:
status: Fix Committed → Fix Released
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: Fix Released → Fix Committed
Michael Terry (mterry)
Changed in mir:
status: Fix Committed → Fix Released
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.