matrix-synapse (1.52.0-1~bpo10+1) buster-backports-sloppy; urgency=medium

  From this version on, Synapse will no longer be updated in the
  buster-backports-sloppy repository. Please upgrade to bullseye
  to continue using packaes from bullseye-backports.

 -- Andrej Shadura <andrewsh@debian.org>  Wed, 16 Feb 2022 13:59:34 +0100

matrix-synapse (1.51.0-1~bpo10+2) buster-backports-sloppy; urgency=medium

  The next Synapse release, 1.52, will be the last Synapse upload to
  buster-backports-sloppy. Please upgrade your system to bullseye to
  continue using packages provided by Debian backports, or switch to
  the packages provided by the upstream.

 -- Andrej Shadura <andrewsh@debian.org>  Wed, 09 Feb 2022 13:16:54 +0100

matrix-synapse (1.27.0-1~bpo10+3) buster-backports; urgency=medium

  Since Synapse won’t be included in Bullseye (see #982991 for more
  details), updating backports will soon no longer be possible. However,
  updates will still be uploaded to unstable and also to the new distribution
  channel: Debian Fasttrack.

  To learn more about Fasttrack and how to enable it, visit the project’s
  website: https://fasttrack.debian.net/

 -- Andrej Shadura <andrewsh@debian.org>  Tue, 09 Mar 2021 13:50:38 +0100

matrix-synapse (1.9.0-1) unstable; urgency=medium

  The default logging config now comes with the logging level for Synapse
  itself set to INFO, but some other modules and Twisted set to WARN.
  This verbosity should be fine for normal uses, but when troubleshooting,
  users may want to revert all WARNs to INFO or maybe even DEBUG.
  The future releases will try to align the defaults to the upstream’s
  one.

 -- Andrej Shadura <andrewsh@debian.org>  Thu, 23 Jan 2020 18:59:21 +0100

matrix-synapse (0.99.0-1) unstable; urgency=medium

  This version of the package introduces support for the Server-to-Server
  Spec r0.1. Since this version of the specification, self-signed
  certificates will no longer be valid for homeservers. While 0.99.0 still
  accepts self-signed certificates, the next release of Synapse will not.

  It is critical that you configure a valid TLS certificate. Synapse will
  not automatically invalidate or warn about existing self-signed
  certificates.

  Starting from 0.99.0, Synapse supports ACME protocol to request
  certificates from Let’s Encrypt, but this code is not yet available
  in Debian packages, which means that you need to set it up manually
  for now.

  Please note that if your homeserver runs under a different domain
  name than your server name, you will need to configure the .well-known
  resource; just having an SRV record will not be enough to federate
  with Synapse 1.0 servers.

  See /usr/share/doc/matrix-synapse/misc/MSC1711_certificates_FAQ.md.gz
  for more details.

 -- Andrej Shadura <andrewsh@debian.org>  Sat, 09 Feb 2019 15:21:23 +0100

matrix-synapse (0.34.0-1) unstable; urgency=medium

  From 0.34.0~rc2 on, matrix-synapse runs using Python 3. This contrasts
  with packages the upstream provides, where matrix-synapse is a Python 2
  version, and the Python 3 version is shipped as matrix-synapse-py3.

 -- Andrej Shadura <andrewsh@debian.org>  Fri, 21 Dec 2018 13:34:26 +0100
