public inbox for development@lists.ipfire.org
 help / color / mirror / Atom feed
From: Adolf Belka <adolf.belka@ipfire.org>
To: development@lists.ipfire.org
Cc: Adolf Belka <adolf.belka@ipfire.org>
Subject: [PATCH] findutils: Update to version 4.11.0
Date: Fri, 24 Jul 2026 19:44:04 +0200	[thread overview]
Message-ID: <20260724174412.3827472-13-adolf.belka@ipfire.org> (raw)
In-Reply-To: <20260724174412.3827472-1-adolf.belka@ipfire.org>

- Update from version 4.10.0 to 4.11.0
- No change to the rootfile
- Changlog
4.11.0
Bug Fixes
  find no longer crashes when diagnosing a directory cycle (without a symlink
   being involved pointing to a parent directory).
   [Bug present since the FTS implementation.]
  'find -used' now behaves correctly on OpenBSD 7.8 with difftime(3) underflow
   bug in the C library (already fixed there) when the access time of a file is
   identical to its change time. [#68264]
  'find -ignore_readdir_race' now better handles races between FTS reading a
   directory and visiting its entries when the file or directory was meanwhile
   removed. [#45930]
  To fix a POSIX compatibility bug, -exec foo Z{} + is no longer a
   complete predicate, because '+' is only a terminator when it follows
   an argument which is exactly '{}'.  The findutils documentation
   already states this, and now find's behaviour matches the
   documentation. [#66365]
  'updatedb.sh' now properly handles the variables for the 'find' and 'frcode'
   utilities, and hence avoids command injection.
Changes in find
  As announced since the release of 4.7.0 (2019) and mandated by POSIX 2024,
   the behaviour of the -mount option changed: while it was a mere alias for
   the -xdev option to prevent descending into directories of another device,
   the -mount option now makes find(1) ignore files on another device, i.e.,
   'find -mount' will skip the entry of active mount points already.
   Example, assuming the PROC filesystem is mounted on '/proc':
     $ find / -mount -path /proc -print
     $ find / -xdev -path /proc -print
     /proc
   [#54745]
  The actions -execdir and -okdir now refuse the '{}' replacement in the zeroth
   argument of the command to be run.  While POSIX allows this for -exec, this is
   deemed insecure as an attacker could influence which files could be found.
  'find -regex' with the default or the 'emacs' regextype now aligns better with
   Emacs behaviour, and therefore e.g. supports character classes:
     $ touch 123 && find -regex './12[[:digit:]]'
     ./123
  find now issues a warning when the punctuation operators '(', ')', '!' and ','
   are passed with a leading dash, e.g. '-!'.  Future releases will not accept
   that any more.  Accepting that was rather a bug "since the beginning".
Improvements
  xargs now gives a better error diagnostic when executing the given command
   failed.
Documentation Changes
  The most recent version of the POSIX standard (IEEE Std 1003.1-2024,
   also known as The Open Group Base Specifications, Issue 8) has
   standardised "find -print0" and "xargs -0".  Our documentation now
   points this out.  Similarly for 'find -iname'.
  The code example for "Finding the Shallowest Instance" in the Texinfo manual
   and the corresponding one in the EXAMPLES section in the find.1 man page have
   been fixed.  [#62259]
  Translators contributed numerous fixes for issues in the find.1 man page.
  The list of actions that suppress the default -print action has been
   supplemented with the missing '-print0' and '-fprint0' actions.
  The manual pages have been updated to give better and/or more
   consistent output with manpage formatters other than GNU roff.
Translations
  Updated the following translations:
   Arabic, Brazilian Portuguese, Bulgarian, Chinese (simplified), Croatian,
   Czech, Dutch, Estonian, French, German, Indonesian, Korean, Polish,
   Portuguese, Romanian, Spanish, Swedish, Ukrainian.
Future Changes
  A future release will remove the warning message find prints about
   the 2007 change in the meaning of "-perm /000".  Everybody who is
   likely to care probably knows about this change by now.

Signed-off-by: Adolf Belka <adolf.belka@ipfire.org>
---
 lfs/findutils | 6 +++---
 1 file changed, 3 insertions(+), 3 deletions(-)

diff --git a/lfs/findutils b/lfs/findutils
index 7fb2383cc..0be449f85 100644
--- a/lfs/findutils
+++ b/lfs/findutils
@@ -1,7 +1,7 @@
 ###############################################################################
 #                                                                             #
 # IPFire.org - A linux based firewall                                         #
-# Copyright (C) 2007-2024  IPFire Team  <info@ipfire.org>                     #
+# Copyright (C) 2007-2026  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        = 4.10.0
+VER        = 4.11.0
 
 THISAPP    = findutils-$(VER)
 DL_FILE    = $(THISAPP).tar.xz
@@ -50,7 +50,7 @@ objects = $(DL_FILE)
 
 $(DL_FILE) = $(DL_FROM)/$(DL_FILE)
 
-$(DL_FILE)_BLAKE2 = 2eebdcb425c04170d17afb80e7270ba095bd691660d961dcfa731141633d3bb597d0b47d69ed17e891ef884a36d4c232885097e45b41d3d3ac79dbeae6ee2282
+$(DL_FILE)_BLAKE2 = d3d881c60efb01eacf14a6bad95513b0186b694d0857a708bb28864fdf949fa99cbb80d2c8bf70e4bac65ebfba852bfa8435bf637fa7716e80e55a8b06ea1313
 
 install : $(TARGET)
 
-- 
2.55.0



  parent reply	other threads:[~2026-07-24 17:44 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-07-24 17:43 [PATCH] btrfs-progs: Update to version 7.1 Adolf Belka
2026-07-24 17:43 ` [PATCH] core205: Ship btrfs-progs Adolf Belka
2026-07-24 17:43 ` [PATCH] core205: Ship cmake Adolf Belka
2026-07-24 17:43 ` [PATCH] core205: Ship findutils Adolf Belka
2026-07-24 17:43 ` [PATCH] core205: Ship fontconfig Adolf Belka
2026-07-24 17:43 ` [PATCH] core205: Ship gawk Adolf Belka
2026-07-24 17:43 ` [PATCH] core205: Ship libffi Adolf Belka
2026-07-24 17:44 ` [PATCH] core205: Ship libtool Adolf Belka
2026-07-24 17:44 ` [PATCH] core205: Ship meson Adolf Belka
2026-07-24 17:44 ` [PATCH] core205: Ship p11-kit Adolf Belka
2026-07-24 17:44 ` [PATCH] core205: Ship xorriso Adolf Belka
2026-07-24 17:44 ` Adolf Belka [this message]
2026-07-24 17:44 ` [PATCH] fontconfig: Update to version 2.18.2 Adolf Belka
2026-07-24 17:44 ` [PATCH] gawk: Update to ver5sion 5.4.1 Adolf Belka
2026-07-24 17:44 ` [PATCH] libffi: Update to version 3.7.1 Adolf Belka
2026-07-24 17:44 ` [PATCH] libtool: Update to version 2.6.2 Adolf Belka
2026-07-24 17:44 ` [PATCH] meson: Update to version 1.11.2 Adolf Belka
2026-07-24 17:44 ` [PATCH] p11-kit: Update to version 0.26.4 Adolf Belka
2026-07-24 17:44 ` [PATCH] taglib: Update to version 2.3.1 Adolf Belka
2026-07-24 17:44 ` [PATCH] xorriso: Update to version 1.5.8.pl02 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=20260724174412.3827472-13-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