Date: Sat, 19 Nov 2011 15:48:11 -0500 From: Sahil Tandon <sahil+freebsd-ports@tandon.net> To: Pav Lucistnik <pav@FreeBSD.org> Cc: Wietse Venema <wietse@porcupine.org>, Sahil Tandon <sahil+freebsd-ports@tandon.net>, Renato Botelho <garga@FreeBSD.org>, Jase Thew <freebsd@beardz.net>, Kurt Jaeger <lists@opsec.eu>, freebsd-ports@FreeBSD.org, Chris Rees <utisoft@gmail.com> Subject: Re: "postfix-current" broken on amd64 platform Message-ID: <20111119204811.GA24792@magic.hamla.org> In-Reply-To: <1321728122.46494.0.camel@hood.oook.cz> References: <3SkvVw2ZYzzk2RT@spike.porcupine.org> <1321728122.46494.0.camel@hood.oook.cz>
next in thread | previous in thread | raw e-mail | index | archive | help
--Qxx1br4bt0+wmkIi Content-Type: text/plain; charset=utf-8 Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Sat, 2011-11-19 at 19:42:02 +0100, Pav Lucistnik wrote: > Wietse Venema p=C3=AD=C5=A1e v =C4=8Dt 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. > > > >=20 > > > > 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. > > >=20 > > > This is interesting. > > >=20 > > > The build jails are configured to have only IPv4 address on lo0, > > > but the host have both IPv4 and IPv6 configured on its lo0. > > >=20 > > > 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...) > >=20 > > 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. > >=20 > > A more proactive workaround would be to treat "protocol not supported" > > as a non-fatal error, just like "address family not supported" is. > >=20 > > 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. >=20 > Yes, this works on the build cluster. >=20 > 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). --=20 Sahil Tandon --Qxx1br4bt0+wmkIi Content-Type: application/pgp-signature -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.11 (Darwin) iQEcBAEBAgAGBQJOyBYLAAoJENvQYAHAFtl3pd8IALqdONTiiDWjgY4wfNvT7Hsc jMPB+vm0BTSmIAXThSAwdbs0hX0gNZt+9fFLgC9mLC2lIrvrfAMQE2BUg4zm6FZZ OiQlnn9nXOyE7KeIAEU0pNXRAzO5kRlVLeLb+OmkPD264AYlw8dhYvJBugBJWzPA ZB9P1nmXmxLHFHdBAAfyftyN9phsRRViEWMiOuNtUK3/r0uKovBOw5Ouq2Ql/2uV HoM16MgqSHjQoZzTqWYBipB3EWfo7mroTAkhS2ZsNxQ3Fn6QtnyXmEF+G26qX98o MEAFbRjBz1TSh/HiiRkxfTM3P5PNDo165+CJ+ZBZ8EZsEc03k/w7S/oZLKsW9mM= =+tns -----END PGP SIGNATURE----- --Qxx1br4bt0+wmkIi--
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20111119204811.GA24792>