I just saw the same problem upgrading to sarge. I had a look around and
it looks like the script simply wasn't written to be run under set -e.
When a script uses $? liberally to explicitly test success/failure of
commands, you can't just enable -e and expect it to work. You have
to carefully ins
If you want to solve this bug once and for all, just replace "--exec
$DAEMON" in your stop target with "--name automount" instead. This way,
it will match pidfile and process name, which is about as reliable for
getting the "right process", but won't fail on inode removal.
I'm making this change
Package: autofs
Version: 4.1.3+4.1.4beta2-3
Severity: grave
Upgrade from 4.1.3+4.1.4beta2-2 fails:
Preparing to replace autofs 4.1.3+4.1.4beta2-2 (using
.../autofs_4.1.3+4.1.4beta2-3_amd64.deb) ...
Stopping automounter:dpkg: warning - old pre-removal script returned error exit
status 2
dpkg - t
3 matches
Mail list logo
