Your message dated Wed, 27 Jul 2016 10:05:33 +0000
with message-id <e1bslix-0005nd...@franck.debian.org>
and subject line Bug#832582: fixed in init-system-helpers 1.41
has caused the Debian Bug report #832582,
regarding update-rc.d foo disable broken without 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 ow...@bugs.debian.org
immediately.)
--
832582: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=832582
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: init-system-helpers
Version: 1.40
Severity: serious
In the latest upload, we dropped the insserv dependency and added some
fallback code for SysV init scripts for the case where insserv is not
installed [1].
Unfortunately, the disable case is not handled correctly. It removes all
symlinks:
# for "disable" we cannot rely on the init script still being present, as
# this gets called in postrm for purging. Just remove all symlinks.
if ("disable" eq $action) { unlink($_) for
glob("/etc/rc?.d/[SK][0-9][0-9]$scriptname"); return; }
On package upgrades, the SysV init script gets enabled again via
update-rc.d foo defaults. This means
1/ For SysV only service, we enable and start a service, overriding the
admins settings.
2/ For a package with native service files and a SysV init script, the
state gets out of sync.
I consider 1/ a blocker, which is why I'm marking this as RC.
The correct why to handle disable a SysV init script, is to turn
existing S symlinks in runlevel S,2,3,4,5 into K symlinks.
For this we don't need the LSB header, we simply have to check for the
existence symlinks on the disk.
The update-rc.d man page says that the sequence number of the K symlink
should be 100 minus the priority of the S symlink.
For simplicities reason, I would simply turn S symlinks into K01
symlinks.
Enable would be the reverse action. We check in runlevels S,2,3,4,5 for
K symlinks and turn them into S symlinks.
Again, I would just use priority S01 here.
So, a disable + enable on service foo might change the priority of that
SysV init script, but under systemd those priorities are ignored and if
sysvinit-core is installed, it will pull in insserv which will correct
the priorities. So we do not lose any relevant (admin) configuration.
Regards,
Michael
[1]
http://anonscm.debian.org/cgit/collab-maint/init-system-helpers.git/commit/?id=f51e81cabe
-- System Information:
Debian Release: stretch/sid
APT prefers unstable-debug
APT policy: (500, 'unstable-debug'), (500, 'unstable'), (200, 'experimental')
Architecture: amd64 (x86_64)
Foreign Architectures: i386
Kernel: Linux 4.6.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
Init: systemd (via /run/systemd/system)
Versions of packages init-system-helpers depends on:
ii perl-base 5.22.2-3
init-system-helpers recommends no packages.
init-system-helpers suggests no packages.
-- no debconf information
--- End Message ---
--- Begin Message ---
Source: init-system-helpers
Source-Version: 1.41
We believe that the bug you reported is fixed in the latest version of
init-system-helpers, which is due to be installed in the Debian FTP archive.
A summary of the changes between this version and the previous one is
attached.
Thank you for reporting the bug, which will now be closed. If you
have further comments please address them to 832...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.
Debian distribution maintenance software
pp.
Michael Biebl <bi...@debian.org> (supplier of updated init-system-helpers
package)
(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive
administrators by mailing ftpmas...@ftp-master.debian.org)
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA256
Format: 1.8
Date: Wed, 27 Jul 2016 11:42:54 +0200
Source: init-system-helpers
Binary: init-system-helpers dh-systemd init
Architecture: source
Version: 1.41
Distribution: unstable
Urgency: medium
Maintainer: Debian systemd Maintainers
<pkg-systemd-maintain...@lists.alioth.debian.org>
Changed-By: Michael Biebl <bi...@debian.org>
Description:
dh-systemd - debhelper add-on to handle systemd unit files - transitional pack
init - init metapackage
init-system-helpers - helper tools for all init systems
Closes: 832582
Changes:
init-system-helpers (1.41) unstable; urgency=medium
.
* update-rc.d: Properly handle enable|disable for SysV init scripts if
insserv is not available. (Closes: #832582)
Checksums-Sha1:
4298cac09e2e5f589de05e34986f9184f51a2b72 1916 init-system-helpers_1.41.dsc
9af9eb9008b770ef21aa43ad74ed5ab51ad620c7 41756 init-system-helpers_1.41.tar.xz
Checksums-Sha256:
3b0151b82c2f6d4605ed65c2791c924264411472364d8fdcf8cd4932027f8519 1916
init-system-helpers_1.41.dsc
e882d004125999f3fed1546978655288b4f926a0e81d3682e4e5ffce00800e66 41756
init-system-helpers_1.41.tar.xz
Files:
e2b48d0208929a9aaab29fc2c1d9a0c0 1916 admin extra init-system-helpers_1.41.dsc
0466a0156e06a043901413fd02aaadf5 41756 admin extra
init-system-helpers_1.41.tar.xz
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2
iQIcBAEBCAAGBQJXmINZAAoJEGrh3w1gjyLcPfcP/1T3jmvyCpiXeBQZkmfn32JI
PZtx1xWl0VN0yXbu5p4DfBwGsoHbrPLHm0G3IGL5RL9kq0NvX3+3cXRZmYFZ8dVO
JMK2mdzsCvYuTUEjz+UUX+KLmacLI0v62cCSxvmAdKp5jolHEDsfWspKkFW221dS
CWsyFX04p9ZwhYmB/xaNCQCnK7/jw0DkeAs6Q4c7ZKYdraMnLjk+QXqTg91k2+AK
Z0avrZzld9yfdFAHHcy/zJ10452v67K9vHGcoBuHMRCiYBpq2Y+Vg2Iskn6yv+pi
PRYB1ZMnDqNiCzMyT+oraDc6lfyn9U5kiMFetTyhFVpzZpY8ce+z2ZSx+SrB24Cv
WQ4eKT9wvM7rUnM9vldWDOgRghFqE86kjGXl9nnVXHrq2hDuCQDIOh3juO1eGsgM
45mfG40f8F3633EIjoFK+uEPeqpNxL1lKbf7/CGkcUoslIJk0r4inbH7xQZ+f565
b5C9/gpSInAhM3k8cNMHj9e++3FTERmcDp5gWUQegWnEdyZ81JT+JncPo33aV8eh
p9tubJFh5+KvfcJfVg4QyF1HZCvfyCyw3ePyB3xgEXcrUerQxSobKSTi/SkYkwrQ
7ABBTifk0zk37ZWtCqb5kZYKX18LRWWA/z4w2B1MBSlk/DpC63aBrC1y3ANz4/br
gUQMirlYdTPiTw0z1tba
=fG2P
-----END PGP SIGNATURE-----
--- End Message ---
