[Bug 239655] lang/crystal: something weird in libevent

[bugzilla-noreply at freebsd.org]

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=239655

Jan Beich <jbeich at FreeBSD.org> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |jbeich at FreeBSD.org
             Blocks|                            |239599
           Keywords|                            |regression

--- Comment #24 from Jan Beich <jbeich at FreeBSD.org> ---
(In reply to w.schwarzenfeld from comment #23)

PATCH_SITES=    https://github.com/${GH_ACCOUNT}/${GH_PROJECT}/commit/
PATCHFILES+=    2fafc7d60825.patch:-p1

then run "make makesum". Upstream fix was reviewed in
https://github.com/crystal-lang/crystal/pull/8058

(In reply to Niclas Zeising from comment #19)
Why not use "portmgr blanket"? Whatever comes from upstream is often already
reviewed. If don't use the port (even occasionally) then ask whoever reported
to confirm the fix is enough and itself doesn't cause other regressions.

Otherwise, reverting the offending libevent commit is better idea as backing
out updates is not risk-free. Don't forget to document the file containing the
revert, so it can be dropped if future libevent updates make it unrebaseable.
In such scenarios it's responsibility[1] of consumers' maintainers to avoid
their ports becoming a burden by keeping up with upstream releases. Most
upstream projects don't support old releases, especially those with 0 as major
version.

[1]
https://www.freebsd.org/doc/en/articles/contributing/ports-contributing.html#maintain-port


Referenced Bugs:

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=239599
[Bug 239599] devel/libevent: update to 2.1.11
-- 
You are receiving this mail because:
You are the assignee for the bug.