From owner-freebsd-python@FreeBSD.ORG Tue Oct 29 09:30:02 2013 Return-Path: Delivered-To: freebsd-python@smarthost.ysv.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 ESMTP id 5F88B277 for ; Tue, 29 Oct 2013 09:30:02 +0000 (UTC) (envelope-from gnats@FreeBSD.org) Received: from freefall.freebsd.org (freefall.freebsd.org [IPv6:2001:1900:2254:206c::16:87]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by mx1.freebsd.org (Postfix) with ESMTPS id 4D76926CA for ; Tue, 29 Oct 2013 09:30:02 +0000 (UTC) Received: from freefall.freebsd.org (localhost [127.0.0.1]) by freefall.freebsd.org (8.14.7/8.14.7) with ESMTP id r9T9U2Xk085368 for ; Tue, 29 Oct 2013 09:30:02 GMT (envelope-from gnats@freefall.freebsd.org) Received: (from gnats@localhost) by freefall.freebsd.org (8.14.7/8.14.7/Submit) id r9T9U17R085367; Tue, 29 Oct 2013 09:30:01 GMT (envelope-from gnats) Date: Tue, 29 Oct 2013 09:30:01 GMT Message-Id: <201310290930.r9T9U17R085367@freefall.freebsd.org> To: freebsd-python@FreeBSD.org Cc: From: Kubilay Kocak Subject: Re: ports/181593: math/py-numpy maintainer gone X-BeenThere: freebsd-python@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list Reply-To: Kubilay Kocak List-Id: FreeBSD-specific Python issues List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 29 Oct 2013 09:30:02 -0000 The following reply was made to PR ports/181593; it has been noted by GNATS. From: Kubilay Kocak To: bug-followup@FreeBSD.org, kentas@hush.com, "Denis Generalov" , Wen Heping , llwang@infor.org Cc: Subject: Re: ports/181593: math/py-numpy maintainer gone Date: Tue, 29 Oct 2013 20:28:27 +1100 Hi Folks, This PR relates to a request to reset maintainership on math/py-numpy due to an email bounce. Li-Lun (maintainer) has subsequently followed-up. Since the PR has evolved into build issue isolation, it is now a little more complex in terms of progressing to resolution. We'd like to resolve this PR as soon as possible, and it seems there are least the following options: 1) If building of py-numpy in poudriere is no longer an issue a) Close without a maintainer reset b) Close with a maintainer reset c) Close with a maintainer change 2) If building of py-numpy IS still an issue a) Change maintainer, change issue synopsis, resolve the issue The current maintainer has the call on where and how to proceed from here. If Denis, Wen or Kenta (submitter) have anything to add, now is the time. Thanks :)