tags 326906 - confirmed thanks I had previously marked this bug 'confirmed', but I'm no longer persuaded that this is the case. The only reason to move these config files out of libpam-modules is to accomodate installation of PAM modules for multiple architectures; libpam-runtime is /not/ the right place for these config files, because these config files are tied to particular PAM modules and libpam-runtime depends on libpam-modules - not the other way around.
Since this is not a shared library package (it does not undergo soname changes), there is no Policy prohibition on shipping the conffiles in this package. And the multiarch proposal on the table accounts for sharing identical files between the different architecture builds of a single package, which should apply to conffiles as well as to any other files (I expect). So I think this bug should probably be closed as 'wontfix'; I'm certainly not going to split files out into a new package just to support the biarch use case. -- Steve Langasek Give me a lever long enough and a Free OS Debian Developer to set it on, and I can move the world. Ubuntu Developer http://www.debian.org/ slanga...@ubuntu.com vor...@debian.org
signature.asc
Description: Digital signature
