Support for Fedora 39 #10232
-
Is your feature request related to a problem? Please describe.So i recently upgraded to fedora 39, like a month ago. Describe the solution you'd likeSupport for Fedora 39 Describe alternatives you've consideredNo response Additional contextNo response |
Beta Was this translation helpful? Give feedback.
Replies: 3 comments
-
There is nothing to support: our RPM package works just fine on Fedora releases between 33 and 39. See server logs for clues. If this was an upgrade to 3.12, most likely you haven't had all feature flags enabled before upgrading. |
Beta Was this translation helpful? Give feedback.
-
From php-amqplib/php-amqplib#1149: Our Erlang RPM (both the Fedora 38 and the CentOS Stream 9 versions) supports Fedora 39 just fine. If this is a development environment, your can remove and purge your installation (that is, its data directory) then install Erlang 26.2 and RabbitMQ 3.12.11. If you cannot afford to do that, you must install Erlang 25 and RabbitMQ 3.11.28, then enable all feature flags, then upgrade to Erlang 26 and RabbitMQ 3.12.11. Our RPM distribution guide explains what repositories you should use if you want the latest stuff. Fedora does not provide RabbitMQ 3.12 (or even the latest 3.11) in its repositories (other than Rawhide) but it does ship with Erlang 26. Just nuke the RabbitMQ and Erlang packages installed from Fedora repositories and follow RabbitMQ's RPM guide, please. |
Beta Was this translation helpful? Give feedback.
-
Apparently the Fedora-packaged RabbitMQ 3.11.10 RPM assumes that it supports Erlang 26 but that's not the case. RabbitMQ 3.12.x does support Erlang 26 but 3.12.10 is only available via Fedora 39 testing repositories or in Fedora Rawhide. In any case, a better solution is the same as for other operating systems: use the repositories maintained by Team RabbitMQ. |
Beta Was this translation helpful? Give feedback.
There is nothing to support: our RPM package works just fine on Fedora releases between 33 and 39.
See server logs for clues. If this was an upgrade to 3.12, most likely you haven't had all feature flags enabled before upgrading.