pam-auth-update: errors on package removal when calling
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
pam (Ubuntu) |
Fix Released
|
Undecided
|
Unassigned |
Bug Description
I have a call to pam-auth-update --package in the ecryptfs-utils postrm script.
It does do the right thing (removing the ecryptfs pam configuration).
However, a bunch of noisy error messages get dumped...
(Reading database ... 24977 files and directories currently installed.)
Removing ecryptfs-utils ...
Use of uninitialized value in numeric comparison (<=>) at /usr/sbin/
Use of uninitialized value in numeric comparison (<=>) at /usr/sbin/
Use of uninitialized value in numeric comparison (<=>) at /usr/sbin/
Use of uninitialized value in numeric comparison (<=>) at /usr/sbin/
Use of uninitialized value in numeric comparison (<=>) at /usr/sbin/
Use of uninitialized value in numeric comparison (<=>) at /usr/sbin/
Use of uninitialized value in numeric comparison (<=>) at /usr/sbin/
Use of uninitialized value in numeric comparison (<=>) at /usr/sbin/
Use of uninitialized value in numeric comparison (<=>) at /usr/sbin/
Use of uninitialized value in numeric comparison (<=>) at /usr/sbin/
Processing triggers for man-db ...
:-Dustin
# FIXME: we need an option that will permit us to remove configs in
# prerm remove, to avoid having a broken config at any point.
USTL ;)
I'll fix this to make the code less whiny in the case of a reference to a non-existent option. In the meantime, please don't call pam-auth-update in the postrm - it should be called with this not-yet-implemented --remove option in the prerm remove case, so that the config is fixed up on disk /before/ the module is pulled out from under us.
Thanks for continuing to be a guinea pig for this :)