On Wed, Nov 02, 2011 at 05:53:57PM +0100, Jakub Wilk wrote: > libpam-smbpass is marked as "Multi-Arch: same", but does this in prerm: > | if [ "$1" = "remove" ]; then > | pam-auth-update --package --remove smbpasswd-migrate > | fi > > This won't do the right thing if multiple copies of the library are > installed and one of them is being removed.
Jakub, Do you have an example of a package that does 'the right thing'? What should the package do? The manpage of pam-auth-update says that pam-auth-update --remove should be called before removing the module, but this isn't correct if the module remains for another architecture. Should pam-auth-update be made multiarch-aware and handle this automatically? If binaries from multiple architectures call pam on the same system, and a pam-module is installed for one of these architectures, but not for the other one, the pam configuration cannot be correct for both of them. Are these issues documented somewhere? Cheers, Ivo -- To UNSUBSCRIBE, email to [email protected] with a subject of "unsubscribe". Trouble? Contact [email protected]
