Date: Wed, 16 Nov 2011 11:36:57 -0500 From: Sahil Tandon <sahil@tandon.net> To: Chris Rees <utisoft@gmail.com> Cc: "freebsd-ports@freebsd.org" <freebsd-ports@freebsd.org>, Kurt Jaeger <lists@opsec.eu>, Renato Botelho <garga@freebsd.org>, Wietse Venema <wietse@porcupine.org> Subject: Re: "postfix-current" broken on amd64 platform Message-ID: <837B0CE2-F5DE-4D75-9FAE-044574D00E30@tandon.net> In-Reply-To: <CADLo839cfXjJYNJDGb-FhvXMm6sAaFw6Ukf=3akGhquz_DiRfA@mail.gmail.com> References: <20111116140223.GI68080@home.opsec.eu> <3Sk9KR4s2czk2RT@spike.porcupine.org> <CADLo839cfXjJYNJDGb-FhvXMm6sAaFw6Ukf=3akGhquz_DiRfA@mail.gmail.com>
next in thread | previous in thread | raw e-mail | index | archive | help
On Nov 16, 2011, at 11:24 AM, Chris Rees <utisoft@gmail.com> wrote: > On 16 Nov 2011 16:00, "Wietse Venema" <wietse@porcupine.org> wrote: >>=20 >> Kurt Jaeger: >>> Hi! >>>=20 >>>>>>>> Postconf opens a socket to determine the mynetworks value > (it >>>>>>>> determines the local interfaces and their netmasks). >>> [...] >>>> Postfix does none of that. >>>=20 >>> The fbsd postfix-current port during the post-install script does >>> something which fails on a jail-based build-cluster where the >>> jail itself has no network connectivity. >>=20 >> Would it be possible to give the jail a loopback interface? >>=20 >> I don't mind if FreeBSD improves its build environment such that >> it breaks the build after 12 years. If adding a loopback interface >> fixes this, then we can all move on to more interesting things. >>=20 >> Wietse >>=20 >=20 > Clamav uses loopback on its testing phase, and works fine on the build > cluster. What irks me is that all other Postfix versions (that also call postconf) ha= ve no problem building/installing on the cluster.=
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?837B0CE2-F5DE-4D75-9FAE-044574D00E30>