Your message dated Tue, 17 Dec 2024 16:13:23 +0100
with message-id <d82563a0-62ce-44f1-aa19-812d8a4ee...@infomaniak.com>
and subject line Fixed
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

Attachment: signature.asc
Description: PGP signature


--- End Message ---
--- Begin Message ---
This was fixed by the upload of 4.0.5-1.
Looks like I uploaded the version *before* I added the Closes: in the debian/changelog.

Cheers,

Thomas

--- End Message ---

Reply via email to