user release.debian....@packages.debian.org usertags 706185 + wheezy-can-defer tags 706185 + wheezy-ignore thanks
On Fri, 2013-04-26 at 02:35 +0200, Andreas Beckmann wrote: > libpam-ldap is a Multi-Arch: same package with shared pam configuration > between all installed architectures of this package. Problems arise if > more than one architecture of the package was installed and one > architecture gets purged while one or more other architectures stay > installed (or are in config-files-remaining state): the configuration > gets deleted while other architectures still need it. > > Consider the following sequence: > > apt-get install libpam-ldap:amd64 > apt-get install libpam-ldap:i386 > dpkg --purge libpam-ldap:i386 > > Thereafter the pam configuration originally set up by libpam-ldap:amd64 > is gone. Whilst I would be interested in seeing a fix for this issue, I don't believe it should be considered a blocker for the release at this point. The fact that it's only being reported at this stage of the cycle, and only as a result of automated testing rather than occurring on real systems, adds to that opinion. Regards, Adam -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
