>>>>> Tobias Klauser <[email protected]> writes: [...]
> I can reproduce this bug here:
> | Setting up nfs-common (1:1.2.1-3) ...
> | insserv: Service portmap has to be enabled to start service nfs-common
> | insserv: exiting now!
> | update-rc.d: error: insserv rejected the script header
> | dpkg: error processing nfs-common (--configure):
> | subprocess installed post-installation script returned error exit status 1
> | Errors were encountered while processing:
> | nfs-common
> | E: Sub-process /usr/bin/dpkg returned an error code (1)
> The message suggests that the portmap initscript is not enabled at
> the time of the installation (which is the case here on my netbook, I
> don't want to have it started at boot by default). And indeed after
> reactivating portmap using 'insserv /etc/init.d/portmap' the
> nfs-common installation was successful.
I have observed a similar issue when trying to build a Debian
Live image with nfs-common and rpcbind. Obviously, in this
particular case /no/ service should be started during the
installation of the packages.
# lh build
[...]
Setting up rpcbind (0.2.0-4) ...
update-rc.d: warning: rpcbind start runlevel arguments (S) do not match LSB
Default-Start values (S 2 3 4 5)
All runlevel operations denied by policy
Setting up nfs-common (1:1.2.1-3) ...
Creating config file /etc/idmapd.conf with new version
Creating config file /etc/default/nfs-common with new version
insserv: Service portmap has to be enabled to start service nfs-common
insserv: exiting now!
update-rc.d: error: insserv rejected the script header
dpkg: error processing nfs-common (--configure):
subprocess installed post-installation script returned error exit status 1
[...]
Eventually, the build fails with:
[...]
Errors were encountered while processing:
nfs-common
E: Sub-process /usr/bin/dpkg returned an error code (1)
P: Begin unmounting filesystems...
Command exited with non-zero status 123
#
--
FSF associate member #7257
pgpYPsZEzJq4Z.pgp
Description: PGP signature
