| 1 |
On Feb 8, 2012 2:38 AM, "Alan McKinnon" <alan.mckinnon@×××××.com> wrote: |
| 2 |
> |
| 3 |
> On Wed, 8 Feb 2012 00:11:26 +0700 |
| 4 |
> Pandu Poluan <pandu@××××××.info> wrote: |
| 5 |
> |
| 6 |
> > On Feb 7, 2012 2:39 PM, "Eray Aslan" <eras@g.o> wrote: |
| 7 |
> > > |
| 8 |
> > > On Tue, Feb 07, 2012 at 01:58:33PM +0700, Pandu Poluan wrote: |
| 9 |
> > > > Soooo... I'm still on 2.8.7. Is it safe to upgrade to 2.9.0-r1 ? |
| 10 |
> > > |
| 11 |
> > > Yes, it should be OK as long as you run |
| 12 |
> > > etc-update/dispatch-conf/similar after the upgrade. Postfix |
| 13 |
> > > daemons now live under /usr/libexec/postfix (not |
| 14 |
> > > under /usr/lib{,64)/postfix). Adjust your main.cf accordingly. |
| 15 |
> > > I'll add a warning to the ebuild. |
| 16 |
> > > |
| 17 |
> > |
| 18 |
> > Ah, thanks for the explanation! |
| 19 |
> > |
| 20 |
> > I'll be certain to pay undivided attention to postfix ebuild warnings. |
| 21 |
> > |
| 22 |
> > Rgds, |
| 23 |
> |
| 24 |
> ALWAYS pay special attention to ALL ebuild warnings. Not just the ones |
| 25 |
> from postfix. |
| 26 |
> |
| 27 |
|
| 28 |
Always do that, actually. But Eray's explanation about postfix's new 'home' |
| 29 |
is especially important in the context of this thread and my situation (I'm |
| 30 |
using postfix as production email server in my office). |
| 31 |
|
| 32 |
> Those warnings are there for a reason - it's how devs let you know that |
| 33 |
> stuff has changed, that the change will make stuff break, and how to |
| 34 |
> fix or prevent it. They are not there for decoration or fluff. |
| 35 |
> |
| 36 |
> You should set the ELOG options in make.conf to store these warnings in |
| 37 |
> some persistent place (log files, mail them, whatever) so you can go |
| 38 |
> through them at your leisure. |
| 39 |
> |
| 40 |
|
| 41 |
I recommend also to install an elog parser/viewer. I personally use elogv, |
| 42 |
an ncurses-based utility. There are GUI-based ones, but I'm running |
| 43 |
text-mode exclusively. |
| 44 |
|
| 45 |
> My usual routine for doing a global update is |
| 46 |
> |
| 47 |
> emerge -avuND world |
| 48 |
> conf-update |
| 49 |
> emerge -av @preserved-rebuild |
| 50 |
> revdep-rebuild -p -i (then without -p if something is found) |
| 51 |
> emerge -a --depclean |
| 52 |
> view portage logs and do what they say |
| 53 |
> often followed by doing one or more steps again to ensure all is clean |
| 54 |
> |
| 55 |
|
| 56 |
Shouldn't revdep-rebuild be ran *after* emerge --depclean? |
| 57 |
|
| 58 |
Rgds, |
Archives