Your message dated Sat, 08 Dec 2012 18:47:29 +0000
with message-id <e1thpqv-0008vv...@franck.debian.org>
and subject line Bug#694403: fixed in bootchart2 0.14.4-2
has caused the Debian Bug report #694403,
regarding Please ship an init script, not just a systemd unit
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.)
--
694403: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=694403
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: bootchart2
Version: 0.14.4-1.1
Severity: serious
Justification: Policy 9.11
The bootchart2 package currently ships systemd unit files, but no init
script. This means the behavior is different when booting with systemd than
when booting with sysvinit. This appears to be a violation of Policy 9.11:
[A]ny package integrating with other init systems must also be
backwards-compatible with `sysvinit' by providing a SysV-style init
script with the same name as and equivalent functionality to any
init-specific job, as this is the only start-up configuration method
guaranteed to be supported by all init implementations.
In practice, my experience is that if I install bootchart, then install
bootchart2 without purging bootchart, and boot with systemd, systemd gets
very confused and leaves the bootchart daemon running indefinitely. In
contrast, if I boot with sysvinit, the init script in /etc/rc2.d/ does a
perfectly adequate job of stopping bootchartd at the right point. So the
lack of sysvinit integration looks to actually hurt integration with systemd
too.
BTW, Ubuntu uses an initramfs hook instead of a boot argument as the means
of starting bootchart (for bootchart 1). Have you considered including such
a method in the package? It seems obvious to me that we would want
bootcharting of the initramfs to be included by default. I'm happy to work
out a patch for this if that would be of use.
--
Steve Langasek Give me a lever long enough and a Free OS
Debian Developer to set it on, and I can move the world.
Ubuntu Developer http://www.debian.org/
slanga...@ubuntu.com vor...@debian.org
signature.asc
Description: Digital signature
--- End Message ---
--- Begin Message ---
Source: bootchart2
Source-Version: 0.14.4-2
We believe that the bug you reported is fixed in the latest version of
bootchart2, 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 694...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.
Debian distribution maintenance software
pp.
David Paleino <da...@debian.org> (supplier of updated bootchart2 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...@debian.org)
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
Format: 1.8
Date: Sat, 08 Dec 2012 19:35:08 +0100
Source: bootchart2
Binary: bootchart2 pybootchartgui
Architecture: source i386 all
Version: 0.14.4-2
Distribution: unstable
Urgency: low
Maintainer: David Paleino <da...@debian.org>
Changed-By: David Paleino <da...@debian.org>
Description:
bootchart2 - boot process performance analyser
pybootchartgui - viewer for boot process performance analysis results
Closes: 694403
Changes:
bootchart2 (0.14.4-2) unstable; urgency=low
.
* Acknowledge NMU.
* Provide also an initscript (Closes: #694403)
Checksums-Sha1:
01ff1e1ed6c861481aed8a142f5459f495690c6e 1366 bootchart2_0.14.4-2.dsc
25f4140c004c4ca90fe05f2b948c6bffeede30c6 7013 bootchart2_0.14.4-2.debian.tar.gz
38795c4f1d6af027d758ead2e8b9e82003218667 32026 bootchart2_0.14.4-2_i386.deb
91acf98581809da0780566aa711f0fd5d5da3d26 32904 pybootchartgui_0.14.4-2_all.deb
Checksums-Sha256:
859fcd49143b802c3f30fee4214c52ecf021182ea3d7ae6301717a102e42c951 1366
bootchart2_0.14.4-2.dsc
9f111ced2cc29217dd7f101e46c639b5abf14a8584de0ffac0b984bcb008fe20 7013
bootchart2_0.14.4-2.debian.tar.gz
91a7504dbf6cb165b3e8df1440107202360ef542be8a245d0c5694fae32d9aec 32026
bootchart2_0.14.4-2_i386.deb
d5f46a64933bacc4639baf39061c5ac044d37c4e45bb51abbc66666fb6e8d7f4 32904
pybootchartgui_0.14.4-2_all.deb
Files:
9f01cc1e9e4dd414a03d9627ea75ce07 1366 utils optional bootchart2_0.14.4-2.dsc
d9194cf40ffb7c49ea1dd90cf5a593fa 7013 utils optional
bootchart2_0.14.4-2.debian.tar.gz
f8d42f1449f628d8ba7cfa0b8e63b7d0 32026 utils optional
bootchart2_0.14.4-2_i386.deb
e02746051766eb3ac141cd44d1b2f594 32904 utils optional
pybootchartgui_0.14.4-2_all.deb
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.12 (GNU/Linux)
iEYEARECAAYFAlDDigAACgkQ5qqQFxOSsXQFlACglGsMaY36ZXrPJrgAUzoCkE6y
pUkAoLT8L3c4gzIu1MmP1fGhSFolxxKs
=X6GN
-----END PGP SIGNATURE-----
--- End Message ---
