[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Bug#796588: marked as done (adjtimex: Has init script in runlevel S but no matching service file)

Your message dated Wed, 02 Dec 2015 23:18:51 +0000
with message-id <E1a4Gfj-0000Ed-7R@franck.debian.org>
and subject line Bug#796588: fixed in adjtimex 1.29-6
has caused the Debian Bug report #796588,
regarding adjtimex: 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 owner@bugs.debian.org
immediately.)


-- 
796588: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=796588
Debian Bug Tracking System
Contact owner@bugs.debian.org with problems
--- Begin Message --- 
Package: adjtimex
Severity: important
User: pkg-systemd-maintainers@lists.alioth.debian.org
Usertags: init-rcs-service

Hi,

Your package adjtimex 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
pkg-systemd-maintainers@lists.alioth.debian.org
-- 

[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: adjtimex
Source-Version: 1.29-6

We believe that the bug you reported is fixed in the latest version of
adjtimex, 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 796588@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Roger Shimizu <rogershimizu@gmail.com> (supplier of updated adjtimex 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 ftpmaster@ftp-master.debian.org)


-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA256

Format: 1.8
Date: Thu, 03 Dec 2015 01:04:06 +0900
Source: adjtimex
Binary: adjtimex
Architecture: source
Version: 1.29-6
Distribution: unstable
Urgency: medium
Maintainer: Roger Shimizu <rogershimizu@gmail.com>
Changed-By: Roger Shimizu <rogershimizu@gmail.com>
Description:
 adjtimex   - kernel time variables configuration utility
Closes: 636404 796588
Changes:
 adjtimex (1.29-6) unstable; urgency=medium
 .
   * New maintainer (Closes: #636404).
   * debian/adjtimex.service: add systemd service (Closes: #796588).
   * debian/dirs: add new path for systemd service
   * debian/control: limit "Architecture" to linux-any
   * debian/patches/:
     - change the patching order to follow 01->02->03
     - 03-remove-a-few-unused-variable-to-avoid-gcc-warnings.patch:
       remove a few unused variables to avoid gcc warnings.
   * debian/watch: update to use real upstream's URL
   * remove unnecessary debian/dirs file
Checksums-Sha1:
 d406416262d46feef8b7ea4af168f0b466f198e2 1842 adjtimex_1.29-6.dsc
 fccc61c761dcc6a2a7bc5e5ffc2547543b255a7c 27036 adjtimex_1.29-6.debian.tar.xz
Checksums-Sha256:
 64394af973264ddf37ead14c41a09a33f06264eb4f942f56d3599f7717f70b00 1842 adjtimex_1.29-6.dsc
 2c011dbebe1c96933c358195f7eceb389047b18451e9321d285aac6a6bee9786 27036 adjtimex_1.29-6.debian.tar.xz
Files:
 5a77dac93ec0f363035ef069e5ec1532 1842 admin optional adjtimex_1.29-6.dsc
 0249e22e7e0f795571d10dacd86ca792 27036 admin optional adjtimex_1.29-6.debian.tar.xz

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2

iQIcBAEBCAAGBQJWX3tlAAoJEKO6uuJAjdbPfcEP+wUNWDoqdDq57EenyOSGplqV
5c4f8WmdeI2MHe//uU1Pb4F4l7I8UgZJb5Q/F1fIWEtHNYiFhiVH4MAEOnSNXlbx
PlTMma4kyhbzDhyhiaOe6BrOFFakEJT9K/EaaDfXfKAfZv9uZczOzUhz06ZBWMt8
rOA1qpT6bIaWtO688iuRZRA+XlyYJop0LktOEDplY2aREgkeLnV9VgxZRxxIZhOl
2EqZt+Mc0PeNPX+yrhf8mxcMbT4tCFTJVtJS6+7PUHZS0j+G/ykj+4yaOpHgSHcm
pHhdGL8YPV+OhbmX7r5yCeuhs+FoMUmUtiI17CJQHJmsDrrg2FI3fW7aUjvn2OvG
NCYRV+lzS4/IWB5nWlHvziiXs7TiIYgWjvxFklbLlFEe8ruk9V9KuXYCOO0Ag/p3
7h2EYLoG0FCPS1sURnEj5IIiVmuQk4ZBX4dMDjDfYKQ1ImgZPrASWAmapl1LB6if
TO1kIV0QY6iTP2CJ3a0siMUgNVc8/BVGDn+fF4DgKiNiq+Uy8wfu/GOmID7/XDtu
+NoWXzYkHt+SB9vLGo7+xOEixNC2d2keZNRNIbICdEVUxnGOE58pM/hAEExjVDtV
5wRQXOwob8dlxVQL1noWkkzCDOwmlk8U1W103O13+x+x1BcvKP9PyF9qUeNkpSBE
975ZetlsNeJNci6dUDMl
=D2rD
-----END PGP SIGNATURE-----

--- End Message ---
Reply to: