Your message dated Sun, 31 Jan 2010 15:23:37 +0100
with message-id <[email protected]>
and subject line Re: autofs5: Error in init script prevents use of insserv
has caused the Debian Bug report #539673,
regarding autofs5: Error in init script prevents use of insserv
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 [email protected]
immediately.)
--
539673: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=539673
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
Package: autofs5
Version: 5.0.4-2
Severity: important
Now that insserv is a required component, all packages must
provide correct init script dependency metadata. When
setting up insserv, it indicates that autofs is broken:
% sudo dpkg-reconfigure insserv
info: Checking if it is safe to convert to dependency based boot.
error: Problems running insserv:
insserv: script K19autofs provides system facility $autofs, skipped!
insserv: script K19autofs provides system facility $autofs, skipped!
insserv: script S19autofs provides system facility $autofs, skipped!
insserv: script S19autofs provides system facility $autofs, skipped!
insserv: script S19autofs provides system facility $autofs, skipped!
insserv: script S19autofs provides system facility $autofs, skipped!
insserv: script K19autofs provides system facility $autofs, skipped!
insserv: script autofs provides system facility $autofs, skipped!
warning: It is not safe to convert to dependency based boot.
I had a quick look at the init script, but I'm not sure what's at
fault here.
BTW, when testing this, I did a "dpkg-configure autofs5", and it blew
away all my changes to /etc/auto.net with the UCF defaults. I was
not too happy about that; it should not be unilaterally destroying
site-specific changes made by the system administrator. Is UCF
really necessary here? Are dpkg conffiles not sufficient?
Regards,
Roger
-- System Information:
Debian Release: squeeze/sid
APT prefers unstable
APT policy: (550, 'unstable')
Architecture: amd64 (x86_64)
Kernel: Linux 2.6.30-1-amd64 (SMP w/4 CPU cores)
Locale: LANG=en_GB.UTF-8, LC_CTYPE=en_GB.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Versions of packages autofs5 depends on:
ii libc6 2.9-23 GNU C Library: Shared libraries
ii ucf 3.0018 Update Configuration File: preserv
Versions of packages autofs5 recommends:
ii module-init-tools 3.9-2 tools for managing Linux kernel mo
ii nfs-common 1:1.2.0-2 NFS support files common to client
autofs5 suggests no packages.
-- no debconf information
--- End Message ---
--- Begin Message ---
Version: 5.0.4-3
The bugs in the init.d script header was fixed a few uploads ago.
Closing this bug.
Happy hacking,
--
Petter Reinholdtsen
--- End Message ---
