Bug 2113210 - erlang-p1_acme: FTBFS in Fedora rawhide/f37
Summary: erlang-p1_acme: FTBFS in Fedora rawhide/f37
Keywords:
Status: CLOSED WORKSFORME
Alias: None
Product: Fedora
Classification: Fedora
Component: erlang-p1_acme
Version: 37
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: Peter Lemenkov
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks: F38FTBFS F37FTBFS F37FailsToInstall
TreeView+ depends on / blocked
 
Reported: 2022-08-01 23:26 UTC by Fedora Release Engineering
Modified: 2022-09-15 15:07 UTC (History)
4 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2022-09-15 15:07:26 UTC
Type: ---
Embargoed:


Attachments (Terms of Use)
build.log (1.22 KB, text/plain)
2022-08-01 23:26 UTC, Fedora Release Engineering
no flags Details
root.log (32.00 KB, text/plain)
2022-08-01 23:26 UTC, Fedora Release Engineering
no flags Details
state.log (848 bytes, text/plain)
2022-08-01 23:26 UTC, Fedora Release Engineering
no flags Details

Description Fedora Release Engineering 2022-08-01 23:26:05 UTC
erlang-p1_acme failed to build from source in Fedora rawhide/f37

https://koji.fedoraproject.org/koji/taskinfo?taskID=89770806


For details on the mass rebuild see:

https://fedoraproject.org/wiki/Fedora_37_Mass_Rebuild
Please fix erlang-p1_acme at your earliest convenience and set the bug's status to
ASSIGNED when you start fixing it. If the bug remains in NEW state for 8 weeks,
erlang-p1_acme will be orphaned. Before branching of Fedora 38,
erlang-p1_acme will be retired, if it still fails to build.

For more details on the FTBFS policy, please visit:
https://docs.fedoraproject.org/en-US/fesco/Fails_to_build_from_source_Fails_to_install/

Comment 1 Fedora Release Engineering 2022-08-01 23:26:07 UTC
Created attachment 1901067 [details]
build.log

Comment 2 Fedora Release Engineering 2022-08-01 23:26:09 UTC
Created attachment 1901068 [details]
root.log

file root.log too big, will only attach last 32768 bytes

Comment 3 Fedora Release Engineering 2022-08-01 23:26:10 UTC
Created attachment 1901069 [details]
state.log

Comment 4 Ben Cotton 2022-08-09 13:25:13 UTC
This bug appears to have been reported against 'rawhide' during the Fedora Linux 37 development cycle.
Changing version to 37.

Comment 5 Hans Ulrich Niedermann 2022-09-13 14:25:19 UTC
As suggested by Miroslav Suchý's mail on fedora-devel, I just tried the following on my F36 system:


# Run this only if you use default Fedora modules
# next time you run any DNF command default modules will be enabled again
sudo dnf module reset '*'

dnf --releasever=37 --setopt=module_platform_id=platform:f37 \
--enablerepo=updates-testing \
$(rpm -q fedora-repos-modular >/dev/null && echo --enablerepo=updates-testing-modular) \
--assumeno distro-sync


which resulted in problems updating a 5 packages, but this package erlang-p1_acme is the only which does not have a F37FailsToInstall bug (referenced to https://bugzilla.redhat.com/show_bug.cgi?id=2045109) yet:


Error: 
 Problem 1: problem with installed package erlang-riak_ensemble-3.0.10-1.fc36.x86_64
  - package erlang-riak_ensemble-3.0.10-1.fc37.x86_64 requires erlang(erl_nif_version) = 2.15, but none of the providers can be installed
  - erlang-riak_ensemble-3.0.10-1.fc36.x86_64 does not belong to a distupgrade repository
  - erlang-erts-24.3.4.4-1.fc36.x86_64 does not belong to a distupgrade repository
 Problem 2: problem with installed package erlang-xmpp-1.4.9-4.fc36.x86_64
  - package erlang-xmpp-1.4.9-4.fc36.x86_64 requires erlang(erl_nif_version) = 2.15, but none of the providers can be installed
  - package erlang-erts-24.3.4.4-1.fc36.x86_64 requires erlang-kernel(x86-64) = 24.3.4.4-1.fc36, but none of the providers can be installed
  - erlang-kernel-24.3.4.4-1.fc36.x86_64 does not belong to a distupgrade repository
 Problem 3: problem with installed package erlang-jiffy-1.0.5-4.fc36.x86_64
  - package erlang-jiffy-1.0.5-4.fc36.x86_64 requires erlang(erl_nif_version) = 2.15, but none of the providers can be installed
  - package erlang-erts-24.3.4.4-1.fc36.x86_64 requires erlang-stdlib(x86-64) = 24.3.4.4-1.fc36, but none of the providers can be installed
  - erlang-stdlib-24.3.4.4-1.fc36.x86_64 does not belong to a distupgrade repository
 Problem 4: problem with installed package erlang-esip-1.0.37-4.fc36.x86_64
  - package erlang-esip-1.0.37-4.fc36.x86_64 requires erlang(erl_nif_version) = 2.15, but none of the providers can be installed
  - package erlang-erts-24.3.4.4-1.fc36.x86_64 requires erlang-stdlib(x86-64) = 24.3.4.4-1.fc36, but none of the providers can be installed
  - package erlang-stdlib-24.3.4.4-1.fc36.x86_64 requires erlang-compiler(x86-64) = 24.3.4.4-1.fc36, but none of the providers can be installed
  - erlang-compiler-24.3.4.4-1.fc36.x86_64 does not belong to a distupgrade repository
 Problem 5: problem with installed package erlang-p1_acme-1.0.8-4.fc36.noarch
  - package erlang-p1_acme-1.0.8-4.fc36.noarch requires erlang-jiffy, but none of the providers can be installed
  - package erlang-p1_acme-1.0.8-4.fc36.noarch requires erlang-jiffy >= 1.0.5, but none of the providers can be installed
  - package erlang-jiffy-1.0.5-4.fc36.x86_64 requires erlang(erl_nif_version) = 2.15, but none of the providers can be installed
  - package erlang-erts-24.3.4.4-1.fc36.x86_64 requires erlang-stdlib(x86-64) = 24.3.4.4-1.fc36, but none of the providers can be installed
  - package erlang-stdlib-24.3.4.4-1.fc36.x86_64 requires erlang-crypto(x86-64) = 24.3.4.4-1.fc36, but none of the providers can be installed
  - erlang-crypto-24.3.4.4-1.fc36.x86_64 does not belong to a distupgrade repository
(try to add '--skip-broken' to skip uninstallable packages)

Comment 6 Miro Hrončok 2022-09-15 15:07:26 UTC
Hello,

Please note that this comment was generated automatically. If you feel that this output has mistakes, please contact me via email (mhroncok).

All subpackages of a package against which this bug was filled are now installable or removed from Fedora 37.

Thanks for taking care of it!


Note You need to log in before you can comment on or make changes to this bug.