From owner-freebsd-ports-announce@FreeBSD.ORG Mon Jun 11 06:17:50 2012 Return-Path: Delivered-To: ports-announce@FreeBSD.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 0ABBB10656A3 for ; Mon, 11 Jun 2012 06:17:50 +0000 (UTC) (envelope-from linimon@lonesome.com) Received: from mail.soaustin.net (pancho.soaustin.net [76.74.250.40]) by mx1.freebsd.org (Postfix) with ESMTP id E0BE28FC1D for ; Mon, 11 Jun 2012 06:17:49 +0000 (UTC) Received: by mail.soaustin.net (Postfix, from userid 502) id 9DB5356205; Mon, 11 Jun 2012 01:17:49 -0500 (CDT) Date: Mon, 11 Jun 2012 01:17:49 -0500 From: Mark Linimon To: ports-announce@FreeBSD.org Message-ID: <20120611061749.GE21099@lonesome.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.5.20 (2009-06-14) X-Mailman-Approved-At: Mon, 11 Jun 2012 06:42:39 +0000 Cc: Subject: [FreeBSD-Ports-Announce] RFC: ports failing in jails X-BeenThere: freebsd-ports-announce@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: "Important news and instructions about the FreeBSD " ports collection" \[moderated\]" List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 11 Jun 2012 06:17:50 -0000 I'd like to request the assistance of our committers and maintainers in fixing a new failure mode of ports which are built in jails. We have recently made the port-building code more restrictive about when builds may access the net. Access to the net is now denied except in the "fetch" phase. This should help us identify ports that either have latent bugs (missing dependencies that are being handled by some kind of auto-fetch code), or are doing some kind of annoying "phone home" action. At best the latter will create non-reproducible packages; at worst they will allow another means of attack. We first tested this on pointyhat-west, which we are using for both -exp runs and the pkgng packages. (The change has also been migrated to redports and poudriere; IIUC the patch for the ports tinderbox is currently being tested.) As bapt, miwi, and I have been trying to analyze the results of these runs, we keep tripping over these failures. There are too many for us to tackle, so we'd like your help. I've been trying to collect them on the following page: http://wiki.freebsd.org/PortsFailingInJails Note that ATM the failures are a moving target, so some of these failures may have already been fixed. If that is the case, please make a note of them in the "already fixed" section, so that when reviewing errorlogs we will know to skip over those. Thanks. mcl From owner-freebsd-ports-announce@FreeBSD.ORG Mon Jun 11 06:18:20 2012 Return-Path: Delivered-To: ports-announce@FreeBSD.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 1ABBC1065670 for ; Mon, 11 Jun 2012 06:18:20 +0000 (UTC) (envelope-from linimon@lonesome.com) Received: from mail.soaustin.net (pancho.soaustin.net [76.74.250.40]) by mx1.freebsd.org (Postfix) with ESMTP id F0C418FC17 for ; Mon, 11 Jun 2012 06:18:19 +0000 (UTC) Received: by mail.soaustin.net (Postfix, from userid 502) id BB78756205; Mon, 11 Jun 2012 01:18:19 -0500 (CDT) Date: Mon, 11 Jun 2012 01:18:19 -0500 From: Mark Linimon To: ports-announce@FreeBSD.org Message-ID: <20120611061819.GF21099@lonesome.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.5.20 (2009-06-14) X-Mailman-Approved-At: Mon, 11 Jun 2012 06:42:39 +0000 Cc: Subject: [FreeBSD-Ports-Announce] RFC: ports failing on current X-BeenThere: freebsd-ports-announce@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: "Important news and instructions about the FreeBSD " ports collection" \[moderated\]" List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 11 Jun 2012 06:18:20 -0000 Recently I was able to do a test run of ports on stock amd64-10 (gcc still as default compiler). The results suggest that we have a lot of work to do. The failures that I have documented are disjoint from the updates to php, png, libgif, and the options framework, due to the simple fact that this run predates it. As well, I have tried to factor out ports that also fail on our stable branches. If you are running current and/or are one of the maintainers of the affected ports, could you take a look to see if you can duplicate and/or fix the problems? Thanks. The URL: http://wiki.freebsd.org/PortsFailingOnCurrent Again, as with the "ports failing on jails", this is a moving target. mcl