On Fri, Apr 11, 2025 at 7:09 PM Karl Berry <k...@freefriends.org> wrote:

> This is to announce automake-1.17.92, a alpha release.
> See the NEWS below for a brief summary of changes.
>
> Download here:
>   https://alpha.gnu.org/gnu/automake/automake-1.17.92.tar.gz
>   https://alpha.gnu.org/gnu/automake/automake-1.17.92.tar.xz
>
> Hello,

I've massively rebuilt Fedora packages that depend on automake with this
new release, and didn't notice any problem so far.

LGTM.

Fred


> Please report bugs and problems to <bug-autom...@gnu.org>
> (instead of replying to this mail),
> and send general comments and feedback to <automake@gnu.org>,
> and patches to <automake-patc...@gnu.org>.
>
> If you install this test release in its own prefix (recommended)
> and you use libtool, you'll need to arrange for the libtool m4 files
> to be found by aclocal. For info on this, see:
>
> https://gnu.org/s/automake/manual/automake.html#Libtool-library-used-but-LIBTOOL-is-undefined
>
> The main change since the previous pretest (1.17.90) is that the
> environment variable CONFIG_SITE is now set to /dev/null for running the
> Automake tests, for the sake of a consistent environment.  Other changes
> are mostly in the documentation.
>
> There have been 54 commits by 11 people in the 39 weeks since 1.17.
>
>   Bogdan (1)
>   Bruno Haible (3)
>   Collin Funk (2)
>   Eric Gallager (1)
>   Gavin Smith (1)
>   Jim Meyering (1)
>   Jose Marchesi (2)
>   Kamila Szewczyk (1)
>   Karl Berry (24)
>   Paul Eggert (3)
>   Richard Hansen (15)
>
> Thanks to everyone who has contributed.
>
> Karl
>  [on behalf of the automake maintainers]
> ==================================================================
> Detailed download/signature information follows.
>
> Here is the GNU automake home page:
>     https://gnu.org/s/automake/
>
> Here are the compressed sources:
>   https://alpha.gnu.org/gnu/automake/automake-1.17.92.tar.gz   (2.3MB)
>   https://alpha.gnu.org/gnu/automake/automake-1.17.92.tar.xz   (1.6MB)
>
> Here are the GPG detached signatures:
>   https://alpha.gnu.org/gnu/automake/automake-1.17.92.tar.gz.sig
>   https://alpha.gnu.org/gnu/automake/automake-1.17.92.tar.xz.sig
>
> Use a mirror for higher download bandwidth:
>   https://www.gnu.org/order/ftp.html
>
> Here are the SHA1 and SHA256 checksums:
>
>   File: automake-1.17.92.tar.gz
>   SHA1 sum:   7608f8f29f56d41d332f28ab291ea02a2ae9a05a
>   SHA256 sum:
> d2d35c249555505be4f9dd6fad3cab187c0c39b92da974961b58085acdf2e69e
>
>   File: automake-1.17.92.tar.xz
>   SHA1 sum:   96878a83f303c4880d8d93af87293057ee8d09d2
>   SHA256 sum:
> d5c1cf38d63ef626bbe7e3ce7ccdd2663e4022da1551cf73f3d120b98027e9c3
>
> Use a .sig file to verify that the corresponding file (without the
> .sig suffix) is intact.  First, be sure to download both the .sig file
> and the corresponding tarball.  Then, run a command like this:
>   gpg --verify automake-1.17.92.tar.gz.sig
>
> announce-gen: NEWS: no matching lines for '1.17.92'
> The signature should match the fingerprint of the following key:
>   pub   rsa2048 2012-06-12 [SC]
>         17D3 311B 14BC 0F24 8267  BF02 0716 748A 30D1 55AD
>   uid   Karl Berry <k...@freefriends.org>
>
> If that command fails because you don't have the required public key,
> or that public key has expired, try the following commands to retrieve
> or refresh it, and then rerun the 'gpg --verify' command.
>   gpg --recv-keys 0x17D3311B14BC0F248267BF020716748A30D155AD
>
> As a last resort to find the key, you can try the official GNU
> keyring:
>   wget -q https://ftp.gnu.org/gnu/gnu-keyring.gpg
>   gpg --keyring gnu-keyring.gpg --verify automake-1.17.92.tar.gz.sig
>
> This release is based on the automake git repository, available as
>   git clone https://git.savannah.gnu.org/git/automake.git
> with commit c0ec787ba9c52dae9a38c6ba4c02026feca88547 tagged as v1.17.92.
>
> For a summary of changes and contributors, see:
>   https://git.sv.gnu.org/gitweb/?p=automake.git;a=shortlog;h=v1.17.92
>
> or run this command from a git-cloned automake directory:
>   git shortlog v1.17..v1.17.92
>
>
> =============================================================================
> New in 1.17.92:
>
> * New features added
>
>   - Default tar format is now ustar, mainly to support longer filenames;
>     the tar-v7 and other explicit options to force a particular tar
>     format are unchanged and still override the default. (bug#74847)
>
>   - New option dist-bzip3 for bzip3 compression of distributions.
> (bug#73795)
>
>   - New option --stderr-prefix for tap-driver.sh, to prefix each line of
>     stderr from a test script with a given string. (bug#72536)
>
>   - Support for Algol 68 added, based on the GNU Algol 68 compiler.
> (bug#75807)
>
> * Bugs fixed
>
>   - Do not make Perl warnings fatal, per Perl's recommendation.
>     (https://lists.gnu.org/archive/html/automake/2025-01/msg00003.html)
>
>   - Avoid Perl 5.41.8+ precedence warning for use of !!.
>     (https://lists.gnu.org/archive/html/automake/2025-01/msg00000.html)
>
>   - a Perl path containing whitespace now emits a warning instead of
>     an error, so ./configure PERL='/usr/bin/env perl' can work. (bug#74453)
>
>   - The py-compile script once again does nothing (successfully) if the
>     PYTHON environment variable is set to ":", or anything that isn't a
>     Python interpreter (according to $PYTHON -V). Exception: if PYTHON
>     is set to "false", do nothing but exit unsuccessfully, also to match
>     previous behavior. (bug#74434)
>
>   - The no-dist-built-sources Automake option hopefully now operates as
>     intended, i.e., omits the dependency on $(BUILT_SOURCES) for the
>     distdir target. (bug#69908)
>
>   - Only warn about install.sh being found, instead of it being a fatal
>     error. (bug#19964)
>
>   - The compile script is more robust to Windows configurations;
>     specifically, avoiding double-path translation on MSYS. (bug#75939)
>
>   - The test infrastructure sets the CONFIG_SITE environment variable to
>     /dev/null, to avoid the local system's Autoconf site defaults from
>     breaking the test environment. (bug#76622)
>
>   - AM_SILENT_RULES once again always ends with a newline. (bug#72267)
>
>   - AM_SANITY_CHECK now outputs "no" on failure, so that a complete line
>     is written to stdout before the error message is written to stderr.
>     (bug#76448)
>
> * Miscellaneous changes
>
>   - Only require the presence of an ABOUT-NLS file at the 'gnits'
>     strictness level.
>
>

Reply via email to