Historically, the MD5 checksums in our LFS files serve as a protection
against broken downloads, or accidentally corrupted source files.
While the sources are nowadays downloaded via HTTPS, it make sense to
beef up integrity protection for them, since transparently intercepting
TLS is believed to be feasible for more powerful actors, and the state
of the public PKI ecosystem is clearly not helping.
Therefore, this patch switches from MD5 to BLAKE2, updating all LFS
files as well as make.sh to deal with this checksum algorithm. BLAKE2 is
notably faster (and more secure) than SHA2, so the performance penalty
introduced by this patch is negligible, if noticeable at all.
In preparation of this patch, the toolchain files currently used have
been supplied with BLAKE2 checksums as well on
https://source.ipfire.org/.
Cc: Michael Tremer <michael.tremer@ipfire.org>
Signed-off-by: Peter Müller <peter.mueller@ipfire.org>
Acked-by: Michael Tremer <michael.tremeripfire.org>
- 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@ipfire.org>
Reviewed-by: Peter Müller <peter.mueller@ipfire.org>
- Update findutils from 4.6.0 to 4.8.0
- Remove findutils-4.6.0-glibc2.28.patch from lfs as all patch items are now
in the new tarball files.
- Remove sed command on gl/lib/mountlist.c from lfs as all fixes are in the
mountlist.c file in the new tarball.
- Update rootfiles
- Changelog
Following are major changes. Further detailed info available in
changelog file in tarball.
* Noteworthy changes in release 4.8.0 (2021-01-09) [stable]
** Changes in xargs
'xargs -t' no longer outputs a trailing blank to stderr after the last argument
of each constructed command line to be executed. [#57291]
xargs now warns when more than one of the conflicting options --max-lines (-L,
-l), --replace (-i/-I) and --max-args (-n) are specified on the command line.
[#52137]
** Bug Fixes
find no longer crashes when an XFS filesystem is heavily changed during the run.
Discussed at: <https://lists.gnu.org/r/bug-gnulib/2020-04/msg00068.html>
find -used works again. This predicate was not working properly since adding
the support for sub-second timestamp resolution for various predicates in
FINDUTILS_4_3_3-1 back in 2007.
Discussed at: <https://lists.gnu.org/r/bug-findutils/2019-11/msg00010.html>
** Improvements
'find -D exec' now diagnoses all -exec, -execdir, -ok and -okdir runs including
the call arguments and the exit code of the launched process. [#59083]
** Documentation Changes
The documentation of 'find -printf %Ak' has been improved: it now refers to the
strftime(3) documentation for a complete list of supported conversion
specifiers, and documents the 'F' conversion specifier ('yyyy-mm-dd').
The man pages (find.1, locate.1, locatedb.5, updatedb.1, and xargs.1) now
consistently end with the sections "REPORTING BUGS", "COPYRIGHT" and "SEE ALSO",
with the latter referring to the online page on the GNU web server.
The "EXAMPLES" section in the find.1 man page now shows the examples in a better
structure and uses consistent formatting.
Various man page fixes - syntax issues and typos.
[#59745, #59330, #59012, #58193, #57807, #57775]
Other documentation changes:
#58654: doc: clarify that 'find -perm +MODE' is unrelated to umask
#58458: doc: improve section 'Hard links', especially fix the description
regarding 'find -L -samefile FILE'.
#58205: find.1: clarify double dash '--' option
#58149: 'xargs --help' now mentions that --replace (-I, -i) splits the input
at newline characters.
#57025: doc: enhance description of tests accepting numeric arguments in find.1
[see also #49640].
#54730: Add additional valuable example of find -quit
#48135: Fix testsuite error on Hurd and BSD related to ln
#35253: Clarify descriptions of -printf %f, %h.
** Changes to the build process
The configure option --without-fts has been removed. The attempt to use
it stopped configure with an error message since 4.5.18 (2015) anyway.
* Major changes in release 4.7.0, 2019-08-29
** Changes to locate / updatedb
Support for generating old-format databases (with updatedb
--old-format or updatedb --dbformat=old) has been removed. The old
database format was deprecated in 2007 (and updatedb has warned about
this since that time). The locate program will will read old-format
databases, though this support also will be removed.
The updatedb script now operates in the C locale only. This means
that character encoding issues are now not likely to cause sort to
fail. It also honours the TMPDIR environment variable if that was
set, and no longer sorts file names case-insensitively.
The (unspecified) order in which filenames are stored in the locate
database is now different to previous versions. However, you should
not rely on locate's output appearing in any particular order in any
case.
** Improvements
All utilities now only show the full usage text when requested via
the --help option. Previously, when the user passed invalid options
or arguments, the user's attention to the corresponding error
diagnostic was distracted by that lengthy text.
find now accepts multiple file type arguments to the -type and -xtype
options separated by comma ','. For example, to search for symbolic
links and directories simply provide the shorter '-type l,d' instead
of the - yet more portable - '( -type l -o -type d )'.
find now diagnoses failures returned by readdir(). This bug was inherent
in the use of FTS.
find now exits in more cases immediately after the error diagnostic, i.e.,
without the following usage text, to make the former more eye-catching.
find now outputs a better hint in case the user passed an unquoted shell-
glob pattern to options like -name, i.e., when the offending argument is
an existing file.
find now supports the debug option '-D all' to include all of the other
debug options at once.
xargs now supports the -o, --open-tty option to reopen stdin as /dev/tty
in the child process before executing the command; useful to run an
interactive application. Added for compatibility with BSD.
xargs now supports the GNU_FINDUTILS_FD_LEAK_CHECK environment
variable to enable/disable fd leak check.
'xargs -t' (--verbose) now properly quotes each part of the command to the
executed if needed when printing it to stderr; likewise -p (--interactive).
** Documentation Changes
Prefer https:// over http:// links where possible, e.g. for '*.gnu.org' servers.
Both find.1 and the find texinfo manual now consistently document all of the
'N', 'L' and '?' possibilities in '-printf %Y' output when the determination of
the type of a symlink target fails.
find.1 now correctly states the -prune has no effect when the -depth option is
given. Before, it wrongly stated that -prune would return false in that case.
Some minor documentation improvements are listed in "Bug Fixes" below.
** Bug Fixes
#56820: find: improve diagnostic when a global option like -maxdepth is
specified after another argument like a test, thus hopefully avoiding
translation issues (at least French, German).
#56142: doc: fix bug #56142 by specifying which actions inhibit the
default -print.
#55272: find: improve diagnostic when -name or -iname is used with a pattern
containing a directory separator ('/'), suggesting to use -wholename
or -iwholename respectively.
#54859: doc: fix typo in 'xargs -l' examples in texinfo manual.
Change from 'xargs -1' (minus one) to 'xargs -l' (minus El) in 3 places.
#54838: doc: fix the examples of the -perm option in the texinfo documentation.
The example '-perm -g+w,o+w' was misplaced.
Bug present since FINDUTILS_4_2_27-1.
#54262: 'find -printf "%Y"' now correctly outputs 'N' for broken symlinks
(ENOENT or ENOTDIR). Previously, it output 'l' in such a case.
Bug introduced while attempting to fix#29460 in version v4.5.8.
#54171: 'find -depth' now outputs the name of unreadable directories.
Previously, FTS-based find missed to output those entries.
Bug present since the FTS implementation in FINDUTILS_4_3_0-1.
#52981: find: the '-delete' action no longer complains about disappeared files
when the '-ignore_readdir_race' option is given, too. That action will
also returns true in such a case now.
#52220: 'find -D' without any further argument no longer crashes.
Bug present since the implementation of -D in FINDUTILS_4_3_1-1.
#51304: doc: use correct IEC unit prefixes in the documentation of 'find -size'.
find(1) uses binary-based units for the suffixes 'k', 'M', and 'G' of
the argument of the '-size' option: 1024, 1024*1024 and 1024^3.
Therefore, the documentation should use the correct IEC prefixes
kibibyte, mebibyte and gibibyte respectively (or their abbreviations
'KiB', 'MiB' and 'GiB').
#50758: doc: fix the description of the -perm examples matching the permission
mode "022" in find's texinfo manual: the match is for the file's group
and 'other' mode bits instead of for user and group.
Bug introduced when adding the -perm examples in FINDUTILS-4.2.11.
#50326: find no longer leaks memory for a recently added member in gnulib's
mount list structure.
#50259: find -printf '%h' now outputs the correct path for arguments with one or
more trailing slashes. Previously, it would e.g. output "foo" instead
of "." when "foo/" was passed; likewise, it would output "/user/xxx/"
instead of "/user" when "/user/xxx//" was passed.
Bug introduced in FINDUTILS-4.2.19.
#48180: find -noop (an internal option not intended to be exposed to the user)
no longer crashes. Bug introduced in FINDUTILS-4.3.1.
#48030: find -exec + does not pass all arguments for certain specific filename
lengths. After the internal (usually 128k) buffer is full and find(1)
executed the given command with these arguments, it would miss to run
the command yet another time if only one other file argument has to be
processed. Bug introduced in FINDUTILS-4.2.12.
#46784: frcode drops last char if no final newline
** Changes to the build process
The configure option --enable-id-cache has been removed. It has been
a no-op since findnutils-4.5.15.
The configure option --enable-debug has been removed. Debugging in
find is now controlled by its -D option only.
The configure option --enable-silent-rules is the default now.
Use --disable-silent-rules or "make V=1" to get verbose build output.
"make dist" no longer builds .tar.gz files.
xz is portable enough and in wide-enough use that distributing
only .tar.xz files is enough.
Maintainer builds from the Git repository now derive the version string from
the version control system instead of using a fixed string (changed after each
release manually). As a result, the inter-release builds can now be
distinguished: e.g. "4.6.0.152-fe9c" is the 152th commit after the tag "v4.6.0"
and has the Git short hash "fe9c". Builds from an unclean tree are marked with
the suffix "-dirty".
The translation files in the PO directory are no longer version controlled;
instead bootstrap auto-updates them from "translationproject.org" during a
maintainer build.
A shell-style test framework borrowed from GNU coreutils has been added.
This allows better tests with more control over stdin, stdout, stderr,
signals, preparatory steps, cleanup, return code verification, root-only
tests, etc.
Signed-off-by: Adolf Belka <adolf.belka@ipfire.org>
Signed-off-by: Michael Tremer <michael.tremer@ipfire.org>
Most of these files still used old dates and/or domain names for contact
mail addresses. This is now replaced by an up-to-date copyright line.
Just some housekeeping... :-)
Signed-off-by: Peter Müller <peter.mueller@link38.eu>
Signed-off-by: Michael Tremer <michael.tremer@ipfire.org>
This will allow us to run multiple builds on the same
system at the same time (or at least have them on disk).
Signed-off-by: Michael Tremer <michael.tremer@ipfire.org>
