** Description changed:

- Snap development using Mir has been using the "stable phone overlay" PPA
- which is both inconvenient and a legacy of the cancelled Unity8 project.
+ [Impact]
+ Snap development using Mir has been using the "stable phone overlay" PPA 
which is both inconvenient and a legacy of the cancelled Unity8 project.
  
  It would greatly simplify things if Mir were updated in the Xenial
  archive.
  
+ [Test Case]
+ 
+ Build a Mir client snap (e.g. lp:~albaguirre/+snap/mir-client-demos)
+ against "Primary Ubuntu Archive" and deploy as described in
+ https://developer.ubuntu.com/en/snappy/guides/mir-snaps/
+ 
+ Expected: the client apps start and are visible on screen
+ Actual: the client don't apps start and are not visible on screen
+ 
+ [Regression Potential]
  Mir has two categories of dependent project:
  
    1 packages related to Unity8 (and unity-system-compositor)
    2 toolkits and other "clients" of Mir
  
- We should remove the first category as it is not helpful to carry these
- in the LTS.
+ We should remove the first category to avoid regressions as it is not
+ helpful to carry these in the LTS.
  
  The second category is dependent only on libmirclient which is ABI
- stable
+ stable.
+ 
+ The principle type of regression would be FTBFS where APIs have been
+ deprecated.
  
  notes:
  
  A recursive search or rdependencies identifies the following packages in
  category 1:
  
  camera-app-autopilot
  gallery-app-autopilot
  indicator-network-autopilot
  indicators-client
  qtdeclarative5-qtmir-plugin
  qtmir-android
  qtmir-desktop
  qtmir-tests
  ubuntu-desktop-mir
  ubuntu-experience-tests
  ubuntu-pocket-desktop
  ubuntu-push-autopilot
  ubuntu-touch
  ubuntu-touch-session
  unity8
  unity8-autopilot
  unity8-desktop-session-mir
  unity-scope-click-autopilot
  unity-system-compositor
  unity-system-compositor-autopilot

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

Title:
  Mir needs to be updated in 16.04 and the dependency tree trimmed

Status in mir package in Ubuntu:
  New

Bug description:
  [Impact]
  Snap development using Mir has been using the "stable phone overlay" PPA 
which is both inconvenient and a legacy of the cancelled Unity8 project.

  It would greatly simplify things if Mir were updated in the Xenial
  archive.

  [Test Case]

  Build a Mir client snap (e.g. lp:~albaguirre/+snap/mir-client-demos)
  against "Primary Ubuntu Archive" and deploy as described in
  https://developer.ubuntu.com/en/snappy/guides/mir-snaps/

  Expected: the client apps start and are visible on screen
  Actual: the client don't apps start and are not visible on screen

  [Regression Potential]
  Mir has two categories of dependent project:

    1 packages related to Unity8 (and unity-system-compositor)
    2 toolkits and other "clients" of Mir

  We should remove the first category to avoid regressions as it is not
  helpful to carry these in the LTS.

  The second category is dependent only on libmirclient which is ABI
  stable.

  The principle type of regression would be FTBFS where APIs have been
  deprecated.

  notes:

  A recursive search or rdependencies identifies the following packages
  in category 1:

  camera-app-autopilot
  gallery-app-autopilot
  indicator-network-autopilot
  indicators-client
  qtdeclarative5-qtmir-plugin
  qtmir-android
  qtmir-desktop
  qtmir-tests
  ubuntu-desktop-mir
  ubuntu-experience-tests
  ubuntu-pocket-desktop
  ubuntu-push-autopilot
  ubuntu-touch
  ubuntu-touch-session
  unity8
  unity8-autopilot
  unity8-desktop-session-mir
  unity-scope-click-autopilot
  unity-system-compositor
  unity-system-compositor-autopilot

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

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to     : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp

Reply via email to