From owner-svn-ports-all@FreeBSD.ORG Tue Jan 21 05:44:23 2014 Return-Path: Delivered-To: svn-ports-all@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 ESMTPS id F0231250; Tue, 21 Jan 2014 05:44:23 +0000 (UTC) Received: from thyme.infocus-llc.com (server.infocus-llc.com [206.156.254.44]) (using TLSv1 with cipher ADH-CAMELLIA256-SHA (256/256 bits)) (No client certificate requested) by mx1.freebsd.org (Postfix) with ESMTPS id C36A61368; Tue, 21 Jan 2014 05:44:23 +0000 (UTC) Received: from draco.over-yonder.net (c-75-65-60-66.hsd1.ms.comcast.net [75.65.60.66]) (using TLSv1 with cipher ADH-CAMELLIA256-SHA (256/256 bits)) (No client certificate requested) by thyme.infocus-llc.com (Postfix) with ESMTPSA id 639F937B499; Mon, 20 Jan 2014 23:37:59 -0600 (CST) Received: by draco.over-yonder.net (Postfix, from userid 100) id 3f7dnK6wc7zsM; Mon, 20 Jan 2014 23:37:57 -0600 (CST) Date: Mon, 20 Jan 2014 23:37:57 -0600 From: "Matthew D. Fuller" To: Antoine Brodin Subject: Re: svn commit: r340451 - head/devel/bzr-grep Message-ID: <20140121053757.GT94892@over-yonder.net> References: <201401201908.s0KJ8wYi025049@svn.freebsd.org> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <201401201908.s0KJ8wYi025049@svn.freebsd.org> X-Editor: vi X-OS: FreeBSD User-Agent: Mutt/1.5.22 (2013-10-16) X-Virus-Scanned: clamav-milter 0.98.1 at thyme.infocus-llc.com X-Virus-Status: Clean Cc: svn-ports-head@freebsd.org, svn-ports-all@freebsd.org, ports-committers@freebsd.org X-BeenThere: svn-ports-all@freebsd.org X-Mailman-Version: 2.1.17 Precedence: list List-Id: SVN commit messages for the ports tree List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 21 Jan 2014 05:44:24 -0000 On Mon, Jan 20, 2014 at 07:08:58PM +0000 I heard the voice of Antoine Brodin, and lo! it spake thus: > > BROKEN= conflicts with dependency bzr > +DEPRECATED= Broken for more than 4 months > +EXPIRATION_DATE=2014-02-20 This can really just bypass the whole deprecation and be removed. It conflicts with bzr because it's been integrated into bzr. (with-hat: devel/bzr maintainer) -- Matthew Fuller (MF4839) | fullermd@over-yonder.net Systems/Network Administrator | http://www.over-yonder.net/~fullermd/ On the Internet, nobody can hear you scream.