Package: boa Version: 0.94.14rc20-1.3 While testing boa with piuparts, I ran into the following problem:
Preparing to replace boa 0.94.14rc20-1.2 (using .../boa_0.94.14rc20-1.3_i386.deb) ... Stopping HTTP server: boastart-stop-daemon: nothing in /proc - not mounted? (Success) dpkg: error processing /var/cache/apt/archives/boa_0.94.14rc20-1.3_i386.deb (--unpack): subprocess pre-installation script returned error exit status 2 netstat: no support for `AF INET (tcp)' on this system. Updating rc.d symbolic links to start boa upon booting. Starting boa ... start-stop-daemon: nothing in /proc - not mounted? (Success) Piuparts tests packages by installing and removing them in a chroot. Packages should not start daemons in that chroot unconditionally when installed. Specifically, they should not run an /etc/init.d script directly, but instead use the invoke-rc.d command to do it (see policy 9.3.3.2 Running initscripts). Piuparts sets up the chroot with a policy-rc.d script that prevents invoke-rc.d from starting the service. This same problem can happen in real life as well. For example, the system administrator may want to configure run levels to have different services running, and a package that unconditionally runs its /etc/init.d script will cause trouble with that. -- Do or do not. There is no stress. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
