Description of problem: authconfig creates /etc/pam.d/password-auth-ac and symlinks /etc/pam.d/password-auth to it. Unfortunately, the latter file is owned by pam, so if a newer pam updates /etc/pam.d/password-auth, it collides with the symlink, and ends up creating /etc/pam.d/password-auth.rpmnew. Version-Release number of selected component (if applicable): authconfig-6.2.6-3.fc19.1.i686 pam-1.1.6-12.fc19.i686 How reproducible: No idea, to be honest. I found an rpmnew file, and worked backwards to figure out what could have gone wrong.
This is not a bug. It works as it is expected.
Compare and contrast: https://bugzilla.redhat.com/show_bug.cgi?id=194246 ... :)
I disagree that this is expected. Certainly, users would find it unexpected. a. What is a user supposed to do anyway, when they see this? Just delete the rpmnew files? b. Aren't we losing information? What if the rpmnew file contained an update? Right now, the 2 packages are just fighting with one another, and I don't see how that can ever be The Right Thing.
I just don't see any way how to workaround this. The configuration in pam package is a default one. The configuration from authconfig is user configured.