Your message dated Sun, 13 Apr 2025 18:19:32 +0000
with message-id <[email protected]>
and subject line Bug#796636: fixed in oss4 4.2-build2020-5
has caused the Debian Bug report #796636,
regarding oss4-base: Has init script in runlevel S but no matching service file
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.)
--
796636: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=796636
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
Package: oss4-base
Severity: important
User: [email protected]
Usertags: init-rcs-service
Hi,
Your package oss4-base has an initscript that is enabled in runlevel
S, but it does not provide a corresponding systemd service unit.
Systemd generates units for all sysv init scripts that do not have a
corresponding systemd unit. By default, it sets
DefaultDependencies=yes, which means they get ordered after early
boot has finished.
The problem is that to preserve the runlevel S semantics, systemd in
debian is currently[1] ordering all S services Before=sysinit.target.
This target is particularly early in the boot sequence, which means
that it is most of the time too strict. In turn, this means it is
fairly easy to end up with dependency cycles. For an example, see bug
[763315]. Do note that the cycle still exists with sysvinit, it is
just that systemd complains more loudly.
Please add a systemd unit for the given service with the appropriate
dependencies, which most of the time will be less strict than
Before=sysinit.target. In other cases, the script is simply not
applicable in systemd, in which case the package should ship a
symlink to /dev/null as /lib/systemd/system/<initscript>.service.
We have prepared a transition wiki page[2] explaining the issue in
more detail, and outlining some general guidance. Please refer to it
as it will have useful information.
If you have any other doubts, feel free to ask in
[email protected]
--
[1]
http://sources.debian.net/src/systemd/222-2/debian/patches/Add-support-for-rcS.d-init-scripts-to-the-sysv-gener.patch/
[763315] https://bugs.debian.org/763315
[2] https://wiki.debian.org/Teams/pkg-systemd/rcSMigration
--- End Message ---
--- Begin Message ---
Source: oss4
Source-Version: 4.2-build2020-5
Done: Samuel Thibault <[email protected]>
We believe that the bug you reported is fixed in the latest version of
oss4, 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 [email protected],
and the maintainer will reopen the bug report if appropriate.
Debian distribution maintenance software
pp.
Samuel Thibault <[email protected]> (supplier of updated oss4 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 [email protected])
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA512
Format: 1.8
Date: Sun, 09 Mar 2025 22:05:03 +0100
Source: oss4
Architecture: source
Version: 4.2-build2020-5
Distribution: unstable
Urgency: medium
Maintainer: Samuel Thibault <[email protected]>
Changed-By: Samuel Thibault <[email protected]>
Closes: 796636 1101743
Changes:
oss4 (4.2-build2020-5) unstable; urgency=medium
.
* liboss4-salsa-dev.install: Fix multiarch patch.
* Drop oss4-base, oss4-gtk, oss4-dkms, oss4-source, oss4-dev packages and
the kernel driver build infrastructure and patches (Closes: Bug#796636,
Bug#1101743)
* salsa-ci.yml: Add hurd CI.
Checksums-Sha1:
67d0668f8048b4a1640427300aceead43ae8fda1 2148 oss4_4.2-build2020-5.dsc
03cc2b36778764143eb4d86ab8aa7becf6c2a305 55484
oss4_4.2-build2020-5.debian.tar.xz
d1423593bd7daae182c2c19ab9dff62b46b364b1 8364
oss4_4.2-build2020-5_source.buildinfo
Checksums-Sha256:
dc31ff0d2643722ef581da3f6c0d6fa388be0a7f24397f4d043320b209d97ae2 2148
oss4_4.2-build2020-5.dsc
33fa06b1b5dc183939ecaafb205c5da98b68faed53f1cc8e3010fa47ed32cf44 55484
oss4_4.2-build2020-5.debian.tar.xz
02625b78a80f3f0c791c099be2f5ae88ba4f3ce52da7a8f703321dff0e46cbdb 8364
oss4_4.2-build2020-5_source.buildinfo
Files:
a3061f8a7e97a941e109ff67347f31b4 2148 sound optional oss4_4.2-build2020-5.dsc
41b0217994882e7d027b5cbd1465e39c 55484 sound optional
oss4_4.2-build2020-5.debian.tar.xz
bd24d30287be5ecbe36a22cfd3ff7556 8364 sound optional
oss4_4.2-build2020-5_source.buildinfo
-----BEGIN PGP SIGNATURE-----
iQIzBAEBCgAdFiEEZTSF1IMOAGwT71n/aHTOWK4tfj8FAmf7+9EACgkQaHTOWK4t
fj/4iA//QKuTqz54rnlQFyTgaiSvZFt0moZiG45pEUGDt1C4UoXCpYtPwATqrJhg
IY3F1nYCIVXFtzqiNbBRzqUcSRWyR4ceZI1Xt9OcfUGNfP2P0blTUBhFGEvi2K/4
nIGR1/uA6SqL02uDkxzpMzgx7Ie32V1LkP5FrBaBlVuZ7Q0tUW8BAcnKSwZ0Q+CC
nfF5YQaPrfUeWGaRLBR5FD47i5sBRA/nMYmSU5ymZj65PLRHMBZCUfntQdClIS1D
EFpyVcuH2p9uPVnhFyv+oKDAnZ0sAY3s6GvdiSQIY8vJoFD5HFZpl4ONIbLpnfN0
QrGZfN1IPbkFZNvSoBEnMcbVRsUDTWtOCrltCEDedu5fILw8eMnFRGvY+UK3r/Zv
XNGXpo41u6Y8RNMAp+iVuwaSNs0OIXoOS//F7avcTTidftV0yYjt1dE5Mypc80PN
VbeQT4mgAEMQtTpdUlfAn8/SvLDGbQ55jQhqSegXSfTYBhhMv9av1wLc/CRO+7VX
AnBgK04FXW+G5YNpq8uOsyfM8WQOlydqA1aStbS7cX8iSWMf4K7ylCvzgxMtttyW
tvHsBGBZQigBQNW5ZTCFrsPczrr+exH7pfSciOdEuOw58BzsC88REymqJ8HLlZBF
oW3JaK4mTEcBg4UMtiJH8QyTRRmTu1l8mAwBzVo0TgZ6WEDe83Y=
=vkLK
-----END PGP SIGNATURE-----
pgpfJn86hAkEN.pgp
Description: PGP signature
--- End Message ---
