Date: Wed, 17 May 2017 13:10:55 +0200 From: Kurt Jaeger <lists@opsec.eu> To: tech lists <tech-lists@zyxst.net> Cc: freebsd-ports@freebsd.org Subject: Re: mesa libs issue Message-ID: <20170517111055.GK87900@home.opsec.eu> In-Reply-To: <20170517110755.GJ87900@home.opsec.eu> References: <20170513235410.GA56717@doctor.nl2k.ab.ca> <20170514021510.GX1406@albert.catwhisker.org> <20170517090505.25a6b684@pumpkin.growveg.org> <20170517110755.GJ87900@home.opsec.eu>
next in thread | previous in thread | raw e-mail | index | archive | help
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-( For details, see: http://www.freshports.org/graphics/mesa-dri/ and https://reviews.freebsd.org/D10448 It was very complicated and so UPDATING somehow slipped through 8-( -- pi@opsec.eu +49 171 3101372 3 years to go !
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20170517111055.GK87900>