Date: Sat, 19 Nov 2011 19:42:02 +0100 From: Pav Lucistnik <pav@FreeBSD.org> To: Wietse Venema <wietse@porcupine.org> Cc: 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: <1321728122.46494.0.camel@hood.oook.cz> In-Reply-To: <3SkvVw2ZYzzk2RT@spike.porcupine.org> References: <3SkvVw2ZYzzk2RT@spike.porcupine.org>
next in thread | previous in thread | raw e-mail | index | archive | help
--=-vRdVSo67+iaC6XOYw+5A
Content-Type: text/plain; charset="ISO-8859-2"
Content-Transfer-Encoding: quoted-printable
Wietse Venema p=ED=B9e v =E8t 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.
Yes, this works on the build cluster.
Sahil, can I commit it to the port?
> Wietse
>=20
> *** src/util/inet_proto.c- Tue Jan 8 15:36:13 2008
> --- src/util/inet_proto.c Thu Nov 17 08:49:31 2011
> ***************
> *** 219,225 ****
> pf->dns_atype_list =3D make_unsigned_vector(3, T_A, T_AAAA, 0);
> pf->sa_family_list =3D make_uchar_vector(3, AF_INET, AF_INET6, 0);
> break;
> ! } else if (errno =3D=3D EAFNOSUPPORT) {
> msg_warn("%s: IPv6 support is disabled: %m", context);
> msg_warn("%s: configuring for IPv4 support only", context);
> /* FALLTHROUGH */
> --- 219,225 ----
> pf->dns_atype_list =3D make_unsigned_vector(3, T_A, T_AAAA, 0);
> pf->sa_family_list =3D make_uchar_vector(3, AF_INET, AF_INET6, 0);
> break;
> ! } else if (errno =3D=3D EAFNOSUPPORT || errno =3D=3D EPROTONOSUPPORT) =
{
> msg_warn("%s: IPv6 support is disabled: %m", context);
> msg_warn("%s: configuring for IPv4 support only", context);
> /* FALLTHROUGH */
--=20
--=20
Pav Lucistnik <pav@oook.cz>
<pav@FreeBSD.org>
Why does the Earth have colors?
--=-vRdVSo67+iaC6XOYw+5A
Content-Type: application/pgp-signature; name="signature.asc"
Content-Description: This is a digitally signed message part
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.11 (FreeBSD)
iEYEABECAAYFAk7H+GcACgkQntdYP8FOsoIo8gCfdMSyNbMTwt+VsPwOo/DAO8QY
+yMAniB3ZPZPzuPivrqF0EvKHZ7wgfnh
=2WKD
-----END PGP SIGNATURE-----
--=-vRdVSo67+iaC6XOYw+5A--
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?1321728122.46494.0.camel>