From owner-freebsd-ports@FreeBSD.ORG  Wed Nov 16 16:24:25 2011
Return-Path: <owner-freebsd-ports@FreeBSD.ORG>
Delivered-To: freebsd-ports@freebsd.org
Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34])
	by hub.freebsd.org (Postfix) with ESMTP id 685A01065678;
	Wed, 16 Nov 2011 16:24:25 +0000 (UTC)
	(envelope-from utisoft@gmail.com)
Received: from mail-gx0-f182.google.com (mail-gx0-f182.google.com
	[209.85.161.182])
	by mx1.freebsd.org (Postfix) with ESMTP id CD36C8FC0C;
	Wed, 16 Nov 2011 16:24:24 +0000 (UTC)
Received: by ggnk3 with SMTP id k3so12860782ggn.13
	for <multiple recipients>; Wed, 16 Nov 2011 08:24:24 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma;
	h=mime-version:in-reply-to:references:date:message-id:subject:from:to
	:cc:content-type;
	bh=h0JY8tRIR6NHtFz3zekfr8VmZcS21B5fquvz6fesgFM=;
	b=FSK75dbYj3/DbtC98h4+BTx6WKt1KPPHjDd2U74iwEBcbIc2aFALiusfK2RD9p04SN
	nqLiIR7bXIvHxEhOmKpGW/zcqMED6vvBXe7HV4TobIBPMJz1IBFVUKzt1Nb5oG+Vf4TG
	hDZ38czg8LkK2gwqGA/z9KkRdlmQULZ/HSmns=
MIME-Version: 1.0
Received: by 10.50.104.137 with SMTP id ge9mr32940479igb.38.1321460663622;
	Wed, 16 Nov 2011 08:24:23 -0800 (PST)
Received: by 10.231.11.140 with HTTP; Wed, 16 Nov 2011 08:24:23 -0800 (PST)
Received: by 10.231.11.140 with HTTP; Wed, 16 Nov 2011 08:24:23 -0800 (PST)
In-Reply-To: <3Sk9KR4s2czk2RT@spike.porcupine.org>
References: <20111116140223.GI68080@home.opsec.eu>
	<3Sk9KR4s2czk2RT@spike.porcupine.org>
Date: Wed, 16 Nov 2011 16:24:23 +0000
Message-ID: <CADLo839cfXjJYNJDGb-FhvXMm6sAaFw6Ukf=3akGhquz_DiRfA@mail.gmail.com>
From: Chris Rees <utisoft@gmail.com>
To: Wietse Venema <wietse@porcupine.org>
Content-Type: text/plain; charset=ISO-8859-1
X-Content-Filtered-By: Mailman/MimeDel 2.1.5
Cc: Kurt Jaeger <lists@opsec.eu>, Renato Botelho <garga@freebsd.org>,
	freebsd-ports@freebsd.org
Subject: Re: "postfix-current" broken on amd64 platform
X-BeenThere: freebsd-ports@freebsd.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Porting software to FreeBSD <freebsd-ports.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-ports>,
	<mailto:freebsd-ports-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-ports>
List-Post: <mailto:freebsd-ports@freebsd.org>
List-Help: <mailto:freebsd-ports-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-ports>,
	<mailto:freebsd-ports-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Wed, 16 Nov 2011 16:24:25 -0000

On 16 Nov 2011 16:00, "Wietse Venema" <wietse@porcupine.org> wrote:
>
> Kurt Jaeger:
> > Hi!
> >
> > > > > > >   Postconf opens a socket to determine the mynetworks value
(it
> > > > > > >   determines the local interfaces and their netmasks).
> > [...]
> > > Postfix does none of that.
> >
> > 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.
>
> Would it be possible to give the jail a loopback interface?
>
> 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.
>
>        Wietse
>

Clamav uses loopback on its testing phase, and works fine on the build
cluster.

Chris