public inbox for gentoo-user@lists.gentoo.org
 help / color / mirror / Atom feed
From: "Bo Ørsted Andresen" <bo.andresen@zlin.dk>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] FW: mail-mta/exim (is blocking mail-mta/ssmtp-2.61-r2) (more info added)
Date: Tue, 29 May 2007 13:51:12 +0200	[thread overview]
Message-ID: <200705291351.18209.bo.andresen@zlin.dk> (raw)
In-Reply-To: <061c01c7a1cb$f365b330$450a0a0a@locutus>

[-- Attachment #1: Type: text/plain, Size: 1991 bytes --]

On Tuesday 29 May 2007 10:32:23 Daevid Vincent wrote:
> *  mail-mta/exim
>       Latest version available: 4.67
>       Latest version installed: 4.54
>       Size of downloaded files: [no/bad digest]
>       Homepage:    http://www.exim.org/
>
> So I have this in my package.mask:
> >=mail-mta/exim-4.55
[SNIP]
> [nomerge      ] sys-process/vixie-cron-4.1-r10 [4.1-r9]
> [ebuild  N    ]  mail-mta/ssmtp-2.61-r2  USE="ipv6 ssl -mailwrapper
[SNIP]
> [blocks B     ] mail-mta/exim (is blocking mail-mta/ssmtp-2.61-r2)
>
> (also, I never understand the --tree option. Does this mean that
> "vixie-cron" is the issue, or "kdegraphics" is the issue? Being reverse
> order, I am guessing vixie-cron, yet it says "nomerge" so that seems
> like, why would it care, plus it's worked fine all these years with the
> exim I have installed.

vixie-cron has a run-time dependency on virtual/mta which can be satisfied by 
both exim and ssmtp (and 8 other packages in the tree). ssmtp is the default 
provider.

What has happened is that all versions of exim in the tree that you haven't 
masked have been removed from the tree. I.e. there are no versions in the 
tree below 4.55. Therefore it suggests installing the default provider of 
virtual/mta which is blocked by the version of exim which is still installed 
although not installable (not in the tree). It matters despite the "nomerge" 
because it's a run-time dependency rather than build-time.

You have at least four options. The first option is to upgrade exim and hope 
it'll work. I have no knowledge about exim so I cannot tell you whether it 
will. The second is to restore the ebuild for your installed version in an 
overlay (you can pull it from /var/db/pkg/mail-mta/exim-4.54/) thereby 
restoring a non-masked version of exim.. The third is to add mail-mta/exim to 
package.provided (see `man portage`). The fourth is to unmerge exim and use 
another mta (I'm using postfix).

-- 
Bo Andresen

[-- Attachment #2: This is a digitally signed message part. --]
[-- Type: application/pgp-signature, Size: 189 bytes --]

  parent reply	other threads:[~2007-05-29 11:58 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-05-29  8:32 [gentoo-user] FW: mail-mta/exim (is blocking mail-mta/ssmtp-2.61-r2) (more info added) Daevid Vincent
2007-05-29 11:46 ` Alan McKinnon
2007-05-29 11:51 ` Bo Ørsted Andresen [this message]
2007-05-30  3:39   ` Boyd Stephen Smith Jr.
2007-05-30 12:20     ` Bo Ørsted Andresen
2007-05-31  2:09       ` Boyd Stephen Smith Jr.
2007-05-31  2:20         ` Bo Ørsted Andresen
2007-05-31  2:37           ` Boyd Stephen Smith Jr.
2007-05-31  3:03             ` Bo Ørsted Andresen
2007-05-31  2:57           ` Paul Varner
2007-05-31  3:09             ` Bo Ørsted Andresen
2007-05-31 18:49               ` Paul Varner

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=200705291351.18209.bo.andresen@zlin.dk \
    --to=bo.andresen@zlin.dk \
    --cc=gentoo-user@lists.gentoo.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox