touch-packages team mailing list archive

[Martin Pitt <martin.pitt@xxxxxxxxxx>]

Merely dropping the python-autopilot build-deps technically builds, but
it does get the previous ImportError for the autopilot module again when
building the docs. Could this just ship an empty dummy autopilot module
to quiesce this? I figure it can't possibly need the actual autopilot
module as the autopilot docs are built by autopilot itself, not by ui-
toolkit?

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to ubuntu-ui-toolkit in
Ubuntu.
https://bugs.launchpad.net/bugs/1446533

Title:
  build-depends on python-autopilot which is in universe

Status in ubuntu-ui-toolkit package in Ubuntu:
  In Progress
Status in ubuntu-ui-toolkit source package in Vivid:
  In Progress

Bug description:
  ubuntu-ui-toolkit is in main, but https://code.launchpad.net/~ubuntu-
  sdk-team/ubuntu-ui-toolkit/sphinxSysPath/+merge/252891 introduced a
  build-dependency to python-autopilot which is in universe. Due to our
  misconfigured silo PPAs we didn't spot that on merging, but it breaks
  main (http://people.canonical.com/~ubuntu-archive/component-
  mismatches.svg) and renders ubuntu-ui-toolkit unbuildable in vivid.

  The build dependency needs to be dropped again. Alternatively it could
  move to python3-autopilot and you write MIRs for autopilot and its
  dependencies, but that's getting tight for vivid.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/ubuntu-ui-toolkit/+bug/1446533/+subscriptions