Your message dated Mon, 20 Jan 2025 19:51:47 +0000
with message-id <e1tzxoj-00hhxu...@fasolo.debian.org>
and subject line Bug#1090027: fixed in rabbitmq-server 4.0.5-2
has caused the Debian Bug report #1090027,
regarding rabbitmq-server: broken with erlang 27
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)
--
1090027: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1090027
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: rabbitmq-server
Version: 3.10.8-4
Control: fixed -1 3.12.1-1.1
Severity: grave
Justification: renders package unusable
As mentioned in #1069929¹, rabbitmq-server does not work with Erlang 27.
Given Erlang 27 has been uploaded to unstable recently, rabbitmq-server
is now broken in unstable.
¹ https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1069929
(transition: erlang)
This manifests, for example, in the autopkgtest for debci², where a
client fails to connect to the server with with Errno::ECONNRESET.
² https://ci.debian.net/packages/d/debci/unstable/amd64/55129536/#S14
Here is a log excerpt in case the above link expires before you have
a chance to look at it:
----------------8<----------------8<----------------8<-----------------
2453s + debci enqueue ruby-defaults
2468s E, [2024-12-08T07:05:46.124736 #5020] ERROR -- #<Bunny::Session:0xcf8
guest@localhost:5672, vhost=/, addresses=[localhost:5672]>: Got an exception
when receiving data: Connection reset by peer (Errno::ECONNRESET)
2468s W, [2024-12-08T07:05:46.124847 #5020] WARN -- #<Bunny::Session:0xcf8
guest@localhost:5672, vhost=/, addresses=[localhost:5672]>: Exception in the
reader loop: Errno::ECONNRESET: Connection reset by peer
2468s W, [2024-12-08T07:05:46.124858 #5020] WARN -- #<Bunny::Session:0xcf8
guest@localhost:5672, vhost=/, addresses=[localhost:5672]>: Backtrace:
2468s W, [2024-12-08T07:05:46.124871 #5020] WARN -- #<Bunny::Session:0xcf8
guest@localhost:5672, vhost=/, addresses=[localhost:5672]>:
/usr/lib/ruby/3.1.0/socket.rb:452:in `__read_nonblock'
2468s W, [2024-12-08T07:05:46.124915 #5020] WARN -- #<Bunny::Session:0xcf8
guest@localhost:5672, vhost=/, addresses=[localhost:5672]>:
/usr/lib/ruby/3.1.0/socket.rb:452:in `read_nonblock'
2468s W, [2024-12-08T07:05:46.124924 #5020] WARN -- #<Bunny::Session:0xcf8
guest@localhost:5672, vhost=/, addresses=[localhost:5672]>:
/usr/share/rubygems-integration/all/gems/bunny-2.19.0/lib/bunny/cruby/socket.rb:58:in
`block in read_fully'
2468s W, [2024-12-08T07:05:46.124932 #5020] WARN -- #<Bunny::Session:0xcf8
guest@localhost:5672, vhost=/, addresses=[localhost:5672]>:
/usr/share/rubygems-integration/all/gems/bunny-2.19.0/lib/bunny/cruby/socket.rb:57:in
`loop'
2468s W, [2024-12-08T07:05:46.124940 #5020] WARN -- #<Bunny::Session:0xcf8
guest@localhost:5672, vhost=/, addresses=[localhost:5672]>:
/usr/share/rubygems-integration/all/gems/bunny-2.19.0/lib/bunny/cruby/socket.rb:57:in
`read_fully'
2468s W, [2024-12-08T07:05:46.124948 #5020] WARN -- #<Bunny::Session:0xcf8
guest@localhost:5672, vhost=/, addresses=[localhost:5672]>:
/usr/share/rubygems-integration/all/gems/bunny-2.19.0/lib/bunny/transport.rb:239:in
`read_fully'
2468s W, [2024-12-08T07:05:46.124955 #5020] WARN -- #<Bunny::Session:0xcf8
guest@localhost:5672, vhost=/, addresses=[localhost:5672]>:
/usr/share/rubygems-integration/all/gems/bunny-2.19.0/lib/bunny/transport.rb:261:in
`read_next_frame'
2468s W, [2024-12-08T07:05:46.124963 #5020] WARN -- #<Bunny::Session:0xcf8
guest@localhost:5672, vhost=/, addresses=[localhost:5672]>:
/usr/share/rubygems-integration/all/gems/bunny-2.19.0/lib/bunny/reader_loop.rb:74:in
`run_once'
2468s W, [2024-12-08T07:05:46.124974 #5020] WARN -- #<Bunny::Session:0xcf8
guest@localhost:5672, vhost=/, addresses=[localhost:5672]>:
/usr/share/rubygems-integration/all/gems/bunny-2.19.0/lib/bunny/reader_loop.rb:39:in
`block in run_loop'
2468s W, [2024-12-08T07:05:46.124982 #5020] WARN -- #<Bunny::Session:0xcf8
guest@localhost:5672, vhost=/, addresses=[localhost:5672]>:
/usr/share/rubygems-integration/all/gems/bunny-2.19.0/lib/bunny/reader_loop.rb:36:in
`loop'
2468s W, [2024-12-08T07:05:46.124990 #5020] WARN -- #<Bunny::Session:0xcf8
guest@localhost:5672, vhost=/, addresses=[localhost:5672]>:
/usr/share/rubygems-integration/all/gems/bunny-2.19.0/lib/bunny/reader_loop.rb:36:in
`run_loop'
2468s W, [2024-12-08T07:05:46.125006 #5020] WARN -- #<Bunny::Session:0xcf8
guest@localhost:5672, vhost=/, addresses=[localhost:5672]>: Will recover from a
network failure (no retry limit)...
2468s
/usr/share/rubygems-integration/all/gems/bunny-2.19.0/lib/bunny/concurrent/continuation_queue.rb:39:in
`block in poll': Timeout::Error (Timeout::Error)
----------------8<----------------8<----------------8<-----------------
I tried running the same test while pulling rabbitmq-server 3.12.1-1.1
from experimental, and it worked. Running the same test on testing, with
the previous Erlang and rabbitmq-server, also works.
-- System Information:
Debian Release: trixie/sid
APT prefers testing
APT policy: (900, 'testing'), (500, 'stable-security'), (500, 'unstable'),
(1, 'experimental')
Architecture: arm64 (aarch64)
Kernel: Linux 6.11.10-arm64 (SMP w/32 CPU threads)
Locale: LANG=pt_BR.UTF-8, LC_CTYPE=pt_BR.UTF-8 (charmap=UTF-8), LANGUAGE not set
Shell: /bin/sh linked to /usr/bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled
Versions of packages rabbitmq-server depends on:
ii adduser 3.137
ii erlang-base 1:25.3.2.12+dfsg-3
ii erlang-crypto 1:25.3.2.12+dfsg-3
ii erlang-eldap 1:25.3.2.12+dfsg-3
ii erlang-inets 1:25.3.2.12+dfsg-3
ii erlang-mnesia 1:25.3.2.12+dfsg-3
ii erlang-os-mon 1:25.3.2.12+dfsg-3
ii erlang-parsetools 1:25.3.2.12+dfsg-3
ii erlang-public-key 1:25.3.2.12+dfsg-3
ii erlang-runtime-tools 1:25.3.2.12+dfsg-3
ii erlang-ssl 1:25.3.2.12+dfsg-3
ii erlang-syntax-tools 1:25.3.2.12+dfsg-3
ii erlang-tools 1:25.3.2.12+dfsg-3
ii erlang-xmerl 1:25.3.2.12+dfsg-3
ii logrotate 3.22.0-1+b1
ii openssl 3.3.2-2
ii python3 3.12.6-1
ii socat 1.8.0.1-2
ii sysvinit-utils [lsb-base] 3.11-1
rabbitmq-server recommends no packages.
rabbitmq-server suggests no packages.
-- no debconf information
signature.asc
Description: PGP signature
--- End Message ---
--- Begin Message ---
Source: rabbitmq-server
Source-Version: 4.0.5-2
Done: Thomas Goirand <z...@debian.org>
We believe that the bug you reported is fixed in the latest version of
rabbitmq-server, which is due to be installed in the Debian FTP archive.
A summary of the changes between this version and the previous one is
attached.
Thank you for reporting the bug, which will now be closed. If you
have further comments please address them to 1090...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.
Debian distribution maintenance software
pp.
Thomas Goirand <z...@debian.org> (supplier of updated rabbitmq-server package)
(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive
administrators by mailing ftpmas...@ftp-master.debian.org)
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA256
Format: 1.8
Date: Mon, 20 Jan 2025 17:30:15 +0100
Source: rabbitmq-server
Architecture: source
Version: 4.0.5-2
Distribution: unstable
Urgency: medium
Maintainer: Debian OpenStack <team+openst...@tracker.debian.org>
Changed-By: Thomas Goirand <z...@debian.org>
Closes: 1090027
Changes:
rabbitmq-server (4.0.5-2) unstable; urgency=medium
.
* Works with Erlang 27 (Closes: #1090027).
* Removed erlang-erl-docgen build-depends.
* Depends on erlang >= 27.
* Fixed Extra # in debian/rabbitmq-env.conf thanks to g0tmi1k.
Checksums-Sha1:
c49d1f79fce93b8bc762d180097f1811b2d65b4c 2925 rabbitmq-server_4.0.5-2.dsc
45ffe4e88c2c1b304fff753e643ad6fb6fa54946 26800
rabbitmq-server_4.0.5-2.debian.tar.xz
a636de34c70c418f3da317b6819268ac61989869 8941
rabbitmq-server_4.0.5-2_amd64.buildinfo
Checksums-Sha256:
da1b99c34e9f65c19bad3e059af5e2fe957eb8bdeadb57e5b4b0df1516c1ae06 2925
rabbitmq-server_4.0.5-2.dsc
0f81031c643ed9dea3a6d139076cfed13734a2fd0c69f2f65b37d414fcd996a9 26800
rabbitmq-server_4.0.5-2.debian.tar.xz
3766eb83e41304765f55c6af43eb6d57b1ee67298700e6891d106f529852644c 8941
rabbitmq-server_4.0.5-2_amd64.buildinfo
Files:
44aefb874e8ff5f517b3409df57fccca 2925 net optional rabbitmq-server_4.0.5-2.dsc
20e9b783a0e17fbfc64e0fda2250ad75 26800 net optional
rabbitmq-server_4.0.5-2.debian.tar.xz
3635285a412a81d23efd7ef8e27e7a1d 8941 net optional
rabbitmq-server_4.0.5-2_amd64.buildinfo
-----BEGIN PGP SIGNATURE-----
iQIzBAEBCAAdFiEEoLGp81CJVhMOekJc1BatFaxrQ/4FAmeOphQACgkQ1BatFaxr
Q/6/uQ//Z3CkWIuvN4nB1tf+du5pKcm2m2xDPoH0fyX1RO0bKadLYJwGPtSeCvaE
7W85AlSmwGMWe8Dby8kXMMXXbEyxtg82pj8X/4v7PSU7cNSPq6S5cnvbBXaXOizP
SZMLsmRe6Kv34mVPxQQzNVAA3Xti4roX1PbN3cmIo5pM/jvjJ+EeMII7Tb9kZfTN
TIIxeX7xIzI0SMF9/wJlPhS949oXcFdkFmG3yPX0/y7uoAMlYPC+1NEHg4PtUtlV
524YM0fatjppSbaY/ZbIHukj27gzcEpGaW/2TruCJODD7OF5/DPSjXVUIMqaARc5
AaoB/SrNbI5dnkrtrPKEOEp86t5ELaWomRdXdIB2Tnju3p791xSOVpHwtkqLg37a
v0Yau8LjeOo9e3jEXbwqO/sJtyar0uWkHRazy4pXRZsVBSPOGlCQYQyjgI5Uy13c
MSD2CoJi3GkFPF5dDTeWvSgM4KnRMXHTQIg7nSgTpLgtnP+NAflgjKThShPHvpMp
pVyT7naRiKtyh8sBRraOXdae5jmwv/gMpBISQmqzMvLxBM8dEzQqSZM5cRtfuT1I
LXmpwqCpMUtFrsRrPQWFGeTSwNgdeT67McwA1Wlc0dhgKUjWankKrzU8Y/d9mXnM
KsDkZGpnN1EpEmw3OijDda3iFwJjalnVcOnY7HCVVmCQtmTzVq8=
=rKDm
-----END PGP SIGNATURE-----
pgpwnJrM1L6d9.pgp
Description: PGP signature
--- End Message ---
