Merge lp:~pitti/ubiquity/systemd into lp:ubiquity
Status: | Merged |
---|---|
Merged at revision: | 6250 |
Proposed branch: | lp:~pitti/ubiquity/systemd |
Merge into: | lp:ubiquity |
Diff against target: |
286 lines (+140/-76) 8 files modified
d-i/update-control (+1/-0) debian/changelog (+12/-0) debian/control (+1/-1) debian/oem-config.oem-config.service (+36/-0) debian/rules (+2/-0) debian/ubiquity.ubiquity.service (+10/-0) debian/ubiquity.ubiquity.upstart (+1/-75) scripts/start-ubiquity-dm (+77/-0) |
To merge this branch: | bzr merge lp:~pitti/ubiquity/systemd |
Related bugs: |
Reviewer | Review Type | Date Requested | Status |
---|---|---|---|
Ubuntu Installer Team | Pending | ||
Review via email: mp+246535@code.launchpad.net |
Description of the change
Port to systemd. For ubiquity-dm I factorized the script as almost all of it is re-usable. For oem-config.service I replicated the necessary shell logic as most of upstart's one can be replaced with systemd directives like Condition=*.
I tested this on today's live image, with upgrading to udisks2 2.1.4-1git3 (for bug 1410851), otherwise ubiquity can't start. I used "init=/bin/systemd
break=casper-
ensured that in ubiquity-only mode ubiquity-dm comes up properly. I did a full test install, and aside from having to work around bug 1408495 the install went fine.
I also tested oem-config by installing systemd-sysv and the local oem-config
debs, rebooted, ran oem-config-prepare, and ran through it.
I didn't test oem-config-debconf, as I currently don't know how. Ubuntu, Kubuntu etc. don't have alternates any more, server's OEM mode doesn't work (just filed bug 1411124), and Mythbuntu etc. don't have vivid images. I tried to install oem-config on a server install, but that brings in tons of desktop/graphical packages, thus I believe that oem-config isn't actually meant for text mode, and that the debconf frontend is just for preseeding?
However, I believe it's not necessary to port oem-config-
Doesn't ubiquity job need "SuccessExitSta tus=1" -> to port "normal exit 0 1" from upstart?
oem-config/ubiquity is a pain to install direct - as usually the wrong type of frontend is pulled in. To try server oem-config (which should work) could you attempt something like: frontend- debconf oem-config-debconf oem-config
$ sudo apt-get install ubiquity-
We had server oem-config bugs before and i thought we fixed them up for trusty srus or some such. Let me look at the bug you filed.