public inbox for development@lists.ipfire.org
 help / color / mirror / Atom feed
From: Adolf Belka <adolf.belka@ipfire.org>
To: development@lists.ipfire.org
Subject: [PATCH] findutils: Update to version 4.9.0
Date: Wed, 09 Feb 2022 22:27:50 +0100	[thread overview]
Message-ID: <20220209212750.2754039-1-adolf.belka@ipfire.org> (raw)

[-- Attachment #1: Type: text/plain, Size: 2792 bytes --]

- Update from 4.8.0 to 4.9.0
- Update of rootfile not required
- Changelog
   GNU findutils NEWS - User visible changes.
   * Noteworthy changes in release 4.9.0 (2022-02-22) [stable]
   ** New features in find
      find now supports the -files0-from option to be able to safely pass an
        arbitrary number of starting points to the tool.  The option requires a file
        name as argument, or "-" to read from standard input.  The entries in that
        file have to be separated by NUL characters. [#60383]
   ** Changes in locate / updatedb
      updatedb now skips (fuse-mounted) s3fs filesystems by default,
        i.e., unless PRUNEFS is set.
   ** Bug Fixes
      'find -D stat -L ...' no longer determines SELinux security information as
        if the -L option was not given.
        [Bug present since the SELinux implementation in 4.5.6]
      'find -inum' and 'find -printf %i' now also work on platforms which allow
        the inode number Zero; e.g. the GNU/Hurd uses inode number 0 for /dev/console.
        Previously, find(1) would abort when visiting such a file.
        [Bug present since FINDUTILS_4_5_4-1.]
      findutils-4.8.0 failed to build on some MacOS versions.
        Fixed by a gnulib update. [#59972, #59991]
   ** Documentation Changes
      The find.1 man page and the Texinfo manual now show environment variables
        in a consistent style. [#59963]
      Furthermore, both add the description of the -printf format directive '%B',
        for a file's birth time, and its limitations. [#61327]
      The description of the -delete action has been improved and aligned among
        the manual page and the Texinfo documentation. [#61774]
      Various other documentation fixes - syntax issues and typos.
        [#61303, #60823, #61341]
      The output of 'find --help' now reads better.
      The HTML online manual is using the official GNU stylesheet again.
   ** Changes to the build process
      The find version without FTS, oldfind, has been completely removed.  It has
      not been installed since 4.5.18 (2015), and was only still used in tests.

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

diff --git a/lfs/findutils b/lfs/findutils
index 0b2753dc1..6c754f8d6 100644
--- a/lfs/findutils
+++ b/lfs/findutils
@@ -24,7 +24,7 @@
 
 include Config
 
-VER        = 4.8.0
+VER        = 4.9.0
 
 THISAPP    = findutils-$(VER)
 DL_FILE    = $(THISAPP).tar.xz
@@ -50,7 +50,7 @@ objects = $(DL_FILE)
 
 $(DL_FILE) = $(DL_FROM)/$(DL_FILE)
 
-$(DL_FILE)_MD5 = eeefe2e6380931a77dfa6d9350b43186
+$(DL_FILE)_MD5 = 4a4a547e888a944b2f3af31d789a1137
 
 install : $(TARGET)
 
-- 
2.35.1


             reply	other threads:[~2022-02-09 21:27 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-02-09 21:27 Adolf Belka [this message]
2022-02-11  8:49 ` Peter Müller

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=20220209212750.2754039-1-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