1 |
On Wed, 8 Feb 2012 00:11:26 +0700 |
2 |
Pandu Poluan <pandu@××××××.info> wrote: |
3 |
|
4 |
> On Feb 7, 2012 2:39 PM, "Eray Aslan" <eras@g.o> wrote: |
5 |
> > |
6 |
> > On Tue, Feb 07, 2012 at 01:58:33PM +0700, Pandu Poluan wrote: |
7 |
> > > Soooo... I'm still on 2.8.7. Is it safe to upgrade to 2.9.0-r1 ? |
8 |
> > |
9 |
> > Yes, it should be OK as long as you run |
10 |
> > etc-update/dispatch-conf/similar after the upgrade. Postfix |
11 |
> > daemons now live under /usr/libexec/postfix (not |
12 |
> > under /usr/lib{,64)/postfix). Adjust your main.cf accordingly. |
13 |
> > I'll add a warning to the ebuild. |
14 |
> > |
15 |
> |
16 |
> Ah, thanks for the explanation! |
17 |
> |
18 |
> I'll be certain to pay undivided attention to postfix ebuild warnings. |
19 |
> |
20 |
> Rgds, |
21 |
|
22 |
ALWAYS pay special attention to ALL ebuild warnings. Not just the ones |
23 |
from postfix. |
24 |
|
25 |
Those warnings are there for a reason - it's how devs let you know that |
26 |
stuff has changed, that the change will make stuff break, and how to |
27 |
fix or prevent it. They are not there for decoration or fluff. |
28 |
|
29 |
You should set the ELOG options in make.conf to store these warnings in |
30 |
some persistent place (log files, mail them, whatever) so you can go |
31 |
through them at your leisure. |
32 |
|
33 |
My usual routine for doing a global update is |
34 |
|
35 |
emerge -avuND world |
36 |
conf-update |
37 |
emerge -av @preserved-rebuild |
38 |
revdep-rebuild -p -i (then without -p if something is found) |
39 |
emerge -a --depclean |
40 |
view portage logs and do what they say |
41 |
often followed by doing one or more steps again to ensure all is clean |
42 |
|
43 |
I haven't been adversely hit by an upgrade for over a year now. I put |
44 |
it down to using the portage tools correctly in the way they were |
45 |
designed to be used. |
46 |
|
47 |
-- |
48 |
Alan McKinnnon |
49 |
alan.mckinnon@×××××.com |