Hi Thomas, On Fri, Jun 26, 2026 at 1:02 PM Thomas Goirand <[email protected]> wrote: > > Well, what you're saying is partly truth. From upstream site: > https://www.rabbitmq.com/docs/which-erlang#erlang-28-support > > "Erlang 28 is partially supported by RabbitMQ 4.3.x: upgrades of > clusters running Khepri has known issues directly related to the > breaking changes in Erlang 28 that equally affect Erlang 29."
I don't think that choosing Erlang 28 for forky is a good idea. It's a bit too old already. > > Though upgrades have been problematic for a long time, so I don't think > this really is a big issue, it's often OK to reset a cluster after an > upgrade. > > Also, after building rabbitmq-server 4.3.2, I did a few tests, and it > seem to me it was working, even with version 29 of Erlang. I may be > wrong though, as I didn't do a lot of tests (just created a queue, if I > remember well). > > Anyways, it is one thing to try to have everything up-to-date. It is > another to do it without caring for reverse-dependencies. As far as I can tell, I did care about reverse dependencies. And for rabbitmq-server as well. > > I would have appreciate if I was made aware of the upload long enough, > and had enough time to engage with upstream to solve the issue *before* > the upload of Erlang 29 to Sid. I don't think there was such an > emergency from the Debian perspective. Sorry about that. I did plan to upload Erlang 29 much later, but Elixir 1.20, which works with Erlang 27, apparently made regular expressions endianness-aware, so rabbitmq-server built with Erlang 27 and Elixir 1.20 on amd64 didn't work on s390x. And instead of trying to fix regexps (a bit pointless effort, since Erlang 29 does not have this problem) I rushed the upload of Erlang 29. > > Normally, this type of updates have to go trough a transition period, > and are to be dealt with the release team. There was a transition of Erlang (see [1], you haven't noticed that this bug did block the transition bug). It happened quicker than I expected though. [1] https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1138785 Cheers! -- Sergei Golovan
