As I posted, the problem is NOT in the boinc-app-seti package at all. The start-stop-daemon for boinc (boinc-client) was producing a pid file containing a different pid number than the actual boinc pid! This would cause the distribution /etc/init.d/boinc_client fails to stop the boinc and this causes all the installation problems for seti.
I changed that script to simply NOT test the pid number but killall boinc if any such pid file exists. Boinc-app-seti will now install. This but, degraded as appropriate belong to either boinc (boinc_client) or start-stop-daemon. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
