From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from pigeon.gentoo.org ([208.92.234.80] helo=lists.gentoo.org) by finch.gentoo.org with esmtp (Exim 4.60) (envelope-from ) id 1Ruwwr-0004Ho-44 for garchives@archives.gentoo.org; Wed, 08 Feb 2012 02:07:53 +0000 Received: from pigeon.gentoo.org (localhost [127.0.0.1]) by pigeon.gentoo.org (Postfix) with SMTP id 8B183E0839; Wed, 8 Feb 2012 02:07:39 +0000 (UTC) Received: from svr-us4.tirtonadi.com (svr-us4.tirtonadi.com [69.65.43.212]) by pigeon.gentoo.org (Postfix) with ESMTP id B63EEE081B for ; Wed, 8 Feb 2012 02:05:25 +0000 (UTC) Received: from mail-wi0-f181.google.com ([209.85.212.181]) by svr-us4.tirtonadi.com with esmtpsa (TLSv1:RC4-SHA:128) (Exim 4.69) (envelope-from ) id 1RuwuS-001H3S-TT for gentoo-user@lists.gentoo.org; Wed, 08 Feb 2012 09:05:25 +0700 Received: by wibhi8 with SMTP id hi8so41390wib.40 for ; Tue, 07 Feb 2012 18:05:21 -0800 (PST) Precedence: bulk List-Post: List-Help: List-Unsubscribe: List-Subscribe: List-Id: Gentoo Linux mail X-BeenThere: gentoo-user@lists.gentoo.org Reply-to: gentoo-user@lists.gentoo.org MIME-Version: 1.0 Received: by 10.180.92.73 with SMTP id ck9mr37958573wib.2.1328666721241; Tue, 07 Feb 2012 18:05:21 -0800 (PST) Received: by 10.223.103.4 with HTTP; Tue, 7 Feb 2012 18:05:20 -0800 (PST) Received: by 10.223.103.4 with HTTP; Tue, 7 Feb 2012 18:05:20 -0800 (PST) In-Reply-To: <20120207213450.076eb4e9@khamul.example.com> References: <1328526401.3021.0@numa-i> <4F300E14.4080108@xunil.at> <1436381.LRbWW7PalW@localhost> <20120207073612.GA3138@zptr-nb18.caf.local> <20120207213450.076eb4e9@khamul.example.com> Date: Wed, 8 Feb 2012 09:05:20 +0700 Message-ID: Subject: Re: [gentoo-user] HEADS UP - postfix-2.9.0 is broken From: Pandu Poluan To: gentoo-user@lists.gentoo.org Content-Type: multipart/alternative; boundary=f46d043892c5f1c98504b86a5311 X-AntiAbuse: This header was added to track abuse, please include it with any abuse report X-AntiAbuse: Primary Hostname - svr-us4.tirtonadi.com X-AntiAbuse: Original Domain - lists.gentoo.org X-AntiAbuse: Originator/Caller UID/GID - [47 12] / [47 12] X-AntiAbuse: Sender Address Domain - poluan.info X-Archives-Salt: d37ad7d1-4fe8-482d-8e97-5bbe0199d2c0 X-Archives-Hash: d4f3114c2fed8e639fc51f17a527de74 --f46d043892c5f1c98504b86a5311 Content-Type: text/plain; charset=UTF-8 On Feb 8, 2012 2:38 AM, "Alan McKinnon" wrote: > > On Wed, 8 Feb 2012 00:11:26 +0700 > Pandu Poluan wrote: > > > On Feb 7, 2012 2:39 PM, "Eray Aslan" 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, --f46d043892c5f1c98504b86a5311 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable


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.inf= o> 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. =C2=A0Po= stfix
> > > daemons now live under /usr/libexec/postfix (not
> > > under /usr/lib{,64)/postfix). =C2=A0Adjust 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 a= nd my situation (I'm using postfix as production email server in my off= ice).

> Those warnings are there for a reason - it's how devs let you k= now 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 i= n
> 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 elog= v, 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,

--f46d043892c5f1c98504b86a5311--