Bug 2363810
| Summary: | gettext-0.25 is available | ||||||||
|---|---|---|---|---|---|---|---|---|---|
| Product: | [Fedora] Fedora | Reporter: | Upstream Release Monitoring <upstream-release-monitoring> | ||||||
| Component: | gettext | Assignee: | Manish Tiwari <matiwari> | ||||||
| Status: | CLOSED RAWHIDE | QA Contact: | Fedora Extras Quality Assurance <extras-qa> | ||||||
| Severity: | unspecified | Docs Contact: | |||||||
| Priority: | unspecified | ||||||||
| Version: | rawhide | CC: | bugs.michael, dueno, i18n-bugs, matiwari, nphilipp, petersen, sundeep_anand | ||||||
| Target Milestone: | --- | Keywords: | FutureFeature, Triaged | ||||||
| Target Release: | --- | Flags: | matiwari:
mirror+
|
||||||
| Hardware: | Unspecified | ||||||||
| OS: | Unspecified | ||||||||
| Whiteboard: | |||||||||
| Fixed In Version: | gettext-0.25-1.fc43 | Doc Type: | --- | ||||||
| Doc Text: | Story Points: | --- | |||||||
| Clone Of: | Environment: | ||||||||
| Last Closed: | 2025-05-22 05:46:30 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: | 2366708 | ||||||||
| Bug Blocks: | |||||||||
| Attachments: |
|
||||||||
|
Description
Upstream Release Monitoring
2025-05-02 18:35:24 UTC
Created attachment 2088177 [details]
Update to 0.24.1 (#2363810)
the-new-hotness/release-monitoring.org's scratch build of gettext-0.24.1-1.fc40.src.rpm for rawhide failed http://koji.fedoraproject.org/koji/taskinfo?taskID=132225283 Releases retrieved: 0.25 Upstream release that is considered latest: 0.25 Current version/release in rawhide: 0.24-1.fc43 URL: https://www.gnu.org/software/gettext/ Please consult the package updates policy before you issue an update to a stable branch: https://docs.fedoraproject.org/en-US/fesco/Updates_Policy/ More information about the service that created this bug can be found at: https://docs.fedoraproject.org/en-US/package-maintainers/Upstream_Release_Monitoring Please keep in mind that with any upstream change, there may also be packaging changes that need to be made. Specifically, please remember that it is your responsibility to review the new version to ensure that the licensing is still correct and that no non-free or legally problematic items have been added upstream. Based on the information from Anitya: https://release-monitoring.org/project/898/ To change the monitoring settings for the project, please visit: https://src.fedoraproject.org/rpms/gettext Created attachment 2088854 [details]
Update to 0.25 (#2363810)
the-new-hotness/release-monitoring.org's scratch build of gettext-0.25-1.fc40.src.rpm for rawhide failed http://koji.fedoraproject.org/koji/taskinfo?taskID=132435537 1) Since the previous upgrade of gettext I've received this FTBFS report about Claws Mail: https://bugzilla.redhat.com/2366512 2) Downgrading to gettext 0.23.1, Claws Mail builds fine. 3) Upgrading to gettext 0.25 from koji, it breaks in new ways: + cd claws-mail-4.3.1 + autoreconf -f configure.ac:234: warning: macro 'AM_ICONV' not found in library configure.ac:245: warning: macro 'AM_GNU_GETTEXT_VERSION' not found in library configure.ac:246: warning: macro 'AM_GNU_GETTEXT' not found in library configure.ac: warning: AM_GNU_GETTEXT_VERSION or AM_GNU_GETTEXT_REQUIRE_VERSION is used, but not AM_GNU_GETTEXT configure.ac:99: error: possibly undefined macro: AC_LIB_PREFIX If this token and others are legitimate, please use m4_pattern_allow. See the Autoconf documentation. configure.ac:234: error: possibly undefined macro: AM_ICONV configure.ac:245: error: possibly undefined macro: AM_GNU_GETTEXT_VERSION configure.ac:246: error: possibly undefined macro: AM_GNU_GETTEXT autoreconf: error: /usr/bin/autoconf failed with exit status: 1 Any ideas, what's going on? (In reply to Michael Schwendt from comment #6) Since this also affects packages I maintain, I opened a new bug ticket to track this issue: https://bugzilla.redhat.com/show_bug.cgi?id=2366708 |