Merge ~saviq/repowerd:wants-android into repowerd:master
Proposed by
Michał Sawicz
on 2016-07-13
| Status: | Merged |
|---|---|
| Approved by: | Alexandros Frantzis on 2016-07-25 |
| Approved revision: | 452cc6592a85e1bdcf83aed17290dc1095e05b95 |
| Merged at revision: | 452cc6592a85e1bdcf83aed17290dc1095e05b95 |
| Proposed branch: | ~saviq/repowerd:wants-android |
| Merge into: | repowerd:master |
| Diff against target: |
12 lines (+1/-1) 1 file modified
debian/repowerd.service (+1/-1) |
| Related bugs: |
| Reviewer | Review Type | Date Requested | Status |
|---|---|---|---|
| Alexandros Frantzis | 2016-07-13 | Approve on 2016-07-25 | |
| Daniel van Vugt (community) | Abstain on 2016-07-25 | ||
|
Review via email:
|
|||
Commit Message
Don't Require lxc-android-config (LP: #1602597)
Requires: means that the service has to be there, but repowerd is
supposed to work on non-android devices, too.
To post a comment you must log in.
| Daniel van Vugt (vanvugt) wrote : | # |
Also the systemd docs do not state that 'Wants' works in the case where the prerequisite doesn't exist at all.
review:
Needs Information
| Daniel van Vugt (vanvugt) wrote : | # |
Sounds better now, but needs testing still.
review:
Needs Information
| Daniel van Vugt (vanvugt) wrote : | # |
Tested on yakkety. With this change repowerd starts by default with one caveat: systemd thinks it's still starting indefinitely. So we're still missing some setting that tells systemd it's finished starting.
review:
Approve
| Daniel van Vugt (vanvugt) wrote : | # |
Whoops.
The process starts but because it apparently never finishes starting, systemd times out and kills it again.
review:
Needs Fixing

Yes, but maybe no.
On systems where lxc-android- config. service exists, using 'Wants' will make the system unreliable and unpredictable. repowerd could then start prematurely when lxc-android-config hasn't, which could presumably mess it up.
But I think I'm now describing a design flaw in systemd in general...?