> 1.0.6-5964_amd64.deb) ...
> * Stopping DNS proxy for HIP hipdnsproxy
> ...fail!
> invoke-rc.d: initscript hipl-dnsproxy, action "stop" failed.
> dpkg: warning: old pre-removal script returned error exit status 1
In this case start-stop-daemon which is used to stop the daemon returns 1 if the daemon is not running and it is treated as an error during installation. Using the option --oknodo fixes this.
> Preparing to replace hipl-firewall 1.0.6-2 (using .../hipl-firewall_1.0.6-5964_amd64.deb) ...
> * Stopping HIP firewall hipfw
> invoke-rc.d: initscript hipl-firewall, action "stop" failed.
> dpkg: warning: old pre-removal script returned error exit status 2
In this case it's the flushing of the firewall rules which returns status 2. We are using 'set -e' so any unchecked command returning nonzero exits the script. Checking the return value of the flush_iptables function fixes this problem.
I have committed the changes in trunk revisions 5968 and 5969 and on my machine it works without problems. Can you check if it's the same for you Miika?
PS: The flags notice of the firewall seems to be just a warning and no error. We are using the option -F to accept all HIP traffic. This means we are not dealing with authentications and this is why specifying any timeouts for them won't have an effect.
There have been two problems with the scripts:
> 1.0.6-5964_ amd64.deb) ...
> * Stopping DNS proxy for HIP hipdnsproxy
> ...fail!
> invoke-rc.d: initscript hipl-dnsproxy, action "stop" failed.
> dpkg: warning: old pre-removal script returned error exit status 1
In this case start-stop-daemon which is used to stop the daemon returns 1 if the daemon is not running and it is treated as an error during installation. Using the option --oknodo fixes this.
> Preparing to replace hipl-firewall 1.0.6-2 (using .../hipl- firewall_ 1.0.6-5964_ amd64.deb) ...
> * Stopping HIP firewall hipfw
> invoke-rc.d: initscript hipl-firewall, action "stop" failed.
> dpkg: warning: old pre-removal script returned error exit status 2
In this case it's the flushing of the firewall rules which returns status 2. We are using 'set -e' so any unchecked command returning nonzero exits the script. Checking the return value of the flush_iptables function fixes this problem.
I have committed the changes in trunk revisions 5968 and 5969 and on my machine it works without problems. Can you check if it's the same for you Miika?
PS: The flags notice of the firewall seems to be just a warning and no error. We are using the option -F to accept all HIP traffic. This means we are not dealing with authentications and this is why specifying any timeouts for them won't have an effect.