[Pkg-sysvinit-devel] Bug#716948: explaining the control requests from above

[Regid Ichira]

  For better readability, here is the 25 lines long comment from the
bottom of the control requests from above.  

Package:  bootlogd
Version:  2.88dsf-43
Severity: normal

  Not sure if severity normal is adequete.  How will the system 
react when a boot scripts are unexpectdly missing?  I am also not
sure if it should be filed against bootlogd.
  Reopen on the ground of 
http://lists.debian.org/debian-user/2013/07/msg01243.html .
Since purging and installing seem to fix the problem, perhaps after
upgrade the maintainer scripts should, at least, check and report
when a problematic file is not on place?  The issue might not be 
noticed at the time it happans.
  I started the thread at 
http://lists.debian.org/debian-user/2013/07/msg01243.html .  I can't
tell much about the circumstances the problem apeared.  This is so
becuase I used a mixture of dpkg and aptitude.  So no aptitude log
files for the upgrade.  It can be that, for some reason, I upgraded
bootlogd only after the other sysvinit packages were upgraded.  dpkg
at the time of the upgrade was 1.16.10.  I think the packages were
upgraded from version 41 to 43.  In fact, I am not sure the missing
files were there when I upgraded from version 41 to 43.  I did try
to reinstall bootlogd, or perhaps bootlogd and initscripts, with
both dpkg 1.16.10 and 1.17.1.  It did not put the missing files back.
I had to purge and reinstall bootlogd in order to get the files
back.  http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=716948#10
mentions some lines that include the word obsolete in 
/var/lib/dpkg/status.  I don't have that word. could it be due to
reinstalling, purging and installing, and all that process?  I did 
not purge initscripts.  Just bootlogd.