IIRC, this is by design. Mir can't possibly know which driver package is
the right one for you at build time. And although we do have probing,
installing all driver packages bloats the dependency tree unnecessarily.
So our solution (IIRC) was to put a seed in the phone image such that
the android drivers package was always included.
I'm not sure if there's something in our packaging that might have made
it easier for your system to become broken...?
** Also affects: mir
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1528304
Title:
Missing dependency between mir and android drivers
To manage notifications about this bug go to:
https://bugs.launchpad.net/mir/+bug/1528304/+subscriptions
--
ubuntu-bugs mailing list
[email protected]
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
