Quoting Jancio Wodnik <jancio_wodnik@xxxxx>:
When i remember, there was an update of sendmail in march, wait, i will grep that for you: 25 of march my system was update with sendmail-8.12.11-4.22.9.legacy and then was problem with AUTH - mail from local lan were rejected, so i greep mailing list, irc and i made: alternatives --configure mta so (when i can well remember) this command rebuild all broken symlink, in /etc/pam.d too. After that, there cam another update of sendmail, sendmail-8.12.11-4.22.10.legacy which broke again AUTH, i fix that by making necessery symbolic links by hand, i make that quickly, alternatives --config mail didn't make necessry symlinks (wired ?).
Yeah, I think that all is "expected behaviour" for that upgrade path. Unfortunately such was not stated in the update release, and wasn't stated on the mailing list until later (in response to your mail).
Saddly, but all these boxes are production servers, so i have no time to do further investigation.
Understood.
Sory, but i can't experiment for that, it is production box and we are planning to move to CentOS.
Yes, if it is working, there is no reason to do anything.
How to apply ? By yum night updates !
I would never (personally) apply automatic updates to a production server... See http://www.fedoraproject.org/wiki/AutoUpdates for full details...
I'm tired, so i close this case for me and will not do further investigation. Sorry.
No problem. I think the long post by David E. about the 4 upgrade paths and what happens in each path documents the path well enough for now. And since any new updates will probably skip the intermediate package, this shouldn't be a problem for anyone in the future (I hope). -- Eric Rostetter The Department of Physics The University of Texas at Austin Go Longhorns! -- fedora-legacy-list@xxxxxxxxxx https://www.redhat.com/mailman/listinfo/fedora-legacy-list
