Martin, could you have a look at this bug when you have a chance,
please? The cause is quite simple, the systemd unit and the upstart job
have differing names. I'm not sure about the correct fix - not least of
all because of the interactions between invoke-rc.d and deb-systemd-
invoke (which I still consider a bad case of NIH that we should correct
at some point) and the differences in the top-level invocations for
systemd vs. not ('nfs-utils.service' vs. individual units).
The semantics of the deb-systemd-invoke aren't even right for the
postinst currently anyway, because we're calling 'deb-systemd-invoke
try-restart' for nfs-utils.service, which is a one-shot service and
therefore 'try-restart' has no effect. This looks like a serious bug in
the semantics of dh_systemd, as 'try-restart' is a deviation from the
established policy that services should be started on upgrade *even if
they were not running before*, *unless* the admin has done something to
specifically declare the service should not be started. (update-rc.d
disable, etc).
** Changed in: nfs-utils (Ubuntu)
Importance: Undecided => High
** Changed in: nfs-utils (Ubuntu)
Status: New => Triaged
** Changed in: nfs-utils (Ubuntu)
Assignee: (unassigned) => Martin Pitt (pitti)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1476010
Title:
package nfs-common 1:1.2.8-9ubuntu8.1 failed to install/upgrade:
subprocess installed post-installation script returned error exit
status 100
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/nfs-utils/+bug/1476010/+subscriptions
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
