On Sat, 2011-11-19 at 19:42:02 +0100, Pav Lucistnik wrote: > Wietse Venema píše v čt 17. 11. 2011 v 15:41 -0500: > > Pav Lucistnik: > > > Wietse Venema p??e v ?t 17. 11. 2011 v 13:23 -0500: > > > > Actually, a Postfix built-in default setting changed on 20110918. > > > > > > > > It now enables IPv6 unless this is turned off in a configuration > > > > file. I can fix that at compile time, and thereby not trigger > > > > the error on build systems with unexpected IPv6 configurations. > > > > > > This is interesting. > > > > > > The build jails are configured to have only IPv4 address on lo0, > > > but the host have both IPv4 and IPv6 configured on its lo0. > > > > > > Changing the jail configuration is possible but if a reasonable > > > workaround can be made in postfix-current port I'd prefer not to touch > > > pointyhat configuration (unexpected consequences and all that...) > > > > I can competely fix this specific error instance with a one-line > > config file change, but I don't want to end up in the same boat > > again when some other program needs to be run during build time. > > > > A more proactive workaround would be to treat "protocol not supported" > > as a non-fatal error, just like "address family not supported" is. > > > > Please let me know if this works in the build cluster. It will log > > a warning but that should be justfied, because the system does have > > an abnormal configuration. > > Yes, this works on the build cluster. > > Sahil, can I commit it to the port?
Wietse has made the change upstream and I plan to commit that in a little bit. Just running it through my tinderbox if folks don't mind the wait (a few hours). -- Sahil Tandon
pgprZl2FD4UW3.pgp
Description: PGP signature
