[Bug 250521] graphics/libansilove: Update to 1.2.7
bugzilla-noreply at freebsd.org
bugzilla-noreply at freebsd.org
Thu Oct 22 07:30:23 UTC 2020
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=250521
Bug ID: 250521
Summary: graphics/libansilove: Update to 1.2.7
Product: Ports & Packages
Version: Latest
Hardware: Any
URL: https://github.com/ansilove/libansilove
OS: Any
Status: New
Severity: Affects Only Me
Priority: ---
Component: Individual Port(s)
Assignee: amdmi3 at FreeBSD.org
Reporter: juraj at lutter.sk
Assignee: amdmi3 at FreeBSD.org
Flags: maintainer-feedback?(amdmi3 at FreeBSD.org)
Created attachment 218966
--> https://bugs.freebsd.org/bugzilla/attachment.cgi?id=218966&action=edit
graphics/libansilove: Update to 1.2.7
Hi,
please find the patch attached.
Changelog for 1.2.7:
- Error out early with ANSILOVE_FORMAT_ERROR in case ctx->length is 0
- Enable FORTIFY_SOURCE level 2
- Set CMAKE_BUILD_TYPE to "Release" in CMakeLists.txt
- Move variables declaration to the top of each loader function
- Initialize ansi_buffer and pcboard_buffer to NULL
- Refactor the IceDraw loader to use a state machine
- Check strndup() return value and error out on failed allocations
- Add some file format integrity checks in the IceDraw loader
- Add range integrity checks for scale_factor values in the output() function
- Return error code directly if ctx->length is 0 in the ANSI and PCBoard
loaders
- Add range integrity checks for columns value in relevant loaders
- Add range integrity checks for bits value in relevant loaders
- Add additional file format integrity check in the XBin loader
Testport results:
https://freebsd-stable.builder.wilbury.net/data/11_4_RELEASE_GENERIC-default/2020-10-22_08h20m18s/logs/libansilove-1.2.7.log
https://freebsd-stable.builder.wilbury.net/data/12_STABLE_GENERIC_amd64-default/2020-10-22_08h32m26s/logs/libansilove-1.2.7.log
https://freebsd-current.builder.wilbury.net/data/13cgx64-default/2020-10-22_08h27m48s/logs/libansilove-1.2.6.log
--
You are receiving this mail because:
You are the assignee for the bug.
More information about the freebsd-ports-bugs
mailing list