On Tue, Nov 2, 2010 at 1:31 PM, Wietse Venema <wie...@porcupine.org> wrote:

> Linux Addict:
> > >> > If the package is not well constructed:
> > >> >
> > >> >       Read the RELEASE_NOTES file for 2.6 and 2.7, then:
> > >> >
> > >> >       # postfix stop
> > >> >
> > >> >       # mkdir -p /etc/postfix/cfsavedir
> > >> >       # cp /etc/postfix/main.cf /etc/postfix/master.cf \
> > >> >               /etc/postfix/cfsavedir/
> > >> >
> > >> >       # some-command-to-install-updated-poorly-constructed-package
> > >> >
> > >> >       # cp /etc/postfix/cfsavedir/main.cf /etc/postfix/cfsavedir/
> > >> master.cf \
> > >> >               /etc/postfix/
> > >> >       # postfix set-permissions upgrade-configuration
> > >> >
> > >> >       # postfix start
> > >> >
> > >> > A package is not well contstructed if it fails to preserve and
> upgrade
> > >> > your existing main.cf and master.cf files.
> > >> >
> > >>
> > >>
> > > Thanks Victor. Reading from 2.6 releasing notes, it looks like postfix
> > > changed how multiple instances are handled. I am going to test on
> sandbox.
> >
> > Sorry about beating the dead horse, but just came to know that there are
> few
> > 2.2 postfix instances which needs to upgraded to 2.7  as well. Does
> upgrade
> > stands true for 2.2 to 2.7 or install a clean 2.7 and just port the
> postconf
> > -n will suffice?
>
> No. The config files need to be upgraded, not overwritten.
>
> If you install clean 2.7, then follow instructions above as with
> "not well constructed package", i.e. save the config files, install
> Postfix, restore the config files and do "postfix set-permissions
> upgrade-configuration".
>
>        Wietse
>


Awsome, thank you. Testing the upgrade from 2.2 to 2.7.

Reply via email to