On Wed, Jul 23, 2008 at 08:06:56PM -0700, Marcin Owsiany wrote: > Package: libpam-modules > Version: 0.99.7.1-6
> /etc/security/opasswd get created by the postinst script, but is never > deleted. > I do know that libpam-modules is unlikely to be purged, but I still > consider this a bug: > - it sets bad example > - it will leave cruft if we even migrate to something different than > libpam-modules Discussed extensively on IRC. This file should not be removed in the postrm because: - it's neither a config file nor a logfile, but rather system data resulting from the use of the package, which is not one of the classes of files policy requires us to remove - in the event that libpam-modules were ever superseded by another technology, it would a) almost certainly coexist with libpam-modules for a time and b) be leverage the existing files, with the result that remove-on-purge would take this data out from under the new package. So instead, I'll discuss with upstream whether it would be appropriate to unconditionally autocreate this file on password changes, and if not, I will add a comment in the postrm explaining why we don't remove it. -- 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/ [EMAIL PROTECTED] [EMAIL PROTECTED] -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
