[Pkg-sysvinit-devel] Bug#585398: sysv-rc: sysv-rc fails to convert at each upgrade

[Tollef Fog Heen]

]] Petter Reinholdtsen 

| [Tollef Fog Heen]
| > Could you please provide a way for me to tell sysv-rc to keep its hands
| > off my configuration as I'm not using sysvinit and would rather keep it
| > that way?  Alternatively, make it not try to convert on each upgrade,
| > but just try once.
| 
| It is intentional to ask on every upgrade, to try to get everyone over
| to the new dependency based boot script ordering, and away from the
| legacy ordering.

Well, I don't want to make that switch and asking me on every upgrade
just annoys me.  What is the purpose of annoying the sysadmin?

| The only way to avoid this question on every upgrade, is to fix the
| problems blocking migration and do the upgrade.

Given that there's a debconf question where you can decline the
conversion, this doesn't look like a legitimate reason.  The reason I'm
not asked the question so I can decline it is that sysv-rc believes my
init scripts don't have the right set of headers.

| Staying with the legacy boot ordering is not a sustainable alternative
| for Debian.

There's nothing stopping me from just faking that the switch has
happened without actually changing any priorities.  Anything changing
the priorities after that without admin intervention would be granted an
RC bug due to not preserving admin changes.

| What kind of problems are detected?

 │ package initscripts left obsolete init.d script behind, package initscripts left obsolete init.d script behind, package  │ 
 │ network-manager left obsolete init.d script behind, package powernowd left obsolete init.d script behind, package udev   │ 
 │ left obsolete init.d script behind, package atftpd removed but not purged, package dhcp3-server removed but not purged,  │ 
 │ package dnsmasq removed but not purged, package ekeyd removed but not purged, package inetutils-inetd removed but not    │ 
 │ purged, package iodine removed but not purged, package ircd-hybrid removed but not purged, package nagger removed but    │ 
 │ not purged, package postgresql-8.3 removed but not purged, package puppet removed but not purged, package rng-tools      │ 
 │ removed but not purged, package samba removed but not purged, package scsitools removed but not purged, package          │ 
 │ sysfsutils removed but not purged, package winbind removed but not purged, insserv: warning: script                      │ 
 │ 'S10powernowd.early' missing LSB tags and overrides, insserv: script bootlogs: service bootlogs already provided!,       │ 
 │ insserv: warning: script 'powernowd.early' missing LSB tags and overrides,                                               │ 

I think this is pointing to the fact that having removed and not purged
packages is not some exceptional state, it's a fairly normal state and
having Priority: required packages failing to deal with it is a serious
(not as in the bug severity) bug.

| I plan to change the migration check in the next upload to only report
| removed but not purged packages as problems if there are loops or
| other dependency problems with the boot ordering, and expect this will
| make it possible for more people to migrate without any manual fixing.

The main point here is: I don't want to migrate, and I'm at the point of
pondering just adding an equivs package to sysv-rc to make it stop
annoying me on upgrades.

Also, I think trying to force people to convert against their will is
silly and wrong and all and while I hope to convince you, I'll be happy
to take this to the TC to make the annoying debconf notices stop.

-- 
Tollef Fog Heen
UNIX is user friendly, it's just picky about who its friends are