From owner-freebsd-ports@FreeBSD.ORG Wed Nov 16 16:00:34 2011 Return-Path: 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 33994106564A for ; Wed, 16 Nov 2011 16:00:34 +0000 (UTC) (envelope-from wietse@porcupine.org) Received: from spike.porcupine.org (spike.porcupine.org [IPv6:2604:8d00:189::2]) by mx1.freebsd.org (Postfix) with ESMTP id D3AA08FC0A for ; Wed, 16 Nov 2011 16:00:33 +0000 (UTC) Received: by spike.porcupine.org (Postfix, from userid 1001) id 3Sk9KR4s2czk2RT; Wed, 16 Nov 2011 11:00:27 -0500 (EST) DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=porcupine.org; s=dktest; t=1321459227; bh=KEkyDao7qbhVSR26SgD7BkDLuFOsZuNpVWzKEdAZ1jY=; h=Subject:In-Reply-To:To:Date:Sender:From:CC:MIME-Version: Content-Transfer-Encoding:Content-Type:Message-Id; b=zekVwGDZH3oq4oviULoiOQ8WmFI0QXuMt5WqbS/xqV9+YtJt7PtkZd84kecnmWL2+ TyjoOciwzdALTQNsEuk3HWEJHiKNh40NpnXP6B4UxwpWBNX+1fidSaaWSm9KbpG8d3 DM5fsNC3ltkNHjrSMA9SZ9V4+CsjCXk6oMdHAmAI= In-Reply-To: <20111116140223.GI68080@home.opsec.eu> To: Kurt Jaeger Date: Wed, 16 Nov 2011 11:00:27 -0500 (EST) Sender: wietse@porcupine.org From: Wietse Venema X-Mailer: ELM [version 2.4ME+ PL124d (25)] MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Type: text/plain; charset="US-ASCII" Message-Id: <3Sk9KR4s2czk2RT@spike.porcupine.org> Cc: freebsd-ports@freebsd.org, Wietse Venema 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 List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 16 Nov 2011 16:00:34 -0000 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