Your message dated Sun, 08 Dec 2013 10:17:05 +0000
with message-id <[email protected]>
and subject line Bug#717495: fixed in bootchart 0.10~svn407-4.1~deb7u1
has caused the Debian Bug report #717495,
regarding sysv-rc: migration to dependency based boot order fails if bootchart
from lenny is still installed
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.)
--
717495: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=717495
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
Package: sysv-rc
Version: 2.88dsf-32
Severity: important
User: [email protected]
Usertags: piuparts
Control: affects -1 + bootchart
Hi,
during a test with piuparts I noticed an error while enabling the
dependency based boot sequencing if the bootchart package from lenny is
still installed.
>From the attached log:
Preparing to replace sysv-rc 2.88dsf-13.1+squeeze1 (using
.../sysv-rc_2.88dsf-32_all.deb) ...
Unpacking replacement sysv-rc ...
Setting up sysv-rc (2.88dsf-32) ...
info: Reordering boot system, log to /var/lib/insserv/run-20121123T0359.log
error: Something failed while migrating.
error: Unable to migrate to dependency based boot sequencing.
See http://wiki.debian.org/LSBInitScripts/DependencyBasedBoot for
more information about dependency based boot sequencing. To
reattempt the migration process run 'dpkg --configure sysv-rc'.
dpkg: error processing sysv-rc (--configure):
subprocess installed post-installation script returned error exit status 1
configured to not write apport reports
Errors were encountered while processing:
sysv-rc
and /var/lib/insserv/run-20121123T0359.log contains:
info: Converting rc0.d/S* and rc6.d/S* to K*.
info: running insserv
insserv: There is a loop at service bootchart if started
insserv: There is a loop at service rmnologin if started
insserv: There is a loop between service rmnologin and mountall if started
insserv: loop involving service mountall at depth 1
insserv: There is a loop between service rmnologin and mountnfs if started
insserv: loop involving service mountnfs at depth 2
insserv: loop involving service mountoverflowtmp at depth 1
insserv: loop involving service urandom at depth 5
insserv: loop involving service checkfs at depth 3
insserv: loop involving service mountnfs-bootclean at depth 6
insserv: There is a loop between service rmnologin and mountoverflowtmp if
started
insserv: loop involving service mountall-bootclean at depth 7
insserv: There is a loop between service rmnologin and bootlogd if started
insserv: loop involving service bootlogd at depth 2
insserv: loop involving service mountdevsubfs at depth 1
insserv: Starting bootchart depends on rmnologin and therefore on system
facility `$all' which can not be true!
insserv: Starting bootchart depends on rmnologin and therefore on system
facility `$all' which can not be true!
insserv: Starting bootchart depends on rmnologin and therefore on system
facility `$all' which can not be true!
...
insserv: Starting bootchart depends on rmnologin and therefore on system
facility `$all' which can not be true!
insserv: Starting bootchart depends on rmnologin and therefore on system
facility `$all' which can not be true!
insserv: Starting bootchart depends on rmnologin and therefore on system
facility `$all' which can not be true!
insserv: Max recursions depth 99 reached
insserv: loop involving service bootlogs at depth 1
insserv: Starting bootchart depends on rmnologin and therefore on system
facility `$all' which can not be true!
insserv: loop involving service hostname at depth 4
insserv: exiting now without changing boot order!
This was observed on a distupgrade test from lenny to squeeze to wheezy.
There is no bootchart package in squeeze, but since there were no conflicts
the lenny package has been kept installed in squeeze, too.
Wheezy comes with an updated bootchart package, but sysv-rc got upgraded first.
Maybe a Breaks/Conflicts could be inserted somewhere to
ensure that bootchart gets upgraded first.
cheers,
Andreas
bootchart_0.10~svn407-3.3.log.gz
Description: GNU Zip compressed data
--- End Message ---
--- Begin Message ---
Source: bootchart
Source-Version: 0.10~svn407-4.1~deb7u1
We believe that the bug you reported is fixed in the latest version of
bootchart, 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.
Andreas Beckmann <[email protected]> (supplier of updated bootchart 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: SHA256
Format: 1.8
Date: Sun, 08 Dec 2013 06:28:17 +0100
Source: bootchart
Binary: bootchart bootchart-view
Architecture: source all
Version: 0.10~svn407-4.1~deb7u1
Distribution: wheezy
Urgency: low
Maintainer: Jörg Sommer <[email protected]>
Changed-By: Andreas Beckmann <[email protected]>
Description:
bootchart - Boot process performance analyser
bootchart-view - Boot process performance analyser (visualisation)
Closes: 717495
Changes:
bootchart (0.10~svn407-4.1~deb7u1) wheezy; urgency=low
.
* Non-maintainer upload.
* Rebuild for wheezy.
.
bootchart (0.10~svn407-4.1) unstable; urgency=low
.
* Non-maintainer upload.
* Fix the upgrade path lenny (bootchart 0.10~svn407-3) => squeeze (bootchart
0.10~svn407-3 from lenny because bootchart was not included in squeeze) =>
wheezy. The initscript from 0.10~svn407-3 prevents migration to dependency
based boot sequencing causing a sysv-rc upgrade failure.
Add bootchart.preinst to replace the problematic "rmnologin" use in the
ancient /etc/init.d/bootchart because it is impossible to ensure the new
bootchart is already configured (which would replace the old initscript)
at the time sysv-rc gets configured. (Closes: #717495)
* Bump Debian revision to -4.1 to restore installability after recent
initscripts having Breaks: bootchart (<< 0.10~svn407-4).
Checksums-Sha1:
f3dd54aca260b615337f0a1b8e3202a8a575472c 2026
bootchart_0.10~svn407-4.1~deb7u1.dsc
2a953ef8adfd200cb6d112e451e29700d6e1a389 15984
bootchart_0.10~svn407-4.1~deb7u1.diff.gz
68332eafa4fc08310a88e74056e207e48daec96e 28276
bootchart_0.10~svn407-4.1~deb7u1_all.deb
b25576e79913ea12d92d9b9eadace55976294dd4 196524
bootchart-view_0.10~svn407-4.1~deb7u1_all.deb
Checksums-Sha256:
489ef83bba96ca69b95e0258209e44fdcdad2e4d5828c0edfad341a027391ea5 2026
bootchart_0.10~svn407-4.1~deb7u1.dsc
2f31d921f8680f5fb0318194a69c71a2e22b2451ac8f44c5f6e6bc13c5f6f510 15984
bootchart_0.10~svn407-4.1~deb7u1.diff.gz
27ca2ad0ef5268becf094918eac652256d597bda99bc2a79194b9aa2ad6524e4 28276
bootchart_0.10~svn407-4.1~deb7u1_all.deb
2852e0dc8b6dbdb1bca4e9d3546ac225c25ff2a4b326b164fc977030f2517646 196524
bootchart-view_0.10~svn407-4.1~deb7u1_all.deb
Files:
93ca1fd8f4e3bc834a4889a16a388a2a 2026 admin optional
bootchart_0.10~svn407-4.1~deb7u1.dsc
452f1e95c94f58dc2ab9f71a51676cc5 15984 admin optional
bootchart_0.10~svn407-4.1~deb7u1.diff.gz
8f3370d34ffa6ebf8775efc3f37b302f 28276 admin optional
bootchart_0.10~svn407-4.1~deb7u1_all.deb
30f7192435d48bda23e8303b77ce5b5a 196524 admin optional
bootchart-view_0.10~svn407-4.1~deb7u1_all.deb
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.12 (GNU/Linux)
iQIcBAEBCAAGBQJSpAuPAAoJEF+zP5NZ6e0InjoP/2/Z3+2dUnYR3SJu9Ymfw8Hx
i0KVm4TSHko310gJ3Yw9r8hxMxAQCiPT23oSV5YKbm6VAp0N4yrHPWvMiYA03NCs
ffdYVk4DKg/g/OVoa/0xOslYkYdWG2+dviYyjcmz4HAQskyuwaZqE+A8fBlQwtS8
E20516008eNqyAe07EySupc1fWZ5VxUA0/D0CK30/w5D1WDKPEkSUJ7s5RA7gi5Z
nZz1c/NMsD7yPdJjAnlT3iIV0Lw6oi2pFvI5y+9eTUaKwOJSlOcMhBUKVl4N+2Sx
zWJGLC4K3tA1ThcEyFZg5VDNz1fDhMHgrMcL79j3K2MZpZl2KEJsc1/kUEpZJT0O
Vsjr3TU7vlP9AYbselq8WliRN0t6xE+iPzi7WlxmG4PJVkLC/N+YYID4JZEcfjwn
jf18qtrJIIB+drPLwuUmtMQxA30ZWmMDQl0TvEwdsxT/EM+OfayVR9A4tI0f+Blf
zcoCICuEmGlJBdbM4NBKlmc5K4XYJCyFBmau4/FPTfR3Tq06kZlQzVM+ANLAR4oL
3rnZkUzHdbz4a8aO5b2OUkGCqEGhGB41pDTPDH+IZLHDncGN4KFzE+ZWZYJkhdzD
O8QrgRyAYx+M53jb7O6oI9uMZPHIXSHD9hwZ1CDEbk0zv/gw4hTZvQteISn27w7u
BTgrgS++ikKkkLrO+eK2
=W99h
-----END PGP SIGNATURE-----
--- End Message ---
