opus 1.3~beta+20180516-1 source package in Debian

Changelog

opus (1.3~beta+20180516-1) unstable; urgency=medium

  * Snapshot from 652c4559f593d3aad78bd5c85a216eeae7859429 as a preview of
    patches pending for the 1.3 release.  The main motivation for doing this
    now is to pull in the fix for the PLC regression introduced just before
    1.2~alpha2, which Closes: #898690, and to get some broader testing on the
    new hardening checks before flipping the switch to enable those by default
    upstream.
  * Fix celt_pitch_xcorr() ARM jump table compiling error for a bug introduced
    in 1.2-rc1.
  * Better rate allocation for stereo SILK in hybrid mode.
  * Add RNN for VAD and speech/music classification.
  * Fixing bandwidth detection for 24 kHz analysis.
  * Enable RFC 8251 changes by default.
  * Better tuning for low-bitrate music.
  * Don't set _FORTIFY_SOURCE and -fstack-protector as part of the packaging
    anymore, the upstream build system will add them where they are supported
    and needed now.
  * Build with --enable-hardening, which isn't related to the compile options
    above, but instead includes additional opus-specific runtime sanity checks
    which are cheap and certain enough to use in production builds.
  * Use dh compat 9, not because it actually brings anything new which we need
    here, but it hushes the increasingly insistent warnings about deprecated
    compat levels, and is a baseline supported by all of the releases we still
    need to be able to support.  I'm going to say this Closes: #810258, since
    the rest of the 'modernisation' there mostly isn't helpful.  We've already
    been running the tests since the very first release, we release directly
    from upstream git and maintain upstream patches there, so format 3(quilt)
    adds nothing but pain, and we have upstream build and install targets that
    are designed to cleanly separate the -arch specific and -indep components,
    so regressing to make those codependent isn't very appealing either.  It
    would have also broken support for building where m-a wasn't supported,
    though that's less of a problem today than it was previously.

 -- Ron Lee <email address hidden>  Thu, 17 May 2018 16:07:39 +0930