From owner-freebsd-ports@FreeBSD.ORG Fri May 9 12:01:49 2014 Return-Path: Delivered-To: ports@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 035575CF for ; Fri, 9 May 2014 12:01:49 +0000 (UTC) Received: from smtp1.multiplay.co.uk (smtp1.multiplay.co.uk [85.236.96.35]) by mx1.freebsd.org (Postfix) with ESMTP id BD604C65 for ; Fri, 9 May 2014 12:01:48 +0000 (UTC) Received: by smtp1.multiplay.co.uk (Postfix, from userid 65534) id 9999320E7088B; Fri, 9 May 2014 12:01:46 +0000 (UTC) X-Spam-Checker-Version: SpamAssassin 3.3.1 (2010-03-16) on smtp1.multiplay.co.uk X-Spam-Level: *** X-Spam-Status: No, score=3.8 required=8.0 tests=AWL,BAYES_05,DOS_OE_TO_MX, FSL_HELO_NON_FQDN_1,HELO_NO_DOMAIN,RDNS_DYNAMIC,STOX_REPLY_TYPE, STOX_REPLY_TYPE_WITHOUT_QUOTES autolearn=no version=3.3.1 Received: from r2d2 (82-69-141-170.dsl.in-addr.zen.co.uk [82.69.141.170]) by smtp1.multiplay.co.uk (Postfix) with ESMTPS id 57E4320E70885 for ; Fri, 9 May 2014 12:01:41 +0000 (UTC) Message-ID: <495738D66545411BA78B31A6615EFA48@multiplay.co.uk> From: "Steven Hartland" To: Subject: Unable to use ports on 8.3 or earlier since r352986 Date: Fri, 9 May 2014 13:01:38 +0100 MIME-Version: 1.0 Content-Type: text/plain; format=flowed; charset="iso-8859-1"; reply-type=original Content-Transfer-Encoding: 7bit X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 6.00.2900.5931 X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.6157 X-BeenThere: freebsd-ports@freebsd.org X-Mailman-Version: 2.1.18 Precedence: list List-Id: Porting software to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 09 May 2014 12:01:49 -0000 Since the following commit ports is now broken on 8.3 and earlier. http://svnweb.freebsd.org/ports?view=revision&revision=352986 Now while 8.3 is now officially EOL as of 9 days ago such a breakage so soon after the EOL seems very bad. Can we consider reverting this and only applying after a decent amount of time to give people the chance to update without preventing them from getting port security updates etc? Regards Steve