Back to ruby-bunny PTS page

Accepted ruby-bunny 2.14.4-4 (source) into unstable



-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA256

Format: 1.8
Date: Thu, 20 Aug 2020 10:55:09 -0400
Source: ruby-bunny
Architecture: source
Version: 2.14.4-4
Distribution: unstable
Urgency: medium
Maintainer: Debian Ruby Extras Maintainers <pkg-ruby-extras-maintainers@lists.alioth.debian.org>
Changed-By: Sergio Durigan Junior <sergiodj@debian.org>
Closes: 968420
Changes:
 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)
Checksums-Sha1:
 651e2bb067ce974c604c1f33c11c9fee1d27cb3e 2242 ruby-bunny_2.14.4-4.dsc
 a6875cfb9fabc909b64166d87fbe3b83bf278679 7236 ruby-bunny_2.14.4-4.debian.tar.xz
 4a00ce7c971d3cb2044193ab977909818d6efaff 9818 ruby-bunny_2.14.4-4_amd64.buildinfo
Checksums-Sha256:
 26d89e2d9f60bb13df8fb828d7767a2af2e2922c435a1fb6779563de0dc323bb 2242 ruby-bunny_2.14.4-4.dsc
 af298d3ab2362531d0ac0fa62a187078988a491718a4a12f2e292b1850eb37bb 7236 ruby-bunny_2.14.4-4.debian.tar.xz
 c13979c7f738fe898037f825b68bf57743b96ac596971a7cfb0e5df0b37bc9e2 9818 ruby-bunny_2.14.4-4_amd64.buildinfo
Files:
 8d14a5eddd78329e1e9c130dff5b8bb2 2242 ruby optional ruby-bunny_2.14.4-4.dsc
 83e6cf88f0ff4bc9c860088bfadda463 7236 ruby optional ruby-bunny_2.14.4-4.debian.tar.xz
 d2ab842941c5a22b4de585b235993756 9818 ruby optional ruby-bunny_2.14.4-4_amd64.buildinfo

-----BEGIN PGP SIGNATURE-----

iQJJBAEBCAAzFiEEjtbD+LrJ23/BMKhw+COicpiDyXwFAl8+vWwVHGthbmFzaGly
b0BkZWJpYW4ub3JnAAoJEPgjonKYg8l8flEQAIMDxFkECPiWurbebuqwNegKRETc
TcPKAP2a03I1mE5m/4ODlCjXKAofFbZY8Npy/90xcmDbx8M/cnKmnXIYILLUFkC2
cjbMMO7X7H7jf7QZGJQlIvEI0uq4I/va0memWe0DaqKWWg1u62DRj/PE7j0DSIBU
v2UMMoqQISRvHkcBbVQq6z19xfjarwNesZc+sOKxorUTfQX6GY7HVcQ2m/k4IN78
ygjLHU4CQVFJKs+sPoxgoXQiYIpSJHJEIRGrF/zXKAVCub2JIz4/tNEPun9zG93J
9jBD3lzaFhMVCaUkDSPZ9FHwPylzmuJzfhR5FBEY22o7ERroio6cfcFAp3EVmmK9
AyDBOa+LPsAu6vyK3RJPbWZwops0U8H9MvO48dvOj+mN9QBLheoE5o5lfUQu2p86
Ee4a2pTFOpVKa3gmFLsW8dpWpz6ULFw29UraWncfwB0/EWbd/ilOvZIyy1+d5N9Q
vpvmjPY+jERXL8MT8ODdFEKO+U5q2TSyJYZ70edZOYxgAsZBKS1qfECNJo67RnSo
Ue0BaVddBeb+zn5PhJ3xmMUZiu5+HT45vow60xcp41uKJVLDAQAjPqabwpBIXqSt
Ug6kFgz/95NP+SNTSB0RX0qiM6l8CQd9Dp3XWA11YH53v79eg67R/ePfzZlHksdv
UgrgCSfoCEz26UX+
=iOXB
-----END PGP SIGNATURE-----