From owner-freebsd-python@FreeBSD.ORG Thu Oct 24 00:50:02 2013 Return-Path: Delivered-To: freebsd-python@smarthost.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTP id 92C1353B for ; Thu, 24 Oct 2013 00:50: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 7FF842D01 for ; Thu, 24 Oct 2013 00:50: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 r9O0o2ae096563 for ; Thu, 24 Oct 2013 00:50:02 GMT (envelope-from gnats@freefall.freebsd.org) Received: (from gnats@localhost) by freefall.freebsd.org (8.14.7/8.14.7/Submit) id r9O0o2Gx096562; Thu, 24 Oct 2013 00:50:02 GMT (envelope-from gnats) Date: Thu, 24 Oct 2013 00:50:02 GMT Message-Id: <201310240050.r9O0o2Gx096562@freefall.freebsd.org> To: freebsd-python@FreeBSD.org Cc: From: Kubilay Kocak Subject: Re: ports/167530: [patch] security/py-fail2ban will never ever start with the given rc.d script 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: Thu, 24 Oct 2013 00:50:02 -0000 The following reply was made to PR ports/167530; it has been noted by GNATS. From: Kubilay Kocak To: bug-followup@FreeBSD.org, theis@gmx.at Cc: julien@tayon.net Subject: Re: ports/167530: [patch] security/py-fail2ban will never ever start with the given rc.d script Date: Thu, 24 Oct 2013 11:43:29 +1100 Hi Christoph, Can you please clarify what needs to happen to progress or close this PR. It is currently in the feedback state for 180 months, but I'm not sure it's clear what Julien (submitter) needs to do, if anything. Some next steps could include: a) Close -> startup script works as intended b) Feedback -> Is this still an issue? c) Feedback -> Request an update to the proposed fix As maintainer the decision is yours as to how to proceed, please let us know so we can take care of it for you. Koobs