[Nathan Scott] > > and the package fail to install in unstable now. > > Can you describe this in more detail? It installs OK for me... I > must be missing something, of course - what is no longer functional?
Sure. Without any runlevel listed in Default-*, there is no start or stop symlinks set in /etc/rc?.d/, and the package fail to start as it should during boot. This is the status after installation in a sid chroot: # ls -l /etc/rc?.d/*pcp /etc/rc?.d/*pmie /etc/rc?.d/*pmproxy ls: cannot access /etc/rc?.d/*pcp: No such file or directory ls: cannot access /etc/rc?.d/*pmie: No such file or directory ls: cannot access /etc/rc?.d/*pmproxy: No such file or directory # Note that RedHat/SuSe and Debian have different runleve defaults. Debian have identical setting for runlevels 2-5, while RedHat/Suse do not start the network services in runlevel 2 (and 4?). > I couldn't find where in the developers reference / policy doc / > ... that these fields are explained in detail - can you point me to > the right place to read further as to what is required of Debian > packages here? The best documentation is currently at <URL:http://wiki.debian.org/LSBInitScripts/DependencyBasedBoot> and <URL:http://wiki.debian.org/LSBInitScripts>. Happy hacking, -- Petter Reinholdtsen -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
