findutils-4.5.5 is released

[James Youngman-5]

I am pleased to announce the release of version 4.5.5 of GNU
findutils.

GNU findutils is a set of software tools for finding files that match
certain criteria and for performing various operations on them.
Findutils includes the programs "find", "xargs" and "locate".  More
information about findutils is available at
http://www.gnu.org/software/findutils/.

This is a "development" release of findutils.  It can be downloaded from
ftp://alpha.gnu.org/gnu/findutils.  The 4.5.x release series is
intended to allow people to try out, comment on or contribute to new
features of findutils.  During the 4.5.x release series some features
may be introduced and then changed or removed as a result of feedback
or experience.  In short, please don't rely on backward compatibility
later in the release series.

While this is a development release, it is tested before being
released, principally with the regression test suite (run "make check"
to use it).  The Savannah website
(http://savannah.gnu.org/bugs/?group=findutils) contains a current
list of known bugs in findutils (for both the stable and development
branches).

Bugs in GNU findutils should be reported to the findutils bug tracker
at http://savannah.gnu.org/bugs/?group=findutils.  Reporting bugs via
the web interface will ensure that you are automatically informed when
the bug has been fixed.  General discussion of findutils takes place
on the bug-findutils mailing list.  To join the 'bug-findutils'
mailing list, send email to <bug-findutils-request@...>.

To verify the GPG signature of the release, you will need the public
key of the findutils maintainer, James Youngman.  You can download
this from http://savannah.gnu.org/users/jay.  Please note that the key
being used is not the same as the key that was used to sign previous
releases.


* Major changes in release 4.5.5, 2009-07-06

xargs now handles the case where the system's actual exec limits are
smaller than the value of ARG_MAX at compile time.  Very few platforms
normally have this property, but it is possible to configure some Unix
systems this way.

** Bug Fixes

#26587: Fix a typo in -execdir documentation (it says -exec by mistake
in the text).

#26537: find -prune now makes sure it has valid stat() information.

#22708: Exit status 126 and 127 from the utility invoked from xargs
now makes xargs return 123, meaning that exit status values 126 and
127 now unambigously mean that the utility could not be run or could
not be found, respectively.


--
James Youngman <jay@...>
GNU findutils maintainer

[Eric Blake]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

According to James Youngman on 7/6/2009 4:43 PM:
> I am pleased to announce the release of version 4.5.5 of GNU
> findutils.

In findutils.git, you pushed a lightweight instead of a signed tag for
FINDUTILS_4_5_5-1.  As a result, 'git describe' claims that the master
branch is still based on 4.5.4 rather than 4.5.5.

Also, many GNU projects are starting to use simpler signed tags (v4.5.5)
rather than lengthy ones (FINDUTILS_4_5_5-1), as it a) works better with
the git-version-gen script (although you aren't using that yet), and b) is
easier to type (mixing underscores, dashes, and numbers is particularly
prone to mistyping).  Would you mind doing the following:

$ git tag -s -m 'Findutils release 4.5.5' v4.5.5
$ git push tag v4.5.5

- --
Don't work too hard, make some time for fun as well!

Eric Blake             ebb9@...
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.9 (Cygwin)
Comment: Public key at home.comcast.net/~ericblake/eblake.gpg
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org

iEYEARECAAYFAkpfG+UACgkQ84KuGfSFAYDqYQCfdrA2B+81PaXPq3buTQHIMJw0
YP0AoNgWiVa09QUkEsquyQNac06J1YrG
=Q/Qt
-----END PGP SIGNATURE-----

[James Youngman-5]

On Thu, Jul 16, 2009 at 1:24 PM, Eric Blake<ebb9@...> wrote:

> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: SHA1
>
> According to James Youngman on 7/6/2009 4:43 PM:
>> I am pleased to announce the release of version 4.5.5 of GNU
>> findutils.
>
> In findutils.git, you pushed a lightweight instead of a signed tag for
> FINDUTILS_4_5_5-1.  As a result, 'git describe' claims that the master
> branch is still based on 4.5.4 rather than 4.5.5.
>
> Also, many GNU projects are starting to use simpler signed tags (v4.5.5)
> rather than lengthy ones (FINDUTILS_4_5_5-1), as it a) works better with
> the git-version-gen script (although you aren't using that yet), and b) is
> easier to type (mixing underscores, dashes, and numbers is particularly
> prone to mistyping).  Would you mind doing the following:
>
> $ git tag -s -m 'Findutils release 4.5.5' v4.5.5
> $ git push tag v4.5.5

$ git checkout FINDUTILS_4_5_5-1 && git tag -s -m "Findutils release
4.5.5" v4.5.5 FINDUTILS_4_5_5-1

$ git push --tags
Counting objects: 1, done.
Writing objects: 100% (1/1), 411 bytes, done.
Total 1 (delta 0), reused 0 (delta 0)
To ssh://jay@.../srv/git/findutils.git
 * [new tag]         v4.5.5 -> v4.5.5

I'm not convinced though that there is much justification for changing
the tag naming scheme.

James.