Your message dated Tue, 10 Dec 2024 20:28:58 +0300
with message-id <26929220-ec34-4c8d-aac6-004219014...@tls.msk.ru>
and subject line Re: Postfix: can't upgrade when in ltsp chroot due to
relayhost==myhostname
has caused the Debian Bug report #758895,
regarding Postfix: can't upgrade when in ltsp chroot due to
relayhost==myhostname
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)
--
758895: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=758895
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: postfix
Version: 2.11.1-1
I run postfix on thin client in a LTSP environment.
I am trying to upgrade from 2.10-2 to 2.11.1-1. However, the upgrade
doesn't work any more, because I have the relayhost set to the hostname of
the LTSP master, and myhostname is not set on the chroot master, but is
set once the clients boot.
I realize that bad things presumably happen if the relayhost is set to the
current hostname, but perhaps it could give a warning, rather than failing
the install at the dpkg level.
I guess the workaround is to change the relayhost to something else, run
the upgrade, and then set it back again, but that is kind of annoying. If
the dpkg code can't be changed, is there anything I can do to get around
this without making config changes on every upgrade?
Thanks.
--
Jon Daley
http://jon.limedaley.com
~~
When a dog bites a man that is not news,
but when a man bites a dog that is news.
-- Charles A. Dana
--- End Message ---
--- Begin Message ---
On Fri, 22 Aug 2014 11:18:40 -0400 (EDT) Jon Daley <deb...@jon.limedaley.com>
wrote:
Package: postfix
Version: 2.11.1-1
I run postfix on thin client in a LTSP environment.
I am trying to upgrade from 2.10-2 to 2.11.1-1. However, the upgrade
doesn't work any more, because I have the relayhost set to the hostname of
the LTSP master, and myhostname is not set on the chroot master, but is
set once the clients boot.
I realize that bad things presumably happen if the relayhost is set to the
current hostname, but perhaps it could give a warning, rather than failing
the install at the dpkg level.
I guess the workaround is to change the relayhost to something else, run
the upgrade, and then set it back again, but that is kind of annoying. If
the dpkg code can't be changed, is there anything I can do to get around
this without making config changes on every upgrade?
It's been quite some time.
What sets the hostname in your ltsp environment? I suggest to order this to
run before postfix is started. Or set myhostname in postfix's main.cf before
it starts.
This is a local configuration error. Postfix expects the system to be in
a configured state before it starts.
Thanks,
/mjt
--- End Message ---
