Bug 2046755 - mpir: FTBFS in Fedora rawhide/f36
Summary: mpir: FTBFS in Fedora rawhide/f36
Keywords:
Status: CLOSED WONTFIX
Alias: None
Product: Fedora
Classification: Fedora
Component: mpir
Version: 36
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: Ben Beasley
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On: 2045772
Blocks: F36FTBFS F37FTBFS 2050761
TreeView+ depends on / blocked
 
Reported: 2022-01-27 09:25 UTC by Fedora Release Engineering
Modified: 2022-02-17 17:44 UTC (History)
6 users (show)

Fixed In Version:
Clone Of:
Environment:
Last Closed: 2022-02-17 17:44:14 UTC
Type: ---
Embargoed:


Attachments (Terms of Use)
build.log (32.00 KB, text/plain)
2022-01-27 09:25 UTC, Fedora Release Engineering
no flags Details
root.log (32.00 KB, text/plain)
2022-01-27 09:25 UTC, Fedora Release Engineering
no flags Details
state.log (954 bytes, text/plain)
2022-01-27 09:25 UTC, Fedora Release Engineering
no flags Details

Description Fedora Release Engineering 2022-01-27 09:25:09 UTC
mpir failed to build from source in Fedora rawhide/f36

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


For details on the mass rebuild see:

https://fedoraproject.org/wiki/Fedora_36_Mass_Rebuild
Please fix mpir 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,
mpir will be orphaned. Before branching of Fedora 37,
mpir 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-01-27 09:25:12 UTC
Created attachment 1855895 [details]
build.log

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

Comment 2 Fedora Release Engineering 2022-01-27 09:25:14 UTC
Created attachment 1855896 [details]
root.log

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

Comment 3 Fedora Release Engineering 2022-01-27 09:25:15 UTC
Created attachment 1855897 [details]
state.log

Comment 4 Ben Beasley 2022-01-31 18:37:07 UTC
One test has started failing with GCC 12. I won’t be able to fix it.

Since mpir is no longer developed upstream [1], and there is only one remaining dependent package (libalkimia), my plan is to try to get libalkimia switched over to using only GMP, and then retire MPIR. I think this would be a good plan even if the tests were still passing.

If I can’t manage to retire MPIR cleanly in time for F36, I’ll just skip the failing test.

[1] https://groups.google.com/g/mpir-devel/c/qTOaOBuS2E4?hl=en

Comment 5 Ben Beasley 2022-01-31 18:51:11 UTC
The tests currently still pass on x86_64 (only): https://koji.fedoraproject.org/koji/taskinfo?taskID=82196332

Comment 6 Ben Beasley 2022-02-02 15:23:14 UTC
I have submitted a PR for libalkimia: https://src.fedoraproject.org/rpms/libalkimia/pull-request/3

Comment 7 Ben Beasley 2022-02-04 13:38:42 UTC
The libalkimia PR was merged (thanks!) but for some reason, I’m not seeing the latest build of libalkimia (libalkimia-8.0.3-8.fc36) in the buildroot yet. I’m waiting for that. Then kmymoney might need a tweak and/or rebuild.

Comment 8 Ben Beasley 2022-02-04 13:43:15 UTC
Actually, not only is it in the buildroot (koji wait-repo --build=libalkimia-8.0.3-8.fc36 f36-build), but “mock -r fedora-36-x86_64 --enablerepo=local -i libalkimia-qt5” now installs libalkimia-qt5-8.0.3-8.fc36.x86_64. I must have had stale metadata or something.

Comment 9 Ben Beasley 2022-02-04 14:53:55 UTC
I’ll wait for a fresh Rawhide compose to confirm whether all mpir dependencies are really removed. Then I will use the devel mailing list to announce my intent to retire mpir beginning with F36.

Comment 10 Ben Cotton 2022-02-08 20:15:33 UTC
This bug appears to have been reported against 'rawhide' during the Fedora 36 development cycle.
Changing version to 36.

Comment 11 Ben Beasley 2022-02-17 17:44:14 UTC
The mpir package has been retired in F36/branched and F37/rawhide, with the message “Unmaintained upstream; FTBFS with GCC 12 due to a failing test; and all dependent packages have been migrated to GMP.”


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