Log message:
*: revebump for new brotli option for freetype2

Addresses PR 57693

Log message:
libass: updated to 0.17.1

libass (0.17.1)
* Fix buffer overread if soft-wrapping occurred and
  ASS_FEATURE_WHOLE_TEXT_LAYOUT was enabled via API or due to Encoding -1
  (bug introduced in 0.16.0)
* x86: detect GNU Hurd and configure NASM appropriately

Log message:
*: Recursive revbup from graphics/freetype2

Log message:
libass: updated to 0.17.0

libass (0.17.0)
* Fix various parts relating to automatic linebreaking
* Fix rendering when hinting was enabled and fontsizes or scales are zero
* Switch build to a non-recursive setup for improved parallelism
* Improve quality of SSA Effects movement
* Further documentation improvements
* Completely invalid Events are now discarded during parsing

* Introduction of LayoutRes{X,Y} script headers
* New AlphaLevel style override to set all alpha values while keeping the color
* Add ASS_FEATURE_WRAP_UNICODE to allow automatic linebreaks in accordance
  with the Unicode line breaking algorithm instead of ASS' much stricter
  breaking rules. For the feature to be available at runtime, libass must be
  linked against the new optional dependency libunibreak.

* Improve VSFilter compatibility:
  * Fix premature truncation of animated alphas (was a 0.15.0 regression)
  * Fix handling of small delay parameters for legacy SSA Effects
  * Fix x-scaling with PlayResX
  * Fix x-scaling for anamorphic video
    (except for \be whose scaling remains buggy in general)
  * Support SSA's AlphaLevel style field
  * Support the \kt override tag from VSFilter's v4++ set
  * Parse ScriptType headers
  * Parse integer header, style and event field values like VSFilter
  * Ignore trailing whitespace in an event's text

Log message:
libass: updated to 0.16.0

libass (0.16.0)
 * Fix missing `-framework` options in libass.pc on macOS
 * Fix missing GDI or DirectWrite options in libass.pc on Win32
 * Fix crashes with fonts missing Postscript names and without one
   being synthesised by the font provider
 * Fix crashes on negative fontsizes and some overflows
 * Fix a rare memory leak introduced in 0.13.0
 * Fix minimum dependency versions in configure and our pc-file
 * Fix our public headers for use with GCC versions between 3.1.0 and 4.5.0
   (was a regression introduced in 0.15.0)
 * x86: Fix potential buffer over-read by 16 bytes with AVX2 assembly
     when large tiles are not enabled (the default)
 * x86: Fix PIC flags not being interpreted by the assembler, breaking the
     asm-enabled build setup on NetBSD and OpenBSD. On 32-bit x86, if the toolchain
     requires PIC objects and relies on compiler defaults to get PIC implicitly,
     you need to pass `--with-pic` to configure to ensure NASM always produces
     PIC objects
 * x86: Fix AVX support not being detected on non-Intel CPUs and some VMs
 * x86: Fix CPUID being used on CPUs not supporting the instruction (<= i486)
     and the way it is used for CPUs with less than 7 CPUID-leafs
     which could lead to crashes due to illegal instructions
 * MS Windows-only issue: Fix crashes with FreeType >= 2.11.1 on Win32
     when rendering strikethrough or underline

 * Improve `\iclip` quality
 * Improve quality of very small outlines
 * Switch to wyhash for much better cache performance
 * Propagate ZWJ/ZWNJ effects across glyph run boundaries
 * Do not depend on compiler-specific defines to actually use built assembly
 * Expand documentation and fix mistakes in it
 * configure now errors out if an explicitly requested feature is unavailable
 * MS Windows-only issue: ease linking against static/shared GNU FriBidi

 * Add ASS_FEATURE_WHOLE_TEXT_LAYOUT to apply bidi, shaping and \fay
     to the entire unsplit event text. The non-portable `Encoding=-1` mode
     always behaves as if the feature were enabled
 * MS Windows-only issue: add support for arbitrary Unicode paths;
     see documentation of related functions for details

 * Improve VSFilter compatibility
    * Do not treat format lines using `Actor` in place of `Name`
      as custom format lines. The former is used by VSFilter itself,
      the latter by Aegisub
    * Run bidi and shaping on each glyph run separately by default
    * Match VSFilter's \fsp effects on bidi and shaping
    * Match VSFilter's \fay behaviour
    * Support non-Unicode font cmaps when Win32 API or iconv
      is available and can convert to the relevant encoding
    * Treat empty clip outlines as if everything was outside the clip
      not inside (was a 0.14.0 regression)
    * Parse integer parameters of override tags more like VSFilter

Log message:
revbump for icu and libffi

Log message:
multimedia: Replace RMD160 checksums with BLAKE2s checksums

All checksums have been double-checked against existing RMD160 and
SHA512 hashes

The following distfiles could not be fetched (for legal reasons?):

./multimedia/adobe-flash-player/distinfo \ 
adobe-flash-player-32.0.0.465/flash_player_npapi_linux.i386.tar.gz
./multimedia/adobe-flash-player/distinfo \ 
adobe-flash-player-32.0.0.465/flash_player_npapi_linux.x86_64.tar.gz
./multimedia/libdvdcss/distinfo libdvdcss-1.4.3.tar.bz2

Log message:
multimedia: Remove SHA1 hashes for distfiles

Log message:
libass: updated to 0.15.2

Release 0.15.2

This is a bug fix release without API or ABI changes, mainly to fix more known \ 
0.15.0 and 0.15.1 regressions. But as a bonus, it is now possible to build the \ 
DirectWrite system font provider for Microsoft’s Universal Windows Platform \ 
(UWP).

Two known minor 0.15.x DirectWrite system font regressions remain:

when a font is attached/memory-loaded but a different (non-attached) style of \ 
the same font is used by the subtitles
(only the attached style[s] will be used; this also affects Core Text since \ 
0.13.0 but not Fontconfig);

in the unlikely case that the full name of a system font equals the family name \ 
of another system font
(only the family name matches will be found).

Also please note that our IRC channel #libass has moved from freenode.net to \ 
Libera.Chat, and all presence on freenode.net has been fully retired.

Changes:

Fix some known 0.15.x regressions:
Fix Core Text font fallback failing on some fonts with multiple names
Fix DirectWrite failing to look up any but the first loaded variant of system fonts
Fix some format string bugs, which could lead to garbled log messages or on some \ 
platforms crashes
Fix ass_set_fonts_dir failing to load long paths
Better handling of control characters that have no associated font glyphs
DirectWrite: font lookup is now closer to VSFilter
DirectWrite: this font provider can now be built for UWP

Log message:
libass: updated to 0.15.1

Release 0.15.1

This is purely a bug fix and polish release, with no significant API or ABI changes.

The only API change is that ass_add_font is now declared to accept const char *. \ 
Previously it took only char *, but const has worked in practice since the very \ 
first standalone libass release.

Fix currently known 0.15.0 regressions:
Fix crashing on some ASS files with embedded fonts
Fix total font fallback failure with some fonts on Core Text
Fix embedded and memory fonts not actually being used unless ass_set_fonts was \ 
called after they have been added
Fix events assuming the largest xbord-value of a preceding event of the same \ 
frame during collision handling
Fix \fscx0 and \fscy0 making more text disappear than they should
Fix shift in vertical positioning of some right-to-left events with \an4-6, \ 
\pos, \move or Scroll effects
Fix imprecise output for \be with huge argument
Fix the --enable-large-tiles configure switch doing nothing
Fix output of ASM-enabled builds deviating from non-ASM builds
Fix ASM-builds on Haiku and 32-bit *BSDs
Overhaul x86 assembly for better performance and to allow ASM-enabled PIC-builds \ 
on 32-bit
Reduce temporary allocation in rendering
DirectWrite: request fonts on demand for better performance and improved \ 
compatibility with external on-demand font activation
Log libass version numbers upon renderer startup
Accept pointers to const as arguments to ass_add_font
Improve VSFilter compatibility:
Disregard zero area events in collision handling
Do not apply \fsp to vector drawings
Fix bug preventing cutting out glyphs from border & shadow with abnormal \ 
\fad values (or causing aliasing artifacts in some cases with normal values)