This is to announce automake-1.16.5, a stable release.
Thanks to Karl for doing all the real work.
See the NEWS below for a brief summary.
There have been 18 commits by 6 people in the 10 weeks since 1.16.4.
See the NEWS below for a brief summary.
Thanks to everyone who has contributed!
The following people contributed changes to this release:
Akim Demaille (1)
Dimitri Papadopoulos (1)
Jan Engelhardt (1)
Jim Meyering (6)
Karl Berry (8)
Nick Bowler (1)
Jim [on behalf of the automake maintainers]
==================================================================
Here is the GNU automake home page:
http://gnu.org/s/automake/
Here are the compressed sources:
https://ftp.gnu.org/gnu/automake/automake-1.16.5.tar.xz (1.6MB)
https://ftp.gnu.org/gnu/automake/automake-1.16.5.tar.gz (2.3MB)
Here are the GPG detached signatures[*]:
https://ftp.gnu.org/gnu/automake/automake-1.16.5.tar.xz.sig
https://ftp.gnu.org/gnu/automake/automake-1.16.5.tar.gz.sig
Use a mirror for higher download bandwidth:
https://ftpmirror.gnu.org/automake/automake-1.16.5.tar.xz
https://ftpmirror.gnu.org/automake/automake-1.16.5.tar.gz
Here are the SHA1 and SHA256 checksums:
8B1YzW2dd/vcqetLvV6tGYgij9tz1veiAfX41rEYtGk automake-1.16.5.tar.xz
B70krQimS8FyUM4J7FbpIdY0OQOUPpnM9ju/BwXjRgU automake-1.16.5.tar.gz
Each SHA256 checksum is base64 encoded, instead of the
hexadecimal encoding that most checksum tools default to.
[*] 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.5.tar.xz.sig
If that command fails because you don't have the required public key,
then run this command to import it:
gpg --keyserver keys.gnupg.net --recv-keys 7FD9FCCB000BEEEE
and rerun the 'gpg --verify' command.
Please report bugs and problems to <bug-automake@gnu.org>,
and send general comments and feedback to <automake@gnu.org>.
==================================================================
NEWS
* Bugs fixed
- PYTHON_PREFIX and PYTHON_EXEC_PREFIX are now set according to
Python's sys.* values only if the new configure option
--with-python-sys-prefix is specified. Otherwise, GNU default values
are used, as in the past. (The change in 1.16.3 was too incompatible.)
- consistently depend on install-libLTLIBRARIES.
* Distribution
- use const for yyerror declaration in bison/yacc tests.
This is to announce automake-1.16.3, a stable release.
There have been 62 commits by 15 people in the 35 weeks since 1.16.2.
Special thanks to Karl Berry and Zack Weinberg for doing so much of the work.
See the NEWS below for a brief summary.
Thanks to everyone who has contributed!
The following people contributed changes to this release:
Akim Demaille (1)
Colomban Wendling (1)
Felix Yan (1)
Issam E. Maghni (1)
Jim Meyering (12)
Karl Berry (23)
Miro Hron\v{c}ok (1)
Paul Eggert (4)
Reuben Thomas (3)
Robert Menteer (1)
Robert Wanamaker (1)
Samuel Tardieu (1)
Samy Mahmoudi (1)
Vincent Lefevre (1)
Zack Weinberg (10)
Jim [on behalf of the automake maintainers]
==================================================================
Here is the GNU automake home page:
http://gnu.org/s/automake/
For a summary of changes and contributors, see:
http://git.sv.gnu.org/gitweb/?p=automake.git;a=shortlog;h=v1.16.3
or run this command from a git-cloned automake directory:
git shortlog v1.16.2..v1.16.3
Here are the compressed sources:
https://ftp.gnu.org/gnu/automake/automake-1.16.3.tar.xz (1.6MB)
https://ftp.gnu.org/gnu/automake/automake-1.16.3.tar.gz (2.3MB)
Here are the GPG detached signatures[*]:
https://ftp.gnu.org/gnu/automake/automake-1.16.3.tar.xz.sig
https://ftp.gnu.org/gnu/automake/automake-1.16.3.tar.gz.sig
Use a mirror for higher download bandwidth:
https://www.gnu.org/order/ftp.html
[*] 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.3.tar.xz.sig
If that command fails because you don't have the required public key,
then run this command to import it:
gpg --keyserver keys.gnupg.net --recv-keys 7FD9FCCB000BEEEE
and rerun the 'gpg --verify' command.
Please report bugs and problems to <bug-automake@gnu.org>,
and send general comments and feedback to <automake@gnu.org>.
==================================================================
NEWS
* New features added
- In the testsuite summary, the "for $(PACKAGE_STRING)" suffix
can be overridden with the AM_TESTSUITE_SUMMARY_HEADER variable.
* Bugs fixed
- Python 3.10 version number no longer considered to be 3.1.
- Broken links in manual fixed or removed, and new script
contrib/checklinkx (a small modification of W3C checklink) added,
with accompany target checklinkx to recheck urls.
- install-exec target depends on $(BUILT_SOURCES).
- valac argument matching more precise, to avoid garbage in DIST_COMMON.
- Support for Vala in VPATH builds fixed so that both freshly-generated and
distributed C files work, and operation is more reliable with or without
an installed valac.
- Dejagnu doesn't break on directories containing spaces.
* Distribution
- new variable AM_DISTCHECK_DVI_TARGET, to allow overriding the
"make dvi" that is done as part of distcheck.
* Miscellaneous changes
- install-sh tweaks:
. new option -p to preserve mtime, i.e., invoke cp -p.
. new option -S SUFFIX to attempt backup files using SUFFIX.
. no longer unconditionally uses -f when rm is overridden by RMPROG.
. does not chown existing directories.
- Removed function up_to_date_p in lib/Automake/FileUtils.pm.
We believe this function is completely unused.
- Support for in-tree Vala libraries improved.
This is to announce automake-1.16.2, a stable release.
There have been 38 commits by 12 people in the two years
(almost to the day) since 1.16.1. Special thanks to Karl Berry
for doing a lot of the recent work preparing for this release.
See the NEWS below for a brief summary.
Thanks to everyone who has contributed!
The following people contributed changes to this release:
Bruno Haible (1)
Gavin Smith (1)
Giuseppe Scrivano (1)
Jim Meyering (5)
Karl Berry (12)
Libor Bukata (1)
Lukas Fleischer (2)
Mathieu Lirzin (8)
Paul Eggert (4)
Paul Hardy (1)
Paul Osmialowski (1)
Vincent Lefevre (1)
Jim [on behalf of the automake maintainers]
==================================================================
Here is the GNU automake home page:
http://gnu.org/s/automake/
For a summary of changes and contributors, see:
http://git.sv.gnu.org/gitweb/?p=automake.git;a=shortlog;h=v1.16.2
or run this command from a git-cloned automake directory:
git shortlog v1.16.1..v1.16.2
Here are the compressed sources:
https://ftp.gnu.org/gnu/automake/automake-1.16.2.tar.xz (1.5MB)
https://ftp.gnu.org/gnu/automake/automake-1.16.2.tar.gz (2.3MB)
Here are the GPG detached signatures[*]:
https://ftp.gnu.org/gnu/automake/automake-1.16.2.tar.xz.sig
https://ftp.gnu.org/gnu/automake/automake-1.16.2.tar.gz.sig
Use a mirror for higher download bandwidth:
https://www.gnu.org/order/ftp.html
[*] 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.2.tar.xz.sig
If that command fails because you don't have the required public key,
then run this command to import it:
gpg --keyserver keys.gnupg.net --recv-keys 7FD9FCCB000BEEEE
and rerun the 'gpg --verify' command.
==================================================================
NEWS
* New features added
- add zstd support and the automake option, dist-zstd.
* Miscellaneous changes
- automake no longer requires a @setfilename in each .texi file
* Bugs fixed
- When cleaning the compiled python files, '\n' is not used anymore in the
substitution text of 'sed' transformations. This is done to preserve
compatibility with the 'sed' implementation provided by macOS which
considers '\n' as the 'n' character instead of a newline.
(automake bug#31222)
- For make tags, lisp_LISP is followed by the necessary space when
used with CONFIG_HEADERS.
(automake bug#38139)
- The automake test txinfo-vtexi4.sh no longer fails when localtime
and UTC cross a day boundary.
- Emacsen older than version 25, which require use of
byte-compile-dest-file, are supported again.
See full announcement at:
<https://lists.gnu.org/archive/html/info-gnu/2018-03/msg00002.html>
See full announcement at:
<https://lists.gnu.org/archive/html/info-gnu/2018-02/msg00008.html>
See full announcement at:
<https://lists.gnu.org/archive/html/info-gnu/2017-06/msg00007.html>
See full announcement at:
<http://lists.gnu.org/archive/html/automake/2015-01/msg00005.html>
See full announcement at:
<http://lists.gnu.org/archive/html/automake/2013-12/msg00024.html>
See announcement here:
<http://lists.gnu.org/archive/html/automake/2013-06/msg00040.html>
See announcement here:
<http://lists.gnu.org/archive/html/automake/2013-06/msg00039.html>
See the announcement here:
<http://lists.gnu.org/archive/html/automake/2013-06/msg00011.html>
See the announcement here:
<http://lists.gnu.org/archive/html/automake/2013-05/msg00049.html>
This is a bug-fixing release, partly remedying to the too-abrupt removal on our part of some long-obsoleted macros which were however still used "in the wild": AM_CONFIG_HEADER and (to a much lesser degree) AM_PROG_CC_STDC. Now the use of these obsolete macros elicit clear and helpful error messages, rather than obscure failures that give no hint about what the real cause of the failure is.
Mailing-list announcement for Automake 1.13.1:
<http://lists.gnu.org/archive/html/automake/2013-01/msg00000.html>
GNU Automake 1.13 has been released.
This is a major release, bringing several changes, a couple of bug-fixes, and some backward incompatibilities over the 1.12.x series.
Mailing-list announcement for Automake 1.13:
<http://lists.gnu.org/archive/html/automake/2012-12/msg00038.html>
Here is a quick summary of the most important changes:
GNU Automake 1.12.6 has been released.
This is a minor release, fixing a couple of bugs in python support (one of them related to PEP-3147), and some issues with Automake's own testsuite and build system.
Announcement for 1.12.6:
<http://lists.gnu.org/archive/html/automake/2012-12/msg00025.html>
GNU Automake 1.12.5 has been released.
This is a minor release, that fixes a couple of small bugs and enhances support for the Vala programming language.
Announcement for 1.12.5:
<http://lists.gnu.org/archive/html/automake/2012-11/msg00041.html>
GNU Automake 1.12.4 has been released.
Starting with it, the warnings in the 'obsolete' category are enabled by default; this way, it will be harder for projects that don't use the '-Wall' option to be suddenly bitten by backward-incompatible changes, without having been properly warned in advance.
In addition, this release addresses few minor testsuite weaknesses that caused reduced coverage or spurious errors.
Announcement for 1.12.4:
<http://lists.gnu.org/archive/html/automake/2012-09/msg00024.html>
GNU Automake 1.12.3 has been released.
This is mostly a bug-fixing release, addressing few old bugs in Yacc/Lex support, and some weaknesses in Automake's own testsuite.
This release also introduces initial support for automatic dependency tracking with the Portland Group C/C++ compilers.
Announcement for 1.12.3:
<http://lists.gnu.org/archive/html/automake/2012-08/msg00023.html>
GNU Automake 1.12.2 has been released. This is a maintenance
release, which, among the other changes, fixes a security issue relevant for packages using Automake (CVE-2012-3386). See the announcements for details.
Announcement for 1.12.2:
<http://lists.gnu.org/archive/html/automake/2012-07/msg00022.html>
Details on the fixed security issue:
<http://lists.gnu.org/archive/html/automake/2012-07/msg00023.html>
GNU Automake 1.11.6 has been released. This is a bug-fixing
release, fixing a security issue relevant for packages using Automake. See the announcements for details.
Announcement for 1.11.6:
<http://lists.gnu.org/archive/html/automake/2012-07/msg00021.html>
Details on the security issue fixed in above releases:
<http://lists.gnu.org/archive/html/automake/2012-07/msg00023.html>