From owner-freebsd-ports@FreeBSD.ORG Tue Mar 17 14:16:11 2015 Return-Path: Delivered-To: freebsd-ports@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id E870A198 for ; Tue, 17 Mar 2015 14:16:11 +0000 (UTC) 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 A707A2B9 for ; Tue, 17 Mar 2015 14:16:11 +0000 (UTC) Received: from pi by home.opsec.eu with local (Exim 4.82 (FreeBSD)) (envelope-from ) id 1YXsHy-0000uy-RR; Tue, 17 Mar 2015 15:16:10 +0100 Date: Tue, 17 Mar 2015 15:16:10 +0100 From: Kurt Jaeger To: Maxim Kirenenko , freebsd-ports@freebsd.org Subject: Re: devel/py-colorama: no update yet Message-ID: <20150317141610.GR62590@home.opsec.eu> References: <20150317122127.GC74328@bein.link> <20150317125311.GQ62590@home.opsec.eu> <20150317141054.GD74328@bein.link> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20150317141054.GD74328@bein.link> X-BeenThere: freebsd-ports@freebsd.org X-Mailman-Version: 2.1.18-1 Precedence: list List-Id: Porting software to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 17 Mar 2015 14:16:12 -0000 Hi! > > > Recently, I submitted a PR about devel/py-colorama: > > > https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=198605 > > > > > > Until now, I didn't get any reply on that. Could anyone update that port > > > for me, please? > > > > It's still pending on maintainer approval ? > Yes. And the maintainer doesn't seem to answer. Section 5.5 of the porters handbook, https://www.freebsd.org/doc/en_US.ISO8859-1/books/porters-handbook/book.html says: [...] If the maintainer does not respond to an update request after two weeks (excluding major public holidays), then that is considered a maintainer timeout, and the update may be made without explicit maintainer approval. [...] So in general he has two weeks. If it's urgent, we can make an exception. For example: - Does it block any other PRs or ports from updating ? - Is it broken right now ? -- pi@opsec.eu +49 171 3101372 5 years to go !