From owner-freebsd-ports@freebsd.org  Mon May 21 14:14:23 2018
Return-Path: <owner-freebsd-ports@freebsd.org>
Delivered-To: freebsd-ports@mailman.ysv.freebsd.org
Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1])
 by mailman.ysv.freebsd.org (Postfix) with ESMTP id BCABDEF2190
 for <freebsd-ports@mailman.ysv.freebsd.org>;
 Mon, 21 May 2018 14:14:23 +0000 (UTC) (envelope-from lists@opsec.eu)
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 36BBE7F4EC;
 Mon, 21 May 2018 14:14:23 +0000 (UTC) (envelope-from lists@opsec.eu)
Received: from pi by home.opsec.eu with local (Exim 4.89 (FreeBSD))
 (envelope-from <lists@opsec.eu>)
 id 1fKlZv-000CR0-Tj; Mon, 21 May 2018 16:14:23 +0200
Date: Mon, 21 May 2018 16:14:23 +0200
From: Kurt Jaeger <lists@opsec.eu>
To: Alfred Perlstein <alfred@freebsd.org>
Cc: freebsd-current <freebsd-ports@freebsd.org>
Subject: Re: Phabricator to ports commit broken?
Message-ID: <20180521141423.GK37752@home.opsec.eu>
References: <1744ab09-4af7-4e6a-c8df-627abb020f4b@freebsd.org>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <1744ab09-4af7-4e6a-c8df-627abb020f4b@freebsd.org>
X-BeenThere: freebsd-ports@freebsd.org
X-Mailman-Version: 2.1.26
Precedence: list
List-Id: Porting software to FreeBSD <freebsd-ports.freebsd.org>
List-Unsubscribe: <https://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: <https://lists.freebsd.org/mailman/listinfo/freebsd-ports>,
 <mailto:freebsd-ports-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Mon, 21 May 2018 14:14:23 -0000

Hi!

> I'm getting some issues due to these systems: svn hooks and phabricator 
> apparently being out of sync:
> 
> Can anyone help or suggest a way forward?

Eitan Adler wrote on phabric-admin@:

> Not currently. https://secure.phabricator.com/T2920 is the upstream
> tracking bug.

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