From owner-freebsd-ports-bugs@FreeBSD.ORG Sat Aug 25 19:00:05 2012 Return-Path: Delivered-To: freebsd-ports-bugs@hub.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 30AD01065673 for ; Sat, 25 Aug 2012 19:00:05 +0000 (UTC) (envelope-from gnats@FreeBSD.org) Received: from freefall.freebsd.org (freefall.freebsd.org [IPv6:2001:4f8:fff6::28]) by mx1.freebsd.org (Postfix) with ESMTP id E972C8FC14 for ; Sat, 25 Aug 2012 19:00:04 +0000 (UTC) Received: from freefall.freebsd.org (localhost [127.0.0.1]) by freefall.freebsd.org (8.14.5/8.14.5) with ESMTP id q7PJ04AM051873 for ; Sat, 25 Aug 2012 19:00:04 GMT (envelope-from gnats@freefall.freebsd.org) Received: (from gnats@localhost) by freefall.freebsd.org (8.14.5/8.14.5/Submit) id q7PJ04i1051872; Sat, 25 Aug 2012 19:00:04 GMT (envelope-from gnats) Date: Sat, 25 Aug 2012 19:00:04 GMT Message-Id: <201208251900.q7PJ04i1051872@freefall.freebsd.org> To: freebsd-ports-bugs@FreeBSD.org From: "Mikhail T." Cc: Subject: Re: ports/170946: [patch] mark certain ports broken on ARM X-BeenThere: freebsd-ports-bugs@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: "Mikhail T." List-Id: Ports bug reports List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 25 Aug 2012 19:00:05 -0000 The following reply was made to PR ports/170946; it has been noted by GNATS. From: "Mikhail T." To: Chris Rees Cc: Eitan Adler , Mark Linimon , bug-followup@freebsd.org Subject: Re: ports/170946: [patch] mark certain ports broken on ARM Date: Sat, 25 Aug 2012 14:50:45 -0400 This is a multi-part message in MIME format. --------------040403030804080801050909 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit On 25.08.2012 12:06, Chris Rees wrote: > It's a big distinction; BROKEN means it is expected to be fixed at > some point, IGNORE means that it is not supposed to work this way. > > Also, don't forget that package building runs are often done with > TRY_BROKEN, which is very helpful when doing !intel builds. I see... Kinda silly, then, that more lines have to change to mark something temporarily broken, than to permanently ignore it... On 25.08.2012 14:32, Mark Linimon wrote: > Finally, I wanted to use this PR as kind of a heads-up to maintainers > that we had a new architecture up and going, so as to reduce the surprise. So, is there an ARM-machine (or a couple) on the cluster, where a committer can try this-and-that? -mi --------------040403030804080801050909 Content-Type: text/html; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit
On 25.08.2012 12:06, Chris Rees wrote:
It's a big distinction; BROKEN means it is expected to be fixed at
 some point, IGNORE means that it is not supposed to work this way.
 
 Also, don't forget that package building runs are often done with
 TRY_BROKEN, which is very helpful when doing !intel builds.
I see... Kinda silly, then, that more lines have to change to mark something temporarily broken, than to permanently ignore it...

On 25.08.2012 14:32, Mark Linimon wrote:
Finally, I wanted to use this PR as kind of a heads-up to maintainers
 that we had a new architecture up and going, so as to reduce the surprise.
So, is there an ARM-machine (or a couple) on the cluster, where a committer can try this-and-that?
-mi
--------------040403030804080801050909--