[23601] in Source-Commits
Re: /svn/athena r23236 - trunk/debathena/config/pam-config/debian
daemon@ATHENA.MIT.EDU (Greg Price)
Tue Nov 4 04:01:23 2008
Date: Tue, 4 Nov 2008 04:00:39 -0500
From: Greg Price <price@MIT.EDU>
To: Anders Kaseorg <andersk@mit.edu>
Cc: source-commits@mit.edu
Message-ID: <20081104090039.GZ20760@vinegar-pot.mit.edu>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <alpine.DEB.2.00.0811040258370.6413@vinegar-pot.mit.edu>
On Tue, Nov 04, 2008 at 02:58:56AM -0500, Anders Kaseorg wrote:
> On Mon, 3 Nov 2008, price@MIT.EDU wrote:
> >work around a pam-auth-update bug in awful fashion
>
> What is the nature of this bug? Did you report it?
I prepared a machine in the following way:
- fresh Hardy machine, from XVM autoinstaller
- install Debathena
- do-release-upgrade -d
- restore sources.list entries, s/hardy/intrepid/, add beta repo
- aptitude update && aptitude full-upgrade
After step 3, the files /etc/pam.d/common-* were still in the old
style and lacked Debathena's entries. After step 4, they were in the
new style, as expected since debathena-pam-config should have run
pam-auth-update --package --force.
But they still lacked Debathena's entries, and meanwhile
/var/lib/pam/seen indicated that pam-auth-update believed it had seen
the Debathena files in /usr/share/pam-configs/. Since each of these
files has the line 'Default: yes', it should be taken up by
pam-auth-update when first seen, not left out.
Removing the relevant lines from /var/lib/pam/seen and rerunning
pam-auth-update --package fixed the problem.
I'm preparing a new test machine to investigate this again.
Greg
