From: Pandu Poluan <pandu@poluan.info>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] HEADS UP - postfix-2.9.0 is broken
Date: Wed, 8 Feb 2012 09:05:20 +0700 [thread overview]
Message-ID: <CAA2qdGVRNYXCNSSbUOdVKhVWFRRbMe6t=6LZawW1BY6Jt7K_Dw@mail.gmail.com> (raw)
In-Reply-To: <20120207213450.076eb4e9@khamul.example.com>
[-- Attachment #1: Type: text/plain, Size: 2040 bytes --]
On Feb 8, 2012 2:38 AM, "Alan McKinnon" <alan.mckinnon@gmail.com> wrote:
>
> 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.
>
Always do that, actually. But Eray's explanation about postfix's new 'home'
is especially important in the context of this thread and my situation (I'm
using postfix as production email server in my office).
> 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.
>
I recommend also to install an elog parser/viewer. I personally use elogv,
an ncurses-based utility. There are GUI-based ones, but I'm running
text-mode exclusively.
> 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
>
Shouldn't revdep-rebuild be ran *after* emerge --depclean?
Rgds,
[-- Attachment #2: Type: text/html, Size: 2756 bytes --]
next prev parent reply other threads:[~2012-02-08 2:07 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 [this message]
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='CAA2qdGVRNYXCNSSbUOdVKhVWFRRbMe6t=6LZawW1BY6Jt7K_Dw@mail.gmail.com' \
--to=pandu@poluan.info \
--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