tags 647429 help tags 647430 help thanks On Mon, May 28, 2012 at 04:16:35PM +0200, Jakub Wilk wrote: > >Jakub, > > > >Do you have an example of a package that does 'the right thing'? > > No, sorry. > > >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. > > Unfortunately, I have no idea what a proper fix would like either. > > >Are these issues documented somewhere? > > I'm not aware of such documentation. > > I tried to bring up this topic on debian-devel once, but there were > no answers: http://lists.debian.org/[email protected]
As I don't know what the proper fix for this bug should be, I'm tagging it 'help'. Same thing for #647430, which is the same bug, but for libpam-winbind. Cheers, Ivo -- To UNSUBSCRIBE, email to [email protected] with a subject of "unsubscribe". Trouble? Contact [email protected]
