Date: Fri, 07 Apr 2017 22:02:56 +0000 From: bugzilla-noreply@freebsd.org To: x11@FreeBSD.org Subject: [Bug 217771] lang/beignet: update to 1.3.1 Message-ID: <bug-217771-7141-C6lU258Y9l@https.bugs.freebsd.org/bugzilla/> In-Reply-To: <bug-217771-7141@https.bugs.freebsd.org/bugzilla/> References: <bug-217771-7141@https.bugs.freebsd.org/bugzilla/>
next in thread | previous in thread | raw e-mail | index | archive | help
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D217771 --- Comment #15 from Jan Beich <jbeich@FreeBSD.org> --- (In reply to Jan Beich from comment #0) > MFH is for security updates and bug fixes. The former does not apply. Doe= s the > latter? IIRC, the users on quarterly branches want less moving parts that result in accidental bustage in cosumer ports, due to old configs, etc. Regular updat= es are fine as long as maintainer or committer understands the risks. It's a tradeoff of maintaining an old version + new version or just a new version which sometimes drives even major backports like with lang/gcc or devel/boost-*. ports-secteam only cares about security fixes while the rest lies on the interested parties. Many bug fixes are also covered under blanket unless ti= ed to the update. > The email you sent just minutes prior suggested that the issue from PR 21= 7635 > is still present and that enabling OpenCL 2.0 was premature. That email a= nd > this last question seem to be in direct opposition. Bug 217635 affects 2017Q2 even without the update here. The regression was introduced in 1.3.0 but even landing upstream didn't help to propagate the = fix to the port. > So which is it, did the 1.3.1 update resolve bugs and thus should be MFHed > because it has low-risk, or does the 1.3.1 update still contain bugs and > present a risk with a possibly premature feature? 1.3.1 has other bug fixes, including for OpenCL 2.0, but ultimately still broken on FreeBSD. It is low-risk compared to 1.3.0 but not 1.2.0 --=20 You are receiving this mail because: You are the assignee for the bug.=
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?bug-217771-7141-C6lU258Y9l>