Date: Sat, 25 Aug 2012 19:00:04 GMT From: "Mikhail T." <mi+thun@aldan.algebra.com> To: freebsd-ports-bugs@FreeBSD.org Subject: Re: ports/170946: [patch] mark certain ports broken on ARM Message-ID: <201208251900.q7PJ04i1051872@freefall.freebsd.org>
next in thread | raw e-mail | index | archive | help
The following reply was made to PR ports/170946; it has been noted by GNATS.
From: "Mikhail T." <mi+thun@aldan.algebra.com>
To: Chris Rees <crees@freebsd.org>
Cc: Eitan Adler <lists@eitanadler.com>, Mark Linimon <linimon@lonesome.com>,
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
<html>
<head>
<meta content="text/html; charset=ISO-8859-1"
http-equiv="Content-Type">
</head>
<body bgcolor="#FFFFFF" text="#000000">
<div class="moz-cite-prefix">On 25.08.2012 12:06, Chris Rees wrote:<br>
</div>
<blockquote
cite="mid:CADLo838Fr98B3cALMQYzih-zvUUQwr23n0rV1P1jOyNYTArzGg@mail.gmail.com"
type="cite">
<pre wrap="">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.</pre>
</blockquote>
I see... Kinda silly, then, that more lines have to change to mark
something temporarily broken, than to permanently ignore it...<br>
<br>
<div class="moz-cite-prefix">On 25.08.2012 14:32, Mark Linimon
wrote:<br>
</div>
<blockquote cite="mid:20120825183251.GA519@lonesome.com" type="cite">
<pre wrap="">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.</pre>
</blockquote>
So, is there an ARM-machine (or a couple) on the cluster, where a
committer can try this-and-that?<br>
<blockquote>-mi<br>
</blockquote>
</body>
</html>
--------------040403030804080801050909--
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?201208251900.q7PJ04i1051872>