From owner-freebsd-ports@FreeBSD.ORG  Tue Mar 17 14:42:56 2015
Return-Path: <owner-freebsd-ports@FreeBSD.ORG>
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 67C6D8BF
 for <freebsd-ports@freebsd.org>; Tue, 17 Mar 2015 14:42:56 +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 295FF83E
 for <freebsd-ports@freebsd.org>; Tue, 17 Mar 2015 14:42:56 +0000 (UTC)
Received: from pi by home.opsec.eu with local (Exim 4.82 (FreeBSD))
 (envelope-from <lists@opsec.eu>)
 id 1YXshr-0001Qe-UP; Tue, 17 Mar 2015 15:42:55 +0100
Date: Tue, 17 Mar 2015 15:42:55 +0100
From: Kurt Jaeger <lists@opsec.eu>
To: Maxim Kirenenko <che@bein.link>, freebsd-ports@freebsd.org
Subject: Re: devel/py-colorama: no update yet
Message-ID: <20150317144255.GS62590@home.opsec.eu>
References: <20150317122127.GC74328@bein.link>
 <20150317125311.GQ62590@home.opsec.eu>
 <20150317141054.GD74328@bein.link>
 <20150317141610.GR62590@home.opsec.eu>
 <20150317141809.GB76924@bein.link>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <20150317141809.GB76924@bein.link>
X-BeenThere: freebsd-ports@freebsd.org
X-Mailman-Version: 2.1.18-1
Precedence: list
List-Id: Porting software to FreeBSD <freebsd-ports.freebsd.org>
List-Unsubscribe: <http://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: <http://lists.freebsd.org/mailman/listinfo/freebsd-ports>,
 <mailto:freebsd-ports-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Tue, 17 Mar 2015 14:42:56 -0000

Hi!

> > For example:
> > - Does it block any other PRs or ports from updating ?
> > - Is it broken right now ?
> > 
> 
>  - It actually does. I want to submit a new port, and it requires a
>    recent version of py-colorama which is not available yet;
>  - No, it isn't AFAIK.

Can you submit the port and make the PR block on the py-colorama PR ?

Then it's more obvious and I can speed this up (this evening CET).

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