-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1
Charles A Edwards wrote: | At the time the upgrade was done there existed a flux in cooker tree | which required that pam-0.77-9mdk be removed. | When pam-0.77-9mdk is removed it causes system-auth to | to be changed to rpmsave. | When then pam-0.77-10mdk is installed it will create | system-auth.rpmnew, believing that system-auth still exist. | | The stated occurrence in an aberration and could only occur under very | limited and specialized circumstances.
Then this is a bug and should be fixed. If there was .rpmsave file already (and no system-auth), why .rpmnew was created instead of just putting the file in place ?? My understanding is, that .rpmnew should be only created when there is a conflicting file, which cannot be safely upgraded. Not when there is *no* file at all.
At least two people encountered this already, so it is not just occuring under "limited and specialized circumstances".
Jan
- --
Jan Ciger VRlab EPFL Switzerland GPG public key : http://www.keyserver.net/ -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.3 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org
iD8DBQE/huTzn11XseNj94gRAoX2AKCfRE/6sV62MA00QoqrGzvSpV3ohwCgsder PVxQEljTSqzDJsCOaEO17yU= =/clX -----END PGP SIGNATURE-----
