Hi!
A small followup with the autopkgtest results (see [1], I forgot to
add the link in the original bugreport).
Also, as far as I see, another autopkgtest for another package
(ruby-bunny) also fails
because of the same reason. It tries to use the
transient_nonexcl_queues feature, which
is disabled due to deprecation (see [2]).
While I think that it's better to adapt tools that work with
rabbitmq-server to the new
conditions (and don't use deprecated features), if you want to
re-enable it then you can
use the attached one-liner patch. It permits this feature by default.
On the other hand, now is the middle of the release cycle, so in my
opinion it's a
good time to temporarily break things. One has to report and/or fix
bugs at least in
ruby-bunny though.
[1] https://ci.debian.net/packages/r/rabbitmq-server/testing/amd64/71929664/
[2] https://ci.debian.net/packages/r/ruby-bunny/testing/amd64/71927945/
Cheers!
--
Sergei Golovan
--- a/deps/rabbit/src/rabbit_amqqueue.erl
+++ b/deps/rabbit/src/rabbit_amqqueue.erl
@@ -113,7 +113,7 @@
-rabbit_deprecated_feature(
{transient_nonexcl_queues,
- #{deprecation_phase => denied_by_default,
+ #{deprecation_phase => permitted_by_default,
doc_url => "https://blog.rabbitmq.com/posts/2021/08/4.0-deprecation-announcements/#removal-of-transient-non-exclusive-queues";,
callbacks => #{is_feature_used => {?MODULE, are_transient_nonexcl_used}}
}}).
