puma (6.6.0-4)

  Added the capability to re-generate test certificates in the examples
  directory. This should require installing
  - default-jre, and
  - ruby-certificate-authority
  which are currently not listed as dependencies of this package. You can also
  use faketime to run the upstream tests in a future date to test if the
  certificates will be valid throughout the Debian release support cycle.

  Note that these certificates are not being re-generated during build time
  because the examples/generate_all_certs script depends on the keytool binary
  shipped in the JRE package (we do not want to build depend on Java just for
  this). It should be possible to re-write the script to use the minijks
  package instead (written in Go) so we can always generate these certificates
  during package builds.

puma (4.3.1-1)

  Several tests have been disabled by default:

  - test/test_puma_server_ssl.rb has been disabled because all tests fail
    randomly. However these tests have never been performed in puma 3.x and
    they also work randomly. So until someone can look into them and fix them,
    we decided to not run them (see also #921931).

  - test_control_for_ssl (test/test_cli.rb) and
    test_control_ssl (test/test_pumactl.rb) show similar issues and don't seem
    to imply that the package fails to work. So they have been disabled too.

 -- Daniel Leidert <dleidert@debian.org>  Wed, 05 Feb 2020 23:51:51 +0100
