From: Adolf Belka <adolf.belka@ipfire.org>
To: development@lists.ipfire.org
Cc: Adolf Belka <adolf.belka@ipfire.org>
Subject: [PATCH] gawk: Update to version 5.3.2
Date: Sun, 4 May 2025 15:17:05 +0200 [thread overview]
Message-ID: <20250504131711.3311134-2-adolf.belka@ipfire.org> (raw)
In-Reply-To: <20250504131711.3311134-1-adolf.belka@ipfire.org>
- Update from version 5.3.1 to 5.3.2
- Update of rootfile
- Changelog
5.3.2
1. The pretty printer now produces fewer spurious newlines; at the
outermost level it now adds newlines between block comments and
the block or function that follows them. The extra final newline
is no longer produced.
2. OpenVMS 9.2-2 x86_64 is now supported.
3. On Linux and macos systems, the -no-pie linker flag is no longer required.
PMA now works on macos systems with Apple silicon, and not just
Intel systems.
4. Still more subtle issues related to uninitialized array elements have
been fixed.
5. Associative arrays should now not grow quite as fast as they used to.
6. The code and documentation are now consistent with each other with
respect to path searching and adding .awk to the filename. Both
are always done, even with --posix and --traditional.
7. As usual, there have been several minor code cleanups and bug fixes.
See the ChangeLog for details.
Signed-off-by: Adolf Belka <adolf.belka@ipfire.org>
---
config/rootfiles/common/gawk | 2 +-
lfs/gawk | 6 +++---
2 files changed, 4 insertions(+), 4 deletions(-)
diff --git a/config/rootfiles/common/gawk b/config/rootfiles/common/gawk
index 5cb380ec8..2d4b162e7 100644
--- a/config/rootfiles/common/gawk
+++ b/config/rootfiles/common/gawk
@@ -1,6 +1,6 @@
usr/bin/awk
usr/bin/gawk
-usr/bin/gawk-5.3.1
+usr/bin/gawk-5.3.2
usr/bin/gawkbug
usr/etc/profile.d
usr/etc/profile.d/gawk.csh
diff --git a/lfs/gawk b/lfs/gawk
index a3671882f..bd61298bb 100644
--- a/lfs/gawk
+++ b/lfs/gawk
@@ -1,7 +1,7 @@
###############################################################################
# #
# IPFire.org - A linux based firewall #
-# Copyright (C) 2007-2024 IPFire Team <info@ipfire.org> #
+# Copyright (C) 2007-2025 IPFire Team <info@ipfire.org> #
# #
# This program is free software: you can redistribute it and/or modify #
# it under the terms of the GNU General Public License as published by #
@@ -25,7 +25,7 @@
include Config
-VER = 5.3.1
+VER = 5.3.2
THISAPP = gawk-$(VER)
DL_FILE = $(THISAPP).tar.xz
@@ -49,7 +49,7 @@ objects = $(DL_FILE)
$(DL_FILE) = $(DL_FROM)/$(DL_FILE)
-$(DL_FILE)_BLAKE2 = be9132324344c0b052e954e004a942ff7c6b14b86b73cda491d7a33485f60341be4d8da1a06d1d7a27445b9b39a528bcce3eee9c2a3f8756de21bdc57a33f54d
+$(DL_FILE)_BLAKE2 = 8536777bb45c63d737ef08b3f1b98285cb29ec54400e35b2139c2bc66b464e3ec4950274614d95d94dc7eae18c57333b7c30a44d993855258155fc82b749042a
install : $(TARGET)
--
2.49.0
next prev parent reply other threads:[~2025-05-04 13:17 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-05-04 13:17 [PATCH] diffutils: Update to version 3.12 Adolf Belka
2025-05-04 13:17 ` Adolf Belka [this message]
2025-05-04 13:17 ` [PATCH] grep: " Adolf Belka
2025-05-04 13:17 ` [PATCH] harfbuzz: Update to version 11.2.0 Adolf Belka
2025-05-04 13:17 ` [PATCH] hwdata: Update to version 0.394 Adolf Belka
2025-05-04 13:17 ` [PATCH] patch: Update to version 2.8 Adolf Belka
2025-05-04 13:17 ` [PATCH] tshark: Update to version 4.4.6 Adolf Belka
2025-05-04 13:17 ` [PATCH] xfsprogs: Update to version 6.14.0 Adolf Belka
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20250504131711.3311134-2-adolf.belka@ipfire.org \
--to=adolf.belka@ipfire.org \
--cc=development@lists.ipfire.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox