Hi Tomas, On Fri, Jun 26, 2026 at 12:53 AM <[email protected]> wrote: > > > On Jun 25, 2026 17:15, Paul Gevers <[email protected]> wrote: > > > > Hi Sergei, > > > > On Wed, 10 Jun 2026 13:06:35 +0300 Sergei Golovan <[email protected]> > > wrote: > > > 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. > > > > 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.
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! -- Sergei Golovan
