[Thanks to Karl Berry for doing so much of work, preparing for this release and even writing most of the following. ]
We are pleased to announce the GNU Automake 1.16.90 test release. This is the next pretest for the upcoming automake-1.17. Please test if you can. We're particularly interested in bugs or regressions in the actual Automake functionality. Some tests are already known to fail on some non-GNU/Linux systems with some configurations, and have open bugs. Barring patches, we won't be able to fix all such test failures for this release (or, likely, ever). Nonetheless, we do welcome all bug reports (and patches!), in the test suite or otherwise. For possible convenience, here is the open bug list: https://debbugs.gnu.org/cgi/pkgreport.cgi?package=automake See below for the detailed list of changes since the previous version, as summarized by the NEWS file. Download here: https://alpha.gnu.org/gnu/automake/automake-1.16.90.tar.gz (2.4MB) https://alpha.gnu.org/gnu/automake/automake-1.16.90.tar.xz (1.6MB) 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>. Thanks to everyone who has reported problems, contributed patches, and helped test Automake! -*-*-*- For planned incompatibilities in a possible future Automake 2.0 release, please see NEWS-2.0 and start following the advice there now. =================================================================== There have been 53 commits by 13 people in the 24 weeks since 1.16i. See the NEWS below for a brief summary. The following people contributed changes to this release: Bogdan (3) Bruno Haible (2) Dave Hart (1) Dimitri Papadopoulos (2) Gianfranco Costamagna (1) Hans Ulrich Niedermann (1) Jim Meyering (3) Karl Berry (32) Mark Wooding (1) Mike Frysinger (1) Paul Eggert (2) Reuben Thomas (3) Zack Weinberg (1) ================================================================== Here is the GNU automake home page: https://gnu.org/s/automake/ For a summary of changes and contributors, see: https://git.sv.gnu.org/gitweb/?p=automake.git;a=shortlog;h=v1.16.90 or run this command from a git-cloned automake directory: git shortlog v1.16i..v1.16.90 Here are the GPG detached signatures: https://alpha.gnu.org/gnu/automake/automake-1.16.90.tar.gz.sig https://alpha.gnu.org/gnu/automake/automake-1.16.90.tar.xz.sig Here are the SHA1 and SHA256 checksums: ea1f7a79825326428e9944cac9b0f1dcf49d797e automake-1.16.90.tar.gz DbyQPkXg8K6h2e6RLYf/L407pSnGI4Vn8445byVra04= automake-1.16.90.tar.gz 3a36c2c3d1a33801ebcea4c8a1c2c02c6fc36d06 automake-1.16.90.tar.xz MYkSRnd4m7QXX2jMJr7Rs1++y5lyGLqqTGRqw8fHQsY= automake-1.16.90.tar.xz Verify the base64 SHA256 checksum with cksum -a sha256 --check from coreutils-9.2+ or OpenBSD's cksum since 2007. 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.16.90.tar.gz.sig The signature should match the fingerprint of the following key: pub rsa4096/0x7FD9FCCB000BEEEE 2010-06-14 [SCEA] Key fingerprint = 155D 3FC5 00C8 3448 6D1E EA67 7FD9 FCCB 000B EEEE uid [ unknown] Jim Meyering <j...@meyering.net> uid [ unknown] Jim Meyering <meyer...@fb.com> uid [ unknown] Jim Meyering <meyer...@gnu.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 0x7FD9FCCB000BEEEE 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.16.90.tar.gz.sig ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ New in 1.17: * New features added - AM_PATH_PYTHON will, after checking "python", prefer any Python 3 version (latest versions checked first) over any Python 2 version. If a specific version of Python 2 is still needed, the $PYTHON variable should be set beforehand. - AM_PATH_PYTHON will also search for Python versions 3.20 through 3.10. It previously searched for 3.9 through 3.0. (bug#53530) - RANLIB may be overridden on a per-target basis. - AM_TEXI2FLAGS may be defined to pass extra flags to TEXI2DVI & TEXI2PDF. - New option "posix" to emit the special target .POSIX for make. (bug#55025, bug#67891) - Systems with non-POSIX "rm -f" behavior are now supported, and the prior intent to drop support for them has been reversed. The ACCEPT_INFERIOR_RM_PROGRAM setting no longer exists. (bug#10828) - Variables using escaped \# will trigger portability warnings, but be retained when appended. GNU Make & BSD Makes are known to support it. (bug#7610) - GNU Make's default pattern rules are disabled, for speed and debugging. (.SUFFIXES was already cleared.) (bug#64743) - For Texinfo documents, if a .texi.in file exists, but no .texi, the .texi.in will be read. Texinfo source files need not be present at all, and if present, need not contain @setfilename. Then the file name as given in the Makefile.am will be used. If @setfilename is present, it should be the basename of the Texinfo file, extended with .info. (bug#54063) - The missing script also supports autoreconf, autogen, and perl. (https://lists.gnu.org/archive/html/automake-patches/2015-08/msg00000.html) - test-suite.log now contains basic system information, and the console message about bug reporting on failure has a bit more detail. (bug#68746) * Bugs fixed - Generated file timestamp checks handle filesystems with sub-second timestamp granularity dynamically, greatly speeding up make check, etc. However, this requires an autom4te from Autoconf 2.72 or later (or random test failures and other timing problems may ensue), as well as a Perl, sleep program, make program, and filesystem that all support sub-second resolution; otherwise, we fall back to one-second granularity as before. When everything is supported, a line "Features: subsecond-mtime" is now printed by automake --version and autom4te --version. (bug#64756, bug#67670, bug#68808) - The default value of $ARFLAGS is now "cr" instead of "cru", to better support deterministic builds. (bug#20082) - Automake's make dist now uses -9 instead of --best with gzip, because Alpine gzip does not support --best. Also, GZIP_ENV is used only for compression, not decompression, because of the same system. (bug#68151) - Dependency files are now empty, instead of "# dummy", for speed. (https://lists.gnu.org/archive/html/automake/2022-05/msg00006.html) - Compiling Python modules with Python 3.5+ uses multiple optimization levels. (bug#38043) - If the Python installation "scheme" is set to posix_local (Debian), it is reset to either deb_system (if the prefix = /usr), or posix_prefix (otherwise). (bug#54412, bug#64837) - As a result of the Python scheme change, the installation directory for Python files again defaults to "site-packages" under the usual installation prefix, even on systems (generally Debian-based) that would normally use the "dist-packages" subdirectory under /usr/local. - When compiling Emacs Lisp files, emacs is run with --no-site-file to disable user config files that might hang or access the terminal; and -Q is not used, since its support and behavior varies. (bug#58102) - Emacs Lisp compilations respect silent make output. - Automake no longer incorrectly warns that the POSIX make variables $(*D) and the like are non-POSIX. Unfortunately, the make implementations which do not correctly implement all the POSIX variables are not detected, but this seems to have little impact in practice. (bug#9587) - Pass libtool tags OBJC and OBJCXX for the respective languages. (bug#67539) - distcleancheck ignores "silly rename" files (.nfs* .smb* .__afs*) that can show up on network file systems. (https://lists.gnu.org/archive/html/automake/2022-09/msg00002.html) - tests: avoid some declaration conflicts for lex et al. on SunOS. (bug#34151 and others) - Pass any options given to AM_PROG_LEX on to AC_PROG_LEX. (bug#65600, bug#65730) - Typos in code and other doc fixes. (bug#68003, bug#68004, et al.) * Obsolescence: - py-compile no longer supports Python 0.x or 1.x versions. Python 2.0, released in 2000, is currently the minimum required version. ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
signature.asc
Description: PGP signature
