I was about to work on this bug (that asks splitting out NSS module from libpam_winbind) and propose a patch adding a libnss_winbind package instead of providing NSS modules in libpam_winbinnd (which indeed always confused me).
However, we need to Do The Right Thing. We can't just split the NSS module out of libpam_winbind because that would drop libnss_winbind for our users, and some of them are certainly relying on having them, of course. What is the recommended course of action in such case? We indeed want those people who are upgrading from libpam_winbind prior to the split to have libnss_winbind installed, while new users of libpam_winbind shouldn't. Unless I'm too tired for this, I do not find any reference for such case. Ideas, other maintainers? --
signature.asc
Description: Digital signature
