On 25 June 2012 02:29, Ivo De Decker <ivo.dedec...@ugent.be> wrote: > 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/20120211115057.ga8...@jwilk.net > > 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 > > >From a naive reading of the Debian Policy Manual (Section 8.2: shared library support files, < http://www.debian.org/doc/debian-policy/ch-sharedlibs.html#s-sharedlibs-support-files>) and Debian Wiki's multi-arch conversion HOWTO (Section: Multi-arch: foreign support packages, < http://wiki.debian.org/Multiarch/Implementation#Multi-Arch:_foreign_support_packages>), it appears that the correct solution would be:
1. Split libpam-winbind into 2 packages (likewise for libpam-smbpass); 2. One package contains files under /lib/* ; 3. The other (libpam-winbind-data?) contains support files under /usr/share/* ; 4. The support files package is made "Multi-Arch: foreign"; 5. The prerm action should be done in the support files package, so that it is done only once, no matter how many co-installations of libpam-winbind there are. I must confess that I'm not a regular Debian contributor, just a grateful user of libpam-winbind who would like to help out (thanks maintainers!). There may be perfectly good reasons why libpam-winbind (and libpam-smbpass) is currently one package that I'm ignorant of. Regards, Frank
