Turns out this is breaking in ubiquity because we don't get initscripts
installed on the rootfs (since procps now depends on init-system-helpers
instead).
For d-i installs this doesn't exactly break, but it's still a good idea
to check for the file to exist before we try to modify it. Looks like in
the d-i case, some other script may be creating an empty file before
clock-setup runs.
On ubiquity, no such empty file is created, and we use a "copy" of
10clock-setup; so there needs to be an update to both packages.
** Also affects: ubiquity (Ubuntu)
Importance: Undecided
Status: New
** Changed in: ubiquity (Ubuntu)
Status: New => In Progress
** Changed in: ubiquity (Ubuntu)
Importance: Undecided => High
** Changed in: ubiquity (Ubuntu)
Assignee: (unassigned) => Mathieu Trudel-Lapierre (cyphermox)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1587555
Title:
Installer crashed during installation
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/clock-setup/+bug/1587555/+subscriptions
--
ubuntu-bugs mailing list
[email protected]
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
