ruby-bunny (2.14.4-4) [PTS] [DDPO]

COMMITS: VCS has seen 1 commit since the debian/2.14.4-4 tag

Git: https://salsa.debian.org/ruby-team/ruby-bunny.git
Enter a full Vcs-* header, supported schemes are: Vcs-Bzr, Vcs-Cvs, Vcs-Darcs, Vcs-Git, Vcs-Hg, Vcs-Mtn, Vcs-Svn.
For Vcs-Git append -b branch to select the branch name; append [subdir] if the debian/ directory is not in the repository root.
The next upload will reset the information from the source package headers.
Branch: master
Path: debian/changelog
Browser: https://salsa.debian.org/ruby-team/ruby-bunny
Last scan: 2020-10-21 17:14:05+00
Next scan: 2020-10-28 05:36:00+00
CI pipeline status: failed

Debian changelog in Git:

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 <sergiodj@debian.org>  Thu, 20 Aug 2020 10:55:09 -0400

This branch is 1 commit ahead of tag debian/2.14.4-4

Git log:

commit 9f06490f0202cb3429229edd74113a5fe671f66d
Author: Cédric Boutillier <boutil@debian.org>
Date:   Tue Sep 1 13:36:35 2020 +0000

    [ci skip] Update team name