In my nightly "emerge -DU world" sSMTP fscked my MTA without uninstalling it. I just installed then munged the symlinks. Oops! I think this has happened with several of the other mail systems in the past. If there is some override that needs to be in place, please let me know.
please give us more information...
Give me a break something happens two months ago an you want more detail? Just like it said some dependency in my nightl "emerge -DU world" cause ssmtp to install and destroyed sendmail on every system. The problem has not happend again please close.
This bug has been around forever and keeps getting reported as fixed but is still there. Note in the output below how SSMTP emerges right after sendmail. That is the bug. When SSMTP emerges it overwrites the sendmail binaries. sock / # emerge sendmail vixie-cron -upv These are the packages that I would merge, in order: Calculating dependencies ...done! [ebuild N ] sys-libs/db-1.85-r1 264 kB [ebuild N ] sys-libs/gdbm-1.8.0-r5 +berkdb -static 130 kB [ebuild N ] net-mail/mailbase-0.00-r5 [empty/missing/bad digest] [ebuild N ] net-dns/hesiod-3.0.2 31 kB [ebuild N ] net-mail/sendmail-8.12.10 +berkdb -gdbm -ldap -mbox -sasl +ssl -tcpd 1,848 kB [ebuild N ] net-mail/mailwrapper-0.1 6 kB [ebuild N ] net-mail/ssmtp-2.60.7 -ipv6 -md5sum +ssl 59 kB [ebuild N ] net-mail/procmail-3.22-r6 221 kB [ebuild N ] sys-apps/vixie-cron-3.0.1-r4 -(selinux) 49 kB
Look at bug 33790 for a previous report of this.
It also nukes mailq for courier ..
@Zeek: your problem is bug 1343
*** Bug 76197 has been marked as a duplicate of this bug. ***
This bug could be fixed by having portage re-check its dependancies when ANY virtual gets updated - JUST like when the portage package itself gets updated :)
*** This bug has been marked as a duplicate of 68220 ***