Your message dated Sat, 19 Mar 2022 18:26:23 +0100
with message-id <d9b566576360a8e6fe15051a9fec3c4f54c2fac7.ca...@decadent.org.uk>
and subject line Re: installation fails when rpcbind is disabled, although
nfs-common is disabled there too
has caused the Debian Bug report #644236,
regarding installation fails when rpcbind is disabled, although nfs-common is
disabled there too
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)
--
644236: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=644236
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: nfs-common
Version: 1:1.2.5-2
Severity: important
Dear Maintainer,
I have found a bug on upgrading nfs-common that might be nfs-common
init script header or insserv related:
* What led up to the situation?
Upgrading nfs-common when nfs-common and (!) rpcbind is disabled in
insserv.
merkaba:~> LANG=C apt-get upgrade
Reading package lists... Done
Building dependency tree
Reading state information... Done
The following packages have been kept back:
kmymoney kmymoney-common tryton-client
0 upgraded, 0 newly installed, 0 to remove and 3 not upgraded.
1 not fully installed or removed.
After this operation, 0 B of additional disk space will be used.
Do you want to continue [Y/n]?
Setting up nfs-common (1:1.2.5-2) ...
insserv: Service rpcbind 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
configured to not write apport reports
Errors were encountered while processing:
nfs-common
E: Sub-process /usr/bin/dpkg returned an error code (1)
* What exactly did you do (or not do) that was effective (or
ineffective)?
Explicetely disabling nfs-common again does not help:
merkaba:~> insserv -r nfs-common
merkaba:~> LANG=C apt-get upgrade
Reading package lists... Done
Building dependency tree
Reading state information... Done
The following packages have been kept back:
kmymoney kmymoney-common tryton-client
0 upgraded, 0 newly installed, 0 to remove and 3 not upgraded.
1 not fully installed or removed.
After this operation, 0 B of additional disk space will be used.
Do you want to continue [Y/n]?
Setting up nfs-common (1:1.2.5-2) ...
insserv: Service rpcbind 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
configured to not write apport reports
Errors were encountered while processing:
nfs-common
E: Sub-process /usr/bin/dpkg returned an error code (1)
* What was the outcome of this action?
The installation failed.
* What outcome did you expect instead?
It should have succeeded. This is on a laptop where I only use NFS
on demand. I do not want to have it running when I do not use it.
I think this is a valid usage scenario.
Thus when nfs-common *and* rpcbind are disabled in insserv installation
should still succeed.
This might be a bug in insserv. If so please reassign.
* Workaround to have apt upgrade nfs-common
Temporarily enabling both nfs-common and rpcbind lets nfs-common upgrade
smoothly:
merkaba:~#100> insserv rpcbind
merkaba:~> insserv nfs-common
merkaba:~> LANG=C apt-get upgrade
Reading package lists... Done
Building dependency tree
Reading state information... Done
The following packages have been kept back:
kmymoney kmymoney-common tryton-client
0 upgraded, 0 newly installed, 0 to remove and 3 not upgraded.
1 not fully installed or removed.
After this operation, 0 B of additional disk space will be used.
Do you want to continue [Y/n]?
Setting up nfs-common (1:1.2.5-2) ...
Stopping NFS common utilities: idmapd statd.
Starting NFS common utilities: statd
Not starting: portmapper is not running ... (warning).
merkaba:~> insserv -r nfs-common
merkaba:~> insserv -r rpcbind
merkaba:~>
Bug script failed due to rpcbind not running, but I do not think
it matters for this bugreport. If you want to have output of it,
please tell.
Thanks,
Martin
*** End of the template - remove these lines ***
-- Package-specific info:
-- rpcinfo --
-- System Information:
Debian Release: wheezy/sid
APT prefers unstable
APT policy: (500, 'unstable'), (500, 'testing'), (120, 'experimental')
Architecture: amd64 (x86_64)
Kernel: Linux 3.0.0-1-amd64 (SMP w/4 CPU cores)
Locale: LANG=de_DE.UTF-8, LC_CTYPE=de_DE.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Versions of packages nfs-common depends on:
ii adduser 3.113
ii initscripts 2.88dsf-13.11
ii libc6 2.13-21
ii libcap2 1:2.22-1
ii libcomerr2 1.42~WIP-2011-09-25-1
ii libdevmapper1.02.1 2:1.02.65-1
ii libevent-1.4-2 1.4.14b-stable-1
ii libgssapi-krb5-2 1.9.1+dfsg-3
ii libgssglue1 0.3-3
ii libk5crypto3 1.9.1+dfsg-3
ii libkeyutils1 1.5.2-2
ii libkrb5-3 1.9.1+dfsg-3
ii libnfsidmap2 0.24-1
ii libtirpc1 0.2.2-5
ii libwrap0 7.6.q-21
ii lsb-base 3.2-28
ii rpcbind 0.2.0-6
ii ucf 3.0025+nmu2
Versions of packages nfs-common recommends:
ii python 2.7.2-7
nfs-common suggests no packages.
-- no debconf information
--- End Message ---
--- Begin Message ---
I could reproduce this in stretch, but not buster. It's not clear to
me whether this was fixed by a change in nfs-utils, init-system-
helpers, or elsewhere. Therefore I'm not specifying a fixed version.
Ben.
--
Ben Hutchings
Beware of programmers who carry screwdrivers. - Leonard Brandwein
signature.asc
Description: This is a digitally signed message part
--- End Message ---
