From: Adolf Belka <adolf.belka@ipfire.org>
To: development@lists.ipfire.org
Cc: Adolf Belka <adolf.belka@ipfire.org>
Subject: [PATCH] patch: Update to version 2.8
Date: Sun, 4 May 2025 15:17:09 +0200 [thread overview]
Message-ID: <20250504131711.3311134-6-adolf.belka@ipfire.org> (raw)
In-Reply-To: <20250504131711.3311134-1-adolf.belka@ipfire.org>
- Update from version 2.7.6 to 2.8
- Update of rootfile not required
- Changelog
2.8
* The --follow-symlinks option now applies to output files as well as input.
* 'patch' now supports file timestamps after 2038 even on traditional
GNU/Linux platforms where time_t defaults to 32 bits.
* 'patch' no longer creates files with names containing newlines,
as encouraged by POSIX.1-2024.
* Patches can no longer contain NUL ('\0') bytes in diff directive lines.
These bytes would otherwise cause unpredictable behavior.
* Patches can now contain sequences of spaces and tabs around line numbers
and in other places where POSIX requires support for these sequences.
* --enable-gcc-warnings no longer uses expensive static checking.
Use --enable-gcc-warnings=expensive if you still want it.
* Fix undefined or ill-defined behavior in unusual cases, such as very
large sizes, possible stack overflow, I/O errors, memory exhaustion,
races with other processes, and signals arriving at inopportune moments.
* Remove old "Plan B" code, designed for machines with 16-bit pointers.
* Assume C99 or later; previously it assumed C89 or later.
* Port to current GCC, Autoconf, Gnulib, etc.
Signed-off-by: Adolf Belka <adolf.belka@ipfire.org>
---
lfs/patch | 6 +++---
1 file changed, 3 insertions(+), 3 deletions(-)
diff --git a/lfs/patch b/lfs/patch
index 039fc2376..2569222de 100644
--- a/lfs/patch
+++ b/lfs/patch
@@ -1,7 +1,7 @@
###############################################################################
# #
# IPFire.org - A linux based firewall #
-# Copyright (C) 2007-2019 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 #
@@ -24,7 +24,7 @@
include Config
-VER = 2.7.6
+VER = 2.8
THISAPP = patch-$(VER)
DL_FILE = $(THISAPP).tar.xz
@@ -47,7 +47,7 @@ objects = $(DL_FILE)
$(DL_FILE) = $(DL_FROM)/$(DL_FILE)
-$(DL_FILE)_BLAKE2 = e3dd2d155a94c39cb60eafc26677e84de14c3a6d5814dff69de091ded52f21862490970254297795f2c42a0c3203f7e88a8f65bb66968f8dfd6e066bf53f2dfb
+$(DL_FILE)_BLAKE2 = 687f566201adb2e32c3832b911adaddd9994aacb25b66886d6315bfe2752e09fd551b3856a39024b8472b2d95efebf412d4a7c085812a13620de811073a397ad
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 ` [PATCH] gawk: Update to version 5.3.2 Adolf Belka
2025-05-04 13:17 ` [PATCH] grep: Update to version 3.12 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 ` Adolf Belka [this message]
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-6-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