From owner-freebsd-ports@FreeBSD.ORG Wed Nov 16 12:46:28 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 097241065673 for ; Wed, 16 Nov 2011 12:46:28 +0000 (UTC) (envelope-from jerry@seibercom.net) Received: from mail-yw0-f54.google.com (mail-yw0-f54.google.com [209.85.213.54]) by mx1.freebsd.org (Postfix) with ESMTP id ACC8C8FC18 for ; Wed, 16 Nov 2011 12:46:27 +0000 (UTC) Received: by ywe9 with SMTP id 9so7244368ywe.13 for ; Wed, 16 Nov 2011 04:46:27 -0800 (PST) Received: by 10.236.192.200 with SMTP id i48mr892249yhn.125.1321447587144; Wed, 16 Nov 2011 04:46:27 -0800 (PST) Received: from scorpio.seibercom.net (cpe-076-182-104-150.nc.res.rr.com. [76.182.104.150]) by mx.google.com with ESMTPS id v5sm85846302anf.3.2011.11.16.04.46.24 (version=TLSv1/SSLv3 cipher=OTHER); Wed, 16 Nov 2011 04:46:25 -0800 (PST) Received: from scorpio (localhost [127.0.0.1]) (using TLSv1 with cipher DHE-RSA-AES128-SHA (128/128 bits)) (No client certificate requested) (Authenticated sender: jerry@scorpio.seibercom.net) by scorpio.seibercom.net (Postfix) with ESMTPSA id 3Sk51W4b7bz2CG5m for ; Wed, 16 Nov 2011 07:46:23 -0500 (EST) X-Virus-Status: Clean X-Virus-Scanned: clamav-milter 0.97.3 at scorpio.seibercom.net Date: Wed, 16 Nov 2011 07:46:23 -0500 From: Jerry To: freebsd-ports@freebsd.org Message-ID: <20111116074623.57d21ec1@scorpio> In-Reply-To: <4EC38223.1090400@FreeBSD.org> References: <20111114083713.29fbecda@scorpio> <20111115022430.GA19970@magic.hamla.org> <1321350319.84509.2.camel@hood.oook.cz> <2859B9B3-0A75-40FD-B444-8885A6589A37@tandon.net> <4EC293FF.2000607@beardz.net> <1321376158.2315.1.camel@hood.oook.cz> <20111116015655.GB20552@magic.hamla.org> <4EC38223.1090400@FreeBSD.org> Organization: seibercom.net X-Mailer: Claws Mail 3.7.10 (GTK+ 2.24.6; amd64-portbld-freebsd8.2) Face: iVBORw0KGgoAAAANSUhEUgAAADAAAAAwBAMAAAClLOS0AAAAHlBMVEUAAABYRlwJCw4FAgAIBwKprDkBAQFQLR0BAgCir7VRttp8AAACAUlEQVQ4jZWUTYvbMBCGTVl8V2hX6Gg5G5FbWQdBj0lEfE7BhN4cyzi5Wt1E5L70roWy6N92xok/skkP+5IYrMcz78xIduDWpNM3vFzuA/jX5EY1AI6KHFwW/CzFuQAwqUBbV12p+CzIh6Awq7sg33pn5D64SQXAexffeuQlA/L35RrkaB551OjGfP/cAO8mCNaDcgvfky5ijoD0pAXlCQCnljiAjsJD9Ax05Ko5sZxbnLQcmM+dZg5IjREfZrWIHK0JuwU68pAGwHvfRxBundRzTxxz3r9dNUikPsEihjz2Dc4kjp1hKsJGuot4EDxaxzMoC7XqhxhOSfZrTS6gSX1JVdjp+o1PvWfekXgw3WL0g70nDEwA0H0HQsEZc8sTmFMTkWUfYWC/vdR1zQy3xLQgLwzu90QnlnFLjeiGWBjwhb4Sa42IqOg2qqS4O1/zhKokFUb1Q8Rj4Eb69WVflXEehJ35DgChVTE5n50eaGyMLOfH8AOodoSM4PVYAQgQdBulOa+knklYks3vAuQ+uX492lTl+A+e8qBV2AKoXalVKFfyuUp0pUp1ARaUHh82lv9MN+Ig7CZtgE6FNYvjlywT2VP2dMgOG46gTIWcqdfvuwyXNz0oMJNd/N5lh1YNiJt19ADTUo3VuFSNeQwVqRSrGjSCp53fk2g+Mvfk/gfoPxHeUS8MH9vRAAAAAElFTkSuQmCC Mime-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit Subject: Re: "postfix-current" broken on amd64 platform X-BeenThere: freebsd-ports@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: freebsd-ports@freebsd.org List-Id: Porting software to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 16 Nov 2011 12:46:28 -0000 On Wed, 16 Nov 2011 10:28:03 +0100 Pav Lucistnik articulated: > On 2011/11/16 02:56, Sahil Tandon wrote: > > On Tue, 2011-11-15 at 17:55:57 +0100, Pav Lucistnik wrote: > > > >> Jase Thew píše v út 15. 11. 2011 v 16:31 +0000: > >> > >>> What networking/DNS configuration is Pointyhat lacking (or have > >>> sufficiently different to break the socket code inside of > >>> postconf)? > >> > >> It is a purposefully no-networking sandbox jail. What networking > >> activity postconf wants to run? > > > > Wietse, in a post[1] on the Postfix mailing list, lends further > > credence to a suspicion that this issue is particular to pointyhat: > > > > Postconf opens a socket to determine the mynetworks value (it > > determines the local interfaces and their netmasks). > > > > I have heard about bizarre errors on FreeBSD (jail) systems where > > the user-land library was out of sync with kernel-land, resulting > > in data structure mis-matches and system calls returning > > nonsensical results. > > > > [1] http://archives.neohapsis.com/archives/postfix/2011-11/0385.html > > That's entirely possible. > > Is it a clever idea to hardcode local interfaces on build machine > into a package that will then be redistributed to other machines? > > Sounds like postfix will have to do without official packages on > FreeBSD from now on. I would find that unacceptable. If the problem is with FreeBSD as Wietse has indicated, then the problem should be rectified on the FreeBSD side of the equation. In any case, since Postfix does apparently build on FreeBSD with the exception of "pointyhat", perhaps the "BROKEN" tag should be removed from the port and just a warning message displayed that "pointyhat" cannot build/install the port successfully but that the end users mileage may vary. At the very least, it would be a more honest approach to the problem. -- Jerry ♔ Disclaimer: off-list followups get on-list replies or get ignored. Please do not ignore the Reply-To header. __________________________________________________________________