Dear all, There was an an issue reported by Thomas Klausner:
> The installed files are still called automake-1.19 etc. > Perhaps because of > APIVERSION=1.19 > in configure.ac?Since the problem has been caught so early, I have re-tagged the release and uploaded new tarballs with the following checksums:
File: automake-1.20.tar.gzSHA256 sum: 00c0e397a3c0096b1b9167eb4a5ecb87a66fe50888d939c4e02111e603936570 SHA3-256 sum: 9144e4677e65c09ecc5de762e7b97982cfe683a4e45b153a199172b11593a03e
File: automake-1.20.tar.xzSHA256 sum: f6f34dad4cbe395715762b0710f7c511e39bd5cf777e6b95818ccbecf7714248 SHA3-256 sum: d5910039d860e26824074f654b1aea70d123932696d8fd0bcda531fc78652edf
Sorry about that! -- With Valediction, Kamila Szewczyk (https://iczelia.net) On 11/7/26 3:18 PM, Kamila Szewczyk wrote:
We are pleased to announce GNU Automake 1.20, a stable minor release.Among new features is `--enable-jobserver' for compiler and linker access to GNU make's jobserver, the delete-on-error option, and a print- distfiles target. distcheck no longer requires TeX by default. This release also fixes some long-standing bugs and limitations concerning dependency tracking, lex/yacc output in VPATH builds, Vala builds, distribution compression, and uninstall checks. Furthermore, GNU automake has upgraded from the GNU GPLv2 (or later) license to the GNU GPL v3 (or later) license.I have substantial plans for the GNU Build System (`autotools') as a whole. I intend to continue resolving old issues and limitations, and adding new features in GNU Automake, slowly dragging it into the future. My ultimate goal is to establish it, once again, as the build system of choice for new software projects while continuing to simplify maintenance and portability for existing users. Hopefully, upcoming releases will get us closer and closer to this goal.-*-*-*- There have been 104 commits by 3 contributors in the 58 days since 1.19. Thanks to everyone who contributed to this release! Kamila Szewczyk (99) Karl Berry (4) Paul Eggert (1) Kamila Szewczyk ([email protected]) ================================================================== See below for the detailed list of changes since the previous version, as summarized by the NEWS file. Here is the GNU Automake home page: https://www.gnu.org/software/automake/ Here are the compressed sources: https://ftp.gnu.org/gnu/automake/automake-1.20.tar.gz (2549281 bytes) https://ftp.gnu.org/gnu/automake/automake-1.20.tar.xz (1694140 bytes) Here are the GPG detached signatures: https://ftp.gnu.org/gnu/automake/automake-1.20.tar.gz.sig https://ftp.gnu.org/gnu/automake/automake-1.20.tar.xz.sig Use a mirror for higher download bandwidth: https://www.gnu.org/order/ftp.html Here are the SHA256 and SHA3-256 checksums: File: automake-1.20.tar.gzSHA256 sum: df7696d9f7cc7e98b9ff46bbbf5fa72c0bbdf629b4ca05ecdc9150ee4561c072 SHA3-256 sum: 7dc50edcb7eb4f11478fc3de8214a19cfe2d7b27929e8be1e26524a47204ece5File: automake-1.20.tar.xzSHA256 sum: 6f7ae4c90b4e89b5f7f50a9c3bf205a10f18b60c2659d3d6f044351bd8a28d5d SHA3-256 sum: 6175fa7daf497eb3206655f27b51e0d5523b45bc268ce27fcaf81628337c0d76Verify SHA256 with sha256sum or 'shasum -a 256'. Verify SHA3-256 with 'openssl dgst -sha3-256 FILE'. 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.20.tar.gz.sig automake-1.20.tar.gz The signature should match the fingerprint of the following key: pub rsa4096 2022-07-31 [C] [expires: 2036-05-11] 6C22 2EA6 B2BD 216A A406 516A C868 F0B6 DE38 409D uid [ultimate] Kamila Szewczyk <[email protected]> uid [ultimate] Kamila Szewczyk <[email protected]> uid [ultimate] Kamila Szewczyk <[email protected]> uid [ultimate] Kamila Szewczyk <[email protected]> sub rsa4096 2022-07-31 [E] sub ed25519 2026-06-29 [S] If that command fails because you don't have the required public key, or that public key has expired, try the following command to retrieve or refresh it, and then rerun the 'gpg --verify' command. gpg --recv-keys 6C222EA6B2BD216AA406516AC868F0B6DE38409D As a last resort to find the key, you can try the official GNU keyring: wget -q https://ftp.gnu.org/gnu/gnu-keyring.gpggpg --keyring ./gnu-keyring.gpg --verify automake-1.20.tar.gz.sig automake-1.20.tar.gzPlease report bugs and problems to <[email protected]> (instead of replying to this mail), and send general comments and feedback to <[email protected]>, and patches to <[email protected]>.Thanks to everyone who has reported problems, contributed patches, and helped test Automake! Changes from NEWS: ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ New in 1.20 (2026-11-07): * Licensing- Automake is now licensed under the GNU General Public License version 3or later (GPLv3+), matching Autoconf and following the Free Software Foundation's recommendation to use GPLv3 or later: https://www.gnu.org/software/autoconf/ https://www.gnu.org/licenses/license-recommendations.html https://www.gnu.org/licenses/rms-why-gplv3.html Existing exceptions for distributed support files remain in place. This does not change the licensing of generated Makefile.in files or require packages using Automake to adopt the GPL. * New features added - New configure option --enable-jobserver lets compilers and linkers inherit GNU make's pipe jobserver, for example for GCC's -flto=jobserver. Dry-run, question, and touch modes still do not run these commands. (bug#45756) - New option delete-on-error. It emits the .DELETE_ON_ERROR special target in the generated Makefile.in, instructing GNU make to delete the target when its recipe fails after having modified it. A failed rule like `foo.h: gen.sh; ./gen.sh > $@' then no longer leaves a truncated result that later runs of make treat as up to date. Other make programs do not support this, so the option will have no effect. - New target print-distfiles lists the files that "make dist" would distribute. * Source tree organization - Historical ChangeLogs, development plans, and NEWS-future are now under attic/. The experimental contrib/tap-driver.pl is retained in attic/testing/; the maintained TAP driver is lib/tap-driver.sh. The manual's link checker moved from contrib/ to maintainer/. * Changes to Automake-generated Makefiles - distcheck no longer runs "make dvi" by default, so TeX is not needed to check a distribution containing Texinfo manuals. Set AM_DISTCHECK_DVI_TARGET in Makefile.am to, e.g., dvi, pdf or html, to check that the documentation can be built. (bug#79053) * Bugs fixed - Repeated target declarations in overlapping Automake conditionals nolonger produce spurious redefinition warnings when adding prerequisites.(bug#13940) - Dependencies on another target's objects in LIBADD or LDADD are now tracked regardless of the order in which targets are processed. (bug#60508) - distcheck now detects symbolic links left in the installation tree after uninstall, including dangling links.- lex and yacc output files distributed from a VPATH build no longer carry"#line" directives pointing to their sources through the build-time srcdir, e.g. "../src/parse.y"; the distributed copies now refer to the sources next to them. (bug#39666) - dist-zstd now honors numeric ZSTD_CLEVEL values, such as 3, instead of treating them as input filenames. This fixes failed or incorrect distribution archives when ZSTD_CLEVEL is set. - lex and yacc rules now create output directories before generating sources, fixing out-of-tree builds with subdir-objects and --disable-dependency-tracking. (bug#27188, Debian bug#807050) - configure now refuses a source directory path containing '<', '>', '(' or ')'. These could be interpreted as shell redirections or syntax in compiler commands, potentially overwriting files in the build directory. - configure now refuses a source directory path ($srcdir) containing ';' or '|', reporting "unsafe srcdir value", as it already did for characters such as '$' and '&'. Such a path used to fail later with misleading errors, from config.status's dependency-tracking setup or from make ("No rule to make target"). These characters remain accepted when $srcdir is '.'. - Non-recursive Vala builds now pass distcheck when generated Vala sources trigger recompilation in the build directory. Generated C files are moved into their subdirectories together, and build-tree stamp files are removed by distclean. (bug#76527) ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ This release is based on the Automake Git repository, available as: git clone https://https.git.savannah.gnu.org/git/automake.git Commit 5613ae2dbb151f73070bb576f21136e5ef5c75c1 is tagged as v1.20. For a summary of changes and contributors, see:https://gitweb.git.savannah.gnu.org/gitweb/? p=automake.git;a=shortlog;h=v1.20Or run this command from a Git checkout of Automake: git shortlog v1.19..v1.20 -- With Valediction, Kamila Szewczyk (https://iczelia.net)
OpenPGP_0xC868F0B6DE38409D.asc
Description: OpenPGP public key
OpenPGP_signature.asc
Description: OpenPGP digital signature
