try unmerge 'ssmtp' first, then update world, then emerge ssmtp if necessary.
On Tue, Mar 29, 2011 at 6:16 AM, Peter Humphrey
<pe...@humphrey.ukfsn.org> wrote:
> How do I get out of this?
>
> $ emerge -uptDN world
>
> These are the packages that would be merged, in reverse order:
>
> Calculating dependencies ... done!
> [nomerge ] app-admin/sudo-1.7.4_p5
> [nomerge ] virtual/mta-0
> [ebuild N ] mail-mta/ssmtp-2.62-r8 USE="ipv6 ssl -maxsysuid (-md5sum)"
> [ebuild N ] virtual/mta-0
> [nomerge ] kde-base/kde-meta-4.4.5
> [nomerge ] kde-base/kdemultimedia-meta-4.4.5
> [nomerge ] kde-base/dragonplayer-4.4.5
> [nomerge ] media-libs/xine-lib-1.1.19
> [nomerge ] media-libs/libmng-1.0.10
> [ebuild R ] virtual/jpeg-0 USE="-static-libs%"
> [blocks B ] mail-mta/ssmtp ("virtual/mta" is blocking mail-mta/ssmtp-2.62-
> r8)
>
> * Error: The above package list contains packages which cannot be
> * installed at the same time on the same system.
>
> (virtual/mta-0, ebuild scheduled for merge) pulled in by
> =virtual/mta-0 required by (dev-lang/php-5.3.5, installed)
> virtual/mta required by (app-crypt/gnupg-2.0.17, installed)
> virtual/mta required by (dev-lang/php-5.3.5, installed)
> (and 7 more)
>
> How do I even interpret it? Why is virtual/mta required suddenly? And why does
> ssmtp conflict with it?
>
> --
> Rgds
> Peter
>
>
--
Best Regards,
Xi Shen (David)
http://twitter.com/davidshen84/
