From owner-freebsd-ports@freebsd.org  Wed May 17 11:07:55 2017
Return-Path: <owner-freebsd-ports@freebsd.org>
Delivered-To: freebsd-ports@mailman.ysv.freebsd.org
Received: from mx1.freebsd.org (mx1.freebsd.org
 [IPv6:2001:1900:2254:206a::19:1])
 by mailman.ysv.freebsd.org (Postfix) with ESMTP id AF978D717F7
 for <freebsd-ports@mailman.ysv.freebsd.org>;
 Wed, 17 May 2017 11:07:55 +0000 (UTC) (envelope-from pi@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 75B8F1587
 for <freebsd-ports@freebsd.org>; Wed, 17 May 2017 11:07:55 +0000 (UTC)
 (envelope-from pi@opsec.eu)
Received: from pi by home.opsec.eu with local (Exim 4.87 (FreeBSD))
 (envelope-from <pi@opsec.eu>)
 id 1dAwo7-000OxU-Og; Wed, 17 May 2017 13:07:55 +0200
Date: Wed, 17 May 2017 13:07:55 +0200
From: Kurt Jaeger <pi@opsec.eu>
To: tech lists <tech-lists@zyxst.net>
Cc: freebsd-ports@freebsd.org
Subject: Re: mesa libs issue
Message-ID: <20170517110755.GJ87900@home.opsec.eu>
References: <20170513235410.GA56717@doctor.nl2k.ab.ca>
 <20170514021510.GX1406@albert.catwhisker.org>
 <20170517090505.25a6b684@pumpkin.growveg.org>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <20170517090505.25a6b684@pumpkin.growveg.org>
X-BeenThere: freebsd-ports@freebsd.org
X-Mailman-Version: 2.1.23
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: Wed, 17 May 2017 11:07:55 -0000

Hi!

> Thanks for this. It was a real help. I got bitten by it on an 11-stable
> system with ports rev 440997 [ 2017-05-16 13:27:43 +0100 ]

Can someone please provide a write-up that we can add to UPDATING ?

> Does anyone know why /usr/ports/UPDATING wasn't, er, updated? 

Braintime is really tight 8-(

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