On Wed, 2005-02-02 at 23:25 -0500, Marshal Newrock wrote:
> All went well, until I tested the mail system, and discovered that
> /usr/sbin/sendmail was a symlink to /usr/sbin/ssmtp, which I thought I had
> removed. Checking the emerge log, I saw that, subsequent to postfix being
> installed, ssmtp was reinstalled, clobbering /usr/sbin/sendmail. Looking
> through the ebuilds, I saw that amavisd-new requires virtual/mta, which
> defaults to ssmtp. portage is failing to recognize that ssmtp satisfies a
> virtual that another program, installed earlier in the batch job, already
> satisfies.
in your /etc/make.conf you can add the FEATURES="collision-protect"
which will make it stop before overwriting files owned by another
package, in this case even if it hadn't seen that virtual/mta *would be*
satisfied partway through the process, it would've stopped before
installing ssmtp, then when you resume the emerge, that virtual would've
already been taken care of so it wouldn't even look for another package
to satisfy that dependancy.
when submitting to bugzilla though, you are generally asked to provide
"emerge info" which in many cases is overkill but it also saves time on
asking for more details about your configuration (like use flags for
example), as that can explain a lot about why certain [unexpected]
packages packages are pulled in. The "mailwrapper" use flag tells
portage to allow any number of mail-related programs to be installed at
the same time. The behavior you described sounds like you were using a
version of portage that was -r3 (or earlier) and should not have
happened with the current version of portage. Of course, that is also
part of what is shown by emerge info.
--
Scott Taylor - <[EMAIL PROTECTED]>
Amoebit:
Amoeba/rabbit cross; it can multiply and divide at the same time.
--
[email protected] mailing list
