Re: [Cooker] Re: Cooker Login Fail after daily Update

[Olivier Blin]

Vincent Danen <vdanen@mandriva.com> writes:

>>The problem here is Msec changing it without my knowledge. I would watch, or
>>at least be more wary, for trouble, if (I knew) my pam config was modified.
>
> Seriously?  msec is changing pam configs?  For crying out loud...

So what? It's part of his goal.

>>> But is it normal that pam_unix does not work anymore in the config
>>> file? In the initial plan, it was said that pam_tcb was backwards
>>> compatible with pam_unix, it does not seem to be the case...
>>>
>>> Anyway, I don't think we should force migration to pam_tcb in %post,
>>> there's no real reason to handle .rpmnew files differently in this
>>> package if pam_tcb is backwards compatible as you claim.
>>
>>I'm not sure I upgraded to that version of pam. I'll check later at home. I
>>think I'll put the old pam and config back and watch how %post handles it.
>
> Ok.  I tested it quite suitably (well, the scripting additions I added)
> so it should do the right thing.  I'm waiting for my local cooker mirror
> to sync up to make sure that the script upgrade goes 100%.  It should
> leave the original file as system-auth.original.

I'd better remove the %post upgrade script, if we can make the package
backward compatible.

This file is marked as config file, meaning that it's best for the
package not to touch it unless strictly needed. I'd better leave such
a major change during the upgrade in the system admin's hands (it's
not the only package that leaves a rpmnew file behind, and we usually
don't merge the change automatically).

-- 
Olivier Blin (blino) - Mandriva