Mir

cross-compile-chroot.sh: E: Can't select candidate version from package liblttng-ust0:armhf as it has no candidate

Bug #1246975 reported by Daniel van Vugt
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Mir
Fix Released
Critical
Mathieu Trudel-Lapierre
mir (Ubuntu)
Fix Released
Critical
Unassigned

Bug Description

cross-compile-chroot.sh: E: Can't select candidate version from package liblttng-ust0:armhf as it has no candidate
[https://jenkins.qa.ubuntu.com/job/mir-android-trusty-i386-build/84/console]

This is blocking CI.

Related branches

Changed in mir:
assignee: Mir development team (mir-team) → Mathieu Trudel-Lapierre (mathieu-tl)
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: In Progress → Fix Committed
Changed in mir:
status: Fix Committed → Fix Released
Changed in mir (Ubuntu):
status: New → Triaged
importance: Undecided → Critical
Changed in mir (Ubuntu):
status: Triaged → Fix Committed
Revision history for this message
Launchpad Janitor (janitor) wrote :

This bug was fixed in the package mir - 0.1.1+14.04.20131120-0ubuntu1

---------------
mir (0.1.1+14.04.20131120-0ubuntu1) trusty; urgency=low

  [ Daniel van Vugt ]
  * New upstream release 0.1.1
    - Add unit tests for V/H scroll events.
    - surfaces: avoid publishing some internal headers, tidy up default
      configuration, integrate surfaces report.
    - client: Add mir_connection_drm_set_gbm_device()
    - graphics: avoid publishing some internal headers.
    - Fixed: unity-system-compositor FTBFS on trusty against new Mir
      (libmirserver9) (LP: #1244192)
    - compositor: avoid publishing some internal headers.
    - shell: Add set_lifecycle_state() to the Session interface.
    - frontend: avoid publishing some internal headers
    - logging: avoid publishing some internal headers.
    - Allow specifying the nested server name by passing --name= or setting
      MIR_SERVER_NAME=.
    - graphics,gbm: Inform the EGL platform about the used gbm device when
      using the native GBM platform
    - examples: Restore GL state after initializing buffers, fixing crashes
      observed in render_surfaces (LP: #1234563)
    - Continue refactoring the mir android display classes.
    - shell: Hoist focus control functions needed by unity-mir into
      FocusController interface
    - client: Remove the timeout for detecting server crashes
    - Avoid a race condition that could lead to spurious failures of server
      shutdown tests (LP: #1245336)
    - test_client_input.cpp: Bump reception time-out in client test fixture.
      (LP: #1227683)
    - Ensure StubBufferAllocator returns buffers with the properties requested,
      and not the same old hardcoded constants.
    - Update docs and scripting for trusty.
    - compositor: Make DefaultDisplayBufferCompositorFactory private to the
      compositor component.
    - Ignore warnings clang treats as errors, about unused functions being
      generated from macros in <lttng/tracepoint.h> (LP: #1246590)
    - Add resize() support to BufferBundle. This is the first step and lowest
      level of surface resize support.
    - Clean up constants relating to SwitchingBundle.
    - Fix the armhf chroot setup script to point to the right library, so
      cross compiling can work again (LP: #1246975)
    - shell: avoid publishing some internal headers.
    - input: avoid publishing some internal headers.
  * Bump timeouts used in socket testing. It seems 100ms isn't always
    enough, which leads to spurious test failures (LP: #1252144) (LP:
    #1252144)
  * Fix uninitialized variable causing random drm_auth_magic test
    failures. (LP: #1252144). (LP: #1252144)

  [ Ubuntu daily release ]
  * Automatic snapshot from revision 1165
 -- Ubuntu daily release <email address hidden> Wed, 20 Nov 2013 07:36:15 +0000

Changed in mir (Ubuntu):
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.