[Josh Triplett] > hotplug only exists in etch. It does not exist in lenny, and Debian > does not support upgrades that skip a release. Thus, please drop > the override for hotplug (and hotplug-net), and conflict with > hotplug instead.
I'm not quite sure this is safe to do, and that is why the overrides for scripts in rcS.d/ was kept. The scenario I am afraid of, is a machine that was installed with Etch or earlier, which used to have hotplug installed, and got the package removed but not purged. This would leave the init.d script behind until the package is purged. If such machine started using dependency based boot sequencing in Lenny, and the ordering worked because of these override files, dropping the override files might break the boot sequence handling completely, because the scripts would be assumed to have the default headers (start in runlevels 2-5, stop in runlevels 0, 1, 6 and depend on $remote_fs and $syslog. Existing scripts in rcS.d/ might still depend on these obsolete scripts, and a loop would be introduced by removing the overrides. The only way to avoid this would be to make sure the old init.d scripts are removed from /etc/init.d/, preferably by forcing the user to purge the old packages. Perhaps we should start warning users about these old packages and ask them to purge them if they exist? Or just remove the scripts ourself - bad and not allowed by policy? Or refuse to upgrade if these scripts are not purged - bad user experience? Not quite sure how to handle these old overrides for scripts in rcS.d/. A good start would probably be to make sure no existing packages have a relationship to these obsolete scripts. Happy hacking, -- Petter Reinholdtsen -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
