Skip lxc-android-config
Bug #1464284 reported by
Iain Lane
This bug affects 1 person
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| Ubuntu Touch Boottest |
New
|
Undecided
|
Unassigned | ||
Bug Description
kenvandine says that lxc-android-config can't be boottested because it cannot be installed from a system in a special state
https:/
If it's not possible to get a device into this state for boottesting then I suggest we just skip this one package. It certainly does have the capability to make devices unbootable though, so fixing would be best. Maybe skip as an interim; admin intervention is busy work at this point.
Revision history for this message
| Steve Langasek (vorlon) wrote | #1 |
Revision history for this message
| Iain Lane (laney) wrote | #2 |
Revision history for this message
| Iain Lane (laney) wrote | #3 |
To post a comment you must log in.
Of all the packages, lxc-android-config is one of the most important to have boot testing of because it modifies the system startup specifically for the phone.
What the boot testing should do (and what I had assumed it was configured to do already) is:
- download the current rootfs locally
- unpack it
- chroot into it
- install the target packages
- repack it
- flash the modified image onto the phone
This is the correct way to avoid the file bind mount problem when upgrading a package on the phone.