From owner-freebsd-ports@freebsd.org  Mon Feb  6 20:43:37 2017
Return-Path: <owner-freebsd-ports@freebsd.org>
Delivered-To: freebsd-ports@mailman.ysv.freebsd.org
Received: from mx1.freebsd.org (mx1.freebsd.org
 [IPv6:2001:1900:2254:206a::19:1])
 by mailman.ysv.freebsd.org (Postfix) with ESMTP id A9CA8CD3E45
 for <freebsd-ports@mailman.ysv.freebsd.org>;
 Mon,  6 Feb 2017 20:43:37 +0000 (UTC) (envelope-from lists@opsec.eu)
Received: from home.opsec.eu (home.opsec.eu [IPv6:2001:14f8:200::1])
 (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits))
 (Client did not present a certificate)
 by mx1.freebsd.org (Postfix) with ESMTPS id 6D0CB1F82;
 Mon,  6 Feb 2017 20:43:37 +0000 (UTC) (envelope-from lists@opsec.eu)
Received: from pi by home.opsec.eu with local (Exim 4.87 (FreeBSD))
 (envelope-from <lists@opsec.eu>)
 id 1caq8R-00015e-7m; Mon, 06 Feb 2017 21:43:39 +0100
Date: Mon, 6 Feb 2017 21:43:39 +0100
From: Kurt Jaeger <lists@opsec.eu>
To: Hiroki Sato <hrs@FreeBSD.org>
Cc: freebsd-ports@FreeBSD.org
Subject: Re: No reaction - what can I do?
Message-ID: <20170206204339.GM13006@home.opsec.eu>
References: <201702060901.v1691T6v084723@fire.js.berklix.net>
 <20170206.195956.1413994210073827079.hrs@allbsd.org>
 <20170206111716.GJ13006@home.opsec.eu>
 <20170207.052701.822941695729815574.hrs@allbsd.org>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <20170207.052701.822941695729815574.hrs@allbsd.org>
X-BeenThere: freebsd-ports@freebsd.org
X-Mailman-Version: 2.1.23
Precedence: list
List-Id: Porting software to FreeBSD <freebsd-ports.freebsd.org>
List-Unsubscribe: <https://lists.freebsd.org/mailman/options/freebsd-ports>,
 <mailto:freebsd-ports-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-ports/>
List-Post: <mailto:freebsd-ports@freebsd.org>
List-Help: <mailto:freebsd-ports-request@freebsd.org?subject=help>
List-Subscribe: <https://lists.freebsd.org/mailman/listinfo/freebsd-ports>,
 <mailto:freebsd-ports-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Mon, 06 Feb 2017 20:43:37 -0000

Hi!

> li> [...]
> li> >  I am aware of this PR but I am still not sure of the cause since I
> li> >  could not reproduce it.

> li> In this case, please write a note into the PR that you can
> li> not reproduce it. It helps the submitter to understand the situation.

>  Okay, I will do it more actively.  Honestly I was leaning to working
>  on upgrading TeXLive-related ports to the latest version instead of
>  fixing issues which I could not reproduce but it has taken a longer
>  time than I expected...

I found, in the past, that if I can not reproduce something,
if I then just add a "can not reproduce, please add more details" to
a PR, that helps to get it closer to a solution -- because
the reporter will try to add details and might find a solution
himself.

-- 
pi@opsec.eu            +49 171 3101372                         3 years to go !