Skip to content

Update libiconv-version to 1.19 from 1.18#47

Open
zosopentoolsmain wants to merge 1 commit intomainfrom
bump-libiconv-version-1.19
Open

Update libiconv-version to 1.19 from 1.18#47
zosopentoolsmain wants to merge 1 commit intomainfrom
bump-libiconv-version-1.19

Conversation

@zosopentoolsmain
Copy link
Copy Markdown

No description provided.

@augmentcode
Copy link
Copy Markdown

augmentcode Bot commented Apr 30, 2026

🤖 Augment PR Summary

Summary: Updates the port to build GNU libiconv 1.19 (from 1.18) by bumping the version used for the stable source tarball download.

Why: Aligns this port with the latest upstream stable release referenced via the automated version bump mechanism.

🤖 Was this summary useful? React with 👍 or 👎

Copy link
Copy Markdown

@augmentcode augmentcode Bot left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Review completed. 1 suggestion posted.

Fix All in Augment

Comment augment review to trigger a new review at any time.

Comment thread buildenv
@@ -1,5 +1,5 @@
# bump: libiconv-version /LIBICONV_VERSION="(.*)"/ https://ftp.gnu.org/gnu/libiconv/|re:/href="libiconv-([\d.]+).tar.gz"/$1/|semver:*
LIBICONV_VERSION="1.18"
LIBICONV_VERSION="1.19"
Copy link
Copy Markdown

@augmentcode augmentcode Bot Apr 30, 2026

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LIBICONV_VERSION was bumped to 1.19, but the repo’s .gitignore still ignores libiconv-1.18/; if the build extracts into a versioned directory, this may start showing up as an untracked artifact after builds.

Severity: low

Fix This in Augment

🤖 Was this useful? React with 👍 or 👎, or 🚀 if it prevented an incident/outage.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant