On 09.07.2012 02:54, Steve Langasek wrote: > On Tue, Jul 03, 2012 at 12:23:54AM +0200, Michael Biebl wrote:
>> Right, the issue is, that we switched to multiarch paths in 44-3. > > What does this have to do with multiarch paths? The module path shouldn't > have been embedded in the pam-auth-update profile anyway - was it? [..] > There should be *no* paths in the configuration, therefore there should be > nothing to update. You should use unqualified module names and trust pam's > internal path - which AFAICS is what is done here. Yeah, I'm really sorry for all the noise. The issue is most certainly not about multiarch paths. What seems to be the problem here is that Teodor has libpam-systemd no longer installed but there is still a corresponding line in common-session. As Tollef already mentioned, this should only happen if Teodor chose to manage common-session by hand. Otherwise pam-auth-update --package --remove systemd would have removed it. (assuming there isn't a bug in pam-auth-update) Teodor, could you attach the output of "debconf-show libpam-runtime" please. Do you remember editing /etc/pam.d/common-session by hand? Michael -- Why is it that all of the instruments seeking intelligent life in the universe are pointed away from Earth?
signature.asc
Description: OpenPGP digital signature
