From: Tanstaafl <tanstaafl@libertytrek.org>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] HEADS UP - postfix-2.9.0 is broken
Date: Tue, 07 Feb 2012 12:37:12 -0500 [thread overview]
Message-ID: <4F316148.3030605@libertytrek.org> (raw)
In-Reply-To: <20120207073612.GA3138@zptr-nb18.caf.local>
On 2012-02-07 2:36 AM, Eray Aslan <eras@gentoo.org> wrote:
> On Tue, Feb 07, 2012 at 01:58:33PM +0700, Pandu Poluan wrote:
>> Soooo... I'm still on 2.8.7. Is it safe to upgrade to 2.9.0-r1 ?
> Yes, it should be OK as long as you run
> etc-update/dispatch-conf/similar after the upgrade.
I was concerned about this at first, but if this was indeed the cause of
the OP and others' problem (as opposed to an actual bug in the ebuild),
then they did it to themselves, because what you said - running
etc-update (or dispatch-conf) is *always* required for packages like
postfix.
next prev parent reply other threads:[~2012-02-07 17:38 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-02-06 11:06 [gentoo-user] HEADS UP - postfix-2.9.0 is broken Helmut Jarausch
2012-02-06 11:23 ` Hinnerk van Bruinehsen
2012-02-06 13:07 ` [gentoo-user] " Holger Hoffstaette
2012-02-06 15:42 ` [gentoo-user] " Paul Hartman
2012-02-06 16:34 ` Stefan G. Weichinger
2012-02-06 17:51 ` Andrea Conti
2012-02-07 7:38 ` Eray Aslan
2012-02-06 17:08 ` Volker Armin Hemmann
2012-02-06 17:29 ` Stefan G. Weichinger
2012-02-06 17:47 ` Michael Mol
2012-02-06 18:00 ` Volker Armin Hemmann
2012-02-06 18:04 ` Michael Mol
2012-02-06 18:05 ` Paul Hartman
2012-02-06 18:31 ` Volker Armin Hemmann
2012-02-07 6:58 ` Pandu Poluan
2012-02-07 7:36 ` Eray Aslan
2012-02-07 17:11 ` Pandu Poluan
2012-02-07 19:34 ` Alan McKinnon
2012-02-08 2:05 ` Pandu Poluan
2012-02-08 10:04 ` Alan McKinnon
2012-02-07 17:37 ` Tanstaafl [this message]
2012-02-07 17:38 ` Tanstaafl
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=4F316148.3030605@libertytrek.org \
--to=tanstaafl@libertytrek.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