From: Rich Freeman <rich0@gentoo.org>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] Heads up: Gentoo fouls up mail transport agent.
Date: Sun, 22 Jul 2018 08:53:44 -0400 [thread overview]
Message-ID: <CAGfcS_m+hGzMwx7XFO-OoD3nQs5Zzgpnxe1jFrYnaNGHt8hjhQ@mail.gmail.com> (raw)
In-Reply-To: <20180722105703.GB5693@ACM>
On Sun, Jul 22, 2018 at 6:57 AM Alan Mackenzie <acm@muc.de> wrote:
>
> On Sat, Jul 21, 2018 at 18:10:58 -0400, Mike Gilbert wrote:
>
> Apologies to the maintainers and users of nullmailer.
Yeah, there is nothing wrong with nullmailer. It is a minimalist MTA
for systems where you just want to relay mail to another host without
running a full MTA.
> > You must have installed a package that depends on virtual/mta,
> > presumably because it needs to send emails.
>
> The package was gnupg, which surely doesn't need to send email.
>
https://wiki.gnupg.org/WKS
https://bugs.gentoo.org/658164
(The latter ironically has yet another person not using
package.provided - this one should know better... Plus, you really
don't want to have a system without any MTA - in your case you had
installed one outside of portage, but if you don't have any that is
what nullmailer is for.)
>
> Thanks, I didn't know about package.provided. It's not quite ideal, but
> suffices as a workaround. What's suboptimal about it is that you can
> only specify particular versions of packages, not the package as such.
> So, if I put
>
> virtual/mta-1
>
> into my package.provided, I'm going to suffer again in the same way when
> somebody releases virtual/mta-2. As a workaround, my p.p. looks like
> this:
So, two things:
First, it is probably better to put one of the qmail variants in your
package.provided and not virtual/mta-1. I believe that will actually
block stuff that interferes with qmail instead of merely making it
less likely for an MTA to be pulled in.
Nobody should be depending on a specific version of virtual/mta unless
there is something wrong with the packages in the previous versions.
If there is something wrong with those packages, then there is
probably something wrong with your configuration which you would want
to know. Since you've put qmail in your packages.provided you'll
actually get blockers instead of portage just walking over your stuff.
You should also be installing qmail in /usr/local so that you don't
have files getting overwritten by portage. You'll still have the path
concerns but in general you shouldn't be writing to /usr without the
package manager. You get to keep the pieces if it happily overwrites
your stuff from time to time otherwise.
--
Rich
next prev parent reply other threads:[~2018-07-22 12:54 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-07-21 21:03 [gentoo-user] Heads up: Gentoo fouls up mail transport agent Alan Mackenzie
2018-07-21 22:10 ` Mike Gilbert
2018-07-22 5:46 ` François-Xavier CARTON
2018-07-22 10:19 ` Alan Mackenzie
2018-07-22 10:57 ` Alan Mackenzie
2018-07-22 12:53 ` Rich Freeman [this message]
2018-07-22 22:22 ` Walter Dnes
2018-07-22 12:57 ` Mike Gilbert
2018-07-21 22:20 ` Ralph Seichter
2018-07-22 11:06 ` Alan Mackenzie
2018-07-21 23:04 ` [gentoo-user] " Grant Edwards
2018-07-22 2:11 ` Ian Zimmerman
2018-07-22 7:27 ` Kai Peter
2018-07-22 10:24 ` Ralph Seichter
2018-07-23 6:56 ` Kai Peter
2018-07-23 11:22 ` Ralph Seichter
2018-07-22 13:32 ` Nikos Chantziaras
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=CAGfcS_m+hGzMwx7XFO-OoD3nQs5Zzgpnxe1jFrYnaNGHt8hjhQ@mail.gmail.com \
--to=rich0@gentoo.org \
--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