Description of problem: "dnf upgrade erlang-erts" (to update from erlang-21 to erlang-22) fails due to erlang-xmpp needing to be rebuilt. Version-Release number of selected component (if applicable): erlang-xmpp-1.3.4-2.fc31.x86_64 erlang-erts-21.3.8.6-2.fc31.x86_64 How reproducible: 100% Steps to Reproduce: 1. "dnf upgrade erlang-erts" Actual results: Problem 1: problem with installed package erlang-xmpp-1.3.4-2.fc31.x86_64 - package erlang-xmpp-1.3.4-2.fc31.x86_64 requires erlang(erl_nif_version) = 2.14, but none of the providers can be installed - cannot install both erlang-erts-22.0.7-2.fc31.x86_64 and erlang-erts-21.3.8.6-2.fc31.x86_64 - cannot install both erlang-erts-21.3.8.6-2.fc31.x86_64 and erlang-erts-22.0.7-2.fc31.x86_64 - cannot install the best update candidate for package erlang-erts-21.3.8.6-2.fc31.x86_64 Problem 2: problem with installed package erlang-stringprep-1.0.16-2.fc31.x86_64 - package erlang-stringprep-1.0.16-2.fc31.x86_64 requires erlang(erl_nif_version) = 2.14, but none of the providers can be installed - cannot install both erlang-erts-22.0.7-2.fc31.x86_64 and erlang-erts-21.3.8.6-2.fc31.x86_64 - cannot install both erlang-erts-21.3.8.6-2.fc31.x86_64 and erlang-erts-22.0.7-2.fc31.x86_64 - cannot install the best update candidate for package erlang-otp_mibs-21.3.8.6-2.fc31.x86_64 ============================================================================= Package Architecture Version Repository Size ============================================================================= Skipping packages with conflicts: (add '--best --allowerasing' to command line to force their upgrade): erlang-erts x86_64 22.0.7-2.fc31 updates-testing 2.2 M Transaction Summary ============================================================================= Skip 1 Package Expected results: Successful update of erlang-erts to Erlang 22. Additional info: # repoquery --requires erlang-xmpp-1.3.4-2.fc31.x86_64 erlang(erl_nif_version) = 2.14 erlang-ezlib >= 1.0.6 erlang-fast_tls >= 1.1.1 erlang-fast_xml >= 1.1.36 erlang-p1_utils >= 1.0.15 erlang-stringprep >= 1.0.16 libc.so.6(GLIBC_2.14)(64bit) rtld(GNU_HASH) # repoquery --provides erlang-erts-22.0.7-2.fc31.x86_64 bundled(pcre) = 8.33 erlang(erl_drv_version) = 3.3 erlang(erl_nif_version) = 2.15 erlang-erts = 22.0.7-2.fc31 erlang-erts(x86-64) = 22.0.7-2.fc31 # repoquery --provides erlang-erts-21.3.8.6-2.fc31.x86_64 bundled(pcre) = 8.33 erlang(erl_drv_version) = 3.3 erlang(erl_nif_version) = 2.14 erlang-erts = 21.3.8.6-2.fc31 erlang-erts(x86-64) = 21.3.8.6-2.fc31 # Basically it looks like every package in Fedora which requires "erlang(erl_nif_version) = 2.14" must be rebuilt with Erlang 22, and thus with a new requirement "erlang(erl_nif_version) = 2.15". The following list of packages might be affected, but I am hoping to trigger a mass rebuild with this bug: erlang-xmpp erlang-esip erlang-riak_ensemble erlang-stringprep erlang-snappy erlang-skerl erlang-sd_notify erlang-mqtreee erlang-js erlang-iconv erlang-hyper erlang-fast_yaml erlang-fast_xml erlang-fast_tls erlang-emmap erlang-eleveldb erlang-ebloom erlang-cl erlang-bitcask erlang-basho_metrics
Right now rebar is broken on Fedora 31+. This is preventing Erlang packages from being built.
Same with rabbitmq-server: "nothing provides erlang(erl_nif_version) = 2.14 needed by erlang-sd_notify-1.0-11.fc31.x86_64" Will these packages be rebuilt before the release?
This also breaks ejabberd, and blocks upgrading from F30.
This update should fix ejabberd and all of its dependencies: https://bodhi.fedoraproject.org/updates/FEDORA-2019-7d35d80acd
Thanks for the work to fix this issues. I tried to find an issue tracking the rebar problem in order to gauge an eta for a fix. Updating or applying the fix above does not seem to fix the issues on getting rabbitmq-server running on an out of the box Fedora 31. Please advice.
Hi espenfl, It looks like you just need erlang-sd_notify*, which is included in the same ejabberd update I listed above: https://bodhi.fedoraproject.org/updates/FEDORA-2019-7d35d80acd Once that update goes stable, it will be possible to install on F31. Or, you can --enablerepo updates-testing to get the dependencies you need. * You also need some of its dependencies, which also seem to be in updates-testing right now.
I believe this is resolved now, but feel free to reopen if you disagree. Thanks for the report!