Comment 5 for bug 242635

motu-sru is subscribed to give clearance for uploading the fix to hardy-proposed:

1. The trousers package cannot be removed in Hardy if the tpm driver is missing. This is a mistake from the user's side since the tpm driver is required for the package to work properly, but we obviously have to cater for it.

2. The bug has been fixed in the release version by adding the --oknodo option to the start-stop-daemon stop action.

3. A minimal patch applicable to the stable version of the package is attached.

4. TEST CASE:

A simple test case is defined here.

4.1 In Hardy, install the trousers (0.3.1-4ubuntu0.1) package with your preferred package manager. The hardy-updates repo must be enabled for you to be able to do this.

4.2 Make sure that the daemon is not running (it won't if you don't have a tpm chip and/or a tpm kernel module loaded).

4.3 Try to remove the package with your preferred package-manager (for instance with the command: sudo apt-get remove trousers).
This should fail with the following message:

Removing trousers ...
Stopping Trusted Computing daemon: invoke-rc.d: initscript trousers, action "stop" failed.
dpkg: error processing trousers (--remove):
 subprocess pre-removal script returned error exit status 1
Starting Trusted Computing daemon: device driver not loaded, aborting.
Errors were encountered while processing:
 trousers
E: Sub-process /usr/bin/dpkg returned an error code (1)

4.4 Enable the hardy-proposed repository. For instance, you can do this by adding the following line to /etc/apt/sources.list:

  deb http://archive.ubuntu.com/ubuntu/ hardy-proposed universe

Update your local cache and INSTALL trousers again.

4.5 During the installation you will be asked what you want to do about the configuration file `/etc/init.d/trousers. Answer Y or I (which means install the package maintainer's version).

4.6 Try again to remove the package. This time it should succeed.

4.7 Disable the hardy-proposed repository.

WARNING: Any user willing to help with testing is more than welcome. Please be aware that there might be some time before the updated packages will be available in your mirror. The sru needs to be approved and the package manually copied by an archive admin, this may take from 1 to several days to be processed.