Bug 1943036

Summary: mpich: FTBFS with upcoming autoconf-2.71
Product: [Fedora] Fedora Reporter: Ondrej Dubaj <odubaj>
Component: mpichAssignee: Zbigniew Jędrzejewski-Szmek <zbyszek>
Status: CLOSED RAWHIDE QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: rawhideCC: dakingun, zbyszek
Target Milestone: ---Keywords: Reopened
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2021-07-01 11:22:38 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Bug Depends On:    
Bug Blocks: 1942967    

Description Ondrej Dubaj 2021-03-25 12:45:45 UTC
Your package fails to build with the newest upcoming autoconf-2.71, which is part of a wide Fedora change. Please see the attached copr: https://copr.fedorainfracloud.org/coprs/odubaj/autoconf-2.70/packages/. More information about testing your package when building with autoconf available here: https://fedoraproject.org/wiki/Changes/Autoconf_271#How_To_Test

Comment 1 Zbigniew Jędrzejewski-Szmek 2021-03-28 11:44:10 UTC
From the copr build log:

warning: line 45: Possible unexpanded macro in: Requires:       (python(abi) = %{python3_version} if python3)
warning: line 104: Possible unexpanded macro in: Requires:       python(abi) = %{python3_version}
error: %changelog not in descending chronological order

This doesn't look related to autoconf stuff at all. Is the copr build set up correctly?

Comment 2 Ondrej Dubaj 2021-03-29 06:19:22 UTC
This is automatically created issue, as this package has failed to build with autoconf-2.71. No details were investigated.

Comment 3 Ondrej Dubaj 2021-04-12 07:12:42 UTC
Gentle ping.

Comment 4 Zbigniew Jędrzejewski-Szmek 2021-04-12 09:17:11 UTC
This original issue was a stupid %changelog incongruity, that was fixed in the rawhide branch when
this was originally reported. But I now see that there's a separate issue that seems to be related
to autoconf. I'll look into it.

Comment 5 Ondrej Dubaj 2021-05-04 07:53:34 UTC
Hi, any updates to this issue ?

Thanks.

Comment 6 Zbigniew Jędrzejewski-Szmek 2021-05-17 08:09:15 UTC
https://src.fedoraproject.org/rpms/mpich/c/0d1f44c9a8ba602bc83d3ba196464f705d2aadcd?branch=rawhide
fixes the issue. I simply removed the part of the configure.ac script that was causing problems
because I couldn't figure out how to fix it. If looking at the patch you understand what was wrong,
let me know, so I can try to tell upstream how to fix it.

Do I need to rebuild it for you to pick it up?

Comment 7 Ondrej Dubaj 2021-07-01 10:38:27 UTC
Thank you for your effort! There is no need to rebuild the package now, after moving to autoconf-2.71 a mass rebuild will be probably scheduled. All seems good now

https://copr.fedorainfracloud.org/coprs/odubaj/autoconf-2.70/package/mpich/

Thank you.

Comment 8 Zbigniew Jędrzejewski-Szmek 2021-07-01 11:22:38 UTC
Let's close this then.