From: Paul Hartman <paul.hartman+gentoo@gmail.com>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] HEADS UP - postfix-2.9.0 is broken
Date: Mon, 6 Feb 2012 12:05:38 -0600 [thread overview]
Message-ID: <CAEH5T2MPJDr9dLqN7Fi8BoyasZmT-R1BN6C3KNN-1gP7BFxDRw@mail.gmail.com> (raw)
In-Reply-To: <1436381.LRbWW7PalW@localhost>
On Mon, Feb 6, 2012 at 12:00 PM, Volker Armin Hemmann
<volkerarmin@googlemail.com> wrote:
> Am Montag, 6. Februar 2012, 12:47:45 schrieb Michael Mol:
>> On Mon, Feb 6, 2012 at 12:29 PM, Stefan G. Weichinger <lists@xunil.at>
> wrote:
>> > Am 06.02.2012 18:08, schrieb Volker Armin Hemmann:
>> >> Am Montag, 6. Februar 2012, 12:06:41 schrieb Helmut Jarausch:
>> >>> Hi,
>> >>>
>> >>> beware of installing postfix-2.9.0
>> >>> When started it tries to access /usr/lib/postfix but files have been
>> >>> installed into /usr/libexec/postfix
>> >>
>> >> postfix 2.9.0 works fine for me.
>> >>
>> >> But I also run cfg-update after the update and made sure to merge the ._
>> >> file correctly.
>> >
>> > Yep, same here for postfix 2.9.0-r1 now.
>> >
>> > Had to kill the master-process manually ... this sorted things out in
>> > the end ...
>>
>> So, to avoid this, when upgrading from < 2.9.0-r1 to 2.9.0-r1, one
>> should stop postfix, do the upgrade, and then start postfix again?
>> that's how I read it.
>>
>> Alternately, copy the old init script prior to upgrade, use that
>> script to bring postfix down, and use the new script to bring postfix
>> up?
>
> I just upgraded and did /etc/init.d/postfix restart and it worked.
The installation path was changed without an ebuild version number
bump, so if you installed before that change, it would have had the
same path as the old version.
next prev parent reply other threads:[~2012-02-06 18:08 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 [this message]
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
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=CAEH5T2MPJDr9dLqN7Fi8BoyasZmT-R1BN6C3KNN-1gP7BFxDRw@mail.gmail.com \
--to=paul.hartman+gentoo@gmail.com \
--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