Control: severity -1 wishlist > We have included spamassassin in a custom installer. During installation > 'start-stop-daemon' is not available (fake) > sa-compile relies on start-stop-daemon to be working (sa-compile.postinst > line 17-19) > or it wil error trying to 'chmod' a directory which does not exist. > (sa-compile.postinst line 23-24). > This was changed with commit 446572164382f2ab4e6781ba751b6ca90364da9
start-stop-daemon is provided by dpkg, which is Priority: required. Thus, the assumption that it is available during the postinst execution is a valid one. As stated in the policy document, "Removing a required package may cause your system to become totally broken...." If you choose to break your system in this way, that's fine, but it's not a bug in spamassassin. My recommendation is that you don't break dpkg in your custom installer. This can probably be fixed in spamassassin, and it's probably not too difficult to do, so I'll leave this open with a wishlist severity. However, it's very likely that you'll find other packages that also break when you remove (parts of) required packages. noah
