Since your prerm does not stop bitlbee on upgrade, by the time the
postinst tries to restart it, the executable has been replaced, and
start-stop-daemon cannot stop it.
To fix, you should instead of using --exec ,
use --pidfile /var/run/bitlbee.pid
I was going to fix this, but:
#
# F
Package: bitlbee
Version: 3.0.3-1
Severity: normal
I upgraded from 3.0.1, and had 2 separate bitlbee processes running.
The init script failed to stop the old, and started a new.
This happens because of the way start-stop-daemon is used.
start-stop-daemon --start --quiet --pidfile $PIDF
2 matches
Mail list logo
