Date: Tue, 23 Jul 2013 12:23:34 +0200 From: Koop Mast <kwm@rainbow-runner.nl> To: Guido Falsi <madpilot@FreeBSD.org> Cc: Ivan Klymenko <fidaj@ukr.net>, svn-ports-head@freebsd.org, svn-ports-all@freebsd.org, x11@freebsd.org, ports-committers@freebsd.org Subject: Re: svn commit: r323260 - in head/multimedia/libva-intel-driver: . files Message-ID: <51EE59A6.2020207@rainbow-runner.nl> In-Reply-To: <51EC0D3E.2060203@FreeBSD.org> References: <201307182219.r6IMJtuw092537@svn.freebsd.org> <74488.1374358020.16480811267322281984@ffe16.ukr.net> <20130721122103.067d6d2a@nonamehost.local> <51EC0D3E.2060203@FreeBSD.org>
next in thread | previous in thread | raw e-mail | index | archive | help
On 07/21/13 18:33, Guido Falsi wrote: > On 07/21/13 11:21, Ivan Klymenko wrote: >> <snip> > > Hi, > > I'm sorry for my mistake. Unluckily the laptop with intel graphics I > test this one on happens to have libdrm 2.4.45 already installed. This > is the reason this one slipped me. I'm not stating this as a > justification, it's just the "technical" reason this happened. > > I can't commit to graphics/libdrm without permission. Depending on the > chance of this PR being committed shortly I can put back the > libva-intel-driver port or just wait a little. > > I'm also CCing x11@ to know if I'm allowed to fix this by updating > libdrm (only the WITH_NEW_XORG case, obviously) or should bring the > libva-intel-driver port back. > > Thanks in advance for any help. > I updated libdrm to 2.4.46, we had that update done for a while and it pretty stable. Please be more carefull in the future about updates and running patches ports. -Koop
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?51EE59A6.2020207>