| 2008-08-22 01:57:26 |
Steve Langasek |
pam: statusexplanation |
# 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 :) |
Fixed in pam 1.0.1-3ubuntu3. Changelog follows:
pam (1.0.1-3ubuntu3) intrepid; urgency=low
* s/pam-auth-config/pam-auth-update/ in the source, I can't seem to get
this name consistent to save my life - I'm starting to think I named it
wrong...
* Fix the regex used when suppressing jump counts when reading the saved
config, so that we don't clobber module options with numbers in them.
* If the target doesn't already exist, don't try to copy it.
* Filter the config list to exclude configs that no longer exist.
LP: #260122.
* Avoid unnecessary sort/grep in the case where we already have a sorted
list.
* Implement pam-auth-update --remove, for use in package prerms when called
with "remove".
|
|
