From owner-freebsd-ports@FreeBSD.ORG Wed Apr 1 20:45:59 2015 Return-Path: Delivered-To: freebsd-ports@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 711D1D9C for ; Wed, 1 Apr 2015 20:45:59 +0000 (UTC) Received: from avasout08.plus.net (avasout08.plus.net [212.159.14.20]) (using TLSv1 with cipher DHE-RSA-AES128-SHA (128/128 bits)) (Client CN "Bizanga Labs SMTP Client Certificate", Issuer "Bizanga Labs CA" (not verified)) by mx1.freebsd.org (Postfix) with ESMTPS id C5854849 for ; Wed, 1 Apr 2015 20:45:57 +0000 (UTC) Received: from curlew.milibyte.co.uk ([84.92.153.232]) by avasout08 with smtp id Akik1q005516WCc01kil5U; Wed, 01 Apr 2015 21:42:46 +0100 X-CM-Score: 0.00 X-CNFS-Analysis: v=2.1 cv=GcuZnGnL c=1 sm=1 tr=0 a=lfSX4pPLp9EkufIcToJk/A==:117 a=lfSX4pPLp9EkufIcToJk/A==:17 a=D7rCoLxHAAAA:8 a=0Bzu9jTXAAAA:8 a=4TIn5Tuy4E8A:10 a=e9J7MTPGsLIA:10 a=r77TgQKjGQsHNAKrUKIA:9 a=9iDbn-4jx3cA:10 a=cKsnjEOsciEA:10 a=gZbpxnkM3yUA:10 a=6I5d2MoRAAAA:8 a=x1pHzWAgVK79VjaDNZkA:9 a=bmER-7W8R7almxNt:21 a=S7iNZJWnxb3908rv:21 a=wPNLvfGTeEIA:10 a=SSmOFEACAAAA:8 a=KGdqb3eytz8NAYsLjYsA:9 a=AB5iw9h85XrKXl2X:21 a=_W_S_7VecoQA:10 a=frz4AuCg-hUA:10 Received: from curlew.lan ([192.168.1.13] helo=milibyte.co.uk) by curlew.milibyte.co.uk with esmtp (Exim 4.85) (envelope-from ) id 1YdPT6-000CX8-NT for freebsd-ports@freebsd.org; Wed, 01 Apr 2015 21:42:44 +0100 From: Mike Clarke To: 'FreeBSD Ports' Date: Wed, 01 Apr 2015 21:42:31 +0100 Message-ID: <4105121.J31zpxLvnq@curlew.lan> User-Agent: KMail/4.14.3 (FreeBSD/10.1-RELEASE-p6; KDE/4.14.3; amd64; ; ) MIME-Version: 1.0 X-SA-Exim-Connect-IP: 192.168.1.13 X-SA-Exim-Mail-From: jmc-freebsd2@milibyte.co.uk X-Spam-Checker-Version: SpamAssassin 3.4.0 (2014-02-07) on curlew.lan X-Spam-Level: X-Spam-Status: No, score=-2.9 required=5.0 tests=ALL_TRUSTED,BAYES_00, HTML_MESSAGE autolearn=ham autolearn_force=no version=3.4.0 Subject: Synchronising ports with package cluster X-SA-Exim-Version: 4.2 X-SA-Exim-Scanned: Yes (on curlew.milibyte.co.uk) Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7Bit X-Content-Filtered-By: Mailman/MimeDel 2.1.18-1 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: Wed, 01 Apr 2015 20:45:59 -0000 I use pkg upgrade to maintain most of my ports but a small number need to be built from source. To avoid problems I aim to keep my ports tree in sync with the snapshots used by the package cluster. Until a couple of weeks ago I was able to obtain the revision number of the ports snapshot by parsing the results of fetching beefy2.isc.freebsd.org/data/101amd64- default/.data.json. That server now appears to be only building 93amd64-default and 101amd64-quarterly. So now my ports are stuck at revision 381523 from about two weeks ago. Where can I now obtain the revision number for the ports tree used for the latest package build? Although the above method has worked in the past it's a bit of a bodge. The ideal way would be if this information could be accessed directly from the relevant package repository. Would it be possible to provide such a facility? -- Mike Clarke