Your message dated Wed, 29 Dec 2021 12:35:36 +0100
with message-id <[email protected]>
and subject line Already fixed
has caused the Debian Bug report #958468,
regarding rabbitmq-server startup timeouts differ between SysV and systemd
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 [email protected]
immediately.)
--
958468: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=958468
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
Package: rabbitmq-server
Severity: normal
Dear Maintainer,
The startup times of the SysV and systemd start scripts were recently
adjusted [1]. These changes should be merged into the Debian package.
[1] https://github.com/rabbitmq/rabbitmq-server-release/pull/129
-- System Information:
Debian Release: bullseye/sid
APT prefers unstable
APT policy: (500, 'unstable')
Architecture: amd64 (x86_64)
Kernel: Linux 5.4.0-26-lowlatency (SMP w/8 CPU cores; PREEMPT)
Locale: LANG=C, LC_CTYPE=C.UTF-8 (charmap=UTF-8), LANGUAGE=C (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: unable to detect
Versions of packages rabbitmq-server depends on:
ii adduser 3.118
pn erlang-base | erlang-base-hipe <none>
pn erlang-crypto <none>
pn erlang-eldap <none>
pn erlang-inets <none>
pn erlang-mnesia <none>
pn erlang-os-mon <none>
pn erlang-parsetools <none>
pn erlang-public-key <none>
pn erlang-runtime-tools <none>
pn erlang-ssl <none>
pn erlang-syntax-tools <none>
pn erlang-tools <none>
pn erlang-xmerl <none>
pn locales-all <none>
pn logrotate <none>
ii lsb-base 11.1.0
ii python3 3.8.2-3
pn socat <none>
rabbitmq-server recommends no packages.
rabbitmq-server suggests no packages.
--- End Message ---
--- Begin Message ---
Hi,
I just had a look, and it looks like to me that it's already fixed in
the Debian package (and it's been so for a long time already). So I'm
closing this bug.
Cheers,
Thomas Goirand (zigo)
--- End Message ---
