[Bug 236867] print/freetype2: Update to 2.10.0

bugzilla-noreply at freebsd.org bugzilla-noreply at freebsd.org
Thu Apr 11 20:26:10 UTC 2019


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

Koop Mast <kwm at FreeBSD.org> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |kwm at FreeBSD.org
              Flags|maintainer-feedback?(gnome@ |maintainer-feedback-
                   |FreeBSD.org)                |

--- Comment #1 from Koop Mast <kwm at FreeBSD.org> ---
Submitter pointed out (via e-mail) that there are a few issues the current
freetype2 releases.

https://savannah.nongnu.org/bugs/?group=freetype

bug #56092: [regression] Awesomenauts crash after upgrading to 2.10.0 
https://savannah.nongnu.org/bugs/?56092
bug #56067: PCF defaultChar changes in 2.10 causes FontConfig to mis-detect(?)
charsets
https://savannah.nongnu.org/bugs/?56067

There is also:
http://git.savannah.gnu.org/cgit/freetype/freetype2.git/commit/?id=6986ddac1ece9404c9b640a512cbd99534205fda

There appears to be also a division by zero, not sure if this is a valid issue
or not. So deny the current patch until upstream can sort out these issues.

Also I run LLVM/Clang v7.0 scan-build command for print/freetype2 port:
-8<--
% cd freetype2
% scan-build70 -no-failure-reports --use-cc=clang70 --use-c++=clang++70 -o
../scan70 make
-->--

It reported following warning:
-8<--
<..>/freetype2/work/freetype-2.10.0/src/base/ftbitmap.c:979:24: warning:
Division by zero
      if ( FT_LONG_MAX / new_pitch < (int)final_rows )
           ~~~~~~~~~~~~^~~~~~~~~~~
1 warning generated.
-->8- 

Which isn't present in freetype 2.9.1

-- 
You are receiving this mail because:
You are the assignee for the bug.
You are on the CC list for the bug.


More information about the freebsd-gnome mailing list