Bug 1943087 - hunspell: FTBFS with upcoming autoconf-2.71
Summary: hunspell: FTBFS with upcoming autoconf-2.71
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Fedora
Classification: Fedora
Component: hunspell
Version: rawhide
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: Caolan McNamara
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
: 1999453 (view as bug list)
Depends On:
Blocks: 1942967
TreeView+ depends on / blocked
 
Reported: 2021-03-25 12:52 UTC by Ondrej Dubaj
Modified: 2021-08-31 11:30 UTC (History)
7 users (show)

Fixed In Version: hunspell-1.7.0-10.fc35 hunspell-1.7.0-10.eln110
Clone Of:
Environment:
Last Closed: 2021-03-25 15:00:53 UTC
Type: ---
Embargoed:

Attachments (Terms of Use)

Description Ondrej Dubaj 2021-03-25 12:52:05 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 Caolan McNamara 2021-03-25 14:50:25 UTC 
The log says:
Can't exec "autopoint": No such file or directory at /usr/share/autoconf/Autom4te/FileUtils.pm line 293.
and autopoint is in gettext-devel while hunspell buildrequires just gettext so it might be that changing that to require gettext-devel instead would solve this
Comment 2 Fedora Update System 2021-03-25 15:00:53 UTC 
FEDORA-2021-f808b909a5 has been pushed to the Fedora 35 stable repository.
If problem still persists, please make note of it in this bug report.
Comment 3 Fedora Update System 2021-03-25 15:12:50 UTC 
FEDORA-2021-e4501e851b has been pushed to the Fedora ELN stable repository.
If problem still persists, please make note of it in this bug report.
Comment 4 Caolan McNamara 2021-08-31 08:58:09 UTC 
*** Bug 1999453 has been marked as a duplicate of this bug. ***
Note You need to log in before you can comment on or make changes to this bug.