From: Alan McKinnon <alan.mckinnon@gmail.com>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] HEADS UP - postfix-2.9.0 is broken
Date: Tue, 7 Feb 2012 21:34:50 +0200 [thread overview]
Message-ID: <20120207213450.076eb4e9@khamul.example.com> (raw)
In-Reply-To: <CAA2qdGVPCeco08RA48_DzfpGdnm29PZ6wAj-OQ0nQjN7gcw8zw@mail.gmail.com>
On Wed, 8 Feb 2012 00:11:26 +0700
Pandu Poluan <pandu@poluan.info> wrote:
> On Feb 7, 2012 2:39 PM, "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. Postfix
> > daemons now live under /usr/libexec/postfix (not
> > under /usr/lib{,64)/postfix). Adjust your main.cf accordingly.
> > I'll add a warning to the ebuild.
> >
>
> Ah, thanks for the explanation!
>
> I'll be certain to pay undivided attention to postfix ebuild warnings.
>
> Rgds,
ALWAYS pay special attention to ALL ebuild warnings. Not just the ones
from postfix.
Those warnings are there for a reason - it's how devs let you know that
stuff has changed, that the change will make stuff break, and how to
fix or prevent it. They are not there for decoration or fluff.
You should set the ELOG options in make.conf to store these warnings in
some persistent place (log files, mail them, whatever) so you can go
through them at your leisure.
My usual routine for doing a global update is
emerge -avuND world
conf-update
emerge -av @preserved-rebuild
revdep-rebuild -p -i (then without -p if something is found)
emerge -a --depclean
view portage logs and do what they say
often followed by doing one or more steps again to ensure all is clean
I haven't been adversely hit by an upgrade for over a year now. I put
it down to using the portage tools correctly in the way they were
designed to be used.
--
Alan McKinnnon
alan.mckinnon@gmail.com
next prev parent reply other threads:[~2012-02-07 19:36 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 [this message]
2012-02-08 2:05 ` Pandu Poluan
2012-02-08 10:04 ` Alan McKinnon
2012-02-07 17:37 ` Tanstaafl
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=20120207213450.076eb4e9@khamul.example.com \
--to=alan.mckinnon@gmail.com \
--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