Bug 1943039 - ncmpcpp: FTBFS with upcoming autoconf-2.71
Summary: ncmpcpp: FTBFS with upcoming autoconf-2.71
Keywords:
Status: CLOSED RAWHIDE
Alias: None
Product: Fedora
Classification: Fedora
Component: ncmpcpp
Version: rawhide
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: Dominic Hopf
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks: 1942967
TreeView+ depends on / blocked
 
Reported: 2021-03-25 12:46 UTC by Ondrej Dubaj
Modified: 2021-05-04 17:54 UTC (History)
2 users (show)

Fixed In Version:
Clone Of:
Environment:
Last Closed: 2021-05-04 17:54:14 UTC
Type: ---
Embargoed:


Attachments (Terms of Use)

Description Ondrej Dubaj 2021-03-25 12:46:07 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 Ondrej Dubaj 2021-04-12 07:12:24 UTC
Gentle ping.

Comment 2 Ondrej Dubaj 2021-05-04 07:54:23 UTC
Gentle ping.

Comment 3 Dominic Hopf 2021-05-04 17:18:39 UTC
Greetings and thanks very much for reporting. I'm sorry I'm sometimes a bit laggy in responding to issues. I just followed the steps to build stuff locally using mock as described on the wiki page above to reproduce and fix the issues. Other than I expected the build worked fine without any issues and I have some RPMs in my /var/lib/mock/odubaj-autoconf-2.70_fedora-rawhide-x86_64/result. I uploaded the stuff here for review: https://dmaphy.fedorapeople.org/ncmpcpp/.

Unfortunately the Copr build seems to be too old and no results are available anymore there. Are you able to trigger a rebuild there to see if the build still fails? Probably with a bit of luck it builds there as well now, we'll see.

Comment 4 Ondrej Dubaj 2021-05-04 17:54:14 UTC
Build succeeded, thanks for your effort!

Closing this issue.


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