Sahil Tandon:
> I do not usually announce FreeBSD port version bumps here, but in this
> case, I felt it appropriate. Sorry to those for whom this is not
> relevant.
>
> I have updated the development port to Postfix 2.9 Snapshot 20120102 and
> removed the erroneous conf/post-install patch that w
On Tue, 3 Jan 2012 21:12:29 -0500
Sahil Tandon articulated:
> I do not usually announce FreeBSD port version bumps here, but in this
> case, I felt it appropriate. Sorry to those for whom this is not
> relevant.
>
> I have updated the development port to Postfix 2.9 Snapshot 20120102
> and remov
I do not usually announce FreeBSD port version bumps here, but in this
case, I felt it appropriate. Sorry to those for whom this is not
relevant.
I have updated the development port to Postfix 2.9 Snapshot 20120102 and
removed the erroneous conf/post-install patch that was discussed earlier
in th
Mark Martinec:
> Sahil Tandon wrote:
> > I do not believe Mark should have to jump through extra hoops, or that
> > you should revert the change. This is a FreeBSD port-specific problem
> > created by me that I will address as soon as I can.
>
> Wietse Venema wrote:
> > Considering the short
Sahil Tandon wrote:
> I do not believe Mark should have to jump through extra hoops, or that
> you should revert the change. This is a FreeBSD port-specific problem
> created by me that I will address as soon as I can.
Wietse Venema wrote:
> Considering the short time left before the next stable
On Wed, 2011-12-28 at 19:48:48 -0500, Wietse Venema wrote:
> Sahil Tandon:
> > I do not believe Mark should have to jump through extra hoops, or that
> > you should revert the change. This is a FreeBSD port-specific problem
> > created by me that I will address as soon as I can.
>
> Considering
Sahil Tandon:
> I do not believe Mark should have to jump through extra hoops, or that
> you should revert the change. This is a FreeBSD port-specific problem
> created by me that I will address as soon as I can.
Considering the short time left before the next stable release I
am considering the
On Wed, 2011-12-28 at 18:34:45 -0500, Wietse Venema wrote:
> ...
> Sites that use Postfix 2.8 without IPv6 have no inet_protocols
> setting in main.cf. They have never needed one because that was the
> default. Having to add "inet_protocols = whatever" for Postfix
> 2.9 is an unnecessary compatib
Sahil Tandon:
> > Sahil Tandon:
> > > FWIW, the FreeBSD Postfix port is patched so that post-install does not
> > > add "inet_protocols=ipv4" to main.cf during upgrades. Instead, users are
> > > notified[1] about the recent change of defaults, and asked to append the
> > > ipv4 line to their main.c
Am 29.12.2011 00:16, schrieb Jeroen Geilman:
> On 2011-12-28 23:58, Reindl Harald wrote:
>>
>> Am 28.12.2011 23:30, schrieb Stan Hoeppner:
>>> On 12/28/2011 2:41 PM, Reindl Harald wrote:
this world would be a better one if more developers would have your
attitude instead permanently thr
On 2011-12-28 23:58, Reindl Harald wrote:
Am 28.12.2011 23:30, schrieb Stan Hoeppner:
On 12/28/2011 2:41 PM, Reindl Harald wrote:
this world would be a better one if more developers would have your
attitude instead permanently throwing things away and replace them
with half-baken replacement a
Am 28.12.2011 23:30, schrieb Stan Hoeppner:
> On 12/28/2011 2:41 PM, Reindl Harald wrote:
>> this world would be a better one if more developers would have your
>> attitude instead permanently throwing things away and replace them
>> with half-baken replacement and shortly before they become bugf
On Wed, 2011-12-28 at 10:08:05 -0500, Wietse Venema wrote:
> Sahil Tandon:
> > FWIW, the FreeBSD Postfix port is patched so that post-install does not
> > add "inet_protocols=ipv4" to main.cf during upgrades. Instead, users are
> > notified[1] about the recent change of defaults, and asked to appe
On 12/28/2011 2:41 PM, Reindl Harald wrote:
>
>
> Am 28.12.2011 21:12, schrieb Wietse Venema:
>> Jerry:
>> [request to preserve a backwards-compatibility migration feature]
Wietse
>>>
>>> +1
>>
>> FWIW, I get no joy from making requests like this. It just annoys
>> me that Sahil, who is o
Am 28.12.2011 21:12, schrieb Wietse Venema:
> Jerry:
> [request to preserve a backwards-compatibility migration feature]
>>> Wietse
>>
>> +1
>
> FWIW, I get no joy from making requests like this. It just annoys
> me that Sahil, who is otherwise a sensible maintainer, works against
> my effor
Jerry:
[request to preserve a backwards-compatibility migration feature]
> > Wietse
>
> +1
FWIW, I get no joy from making requests like this. It just annoys
me that Sahil, who is otherwise a sensible maintainer, works against
my efforts to make Postfix upgrades as painless as possible.
When
On Wed, 28 Dec 2011 10:08:05 -0500 (EST)
Wietse Venema articulated:
> Sahil Tandon:
> > FWIW, the FreeBSD Postfix port is patched so that post-install does
> > not add "inet_protocols=ipv4" to main.cf during upgrades. Instead,
> > users are notified[1] about the recent change of defaults, and
> >
Sahil Tandon:
> FWIW, the FreeBSD Postfix port is patched so that post-install does not
> add "inet_protocols=ipv4" to main.cf during upgrades. Instead, users are
> notified[1] about the recent change of defaults, and asked to append the
> ipv4 line to their main.cf, if necessary.
Sorry, THAT IS
Wietse Venema:
> After I made "inet_protocols=all" the default on your request, I
> received notice that Postfix no longer would build on freebsd.org
> "build" systems, and that it would be removed from ports. These
> build environments have IPv6 in the kernel but they have no IPv6
> interfaces. B
On Tue, 2011-12-27 at 17:24:57 -0500, Wietse Venema wrote:
> ...
> After I made "inet_protocols=all" the default on your request, I
> received notice that Postfix no longer would build on freebsd.org
> "build" systems, and that it would be removed from ports. These
> build environments have IPv6
Wietse Venema:
> Wietse Venema:
> > Mark Martinec:
> > > Trying to install postfix-2.9-20111219 from ports on FreeBSD 9.0
> > > (with an inet6-only kernel), the installation fails as before:
> > >
> > > postfix-current$ make install
> > > ...
> > > Skipping /usr/local/share/doc/postfix/postfix-pow
Mark Martinec:
> > I'm assuming that you have "inet_protocols=ipv6" in main.cf, instead
> > of the backwards-compatibility "inet_protocols=ipv4" workaround,
> > because that would not work on your machine.
>
> No, that was a fresh install attempt, no directory /etc/postfix
> or /usr/local/etc/post
> I'm assuming that you have "inet_protocols=ipv6" in main.cf, instead
> of the backwards-compatibility "inet_protocols=ipv4" workaround,
> because that would not work on your machine.
No, that was a fresh install attempt, no directory /etc/postfix
or /usr/local/etc/postfix, no previous main.cf or
> > postfix: fatal: could not find any active network interfaces
> > *** Error code 1
>
> How do you want to proceed: wait until I have time to reproduce
> your IPv6-only setup for which I have no specification, or spend
> all of next year doing blind testing?
No offense and not intending to rush
Wietse Venema:
> Mark Martinec:
> > Trying to install postfix-2.9-20111219 from ports on FreeBSD 9.0
> > (with an inet6-only kernel), the installation fails as before:
> >
> > postfix-current$ make install
> > ...
> > Skipping /usr/local/share/doc/postfix/postfix-power.png...
> > Skipping /usr/loc
Mark Martinec:
> Trying to install postfix-2.9-20111219 from ports on FreeBSD 9.0
> (with an inet6-only kernel), the installation fails as before:
>
> postfix-current$ make install
> ...
> Skipping /usr/local/share/doc/postfix/postfix-power.png...
> Skipping /usr/local/share/doc/postfix/scache.8.h
Reviving an old thread from 2011-09:
Mark Martinec:
> Trying to install postfix on an IPv6-only host
> FreeBSD 9.0B1, http://wiki.freebsd.org/IPv6Only
> ports: mail/postfix-current,
> but the installation chokes in the post-install phase.
> Running that failing command manually (in the ports w
Mark Martinec:
> Well, I followed Wietse's suggestion:
>
> | A workaround is to do the same thing as when local_recipient_maps
> | was introduced: the inet_protocols built-in default different from
> | the installed configuration.
> |
> | In this case, the built-in default would enable IPv6, while
> On Aug 23, 12:30 pm, Mark Martinec wrote:
> > Trying to install postfix on an IPv6-only host
> > FreeBSD 9.0B1,http://wiki.freebsd.org/IPv6Only
> > ports: mail/postfix-current,
> > but the installation chokes in the post-install phase.
> > Running that failing command manually (in the ports w
Mark Martinec:
> Trying to install postfix on an IPv6-only host
>
> FreeBSD 9.0B1, http://wiki.freebsd.org/IPv6Only
> ports: mail/postfix-current,
>
> but the installation chokes in the post-install phase.
>
> Running that failing command manually (in the ports work directory)
> gives:
>
>
Trying to install postfix on an IPv6-only host
FreeBSD 9.0B1, http://wiki.freebsd.org/IPv6Only
ports: mail/postfix-current,
but the installation chokes in the post-install phase.
Running that failing command manually (in the ports work directory)
gives:
# bin/postfix -v post-install
postfix
31 matches
Mail list logo
