touch-packages team mailing list archive

[Launchpad Bug Tracker <1353855@xxxxxxxxxxxxxxxxxx>]

This bug was fixed in the package unity-scopes-api -
0.6.11+15.04.20150121.2-0ubuntu1

---------------
unity-scopes-api (0.6.11+15.04.20150121.2-0ubuntu1) vivid; urgency=low

  [ Ubuntu daily release ]
  * debian/libunity-scopes3.symbols: auto-update to released version

  [ thomas-voss ]
  * Switch from QNetwork to net-cpp (LP: #1326816, #1409995)

  [ Michał Sawicz ]
  * Depend on :native version of g++ to allow cross-compiling to work.
    Also run `wrap-and-sort -at` (LP: #1353855)

  [ Marcus Tomlinson ]
  * Switch from QNetwork to net-cpp (LP: #1326816, #1409995)

  [ Michi Henning ]
  * Added utility subdir to header tests.
  * Bunch of miscellaneous fixes:

  [ James Henstridge ]
  * Expose the deserialize() static method on FilterBase and FilterState
    for use by the Go bindings.
 -- Ubuntu daily release <ps-jenkins@xxxxxxxxxxxxxxxxxxx>   Wed, 21 Jan 2015 12:46:41 +0000

** Changed in: unity-scopes-api (Ubuntu)
       Status: In Progress => Fix Released

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to unity-scopes-api in
Ubuntu.
https://bugs.launchpad.net/bugs/1353855

Title:
  Explicit g++ 4.9 dependency breaks cross-building

Status in Mir:
  Confirmed
Status in mir package in Ubuntu:
  Confirmed
Status in qtmir package in Ubuntu:
  Fix Released
Status in unity-scopes-api package in Ubuntu:
  Fix Released
Status in unity8 package in Ubuntu:
  Fix Released

Bug description:
  With the new explicit g++ 4.9 dependency apt falls over when trying to
  install cross-dependencies for e.g. Mir:

  The following packages have unmet dependencies:
   g++-4.9:armhf : Depends: gcc-4.9:armhf (= 4.9.1-4ubuntu3) but it is not going to be installed
  E: Build-dependencies for sbuild-build-depends-mir-dummy could not be satisfied.

  This means cross-building doesn't work for any packages that have that
  dependency added. We were told it's going to be fine due to 4.9
  becoming default, but it is now, and the situation remains.

To manage notifications about this bug go to:
https://bugs.launchpad.net/mir/+bug/1353855/+subscriptions