Dear Maintainer,

I'm planning to update Erlang for Debian 14 (forky) to version 29.
And it appears that rabbitmq-server (4.0.5-14) currently in testing does not work
with Erlang 29, and rabbitmq-server (4.3.0-2) currently in unstable
builds fine (with tons of warnings about newly deprecated language
features, which is annoying but harmless) but also doesn't work because
its dependency (horus) uses Erlang internal ASM format which has
been changed in Erlang 29.

The attached patch makes rabbitmq-server working with Erlang 29 while
maintaining compatibility with the currently in unstable Erlang 27.
Please, consider appllying it and/or reporting the bug upstream.

I'm not sure that the patch fixes the bug optimally, it adds the necessary
field to an ASM code just before compiling it, but maybe it'd be
better to add it at the step of constructing the ASM code.

For now I'm setting the severity as normal, I'll bump it after Erlang 29
uploaded to unstable.

Cheers!

Hello,

Bug #1139624 in rabbitmq-server reported by you has been fixed in the
Git repository and is awaiting an upload. You can see the commit
message below and you can check the diff of the fix at:

https://salsa.debian.org/openstack-team/rabbitmq/rabbitmq-server/-/commit/c924d172403aa0e70317b34e502a6be3aac91fcb

(this message was generated automatically)
-- 
Greetings

https://bugs.debian.org/1139624

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 1139624@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Thomas Goirand <zigo@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 ftpmaster@ftp-master.debian.org)
Format: 1.8
Date: Thu, 11 Jun 2026 11:12:14 +0200
Source: rabbitmq-server
Architecture: source
Version: 4.3.0-3
Distribution: unstable
Urgency: medium
Maintainer: Debian OpenStack <team+openstack@tracker.debian.org>
Changed-By: Thomas Goirand <zigo@debian.org>
Closes: 1138887 1139624
Changes:
 rabbitmq-server (4.3.0-3) unstable; urgency=medium
 .
   * Add do-not-deprecate-transient_nonexcl_queues.patch, thanks to Sergei
     Golovan <sgolovan@debian.org> (Closes: #1138887).
   * Add erlang-29.patch thanks to Sergei Golovan also (Closes: #1139624).
Checksums-Sha1:
 04a6bba1cb9cfaa778b829694fbc13ff001a112f 2720 rabbitmq-server_4.3.0-3.dsc
 bc64db2e9c2d1e49f5d9a84b5e9095921e347497 47116 rabbitmq-server_4.3.0-3.debian.tar.xz
 3389765c18cdb000ce64e2aa54071a8382af9f9e 8861 rabbitmq-server_4.3.0-3_amd64.buildinfo
Checksums-Sha256:
 da4a639c4df55d3101c5581371a1dfb7555aca368d0744e951ecd55ce5ac3886 2720 rabbitmq-server_4.3.0-3.dsc
 add73c7233aa07fd756aaf7803cb9f7a934be810edcff3b78b86cf5f7bc8761b 47116 rabbitmq-server_4.3.0-3.debian.tar.xz
 aee5d5d1dfcb5e36de0944b4e909b19935a67a20070d2b1a481a4acc1b72082e 8861 rabbitmq-server_4.3.0-3_amd64.buildinfo
Files:
 1bee86e60025e52fa3834e7e4f708f07 2720 net optional rabbitmq-server_4.3.0-3.dsc
 fd09ec6320ba1881ec0226ab8a891368 47116 net optional rabbitmq-server_4.3.0-3.debian.tar.xz
 1c217b3633a3e92293686b800ee08de5 8861 net optional rabbitmq-server_4.3.0-3_amd64.buildinfo
-----BEGIN PGP SIGNATURE-----

iQIzBAEBCgAdFiEEoLGp81CJVhMOekJc1BatFaxrQ/4FAmoqfwUACgkQ1BatFaxr
Q/5slg/+OpN8sm+CIOOuCt9WQ05yzyCUPBmPSnBH+mAsG0JnO8azJ95dKQL/SRpC
urJ1FZPOQ18PVOSYyUQffOs8ljRugxmI0VFo5yVtFybv4jRAr4oH70p2yYiCrGez
v4cdBTiJF4dgkCh9A0SPD3xxA9d0Xa2k72Ndw4DbzCfKQU+H3OH/pAXvuxkSu+sK
zJqR4hD6Awdf6a8V5/BNBgCXMbbTG89BmnNs9cvF50Gr8DFlqf5L+QasUIFu9du0
YjRElFZTpjdPXn38/PxIwv+LwFCdHwXg0fzxJreHcMu/D4M8DKKPQArMJ1g5mKkx
HuOrvU2/oaI39u8h0uh4uJW9TOmBdAGSfGMYHf1yUDRFFRUHot6os4qvyDRz7pWs
VtV/eyXpCh8xlS5kZPYEdh5fIksu7RytstKdlQbVZ5tGi2ekrynkvxcmGqtV2qnF
haqC0G1MMnVzadH2OpBFDJpC4I7WaRnDDlRxi6US4Wn5abAaTZlJPNIBVF8N7v97
ASjUd2ySCD4isrYuY6B3JLtMDKeHEdu5xWyRYgJ1N+xmAmuy6gk6a4/FD/EQLjOG
VirBNjccLPokIFAJjxSqH9BUxjoV/8AZj3CGeNmJFGQ5rUpQQxtamTzs6AzC2H+9
ZWxPQKB3GK5qtDw1//PbMZnzzh0KwxuGenZ5fm1Ib6FTJw7u5Qs=
=UJBr
-----END PGP SIGNATURE-----

Hi Sergei,

For a next round of Erlang major upgrades, could you please add
versioned Breaks against known broken stuff to the erlang binaries to
ensure it doesn't migrate before the fix of reverse dependencies
migrate? rabbitmq-server was broken in testing because the fixed version
only migrated today.

Paul

It is documented upstream that rabbitmq is not yet compatible with Erlang 29. IMO Erlang 29 shouldn't have been uploaded to Sid to begin with.


Thomas

Hi Paul,

You're right, next time I will add versioned Breaks. I assumed that Erlang
won't advance to testing until autopkgtests for Erlang reverse dependencies
pass . Looks like things are more complicated than that.

Cheers!

Hi Tomas,

It is documented upstream that rabbitmq-server is not yet compatible
with Erlang 28 which was released a year ago. Also, upstream support
for Erlang 27 will end in May-June 2027. I don't think It's a good
idea to support an unsupported version for another 3 years. At least
now we have 5-6 months to fix bugs if there are any left.

Cheers!

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."

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.

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.

Normally, this type of updates have to go trough a transition period,
and are to be dealt with the release team.

Cheers,

Thomas Goirand (zigo)

Hi Thomas,

I don't think that choosing Erlang 28 for forky is a good idea. It's a
bit too old
already.

As far as I can tell, I did care about reverse dependencies. And for
rabbitmq-server as well.

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.

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!

Hi,


That's because the reverse dependency got fixed. The fixed version has a
*versioned* Depends on things from erlang, so the tests of the reverse
dependency got scheduled with erlang from unstable, passed *and counted
for passing* for erlang too (because of the versioned Depends).

Paul

Let's try to move forward. I'll try running my OpenStack CI with Erlang 29 and latest rabbit, to see how it goes.


Cheers,


Thomas