Bug#676463: #676463 sysv-rc: complains incorrectly(?) about obsolete init.d scripts for fuse and others

2012-06-11 Thread Timo Juhani Lindfors
Hi,

after changing

 add_problematic package $package left obsolete init.d script behind

in /var/lib/dpkg/info/sysv-rc.postinst to

 add_problematic package $package left obsolete init.d script $initscript 
behind

I get

...
info: Checking if it is safe to convert to dependency based boot.
Configuring sysv-rc
---

Unable to migrate to dependency-based boot system

Problems in the boot system exist which are preventing migration to 
dependency-based boot sequencing:

package fuse left obsolete init.d script /etc/init.d/fuse behind, package 
initscripts left obsolete init.d script /etc/init.d/stop-bootlogd behind, 
package initscripts
left obsolete init.d script /etc/init.d/bootlogd behind, package initscripts 
left obsolete init.d script /etc/init.d/stop-bootlogd-single behind

If the reported problem is a local modification, it needs to be fixed manually. 
 These are typically due to obsolete conffiles being left after a package has 
been
removed, but not purged.  It is suggested that these are removed by running:

dpkg --purge fuse initscripts initscripts initscripts

Package installation can not continue until the above problems have been fixed. 
 To reattempt the migration process after these problems have been fixed, run 
dpkg
--configure sysv-rc.


error: Unable to migrate to dependency based boot sequencing.
error: Problems detected: package fuse left obsolete init.d script 
/etc/init.d/fuse behind, package initscripts left obsolete init.d script 
/etc/init.d/stop-bootlogd behind, package initscripts left obsolete init.d 
script /etc/init.d/bootlogd behind, package initscripts left obsolete init.d 
script /etc/init.d/stop-bootlogd-single behind

If this is due to the presence of unpurged obsolete initscripts,
it is suggested that the following is run to remove them:
  dpkg --purge fuse initscripts initscripts initscripts

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
Errors were encountered while processing:
 sysv-rc




-- 
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org



Bug#676463: #676463 sysv-rc: complains incorrectly(?) about obsolete init.d scripts for fuse and others

2012-06-11 Thread Paul Menzel
Dear Timo,


Am Montag, den 11.06.2012, 16:11 +0300 schrieb Timo Juhani Lindfors:

 after changing
 
  add_problematic package $package left obsolete init.d script behind
 
 in /var/lib/dpkg/info/sysv-rc.postinst to
 
  add_problematic package $package left obsolete init.d script $initscript 
 behind
 
 I get

nice, the suggestion worked. ;-)

 ...
 info: Checking if it is safe to convert to dependency based boot.
 Configuring sysv-rc
 ---
 
 Unable to migrate to dependency-based boot system
 
 Problems in the boot system exist which are preventing migration to 
 dependency-based boot sequencing:
 
 package fuse left obsolete init.d script /etc/init.d/fuse behind, package 
 initscripts left obsolete init.d script /etc/init.d/stop-bootlogd behind, 
 package initscripts
 left obsolete init.d script /etc/init.d/bootlogd behind, package initscripts 
 left obsolete init.d script /etc/init.d/stop-bootlogd-single behind

Please take a look at #653050 [1].

[…]


Thanks,

Paul


PS: To get the whole thread do `bts show --mbox 676463`.


[1] http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=653050


signature.asc
Description: This is a digitally signed message part


Bug#676463: #676463 sysv-rc: complains incorrectly(?) about obsolete init.d scripts for fuse and others

2012-06-11 Thread David Baron
 If the reported problem is a local modification, it needs to be fixed
 manually.  These are typically due to obsolete conffiles being left after
 a package has been removed, but not purged.  It is suggested that these
 are removed by running:
 
 dpkg --purge fuse initscripts initscripts initscripts
 

As previously posted:

I purged all the fuse and fuse-dependent packages for the time being (since I 
was not using them). This purge REMOVED packages, not just obsolete 
configuration files. Se la vie.

I am obviously not going to purge the initscripts and its zillion dependents! 
I have downgraded to testing to enable normal upgrades of other packages to 
proceed.

Please take a look at #653050 [1].

Everything suggested here is long obsolete or unavailable.



-- 
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org



Bug#676463: #676463 sysv-rc: complains incorrectly(?) about obsolete init.d scripts for fuse and others

2012-06-11 Thread Gordon Haverland
On June 11, 2012, Paul Menzel wrote:
 Am Montag, den 11.06.2012, 16:11 +0300 schrieb Timo Juhani 
Lindfors:
  after changing
 
  
   add_problematic package $package left obsolete init.d
 script behind 
 
  in /var/lib/dpkg/info/sysv-rc.postinst to
 
  
   add_problematic package $package left obsolete init.d
 script $initscript behind 
 
  I get
 
 nice, the suggestion worked. ;-)

The 3 scripts from initscripts this flags for me, all involved 
bootlogd.  Bootlogd stuff with the same 3 file names was in the 
version of initscripts currently in stable.  There are some 
bootlogd scripts in the version of initscripts in testing, but not 
all of them.  The bootlogd package is available for unstable, with 
these same scripts in them (by name, not necessarily content).  
Manually deleting those files and then installing bootlogd got rid 
of the 3 initscript errors for sysv-rc.

With fuse, the upgrade of fuse-utils was supposed to let people 
purge fuse-utils (its marked as transitional).  The problem that I 
see, is that fuseiso still depends on fuse-utils.  Purging fuse-
utils and fuseiso, I still get the sysv-rc complaining about fuse 
(and smartmontools).

Manually deleting /etc/init.d/fuse and any /etc/rc[0-6].d/*fuse 
symlinks, and then doing a reinstall of fuse got rid of the fuse 
problems for sysv-rc.  Manually deleting smartmontools and smartd 
from /etc/init.d/ and any *smart* symlinks from /etc/rc[0-6].d/ 
and then doing a reinstall of smartmontools got rid of the 
smartmontools problems for sysv-rc.

Which just leaves the LSB tags and overrides of scsi-idle and its 
symlink.  Scsi-idle as a package was removed from Debian in 2007 
(the file of mine is dated 2004).  I still show scsi-idle-2.4.23-5 
as being installed.  Purging that package, allows dependency based 
booting to be set by sysv-rc for me.

Gord



-- 
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org



Bug#676463: #676463 sysv-rc: complains incorrectly(?) about obsolete init.d scripts for fuse and others

2012-06-11 Thread David Baron
On Monday 11 June 2012 17:57:53 Gordon Haverland wrote:
 On June 11, 2012, Paul Menzel wrote:
  Am Montag, den 11.06.2012, 16:11 +0300 schrieb Timo Juhani
 
 Lindfors:
   after changing
   
add_problematic package $package left obsolete init.d
  
  script behind
  
   in /var/lib/dpkg/info/sysv-rc.postinst to
   
add_problematic package $package left obsolete init.d
  
  script $initscript behind
  
   I get
  
  nice, the suggestion worked. ;-)
 
 The 3 scripts from initscripts this flags for me, all involved
 bootlogd.  Bootlogd stuff with the same 3 file names was in the
 version of initscripts currently in stable.  There are some
 bootlogd scripts in the version of initscripts in testing, but not
 all of them.  The bootlogd package is available for unstable, with
 these same scripts in them (by name, not necessarily content).
 Manually deleting those files and then installing bootlogd got rid
 of the 3 initscript errors for sysv-rc.
I will try this!

 
 With fuse, the upgrade of fuse-utils was supposed to let people
 purge fuse-utils (its marked as transitional).  The problem that I
 see, is that fuseiso still depends on fuse-utils.  Purging fuse-
 utils and fuseiso, I still get the sysv-rc complaining about fuse
 (and smartmontools).

I purged all fuse stuff, guess I can reinstall now!

 Manually deleting /etc/init.d/fuse and any /etc/rc[0-6].d/*fuse
 symlinks, and then doing a reinstall of fuse got rid of the fuse
 problems for sysv-rc.  Manually deleting smartmontools and smartd
 from /etc/init.d/ and any *smart* symlinks from /etc/rc[0-6].d/
 and then doing a reinstall of smartmontools got rid of the
 smartmontools problems for sysv-rc.
A have no smarts either so guess I can reinstall that as well.

I wish those were the whole story on my system!



-- 
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org



Bug#676463: #676463 sysv-rc: complains incorrectly(?) about obsolete init.d scripts for fuse and others

2012-06-11 Thread Paul Menzel
Am Montag, den 11.06.2012, 08:57 -0600 schrieb Gordon Haverland:

[…]

 Manually deleting smartmontools and smartd from /etc/init.d/ and any
 *smart* symlinks from /etc/rc[0-6].d/ and then doing a reinstall of
 smartmontools got rid of the smartmontools problems for sysv-rc.

I submitted this as #677095 [1].


Thanks,

Paul


[1] http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=677095


signature.asc
Description: This is a digitally signed message part