Comment 2 for bug 1891842

This bug was fixed in the package ruby-bunny - 2.14.4-4

---------------
ruby-bunny (2.14.4-4) unstable; urgency=medium

  * Team upload.

  [ Lucas Kanashiro ]
  * d/ruby-tests.rake: add a reminder to revisit the blacklisted spec file
  * d/control: update the Homepage url, the former does not work

  [ Sergio Durigan Junior ]
  * Adjust test infrastructure to use a customized rabbitmq-server.
    In order to perform our tests, we have to install the rabbitmq-server
    package. This means that when we build the package outside a chroot,
    the systemd service of rabbitmq-server is started automatically. This
    is expected behaviour, but it conflicts with what the setup step of
    our tests does: it tries to start its own instance of rabbitmq-server
    using a customized configuration file.
    In order to overcome this problem, it is possible to start another
    instance of rabbitmq-server listening at a different port. This is
    what this commit does, which ultimately fixes a FTBFS that happens
    when building ruby-bunny outside a chroot. Unfortunately, the
    solution here is a bit hacky and prone to failures, but it works
    reasonably well enough that I think it's safe to adopt it into
    package.
    - d/ruby-tests.rake: Use Socket.gethostname to compose the pidfile
      name.
    - d/rules: On override_dh_auto_install, adjust the local rabbitmq.conf
      file and instruct it to listen on localhost:16688; adjust several
      environment variables needed to properly start rabbitmq-server and
      ruby-bunny at the customized port; adjust the tests inside spec/ and
      make sure they explicitly connect to the rabbitmq-server instance
      running on the customized port. (Closes: #968420) (LP: #1891842)

 -- Sergio Durigan Junior <email address hidden> Thu, 20 Aug 2020 10:55:09 -0400