Hi, On Thursday, September 29, 2005 3:36 PM, Michael Setzer <[EMAIL PROTECTED]> wrote: [...] > This means that you have to add something like > > [EMAIL PROTECTED] > > to your /etc/security/pam_env.conf and everything should work again as > usual.
That's a workaround, not a solution. The correct solution is to upgrade to the fixed version of libpam-modules - the package that caused the problem - which should hit mirrors tonight (0.79-2) > Maybe this issue should be reflected in the next version of the > locales package so that the pam_env.conf file will be upgraded > properly by any `dpkg-reconfigure locales`. No. locales shouldn't, and more to the point *can't*, touch pam_env.conf, as it belongs to an entirely different package. [EMAIL PROTECTED]:~$ dpkg -S /etc/security/pam_env.conf libpam-modules: /etc/security/pam_env.conf (Hence the first paragraph above, and the fact that I reassigned and closed this bug earlier). Regards, Adam -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
