"dpkg-reconfigure libpam-runtime" does not respect debconf frontend
Bug #295444 reported by
Daniel Richard G.
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| debconf (Ubuntu) |
New
|
Undecided
|
Unassigned | ||
Bug Description
Binary package hint: libpam-runtime
This concerns libpam-runtime 1.0.1-4ubuntu5 in intrepid.
Run "dpkg-reconfigure -f editor libpam-runtime".
Why does the dialog interface come up when we explicitly asked otherwise?
Revision history for this message
| Steve Langasek (vorlon) wrote | #1 |
| Changed in pam: | |
| status: | New → Invalid |
Revision history for this message
| Daniel Richard G. (skunk) wrote | #2 |
| Changed in pam: | |
| status: | Invalid → New |
To post a comment you must log in.
Thank you for taking the time to report this bug and help to improve Ubuntu.
The -f argument to dpkg-reconfigure is ineffectual for libpam-runtime because -f only sets the debconf frontend used when calling the .config script for a package, and libpam-runtime doesn't use a .config script: it calls (and must call) pam-auth-update from the postinst.
To set the frontend used by pam-auth-update, you can run either of these commands:
DEBIAN_
DEBIAN_
Marking this report as invalid because the pam scripts are functioning as designed; if you believe dpkg-reconfigure's behavior is incorrect and that -f should be applied when invoking any of the maintainer scripts, this bug report should be reassigned to debconf.